All Products
Search

This Product

    Cloud Backup:FAQ about database backup

    Document Center

    Cloud Backup:FAQ about database backup

    Last Updated:Apr 17, 2024

    This topic provides answers to some frequently asked questions (FAQ) about the database backup feature of Cloud Backup.

    What do I do if the status of a MySQL database is Inactivated?

    image.png

    • When you register a database, the value that you specify for Database Account or Password is incorrect, or you do not have the required permissions. After you check that the specified username and password are correct, grant the required permissions to the backup account. We recommend that you create a dedicated backup account.

      The minimum permission set of the user is RELOAD, LOCK TABLES, REPLICATION, and PROCESS.

    • You can run the systemctl status dbackup3-agent command to view the process status of the Cloud Backup client. The value active indicates that the client is running properly. 

      ● dbackup3-agent.service - dbackup3 agent daemon
   Loaded: loaded (/usr/lib/systemd/system/dbackup3-agent.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2023-12-11 13:47:34 CST; 1min 13s ago
 Main PID: 22192 (dbackup3-agent)
   CGroup: /system.slice/dbackup3-agent.service
           └─22192 /opt/scutech/dbackup3/bin/dbackup3-agent -f /etc/opt/scutech/dbackup3/agent/svc.conf.d

Dec 11 13:47:34 iZbp1******gktZ systemd[1]: Started dbackup3 agent daemon.

    • The client log path is /var/log/dbackup3/agent.log.

    What do I do if the status of a MySQL database is Database Offline?

    image.png

    Log on to the Elastic Compute Service (ECS) instance and run the systemctl status mysqld command to query the status of the MySQL database. The process status is inactive. The MySQL database service is not started.

    After you run the systemctl start mysqld command to restart the MySQL database service, the database status is Online in the console.

    How do I view the process status and log path of a Cloud Backup client for database backup?

    You can run the systemctl status dbackup3-agent command to view the process status of the Cloud Backup client for database backup. The value active indicates that the client is running properly. 

    ● dbackup3-agent.service - dbackup3 agent daemon
   Loaded: loaded (/usr/lib/systemd/system/dbackup3-agent.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2023-12-11 13:47:34 CST; 1min 13s ago
 Main PID: 22192 (dbackup3-agent)
   CGroup: /system.slice/dbackup3-agent.service
           └─22192 /opt/scutech/dbackup3/bin/dbackup3-agent -f /etc/opt/scutech/dbackup3/agent/svc.conf.d

Dec 11 13:47:34 iZbp1******gktZ systemd[1]: Started dbackup3 agent daemon.

    The client log path is /var/log/dbackup3/agent.log.

    What do I do if the status of a MySQL database is Unknown in the console?

    image.png

    Log on to the server where the Cloud Backup client for database backup is installed, and run the systemctl status dbackup3-agent command to query the client process status. The process status is inactive. The client process is not started.

    After you run the systemctl start dbackup3-agent command to restart the client process, the database status is Online in the console.

    Are limits imposed on the MySQL database versions and operating systems that support backup?

    Cloud Backup supports a limited number of database versions, operating systems, and backup features. For example, Cloud Backup does not support backup of a MySQL database deployed on Windows. For more information, see the "Supported database versions" section in Overview (ECS-hosted databases).

    How does Cloud Backup clear expired database backup files?

    To perform an incremental backup, cumulative incremental backup, and log backup, Cloud Backup obtains the most recent backup files of full backup, incremental backup, cumulative incremental backup, and log backup. All backup files in a backup chain are retained in the backup vault until the last backup file expires. The backup files occupy backup space. We recommend that you configure a reasonable backup cycle and expiration time.

    For example, you perform a full backup on September 1 and an incremental backup every day from September 2 to 7, and retain the backup data for seven days. In this case, the backup data from September 1 to 7 is retained until September 14 when all backup files expire.

    How do I view the amount of database backup data and backup vault usage? Which item is used for billing?

    Backup Data indicates the accumulated data volume of backup jobs. For example, after a 1 TB file is backed up twice, Cloud Backup saves two independent data copies, and the value of this parameter is counted as 2 TB. Cloud Backup deduplicates and compresses backup data to reduce the backup vault usage, saving your costs. The value of Vault Usage is used for billing. You can view the amount of database backup data and the backup vault usage on the Overview page in the Cloud Backup console.image.png

    How do I cancel MySQL database backup?

    After you accurately and completely cancel database backup, no additional costs are incurred and no additional resources are used.

    Important

    After you cancel database backup, your backup data is deleted and cannot be restored. Proceed with caution.

    1. Delete the backup plan.

    2. Unregister the database. When you unregister an ECS-hosted database, Cloud Backup automatically uninstalls the Cloud Backup client.

    3. If the MySQL database is installed on an on-premises server, log on to the server to uninstall the Cloud Backup client.

      CentOS

      sudo rpm --erase "dbackup3-agent-mysql"
sudo rpm --erase "dbackup3-agent"
sudo rpm --erase "dbackup3-common"

      Ubuntu

      sudo dpkg -r "dbackup3-agent-mysql" "dbackup3-agent" "dbackup3-common"

    4. Delete the backup vault.

      In the left-side navigation pane, click Storage Vaults, and find and delete the backup vault.

    How do I back up a new MySQL database?

    Cloud Backup backs up MySQL databases based on database instances. No manual configurations are required for new databases. New databases are automatically backed up in the next backup cycle.

    How do I resolve a MySQL database backup failure?

    On the Job History tab, the status of a MySQL database backup job is Error.image.png

    We recommend that you perform the following steps to resolve the error:

    1. Log on to the ECS instance or on-premises server and check the status of the MySQL database service. For example, you can run the systemctl status mysqld command to check the service status. The value active indicates that the service status is normal. The value inactive indicates that the service status is abnormal. If the service status is inactive, we recommend that you restart the service and check the service status again.

    2. Check that the database username and password and the related user permissions are configured correctly. If the password has expired or the user permissions have been changed and become insufficient, a MySQL database backup failure may occur.

      When you register the database, the value that you specify for Database Account or Password is incorrect, or you do not have the required permissions. After you check that the specified username and password are correct, grant the required permissions to the backup account. We recommend that you create a dedicated backup account.

      The minimum permission set of the user is RELOAD, LOCK TABLES, REPLICATION, and PROCESS.

    What is a database backup vault?

    Before you create a backup plan to back up a database, you must create a backup vault for the database.

    A database backup vault is a storage vault that stores the backup data of your database. When you use the database backup feature, you are charged for the rental of database backup vaults and the storage usage. For more information, see Billable items and billing methods.

    What do I do if the error message The difference between the request time and the current time is too large appears?

    Cause: The difference between the time of the on-premises server on which the Cloud Backup client is installed and the time of the Cloud Backup backend server is greater than 15 minutes.

    Solution: We recommend that you check the on-premises server time (time zone) and the Network Time Protocol (NTP) configuration. If an issue is found, modify the settings and restart the Cloud Backup client.

    What do I do if an error occurs when I back up an SQL Server database?

    When you use Cloud Backup to back up an SQL Server database, the backup fails. Resolve the error based on the corresponding solution.

    • Error message: The account does not have the required permissions.

      Cause: The account does not have the permissions required to back up the SQL Server database.

      Solution: Check the backup account and the permissions of the account. For more information, see Step 2: Create a backup account and configure permissions.

    • Error message: Unable to overwrite files.

      Cause: The recovery path of the SQL Server database is occupied by another database.

      Solution: Cloud Backup does not support the modification of the recovery path.

    • Error message: The SQL Server database does not exist. Enter a valid database name.

      Cause: The SQL Server database does not exist.

      Solution: Check whether the specified database exists.

    • Error message: The database is included in a database mirroring session or an availability group. Some operations are not allowed to be performed on databases that are included in database mirroring sessions or availability groups.

      Cause: SQL Server AlwaysOn is enabled for the SQL Server database.

      Solution: Disable replica synchronization or mirroring.

    • Error message: The database has been configured for database mirroring or has been added to an availability group. If you want to restore the database, execute the ALTER DATABASE statement to delete the image or remove the database from the availability group.

      Cause: SQL Server AlwaysOn is enabled for the SQL Server database.

      Solution: Disable replica synchronization or mirroring.

    What do I do if the status of an Oracle database is Unknown in the console?

    image.png

    1. Check that the ECS instance is in the Running state and the Oracle service is normal.image.png

    2. Log on to the server where the Cloud Backup client for database backup is installed and run the systemctl status dbackup3-agent command to query the client process status. The process status is inactive. The client process is not started.

    3. After you run the systemctl start dbackup3-agent command to restart the client process, the database status is Online in the console.

    How do I cancel Oracle database backup?

    After you accurately and completely cancel database backup, no additional costs are incurred and no additional resources are used.

    Important

    After you cancel database backup, your backup data is deleted and cannot be restored. Proceed with caution.

    1. Delete the backup plan.

    2. Unregister the database. When you unregister an ECS-hosted database, Cloud Backup automatically uninstalls the Cloud Backup client.

    3. If the Oracle database is installed on an on-premises server, log on to the server to uninstall the Cloud Backup client.

      • Windows

        1. Go to the installation directory of the Cloud Backup client by using PowerShell, for example, C:\Program Files\aliyun\unibackup>.

        2. Run the following command: 

           .\uninstall-unibackup.exe /S /NCRC

      • Linux

        • CentOS

          sudo rpm --erase "dbackup3-agent-oracle"
sudo rpm --erase "dbackup3-agent"
sudo rpm --erase "dbackup3-common"

        • Ubuntu

          sudo dpkg -r "dbackup3-agent-oracle" "dbackup3-agent" "dbackup3-common"

    4. Delete the backup vault.

      In the left-side navigation pane, click Storage Vaults, and find and delete the backup vault.

    What do I do if the status of an SQL Server database is Inactivated in the console?

    • When you register the database, the value that you specify for Database Account or Password is incorrect, or you do not have the required permissions. After you check that the specified username and password are correct, grant the required permissions to the backup account. We recommend that you create a dedicated backup account and try again.

      Create an SQL Server backup account and grant the required permissions. For more information, see Step 2: Create a backup account and configure permissions and Step 3: Configure network settings.

    • The client log path is C:\ProgramData\scutech\dbackup3 \agent\log\dbackup3-agent.log.

    How do I cancel SQL Server database backup?

    After you accurately and completely cancel database backup, no additional costs are incurred and no additional resources are used.

    Important

    After you cancel database backup, your backup data is deleted and cannot be restored. Proceed with caution.

    1. Delete the backup plan.

    2. Unregister the database. When you unregister an ECS-hosted database, Cloud Backup automatically uninstalls the Cloud Backup client.

    3. If the SQL Server database is installed on an on-premises server, log on to the server to uninstall the Cloud Backup client.

      1. For Windows, go to the installation directory of the Cloud Backup client by using PowerShell, for example, C:\Program Files\aliyun\unibackup>.

      2. Run the uninstall-unibackup.exe command to uninstall the client as prompted.

    4. Delete the backup vault.

      In the left-side navigation pane, click Storage Vaults, and find and delete the backup vault.

    How do I change my username and password used for database backup?

    To change the username and password that are used for database backup, you can Reactivate your database. For example, you can reactivate your database if the database password expires. Reactivation does not affect the existing backup plan. You do not need to change the backup plan. However, reactivation has an impact on running backup jobs. We recommend that you perform the following steps:

    1. On the Backup Plan tab, pause real-time log backup (if any).

    2. Find the database and choose More > Reactivate in the Actions column.