Backup Failures After Updating

For number 2, it looks like the ESXi Configuration Backups work if I recreate the task using backup format version 12, but not if I recreate it using version 11.

In the previous build, it worked fine using version 11.

We prefer version 11 because it allows us to keep the backups in separate files, which allows us to sync it in Google Drive and never delete anything, retaining all backups indefinitely (we have unlimited storage).

Using a single file means that to sync to Google Drive we need to upload the entire file each time, and older versions will be deleted from the file by Acronis automatically.  Thus we have to manually manage versioning on Google Drive to ensure older versions are not lost.

For the ESXi Configurations, this isn't a huge deal because we don't really need to keep older backups around indefinitely, and the file size is small.

Our regular VM backups seem to still work with version 11 and multiple files.  This is critical for us so we can upload backups as individual .TIB files to Google for indefinite retention, as required for various legal reasons.  I hope that version 11 is not dropped from the regular backups any time soon!

After testing the job multiple times, it looks like even though version 12 is used, separate files are still maintained for the ESXi Configuration backup plans.  Is this intended behavior?

And after more testing, it looks like this is related to the plan name.  If I name the plan "Test" it works.  If I name it "Weekly ESXi Configuration Backup", it fails.  Is this due to the space?  We had no issues before.  The release notes mention:

[ABR-173518] Backup to NFS shares fails if the name of the backed-up machine contains spaces. Applicable to agentless VM backup performed by Agent for VMware or Agent for Hyper-V.

We are not using NFS, we are using SMB.  And this isn't the machine name that has a space, but the plan name.

Again for number 2:

I've updated one of our instances to build 10330, and I'm still getting this error.

If I run the task with the name "Weekly ESXi Configuration Backup", the files are created in the first location but no copying / verification takes place.  Instead, after all 3 hosts are backed up (3 .TIB files and 1 XML file) I get the error described above.

If I edit the task and change the plan name to "Weekly_ESXi_Configuration_Backup" (using underscores instead of spaces) it works fine.

This problem was introduced with build 10130 and it persists in 10330.  We are using SMB, not NFS.

This problem does not seem to affect our VM backups, which also contain spaces in the plan name (Daily Backup - VMName).  I'll have to check tomorrow to see if they still succeed after updating to 10330 as well as test actual recovery.

For number 1:  I now get a list of disks to select from.  It's got more disks than before, but I believe we still only need to select the first disk and the dynamic volumes.  Is that correct?

Hi Brian,

For item #1 please see my comment in the referenced thread.

For item #2 - the ESXi configuration backups are special type of backups which are unaffected by "Backup format" version and are always created in single format (version 11). The problem you've run into might be caused by spaces in the name of these archives (VM backups are not affected since there is different format) and we'll check it with our QA team.

Thank you.

Thanks for confirming.

FYI after restarting our Acronis Appliance (due to some stuck backup jobs that wouldn't cancel), it appears that all of our backup plans (not just the ESXi Configruation backup plans) are throwing the error if a space is included in the plan name.  The backup runs fine and the file is created, but the error is thrown just before the copy operation starts.  No validation takes place.

I've had to go in and rename all of our plans and scripts to use underscores instead of spaces, and am rerunning our backups again.