Failed to open backup #XXXX for reading

ISSUE

Archive fails with the following errors:

5933 WBSVMMGR.xxxx.local|WBMIccCONTACT VMwareFull 05-08-16 18:00 82651MB Failed to open backup #XXXX for reading 
5943 WBSVMMGR.xxxx.localWBSFAX VMwareFull 05-08-16 21:35 29452MB Failed to open backup #XXXX for reading 
5938 WBSVMMGR.xxxx.local|WBSIVR VMwareFull 05-08-16 20:00 28500MB Failed to open backup #XXXX for reading 
5935 WBSVMMGR.xxxx.local|WBMiVoiceCR VMwareFull 05-08-16 19:00 26241MB Failed to open backup #XXXX for reading 
6009 WBSVMMGR.xxxx.local|WBSMCD VMwareFull 05-09-16 21:00 9657MB Failed to open backup #XXXX for reading 
5942 WBSVMMGR.xxxx.local|WBSCONF VMwareFull 05-08-16 21:31 22105MB Failed to open backup #XXXX for reading

RESOLUTION

There are a few approaches to take when encountering this issue:

  • Archive more frequently.
  • Reduce the amount of backups being performed on the system.
  • Increase the retention within the system on clients to allow for backups to stay on the system longer.
  • Connect to the appliance via SSH and edit "master.ini". Under the [StorageManager] section, change the following line to equal True:
  • ProtectArchiveBackups=False   ; Protect backups in executing archive jobs from being purged
    change to:
    ProtectArchiveBackups=True   ; Protect backups in executing archive jobs from being purged

CAUSE

When the system attempts to archive the backup, it had already been purged. This typically occurs when the system is needing storage space for new backups to land.

NOTES

NOTE: With changing the "ProtectArchiveBackups" value to True, the system runs the risk of filling up the system during the archive (depending on the time archive takes to complete).
 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Contact us