HP P6000 Replication Solutions Manager Administrator Guide (T3680-96069, June 2012)

Volume replacement
The volume replacement method completely removes the existing source volume and replaces it
with a backup copy. This method is preferred when a physical failure of the source volume has
occurred, or if the combined size of the files that need to be restored is large enough that a selective
file replacement would take too long to complete.
There are two volume replacement methods, as described in the following sections:
Direct snapclone
The source volume is removed from the source host and replaced with a snapclone copy, using
the same drive letter or mount point.
Tape to intermediate device
If no snapclone copy is available, but the required fileset is available on tape, perform the following
steps:
1. Create a new volume of the desired size and redundancy level.
2. Present the new volume to the backup server.
3. Restore the data from tape to the new volume.
4. Use the new volume as a replacement for the original source.
CAUTION: The volume replacement method replaces the entire contents of the source. If the
source volume contains data or log files for tablespaces that were not placed in online backup
mode when the copy was created, then replacing the entire volume with a snapclone copy will
corrupt these tablespaces. When using the volume replacement method, ensure that all files on the
replacement volume belong to databases that were backed up at the same time.
NOTE: Backups based on snapshots or fractured mirrorclones (as opposed to snapclones) are
not suitable for volume replacement because snapshots and fractured mirrorclones are virtual
volumes that depend on the integrity of the source. If the source volume has physically failed, any
snapshots or fractured mirrorclones of it will have likely failed as well.
Selective file replacement
This method leaves the original source volume in place and replaces some or all of the volume
files with backup copies. This method is generally preferred over volume replacement when only
a subset of the tablespaces that reside on the volume need to be restored.
There are two selective replacement methods, as described in the following sections:
Drag and drop from snapshot, snapclone, or fractured mirrorclone
If a snapshot, snapclone, or fractured mirrorclone copy of the required data and log files is
available:
• The snapshot, snapclone, or fractured mirrorclone devices can be presented to the source
host.
• The devices can be mounted manually using the operating system utilities.
• The required files can simply be dragged and dropped from the snapshot, snapclone, or
fractured mirrorclone back to the original source volume.
From tape
If the backup tape is available, you may be able to restore the required files from tape directly
back to the source volume. This process is complicated by the fact that the files being restored
were originally backed up from the snapshot or snapclone copies, probably on a different server.
To restore back to the source volume, the restore process must be redirected to the desired location.
Most backup applications support this feature.
Recovering the database and applying redo logs
This step in the recovery process depends on the nature of the failure from which the data is being
recovered, and whether the database must be online during recovery. Oracle provides several
Restoring an Oracle tablespace that was backed up using the replication manager 73