HP XP Racks - Manual (Page 375)

2. Back up database A only. The replica 2010/9/06 08:15:00 is created.
The following figure shows the correspondence of the backup catalog and copy group.
Figure 14 Correspondence of backup catalog and copy group
When you back up database A only (as described in step 2), the replica 2010/9/06 08:15:00
is created, and the old backup information (replica 2010/8/31 07:14:00 ) about the copy group
vg01,obj01 on database A is deleted from the backup catalog. In other words, because the backup
information about database B (included in replica 2010/8/31 07:14:00 ) is also deleted from the
backup catalog, database B cannot be restored even though the backup data exists in the secondary
volume. When you restore database B, restore the backup data obtained using step 1 (backing up
database A and database B concurrently) from tape to the secondary volume, and then restore the
backup data from the secondary volume to the primary volume.
Remote operations
When a backup or restore operation is performed between different sites, Device Manager needs to
be active on the server that is running Replication Manager at the local site. However, Device Manager
does not need to be active on the management server at the remote site. (This differs from operations
such as copy pair definition, where Device Manager must be active on the remote site.)
Refreshing hosts after changes to system configuration
When any of the following occurs you should execute a Refresh Hosts for the relevant database server:
• The configuration definition file for P9000 RAID Manager is changed (excluding changes made
with Replication Manager).
• The mount point (drive letter for Windows) is changed.
• The disk configuration is changed by adding and removing a hard disk.
• The configuration of a database is modified.
• An SQL Server instance is constructed or deleted.
• An SQL Server database is added or deleted.
• The name of an SQL Server database is changed.
User Guide 375