Interrupted mirror process causes corrupt files on resume

Article ID: 184

Last updated: 30 Jun, 2014

Note:
This bug has been addressed in V6.2.4 and will not occur any more. However, it is important that all data mirrored using V6.2.3 or earlier must still be checked and fixed by using step 2 below (after the upgrade to V6.2.4).

Symptom

During a roll-up an error is found and an Integrity Check is initiated. The Integrity Check will then report one or more corrupt files.

Cause

A problem with the mirror resume results in one or more resumed files to be corrupt.

Solution

For Backup Account where you know the above took place, the Integrity Check will fix the Backup Account by removing the corrupt files from the data set. However, the files will not be mirrored again. To ensure the files are mirrored from the SS (if still available) follow these steps on the MirrorServer only:

Browse to the GUID folder for the Backup Accounts in question

Delete the Backups folder

Delete the dataindex.dat file located in the Data folder

Delete the smallfiles.a5files file located in the Data folder

Initiate the mirror process

To check all Backup Accounts on the MirrorServer for corrupt files please follow these steps on the MirrorServer only:

Run a standard Integrity Check on all Backup Accounts. This can be done using a task file.