An attempt to remove a backup of some container results in the error message:
~# vzarestore -r 050eef72-0425-db43-b0d5-bd4c7d6aa10e/20130911224014 Remove backup: 050eef72-0425-db43-b0d5-bd4c7d6aa10e/20130911224014 Failed to get information about backup: 050eef72-0425-db43-b0d5-bd4c7d6aa10e/20130911224014
The backup is not present physically:
~# vzabackup --view-folder localhost path = /vz/backups/ login = ~# ll /vz/backups/050eef72-0425-db43-b0d5-bd4c7d6aa10e/20130911224014 ls: cannot access /vz/backups/050eef72-0425-db43-b0d5-bd4c7d6aa10e/20130911224014: No such file or directory
PVA version is lower than 4.6-1866:
~# rpm -qa pva-release pva-release-4.6-1722.x86_64
This happens because PVA Agent tries to unconditionally remove backup files even if those files do not exist on the file system. The necessary steps to check presence of files are added to PVA Agent 4.6-1866 as the result of fixing the request PVA-31725.
This problem was fixed in the later versions of PVA Agent.
- Update your PVA version: Parallels Virtual Automation builds
If update is not possible (for example, if you are using PVC 4.6: Parallels Virtual Automation builds), you can use the following workaround:
~# vzabackup --view-folder localhost path = /vz/backups/ login = ~# vzabackup --set-folder --backup-folder-path /vz/backups/ localhost ~# vzabackup --view-folder localhost path = /vz/backups/ login =
Resetting the backup folder to the same location will remove all non-existent backups from the list.