AnyBackup Failed to Back Up UIS Virtual Machine – Fix & Troubleshooting Guide
Problem Description
A user reported that the Aishu AnyBackup system failed when attempting to back up a specific business system. The failure reason was: The virtual machine does not support CBT.
Symptoms:
AnyBackup shows a backup failure. Reason: The VM does not support CBT.
Versions:
User Business System: openEuler 22.03 (LTS-SP3)
AnyBackup Version: 7.0.18.4.165
HCI Version: H3C UIS V8.0 (R0886P03)
Standard 4-node HCI.
Troubleshooting and Analysis:
1. On-site, the CBT backup button in the VM console was grayed out and could not be selected.
2. Checked the VM settings in the console; the disk format was indeed set to "Intelligent," and there were no multi-level images. However, the VM had existing snapshots.
3. Logged into the backend terminal to check disk information. The backend showed the VM was using only one disk but had snapshots, and it was currently linked to a snapshot file.
4. After cloning the original VM, the cloned VM only had a single-level image.
Why did AnyBackup fail to Back Up UIS Virtual Machine?
If AnyBackup failed to back up the UIS virtual machine, the issue is usually related to:
-
Snapshot failure
-
Permission or credential errors
-
Insufficient storage space
-
Network interruption
-
Incompatible hypervisor version
AnyBackup relies on stable connectivity and correct VM permissions to complete backup jobs successfully.
If your VM is hosted on UIS infrastructure, integration issues may cause snapshot timeout errors.
Root Cause:
The VM has multi-level images, which prevents the backup device from backing it up.
Solutions:
Power off the VM and merge the multi-level image disk files.
The specific steps are as follows:
1. Perform a safe shutdown after cloning the VM as a backup.
2. Click "Merge Image."
3. Confirm the image merge. Once the merge is successful, restart the VM.
4. Check the VM disk status; the files have been merged. Backup should now work normally.
Usual Step-by-Step Fix for AnyBackup VM Backup Error
1. Check VM Snapshot Status
-
Log into hypervisor console
-
Verify snapshot is not locked
-
Delete old or failed snapshots
-
Retry backup task
Snapshot conflicts are one of the most common causes of backup failure.
2. Verify Credentials & Permissions
Ensure the backup account has:
-
Administrator privileges
-
Snapshot permission
-
Storage access rights
Incorrect role assignments often cause silent backup failures.
3. Check Storage Availability
Low storage space may interrupt the backup writing process.
Run storage check on:
-
Backup repository
-
Target NAS or SAN
-
Local disk path
4. Confirm Network Stability
Test connection between:
-
Backup server
-
UIS host
-
Backup repository
High packet loss or firewall restrictions can block backup transfer.
Related Readings:
This improves crawl depth and keeps users engaged longer.