408 IBM ProtecTIER Implementation and Best Practices Guide
Which database copy is optimal
Before running a restore for DR, verify that the list of associated cartridges are replicated to
the DR site; otherwise, an earlier full backup image must be used for recovery. The time of
the last full backup is the specific time each day where your replication backlog is zero (there
is no pending data to replicate).
If you do not know a specific time each day when your backlog is zero, assess the cartridges
by recovering the backup application catalog and scanning it to find the last full backup where
its associated cartridges completed replication. There are two primary methods to obtain a
copy of the catalog at the DR site:
򐂰 From a catalog backup on a virtual cartridge that is replicated to the DR site
򐂰 From disk-based replication
If the catalog is backed up to a virtual cartridge, through the cartridge view of the library in
ProtecTIER Manager, query each of the cartridges used for catalog backup to find the most
recent sync dates marked on the cartridges. If there are multiple backup copies, find the latest
backup that finished replication. To recover the backup application catalog from a backup on
a virtual cartridge, you must work with the replicated cartridges to get an updated copy of the
catalog to the DR site.
Each cartridge contains a time stamp of a last sync time that displays the last time the
cartridge's data was fully replicated to the DR site. The sync time is updated during the
replication process, not just when the replication for this cartridge is finished. The cartridge
marked with the most recent last sync time date must be used to recover the backup
application catalog.
Which cartridges at the DR site are valid for restore
When the Tivoli Storage Manager server at the DR site is recovered, review the status of the
replicated cartridges to ensure their replication consistency with Tivoli Storage Manager
database. Use the available ProtecTIER Manager system Replicated Cartridges
Status Report.
To eject a cartridge from a library, run the following command:
CHECKOUT libvolume
For example:
TSM:TUSCSON1>CHECKOUT LIBVOL <name of library> REMOVE=BULK FORCE=yes
CHECKLABEL=YES VOLLIST=<volume1,volume2,...volume3>
To inject or import (insert) a cartridge to a library, run the following command:
CHECKIN libvol
For example:
TSM:TUCSON1>CHECKIN libvol <name of library> search=BULK checklabel=barcode
status=SCRATCH WAITTIME=0
22.9 Symantec NetBackup deployment with ProtecTIER
replication
In this section, we describe the usage of the IBM ProtecTIER (TS7650 Appliance) IP
replication system in a NetBackup environment and describe the ramifications of possible
scenarios related to DR.
Chapter 22. Replication and DR deployment with backup applications 409
Here are possible automation options within a NetBackup backup application environment:
򐂰 Vault profile
You can create a vault profile for ejecting cartridges from a library by running the
following command:
vltrun <vault profile name>
You can inject a cartridge in to the library at the DR site by running the
following command:
vltinject <vault profile name>
򐂰 Barcodes
You can eject cartridges from a library by running the following command:
vmchange –res –multi_eject -ml <barcodeA:barcodeB:..:barcodeZ>
You can inject cartridges to a library by entering the following command:
vmchange –res –multi_inject -ml <barcodeA:barcodeB:..:barcodeZ>
򐂰 Inventory command
This command scans the import/export slots and injects all available cartridges to
the library:
vmupdate –rt <robot type>-m<robot #> -empty_map
22.9.1 Scripting the inject/eject commands
Vault and inject/eject commands can be scripted to run periodically on the backup application
host (see Example 22-4). These commands trigger automatic cartridge movement from the
import/export slot to the library whenever the relevant cartridge is in the import/export slot.
This process ensures free import/export slots.
Example 22-4 Example script of inject/eject commands
#!/bin/csh
while (1)
vltinject myVault
sleep 600
end
22.9.2 Scripting the inventory commands
Scripting the inventory command is not recommended because it scans the robot, and
therefore might take a long time to complete on libraries with many cartridges.
22.9.3 Setting up NetBackup for backup and restore
NetBackup deployments typically use a schema of weekly full backups and daily incremental
backups. There are two types of incremental backups:
򐂰 Cumulative: Backs up everything since the last full backup.
򐂰 Differential: Backs up everything since the last backup.

Get IBM ProtecTier Implementation and Best Practices Guide now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.