We upgraded our backup node from Virtuozzo 6 to 7.0.3. Backups ran OK until Friday night when I upgraded to 7.0.4 and Virtual Automator 7.0.2. Short version of the story: the backup path changed Friday. I do not see an option for the backup path in VA...I am not sure now if that was in 7.0.1 and removed, or I didn't notice it had just used the same path from v6. In VZ 6 it was a separate option from the location of the container backups, and I thought I remembered checking that path after upgrading VA. Per the 7.0.4 documentation: "By default, backups are placed in the /vz/vmprivate/backups directory. To set a different default backup directory, use the prlsrvctl set --backup-path <path> command." The backups are in fact now being saved to /vz/vmprivate/backups which on this server is a 100 GB partition, instead of our 4 TB backup drive (the path was /backups/vm). I changed the location and moved the files, but VA only recognizes the backups that were made in /vz/vmprivate/backups. So, it seems either the upgrade to 7.0.4 or the subsequent restart must have changed the location, since there were no files in /vz/vmprivate/backups before Saturday morning and backups in the old location up until Friday. That also explains why our Windows VM backups failed since Saturday..they are running out of space for the "initial" full backup. Since I couldn't find the error in Google or Virtuozzo's KB, the backup task failure message was "Operation is finished with errors: operation on VE "windowsVMname" failed: Cannot backup VM. The backup command for the "windowsVMname" virtual machine failed with code 255." Unfortunately we didn't get emailed an alert for that error.