After you create an anti-ransomware policy for a database, run a precheck to verify that the database can connect to Object Storage Service (OSS) and the control network. The precheck takes about 1 minute. If it passes, Security Center can back up the database.
Anti-ransomware for databases supports MySQL, Oracle, and SQL Server databases deployed on Elastic Compute Service (ECS) instances.
Prerequisites
Before you begin, ensure that you have:
Created an anti-ransomware policy for the database. For supported database versions and backup types, see Overview (ECS-hosted databases)
Run the precheck
Log on to the Security Center console. In the top navigation bar, select the region of the asset. You can select China or Outside China.
In the left-side navigation pane, choose Protection Configuration > Host Protection > Anti-ransomware.
On the Database extortion virus protection tab, find the anti-ransomware policy and click Pre-check in the Actions column.
In the Pre-check dialog box, click Starting.
The precheck runs and displays results for each check item. If an item fails, follow the on-screen instructions to check whether the failure affects the backup and restoration operations in the database. If the failure affects the backup and restoration operations, we recommend that you handle the issue at the earliest opportunity.
Check items
The precheck validates different items depending on your database type.
MySQL
| Check item | What it verifies | Impact if it fails |
|---|---|---|
| OSS connectivity | Whether the MySQL database is connected to the VPC Access from ECS (Internal Network) endpoint of an OSS bucket. The instance and the bucket must be in the same region. | Backup and restore are unavailable. |
| Control network connectivity | Whether the MySQL database is connected to the control network. | Backup and restore are unavailable. |
| Versions of databases that support full backup | Whether the MySQL version supports full backup. | — |
| Binary log check | Whether the binary log configuration is valid. | Backup and restore are unavailable. |
MySQL 8.0 does not support incremental backup.
Oracle
| Check item | What it verifies | Impact if it fails |
|---|---|---|
| OSS connectivity | Whether the Oracle database instance is connected to the VPC Access from ECS (Internal Network) endpoint of an OSS bucket. The instance and the bucket must be in the same region. | Backup and restore are unavailable. |
| Control network connectivity | Whether the Oracle database instance is connected to the control network. | Backup and restore are unavailable. |
| Status of the Oracle database instance | Whether the Oracle database instance is running as expected. | Backup and restore are unavailable. |
| Oracle database status | Whether all Oracle databases in the instance are running as expected. | Backup and restore are unavailable. |
| Archive mode | Whether archive mode can be enabled for the Oracle database instance. To enable archive mode, see Enable archive mode for an Oracle database. | Backup and restore are unavailable. |
SQL Server
| Check item | What it verifies | Impact if it fails |
|---|---|---|
| OSS connectivity | Whether the SQL Server database is connected to the VPC Access from ECS (Internal Network) endpoint of an OSS bucket. The database and the bucket must be in the same region. | Backup and restore are unavailable. |
| Control network connectivity | Whether the SQL Server database is connected to the control network. | Backup and restore are unavailable. |
| Recovery model | The recovery model of the SQL database. | Incremental backup and log backup are unavailable. |
| SQL Server database status | Whether the SQL Server database is running as expected. | Backup and restore are unavailable. |
For the recovery model check:
Databases that fail this check support only the SIMPLE recovery model and cannot perform log backups.
Master databases support only full backups. If you run an incremental or log backup on a master database, the system automatically runs a full backup instead.
To change the recovery model, see the SQL Server documentation.