Database Backup (DBS) provides a complete sandbox solution for MySQL and Oracle databases based on copy data management (CDM). You can use the DBS sandbox feature to create a sandbox instance (ApsaraDB RDS emergency instance) to restore data in a backup set within seconds. Read and write operations performed within sandbox instances do not affect source databases. You can perform a variety of operations within sandbox instances, such as data restoration within seconds, recovery drill, test, analysis, and emergency disaster recovery. This topic describes the architecture, benefits, scenarios, billing, and limits of the DBS sandbox feature.
- Increasing storage costs: Full and incremental backups are performed on a regular basis to ensure recovery point objectives (RPOs). However, this generates large amounts of duplicate data and leads to high storage costs.
- Increasing use costs: You must restore data before it can be used. Restoring large amounts of data can consume large amounts of bandwidth and disk I/O resources and lead to high CPU utilization. Restoration is costly and extends the data recovery time objective (RTO) to hours.
DBS provides a complete sandbox solution for MySQL and Oracle databases based on CDM. Solutions for other database types are to be released soon.
- MySQL sandbox instance: DBS provides storage and computing resources for MySQL sandbox instances and hosts the service process of instances. You can remotely access your database instances.
- Oracle sandbox instance: DBS provides storage resources for Oracle sandbox instances based on a remote file system and hosts the service process of instances. The computing resources of MySQL sandbox instances are provided by your ECS instances.
- Database physical backup: accelerates data backup and recovery for database files.
- Data deduplication: significantly reduces the storage costs of backup data.
- Storage snapshot and clone: allows backup data to be available within seconds. The RTO is within several seconds. No data is copied.
- Storage virtualization: This feature uses sandbox instances of cloud resources without dependencies on your production instances. Read and write operations performed within sandbox instances do not affect source databases.
- Development and testing based on online data (Dev or Ops):
Testing and prerelease are verified based on existing online data. However, online data must be protected from being corrupted. The DBS sandbox feature can provide replicas of full historical data and meet the requirements of rapid test iterations and data reliability.Note The DBS sandbox feature plans to support fast data masking to shield sensitive fields in databases for common developers and testing personnel. This can meet the core requirements of financial and cloud computing industries for data privacy.
- Online emergency disaster recovery:
The DBS sandbox feature allows the backup system to deliver an RPO or RTO within seconds and immediately restore online data. Compared with multi-active and hot backup, the DBS sandbox feature also provides data rollback capabilities, which allows you to quickly roll back dirty data.Note DBS plans to provide the disaster recovery drill feature. You can use the recovery capabilities of the sandbox feature and the pay-as-you-go billing method to initiate disaster recovery drills on a regular basis. This can meet the requirements of high data reliability.
- Ad hoc analysis of historical data:
In data analysis scenarios, you must perform ad hoc queries on historical data based on your current requirements. The DBS sandbox feature can provide replicas of full historical data for queries. Unlike solutions for offline historical data analysis based on big data platforms, the DBS sandbox feature can provide SQL interfaces of original databases. This eliminates the need for developers to write offline analysis scripts and reduces storage costs by using snapshot storage.