Error Message

No error messages are seen. The storage tab provides the details. No backup sets are available even though a successful backup is done before the upgrade/ migration of Backup Exec is performed.

This issue can occur when a Backup Exec server is renamed, migrated to a new server with a different name, catalog files copied into the catalog folder from another Backup Exec server with a different name, and less frequently during an in-place upgrade.

During the above scenarios, Backup Exec performs certain internal tasks during service startup to update the Backup Exec database with new server name information and attempt to update the catalog file information in the Backup Exec database.  

During this time, the catalog indexing is paused when Backup Exec creates either be_cat_blocksyncandindex.txt or be_cat_blockSyncToCAS.txt files in the Catalogs folder.

The default location of Catalogs folder is C:\Program Files\Veritas\Backup Exec.

If this internal process is interrupted by a services restart or server restart, these files may become orphaned and they block the indexing of the Catalogs, thus partial backup sets or restore selection or no restore selection is visible on the Backup Exec console.

.

To ensure that the backup sets are visible in the storage tab properly, please perform the following steps.

1. Stop the Backup Exec services using Backup Exec Services Manager.

2. Delete the files be_cat_blocksyncandindex.txt or be_cat_blockSyncToCAS.txt from the Catalogs folder.

3. Perform BEMIG as per the article How to use BEMIG to manually upgrade the Backup Exec database from a previous version (veritas.com)

4. Restart the Backup Exec SQL Services (BKUPEXEC) and Backup Exec services.

5. Launch the Backup Exec Console and the backup sets should be visible properly in the respective storage.

NOTE: If be_cat_blocksyncandindex.txt or be_cat_blockSyncToCAS.txt appear after deleting the file and Backup Exec services restart, please contact Veritas Technical Support.