I started with a Backup Exec 2012 project for a larger company some months ago. One of their demands was to build a high-available solution with enough scalability for the next two years. The first thing that pops-up in my mind was an implementation of a Backup Exec Central Administration Server Option (CASO) with catalog replication. That should do the trick!
What are catalogs? The catalog and the database are required to perform restores of the data that has been written to tape. When losing the catalog, you are unable to select data to be restored. Compare it with a book without an index. You know it’s somewhere in the book, but can’t tell if it’s in chapter 1 or in chapter 25.. Ofcourse you have the ability to rebuild your catalog by performing a “catalog media” job. Needless to say this is a time-consuming job!
During the implementation, it came to my attention that this was not a redundant setup. I started a search with the best consultant on the world = Google and I was quiet disappointed with the results. Apparently nobody posed this question before or has written something about it. I saw this as an opportunity and wanted to clear this one out.
First of all, there are three ways catalogs can be stored. These are described in the Backup Exec 2012 Administrator’s Guide.