All Products
Search
Document Center

Security Center:Troubleshoot abnormal anti-ransomware policies and backup tasks

Last Updated:Jun 11, 2026

If your Database anti-ransomware policy or a backup task has an abnormal status in the Security Center console, such as Wrong Account Password, Initialization Failed, or Excess Is Automatically Closed, this topic explains how to identify the cause and resolve the issue.

Prerequisites

Your database is protected by an anti-ransomware policy. For more information, see Create a protection policy.

Troubleshoot an abnormal anti-ransomware policy status

Check the cause of an abnormal policy status

  1. Log on to the Security Center console. In the left-side navigation pane, choose Protection Configuration > Host Protection > Anti-ransomware. In the upper-left corner of the console, select the region where your asset is located: Chinese Mainland or Outside Chinese Mainland.

  2. On the Anti-ransomware for Databases tab, view the reason for the abnormal policy status in the protection policy list. Abnormal policy statuses include Wrong Account Password, Deletion Failed, and Initializing. You can view the specific cause directly in the Policy Status column.

  3. Resolve the issue based on the cause of the abnormal status.

    For information about the causes and recommended solutions for abnormal policy statuses, see Policy status descriptions and solutions.

Policy status and solutions

Status

Description

Solution

Wrong Account or Password

The database account or password is incorrect.

Enter the correct database account and password, and then re-enable the policy.

Initializing

The environment is initializing.

Wait for the policy initialization to complete.

Initialization Failed

The policy failed to initialize.

Reinstall the agent and then edit the policy. For more information, see Manually install the agent and Edit a protection policy.

Enabling

The policy is being enabled.

Wait for the policy to be enabled.

Enabled

The policy is enabled.

No action is required.

Disabled

The policy is disabled.

No action is required.

Disabling

The policy is being disabled.

Wait for the policy to be disabled.

Automatically Disabled Due to Excessive Data

The anti-ransomware capacity is full.

Manually delete historical data to free up space or renew and upgrade your plan. For more information, see What do I do if my anti-ransomware data protection capacity is insufficient?.

Deleting

The policy is being deleted.

Wait for the policy to be deleted.

Deletion Failed

Failed to delete the policy.

Retry deleting the policy later. For more information, see Delete a protection policy.

Restoring

Data is being restored.

Wait for the data restoration to complete.

Backing Up

Data is being backed up.

Wait for the backup task to complete.

Troubleshoot an abnormal backup task status

Check the cause of a failed backup task

  1. Log on to the Security Center console.

  2. In the left-side navigation pane, choose Protection Configuration > Host Protection > Anti-ransomware. In the upper-left corner of the console, select the region where your asset is located: Chinese Mainland or Outside Chinese Mainland.

  3. In the upper-right corner of the Anti-ransomware page, click Backup Tasks.

  4. In the Backup Tasks panel, click the Database Backup Task tab, select a region, and then Add a filter condition to set Status to Failed, and click the image icon.

  5. Click the image.png icon in the Status column for the target backup task to view the reason for the failure.

Causes and solutions for backup failures

Agent error code

Error details

Cause

Solution

CLIENT_CONNECTION_ERROR

Backup failed.

The backup failed because the Database anti-ransomware agent is offline.

  • Method 1: Restart the Database anti-ransomware agent.

    Note

    You must disable self-protection before you follow these steps to restart the agent.

    • Linux: Run the systemctl restart dbackup3-agent command.

    • Windows:

      • In the UI: Go to the Services page, right-click Dbackup3 Agent, and click Restart.

      • Command-line method: Run net stop "dbackup3 agent" to stop the service and then run net start "dbackup3 agent" to restart it.

  • Method 2: Reinstall the Database anti-ransomware agent.

    Reinstall the agent from the Security Center console. For more information, see Manage protection policies and agents.