Tape Catalog
Tape catalog can be to perform tape inventory to find the information about the backup contents that are stored in the Media. With the metadata we have added during backup, we will need to populate DB entries with details of newly detected backups in the server as well as in the Tape Agent. We can use the Tape Catalog option in order to restore data from Older tape media.
Possible scenarios to use the Tape catalog option
BDRSuite Backup Server uninstalled
Tape Agent Uninstalled (Tape server connected machine)
Tape Backup deleted from BDRSuite Backup Server
Try to attach the tape media to a different BDRSuite Backup server.
BDRSuite Backup Server uninstalled
Case-1: BDRSuite Backup Server uninstalled, but Tape Server having the agent connected with Tape library containing media with data.
- Install the BDRSuite Backup Server and push the agent to Tape Server. It will not be allowed and will throw an error like (Error 117030: Vembu Integration Service is already installed in the target host by a different backup server.)
- In this case , the old tape agent should be removed from the Tape Server machine and have to be added again in BDRSuite Backup Server.
- Once done, perform rescan and inventory to detect the media. Run Catalog for the media present in the Tape Library.
Case-2: BDRSuite Backup Server uninstalled by removing Tape agent from Tape Server. Only Tape Media present with data.
- Install BDRSuite Backup Server and add the Tape Server. Agent will be pushed and installed in Tape Server. Perform rescan and inventory to detect the media. Run Catalog for the media present in Tape Library.
Tape Agent Uninstalled (tape server connected machine)
Case-1: BDRSuite Backup Server present with Data, but in Tape Server, agent was uninstalled manually and Tape library having media with data.
- Since Tape agent is not present in the Tape Server, it has to be removed from BDRSuite Backup Server UI. Then, have to re-add it so that a new tape agent can be installed in Tape Server.
- Perform rescan and inventory to detect the available media. Run Catalog for the media present in Tape Library.
Case-2: BDRSuite Backup Server present with Data, but in Tape Server, agent was uninstalled from BDRSuite Backup Server UI and Tape library having media with data.
- Add the Tape Server again in BDRSuite Backup Server to push the agent. Once agent is pushed, perform rescan and inventory to detect the available media. Run Catalog for the media present in the Tape Library.
Tape Backup deleted from BDRSuite Backup Server
- If Tape backup is deleted from BDRSuite Backup Server, then the backup entries will be removed only from BDRSuite Backup Server DB and Tape agent DB. Backed-up data will not be removed from the Tape media.
- If we want to recover that deleted backup’s data, and if we know the media, we can directly run catalog for that media and get the backend entries backup to DB and make it available for restores.
Try to attach the tape media to a different BDRSuite Backup Server
- We can place the media used in the different BDRSuite Backup Server to the current BDRSuite Backup Server’s Tape Library.
- We can perform rescan and inventory to get the media properties and then can run catalog to get the metadata of backups present in it.
|
Notes:
|
How to run the Util
Install BDRSuite Backup Server (if not already installed)
Add Tape Server to the BDRSuite Backup Server (if not already done)
Perform Rescan & Tape Inventory process to detect the available media.
Run the following Util,
bin\VembuBDR.exe TapeOperation catalog media_barcode
e.g: bin\VembuBDR.exe TapeOperation catalog G0PK0FJLZPD_1000000000Q
It will create a catalog for the attached media. Once the catalog operation is completed, we can see the corresponding tape backup in the ‘Tape Archive -> List Tape Archive Jobs’ page.
| | Note : The cataloged backups will be in suspended state by default and from that we can perform recovery operations. |
How To Run Tape Catalog
- Tape Media which needs to perform catalog should be placed in the Tape Library connected to BDRSuite Backup Server.
- Need to perform rescan and inventory from UI, to detect the media details and update it in the database in both the Tape Agent and BDRSuite Backup Server .
- Need to initiate Catalog Util in BDRSuite Backup Server with required details (as mentioned separately above - How to run the Util).
- Based on the barcode information we got, we load the corresponding media to Tape drive and start reading.
If the data is written to more than one media, we will get the next media information in Tape Backup config XML. (Like wise, we can loop all media in the set and perform catalog.)
After reading all the backup configuration details, it will be fetched by the BDRSuite Backup Server and it will update the DB. All the Tape backup jobs will be listed again 'List Tape Archive Jobs' in the BDRSuite Backup Server.
If backup data present in multiple media
Example Scenario;
Say, one VM having 3 disk, 2 disk data present in 1st media, 3rd disk data partial in 1st media, continued in 2nd media and completed. If we run catalog for 1st media, we will get the VM start offset and 2 disk's start and end offset, then 3rd disk start offset. These details will be updated in database periodically when we receive filemarks.
Once after reaching the end of media, it will try to load 2nd media, if it is not present, we will come out of Catalog operation and DB will have details till we read the 1st media. The end offset for that 3rd disk will be -1. It means incomplete data.
During restore, we will get VM list from Tape agent based on the number of success disks present. So, we will restore 2 disks of that backup.
|
|
Note:
We will fetch the backup details from the media, and if the last backup points to the next media, then we will load that media and get backup details. Like this we will traverse all the media and get details.
|