If a catalog becomes damaged, Cumulus may be able to rebuild it. When you try to open a damaged catalog, Cumulus asks to repair it. You can also initiate the repair process for local catalogs from within the program by selecting File > Administration > Rebuild Catalog. For repairing remote or mirrored catalogs, use the Rebuild button in the Catalog Access window when logged in as administrator (File > Connect To.)
Catalogs are most commonly damaged by an abnormal termination of the Cumulus Server that, for example was caused by an improper shutdown or a system crash.
After choosing the rebuild function, a dialog opens that asks whether you really want to do this. If you used the Rebuild button in the Catalog Access window, you are offered two options.
If you choose Rebuild Locally, the catalog is rebuilt locally on the information found.
If you choose Rebuild from Mirror, a window is displayed that contains all relevant information, if the catalog can provide it. If this is not the case, you must enter the information required to identify the mirror manually.
Enter the required information, if necessary, and click OK. Then Cumulus will rebuild the catalog with the data from the mirror and – if there is one – from the queue.
The rebuilt catalog becomes the master of the catalog from which it was rebuilt (the slave catalog), i.e., all further changes to the rebuilt catalog are automatically mirrored to this slave catalog.
NOTE: Catalog rebuilding is performed in the background. However, this process can affect the performance of the Cumulus system.
Where to Get the Queue ID?
Each mirrored catalog has an XML file (*.ccm) that contains the mirroring information. This file is stored in the same folder as the Cumulus catalog. It provides the information on the queue ID under CUID. In the following example the queue ID is {FF9E643F-11BB-4E95-9B62-6BAFE841A5F8}.