The requirement is for our SaaS based intelligent document management system. (www.myofficedocs.com)
SaaS solution providers not only have to maintain reliable storage and backup devices, but also operate a reliable network with redundant networking devices, transit connections, and physical connections between data centers. In addition to backup and reliable networking, SaaS providers must also have a tested, working solution for disaster recovery. This includes deploying data and applications across multiple data centers – either with failure resilient software or in a more traditional hot/cold standby approach. To achieve realistic disaster recovery, all the data centers and servers involved must be constantly utilized; if they sit idle, it’s almost certain they won’t function as desired when activated from a cold start. SaaS providers need to account for both the cost and the complexity of this redundancy when evaluating their deployment.
Backup and Restore
Automatic Snapshots of Amazon EBS volumes, Amazon RDS database are stored in Amazon S3. Alternatively, the files are directly copied into Amazon S3 using a Lambda trigger on a weekly basis.
- Selecting an appropriate tool or method to back up the AWS.
- Ensure to associate an appropriate retention policy for this data.
- Ensure that appropriate security measures are in place for this data, including encryption and access policies.
- Regularly test the recovery of this data and the restoration of the system using test failover strategies.
Production to DR Solution Using Multiple AWS Regions
SaaS applications have an additional business requirement to deploy their components using multiple regions. A multi-region, active-active architecture gets all the services on the client request path deployed across multiple AWS Regions. To do so, below mentioned steps must be performed.
- Fastand Reliable data replication between regions.
- Globalnetwork infrastructure to connect different regions.
- Services must bestateless, and state should be shared between regions.
- Synchronous cross-regional calls are avoided when possible.
- Application uses regional resources.
- DNS routingis used to permit for different scenarios.
Faster turnaround time – When disaster strikes, it would take just minutes to copy or move the backed-up systems, so the application can resume operations right away and meet customers RPO & RTO requirements
Minimal downtime expense- Cost savings to fix the system as well as the financial losses incurred by significant downtime.
Less complexity – With traditional systems, the replacement software and programs have to mesh with the salvaged programs. Alternatively, if no salvage is possible, the new hardware and software need to be tested and reviewed to make sure all the component parts work properly.
AWS EBS, AWS EC2, S3, Route 53, Snapshots