Ask the Community
Groups
Failed to open backup #XXXX for reading - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p>Archive fails with the following errors:</p> <pre class="code codeBlock" spellcheck="false" tabindex="0">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</pre> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p>There are a few approaches to take when encountering this issue:</p> <ul><li>Archive more frequently.</li> <li>Reduce the amount of backups being performed on the system.</li> <li>Increase the retention within the system on clients to allow for backups to stay on the system longer.</li> </ul><p>We will now need to edit the field called ProtectArchiveBackups to allow (or not allow) the backups that are going to be placed on your Cold Backup Copy media to be held in place until the data is confirmed on the media.</p> <p><br><strong>FROM THE WEB INTERFACE</strong></p> <p>Click <strong>CONFIGURE</strong> (page)> <strong>Appliances</strong> (tab) and select the name of your Unitrends appliance. Click the <strong>Edit</strong> button above. Click the<strong> Advanced</strong> (tab). Click the <strong>General Configuration</strong>.</p> <p><br><img src="https://us.v-cdn.net/6032361/uploads/migrated/WA6O158DRH66/mceclip0.png" alt="mceclip0.png" class="embedImage-img importedEmbed-img"></img></p> <p> </p> <p><strong>FROM THE SSH COMMAND LINE:</strong></p> <p>Connect to the appliance via SSH and edit "master.ini". Under the [StorageManager] section, change the following line to equal True:</p> <pre class="code codeBlock" spellcheck="false" tabindex="0">ProtectArchiveBackups=False ; Protect backups in executing archive jobs from being purged</pre> <p>change to:</p> <pre class="code codeBlock" spellcheck="false" tabindex="0">ProtectArchiveBackups=True ; Protect backups in executing archive jobs from being purged</pre> <h2 data-id="cause"><strong>CAUSE</strong></h2> <p>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.</p> <h2 data-id="notes"><strong>NOTES</strong></h2> <p>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).<br> </p> </article> </main>