After you create a protection policy for a database, you must precheck the connectivity between not only the database and Object Storage Service (OSS) but also the database and the control network. If the precheck succeeds, you can back up the data in the database. Anti-ransomware for databases is available only for MySQL databases, Oracle databases, and SQL Server databases that are deployed on Elastic Compute Service (ECS) instances. This topic describes how to precheck database instances.

Background information

If you want to back up data in MySQL databases, Oracle databases, or SQL Server databases that are deployed on ECS instances, you need to pay attention to the database versions and backup features that are supported by each version. For more information, see Overview.

Procedure

  1. Log on to the Security Center console.
  2. In the left-side navigation pane, choose Defense > Anti-ransomware.
  3. On the General Anti-ransomware Solutions page, click the Database extortion virus protection tab.
  4. In the protection policy list, find the newly created policy and click Pre-check in the Actions column.
  5. In the Pre-check dialog box, click Starting.
    • Check items for a MySQL database
      Check item Description
      OSS connectivity Checks 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 reside in the same region. If the connectivity check fails, you cannot back up or restore data in the database.
      Control network connectivity Checks whether the MySQL database is connected to the control network. If the connectivity check fails, you cannot back up or restore data in the database.
      Versions of databases that support full backup Checks whether the version of the MySQL database supports full backup.
      Note MySQL 8.0 does not support incremental backup.
      Binary log check Checks whether the binary log configuration of the MySQL database is valid. If the check fails, you cannot back up or restore data in the database.
    • Check items for an Oracle database
      Check item Description
      OSS connectivity Checks 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 reside in the same region. If the connectivity check fails, you cannot back up or restore data in the database.
      Control network connectivity Checks whether the Oracle database instance is connected to the control network. If the connectivity check fails, you cannot back up or restore data in the database.
      Status of the Oracle database instance Checks whether the Oracle database instance runs as expected. If the instance does not run as expected, you cannot back up or restore data in the database.
      Oracle database status Checks whether all Oracle databases in the Oracle database instance run as expected. If a database in the instance does not run as expected, you cannot back up or restore data in the database.
      Archive mode Checks whether the archive mode can be enabled for the Oracle database instance. If the check fails, you cannot back up or restore data in the database. For more information about how to enable the archive mode, see Enable archive mode for an Oracle database.
    • Check items for a SQL Server database
      Check item Description
      OSS connectivity Checks 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 reside in the same region. If the connectivity check fails, you cannot back up or restore data in the database.
      Control network connectivity Checks whether the SQL Server database is connected to the control network. If the connectivity check fails, you cannot back up or restore data in the database.
      Recovery model Checks the recovery model of the SQL database. If the check fails, you cannot perform incremental backups or log backups in the database.
      Notice
      • Due to the limits of SQL Server, databases that fail the check support only the SIMPLE recovery model. You cannot perform log backups on these databases.
      • You can perform only full backups on master databases. If you perform an incremental backup or log backup for a master database, HBR automatically changes the backup to full backup.
      • For more information about how to change the recovery model, see SQL Server documentation.
      SQL Server database status Checks whether the SQL Server database runs as expected. If the database does not run as expected, you cannot back up or restore data in the database.

    The precheck takes about 1 minute.

    If an item fails the precheck, 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 based on this topic.