Backup (KBU)
Articles related to the Kaseya Backup Module powered by Acronis.
- Recovery Guide - Universal Restore
- Recovery of Acronis backup fails with "Failed to get backup URIs from archive"
- Resolving “orphaned” offsite synthetic full backups
- Restore backup to a 2008 Domain Controller with authoritative restore
- Restoring backup image to Hyper-V virtual machine
- Restoring to M.2/NVMe drive using Acronis 11.7 & WinPE bootable media
- Returning backup licenses from offline agents
- Schedule Volumes page does not contain correct disk layout
- Support for Advanced Format (4K-sector) hard disks
- Synthetic backup failed - ERROR! Unable to open source archive
- Synthetic full backups appear to be "hung" or stuck at 95% estimated completion
- This machine does not have enough local hard drive space to copy backups sets for a synthetic full backup
- Troubleshooting backup failure
- Troubleshooting CD Recovery
- Troubleshooting Explore Volumes
- Troubleshooting Image to VM conversion
- Troubleshooting Universal Restore
- Unable to restore MBR from Acronis backup image - system will not boot
- Unable to restore to RAID disk - each physical RAID disk unit appears as a seperate disk when selecting the destination disk
- Universal restore fails with "File 'restore_aw_assistant.exe', that is required for installation of device ..."
- Unscheduled Full backup runs after previous backup attempt using "Backup Now" button was skipped
- Using BUDR/KBU Synthetic Local Consolidation
- Verify Backup task hangs after scheduled backup job
- Verify fails with "Insufficient system resources exist to complete the requested service"
- Verify or recovery of backup fails
- WARNING: Unable to find the archive index. Assuming archive index is the same as the file index.
- What are the options and guidelines for backing up SQL, Exchange?
- What do I do when backup fails with error "Backup failed - Command line parameters are incorrect or incomplete"?
- When running a image location check for about 60 computer at the same time, 75% return "Bad Path" while other succeed.
- When running an image location check for about 60 computers at the same time, all with the same UNC path, why do 75% return "Bad Path" while others succeed?