HP Integrity NonStop J-Series - Manual (Page 104)

File Protection and Recovery for Virtual Disks
HP NonStop Storage Management Foundation User's Guide—523562-007
7-4
Other File Recovery Methods
PHYSVOL Option (RESTORE)
A file’s location is selected at the time the file is restored: therefore, it generally is not
restored to the same physical volume where it resided at the time of the backup. You
can specify the volume on which to restore files by using the PHYSVOL option of the
RESTORE command. The following command:
RESTORE $TAPE, $VIRT.MY.FILE*
restores all files on $VIRT that match the pattern MY.FILE*. In this case, the virtual disk
process selects the new locations for the files. The following command:
RESTORE $TAPE, $VIRT.MY.FILE, PHYSVOL $P7
restores all files on $VIRT that match the pattern M.FILE* to the physical volume $P7
(provided that it is in the storage pool with which $VIRT is associated and has sufficient
space).
Using the ZOT Command
If the physical disk where a file to be restored resides is unavailable, the RESTORE
operation will fail. The failure occurs because the virtual disk process cannot delete the
old file.
The SMFIXUP ZOT command can be used to delete the file’s VDP catalog entry prior
to the RESTORE operation. This method allows the RESTORE utility to place the file
on a different physical volume using the same logical file name. For example, suppose
that physical disk $P4 contains the unaudited file $VIRT.CRITICAL.FILE. If $P4 suffers
an unrecoverable hardware error, the file can be recovered by first issuing an
SMFIXUP ZOT command on the file and then by issuing a RESTORE command on
the file.
For more information on the ZOT command, see Section 9, SMFIXUP Utility . For more
information on the RESTORE utility, see the Guardian Disk and Tape Utilities
Reference Manual.
Other File Recovery Methods
Other file recovery methods can include volume mode BACKUP and RESTORE
operations and, for D-series versions of SMF only, archiving disk mirrors by using a
PUP utility REVIVE scheme.
For G-series versions, whenever a disk is started, a REVIVE is accomplished
automatically.
Caution. These methods can result in inconsistencies between SMF catalogs and data on
disk, and in addition can result in missing or corrupted files. These methods should not be
used for disks in SMF pools.