After restoring a backed-up index, the files in the file store and the references to them in the index might not be synchronized. This is especially the case when only a slightly older version of the index is restored instead of restoring a matching backup of the file store.
To validate if a repair is necessary and to optionally perform the repair, the File Store Rescue Tool can be used.
Note: Running the File Store Rescue Tool can potentially result in false positives being reported by the tool. To prevent this, it is advised to not perform this action on a production environment, but to schedule maintenance time for this.
Accessing the File Store Rescue Tool
The File Store Rescue Tool is available in the Management Console.
Step 1. Access the Management Console by doing one of the following:
- Access the following URL and log in using system administrator credentials (a 'Super user' account):
<Assets Server URL>/console
- In Assets, access the Avatar menu and choose Management Console.
Step 2. Choose File store rescue tool in the menu on the left side of the page.
Validating if a repair is necessary
The first step in the process is to see if any files need to be repaired.
Step 1. On the File Store Rescue Tool page, carefully read the instructions.
Step 2. Click the Dry run option for the task that you want to perform.
The results of the Dry run are published in the log files.
Repairing assets
Step 1. On the File Store Rescue Tool page, carefully read the instructions.
Step 2. Choose an action:
- To repair files, click Rescue and repair.
- To clean up files that do not have an index entry: click Permanently remove version originals that have no entries in the index.
The results are published on the Server Status page of Assets Server in the Running processes section.
Comments
0 comments