Attix5 Pro FAQ
Search:     Advanced search

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

  1. 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:
    1. Browse to the GUID folder for the Backup Accounts in question
    2. Delete the Backups folder
    3. Delete the dataindex.dat file located in the Data folder
    4. Delete the smallfiles.a5files file located in the Data folder
    5. Initiate the mirror process
  2. To check all Backup Accounts on the MirrorServer for corrupt files please follow these steps on the MirrorServer only:
    1. Run a standard Integrity Check on all Backup Accounts. This can be done using a task file.
    2. Download and extract ICtaskfile.zip.
    3. Place the extracted file, stdICall.integritycheck, in the MirrorServer task folder (e.g.: C:\ProgramData\Attix5 Pro\SS_Service\TaskQueue)
    4. The MirrorServer will then run a standard Integrity Check on all Backup Accounts where an encryption key is present
    5. Inspect the SSLog on the MirrorServer and see which Backup Accounts report corrupts files
    6. Browse to the GUID folder for the Backup Accounts affected
    7. Delete the Backups folder
    8. Delete the dataindex.dat file located in the Data folder
    9. Delete the smallfiles.a5files file located in the Data folder
    10. Initiate the mirror process
Article ID: 184
Last updated: 30 Jun, 2014
Revision: 13
Views: 54956
Comments: 0
Posted: 23 Aug, 2012 by Van Rensburg J.
Updated: 30 Jun, 2014 by Van Rensburg J.
This article was:  
Prev   Next
Article 183 - SQL Server instance shows in Restore tab despite the database...     Article 191 - Runner errors after an upgrade from V5