This topic describes the on-premises database backup feature of Cloud Backup. It covers the benefits, how it works, procedures, billing, and supported database versions.
Introduction
On-premises database backup is a data protection solution from Cloud Backup for self-managed databases in on-premises data centers. Cloud Backup (HBR) provides a simple, secure, and reliable way to back up database data to the cloud. If your database system or its server fails, production data is accidentally deleted, or a ransomware attack occurs, you can recover the data from a Cloud Backup vault.
The on-premises database server must be connected to an Alibaba Cloud virtual private cloud (VPC) through a leased line or VPN. The network routing must allow traffic from the on-premises server to the following Alibaba Cloud CIDR blocks: 100.64.0.0/10, 100.64.0.0/11, or 100.96.0.0/11. For more information, see Connect a VPC to a data center in single-tunnel mode.
Cloud Backup does not support backing up databases that are deployed in containers. Limits apply to the supported database versions, operating systems, and backup features. For more information, see Compatibility list and limits.
The on-premises database backup feature is available in the following regions: Singapore, China (Shanghai), China (Shenzhen), China (Qingdao), and SAU (Riyadh - Partner Region). For more information, see Features by region.
The MySQL backup feature does not support backing up multiple MySQL instances on a single on-premises server or ECS instance.
Key advantages
Low cost
Cloud Backup does not charge instance configuration fees. You are charged only for the storage space that your deduplicated and compressed backup data occupies.
High performance
Backups consume low resources, typically less than 0.5 CPU cores and 100 MB of memory. Cloud Backup provides real-time backup for MySQL and Oracle with a near-zero recovery point objective (RPO).
Wide compatibility
Major versions of MySQL, Oracle, and SQL Server are supported.
Automated alerting
You can configure alert rules in the Cloud Backup console to monitor backup jobs. If a backup job fails, the system automatically sends alerts by email, text message, and phone call.
Immutable backup
Cloud Backup provides an immutable backup feature for backup vaults. This feature prevents backup data from being deleted by any account or method before the configured retention period expires.
How it works
You obtain the installation script from the Cloud Backup console and run it to install the client on your on-premises server. The client then backs up the specified database based on the configured backup plan.
When a backup job runs, the Cloud Backup client uses the database's native backup component to run a backup command. The client reads the source data, performs deduplication and compression, and then uploads the data to the backup vault to complete the backup.
Procedure
The following procedure shows how to back up an on-premises database in the Cloud Backup console.
The procedures for backing up on-premises MySQL, Oracle, and SQL Server databases are basically the same. In this example, a MySQL database is backed up.
To back up a MySQL, Oracle, or SQL Server database, you must obtain the username and password from the database administrator.
You are not charged for activating Cloud Backup. You are charged for the rental and storage usage of database backup vaults. You are not charged for using a vault in the first 30 days. You are charged after the free-trial period ends. You are charged for the backup storage based on the storage space occupied by the data that is deduplicated and compressed. A free capacity of 100 GB is provided for each backup vault per month. After the free quota is used up, you are charged based on tiered pricing. For more information, see Billing methods and billable items.
When you register an on-premises database in the Cloud Backup console, you must log on to the on-premises server where the database is deployed to install a backup client. Cloud Backup can discover the database that you want to back up only after you register the database. You are not charged for using Cloud Backup if you only register a database in the Cloud Backup console.
To ensure that your database can be backed up as expected, Cloud Backup provides the precheck feature to identify issues that may cause backup failure.
When you create a backup plan, configure the backup vault, data source, backup cycle, retention period, and backup policies (such as full backup and incremental backup). Cloud Backup starts the backup plan and continuously backs up data from the specified database.
You are not charged for restoring a database. If a database exception occurs, you can restore the data of the database to the source database or another registered database within the same account in the same region based on recovery points.
Billing
On-premises database backup with Cloud Backup is subject to the following two fees:
Database backup vault rental fee
You must create backup vaults for your databases. Multiple databases in a region can share a backup vault. Each backup vault includes a certain amount of free capacity. For more information, see Pricing details.
Database backup storage capacity fee
Each database backup vault provides 100 GB of free capacity. You are charged for any excess storage usage. You are charged based on the storage space occupied by the deduplicated and compressed data. For more information, see Pricing details.
What to do next
Learn how to back up on-premises databases. For more information, see Register an on-premises MySQL database, Register an on-premises Oracle database, and Register an on-premises SQL Server database.
View answers to frequently asked questions (FAQ). For more information, see FAQ.
Learn about best practices for Cloud Backup. For more information, see Best practices.