Sipradi - Genese Software Solution

Sipradi Trading Pvt. Ltd.

Case Study on Business Continuity and Disaster Recovery (BCDR)

About the company

SIPRADI is a major player in AUTOMOTIVE & ALLIED business, one of the largest and most driving brands in Nepal. 37 years down the line, Sipradi has exceeded USD 350 million annual revenue and growing rapidly in the automotive, lubricant, financial service, and equipment business sectors. It has more than 750 employees and over 650 support staff working to accomplish a shared objective –To deliver quality products and services while adding synergy to the growth of overall brand value.

Sipradi Trading Private Ltd (STPL) has been a sole distributor of Tata Motors Ltd. India, for Nepal since 1982 and certified with ISO 9001:2008. The company has been providing Sales, Services and Spare parts, a facility for the full range of Tata Motor’s commercial as well as passenger vehicles. The company has immense networks throughout Nepal having 22 sales network offices and 25 service centers dedicated to Commercial vehicles, 16 showrooms and 25 service centers dedicated to Passenger Vehicles and allocated 300 spare parts outlet across the country.

Sipradi is also an exclusive distributor of Mak Lubricants, Michelin tires, Exide batteries and other various lines of products. Sipradi Earthmovers distributes heavy construction equipment manufactured by Tata-Hitachi. Sipradi Auto parts have a dealership with garage equipment’s and genuine spare parts from Tata Motors, it is the market leader in its segment. Established with a view to revolutionize the pre-owned vehicle industry in Nepal, Sipradi Assured is the latest addition to the Sipradi family.

Sipradi has embraced major CSR initiatives in driver training, traffic management, road building, drinking water supply, education, and tree plantations.

Problem Statement

The challenge in every organization is the overhead of managing on-premise infrastructure. Sipradi maintains its system in the on-premise infrastructure. They are using 1210Gb of storage for the database, 160GB for ERP application and 80GB for Active Directory servers. With the increasing data and workloads, it’s getting complicated in managing both production and DR environment on the on-premise servers.

Proposal

As an advanced consulting partner of AWS, Genese Software Solution proposed a solution to facilitate Disaster Recovery environment on AWS cloud for disaster scenarios with minimal disruption and downtime.

For this, we proposed different options for disaster recovery available in AWS.

Backup and Restore:

  • Cheapest setup with High RTO and RPO.
  • In this approach, we must periodically backup data from the system to AWS.
  • Amazon S3 is an ideal destination for backing up data that might be needed quickly to perform a restore.
  • We can use AWS Snowball to transfer very large data sets by shipping storage devices directly to AWS.
  • For longer term data storage where retrieval times of several hours are adequate, we can leverage Amazon Glacier. Also, Amazon S3 and Amazon Glacier can be used in conjunction to produce a tiered backup solution.

Pilot Light:

  • Slight expensive than Backup and restore approach but RTO and RPO are shorter.
  • A minimal version of an environment is always running in the cloud.
  • In AWS, we maintain a pilot light by configuring and running the most critical core elements of the system and when the time comes for recovery, we can rapidly provision a full-scale production environment around the critical core.
  • Beside critical infrastructures, to provision the remainder infrastructure to restore business critical servers, we can typically have some pre-configured servers bundled as Amazon Machine Images (AMIs).

Warm Standby:

  • Costs more and decreased RTO and RPO than Pilot light approach.
  • A scaled-down version of a fully functional environment is always running in the AWS Cloud.
  • A warm standby solution extends the pilot light elements and preparation.
  • Servers can be running on a minimum sized fleet of Amazon EC2 instances on the smallest possible sizes. The solution is not scaled to take a full production load but it is fully functional
  • The setup can also be used for non-production work such as testing, QA, and internal use.
  • In a disaster, the system is scaled up quickly to handle the production load.

Multisite:

  • This is the active-active setup. The RTO and RPO are nearly zero but it is the most expensive approach to Disaster recovery.
  • Primary as well as secondary environment both run full production setup in an active-active configuration.
  • We can use Route53 to route traffic to both sites either symmetrically or asymmetrically.
  • In an on-site disaster situation, we can adjust the DNS weighting and send all traffic to the secondary AWS environment.
  • We might need additional application logic to detect the failure of primary database services and cut over to the parallel database running in AWS..

Solution

Sipradi thought of implementing the full multi-site disaster recovery option as this has the least RPO and RTO compared to other options. They wanted a full running environment for the DR environment.

Sipradi has used EBS encryption (AES-256) in its EBS volume for data security. Encryption will encrypt all the data moving between volume and instance. All the snapshots created by the volume are self-encrypted.nMultiple EBS volumes have been used in the single instance which will stripe data across the volumes for increased I/O and throughput performance.

Sipradi has got a big boost by using EBS because Elastic Volumes allows to dynamically increase capacity, tune performance, and change the type of any new or existing current-generation volume with no downtime or performance impact. Amazon EBS volumes are designed for an annual failure rate (AFR) of between 0.1% – 0.2%, where failure refers to a complete or partial loss of the volume, depending on the size and performance of the volume. This makes EBS volumes 20 times more reliable than typical commodity disk drives, which fail with an AFR of around 4%.

We have used CloudEndure Disaster Recovery service to replicate the on premises data into AWS cloud. To automatically use AWS environment in case of any disaster scenarios, we have used the Route53 failover policy to switch the traffic to the AWS environment. Also all the AWS resources that has been created, are compliant with all the AWS security best practices for a secure running of the cloud infrastructure. A VPN Connection created for the custom VPC is the way to communicate between the AWS and On-premise environment.

Result

As an advanced consulting partner of AWS, Genese Software Solution proposed a solution to facilitate Disaster Recovery environment on AWS cloud for disaster scenarios with minimal disruption and downtime.

For this, we proposed different options for disaster recovery available in AWS.