Disaster Recovery Strategy: RTO and RPO Analysis on On-Premises and Cloud Infrastructure

App availability is critical today. Losing access to an app for even a minute can be a big problem for a company, especially for apps that require 24-hour availability, and can damage a company's reputation. Companies with local environments often need to replicate their infrastructure to ensure backup capacity in the event of a disaster. Causing suitable local infrastructure as a backup is not cost-effective. Utilizing data backup in the cloud is now a cheaper and more efficient cost option. Data backup in the cloud will be enabled when a disaster occurs in the main data center and will be restored after the disaster ends. This is done because of sensitive data, some countries stipulate that sensitive data is not recommended to run in the cloud permanently or the consideration of users who are mostly on-premises. The process from on-premises to cloud and back from cloud to on-premises needs to be measured based on time and data consistency. Many cloud providers now offer services such as DRaaS (Disaster Recovery as a Service) to help businesses recover from disasters, maintain business continuity temporarily, and return to onpremises operations after disasters. Many companies or agencies still don't know how much value in terms of RTO and RPO is needed from on-premises to the cloud and back from the cloud to on-premise. This article presents the implementation design and analysis methods for both metrics.