Recovery from Clone Volumes

For recovery from clone volumes, use the mmrecovcommand, as described in "Using the mmrecovCommand" on page 24.
Select the bootstrap save set ID that includes the information associated with the cloned save set. The most recent bootstrap is the last save set listed in the bootstrap output.
In the following example, the ssid of the most recent bootstrap is
17851237. The clone of the bootstrap save set resides on mars_c.3. The value for the file location is 6, and the value for the record location is 0..

Jun 1722:21 1996mars's Backup bootstrap information Page 1
datetime level ssid filerecordvolume
6/14/96 23:46:13full17826163480mars.1
6/14/96 23:46:13full17826163120mars_c.1
6/15/96 22:45:15917836325870mars.2
6/15/96 22:45:15917836325240mars_c.2
6/17/96 22:20:25917851237520mars.3
6/17/96 22:20:2591785123760mars_c.3

After mmrecovrecovers the bootstrap save set, it continues recovering the remainder of the server's client index to complete the recovery. The cloned bootstrap contains information about the original and cloned volumes.

Caution - To most easily recover data from clone volumes, make sure that all the required clone volumes are mounted in attached devices at the time you run mmrecov. If some of the clone volumes ar e not online, mmrecovattempts to recover the server's client index from the original volume, not the clone volume.

Based on the preceding example of bootstrap output, the mars_c.1andmars_c.3 volumes both need to be online. If themars_c.3volume is the only one online, mmrecovalso requests mars.1.

Solstice Backup 5.1 Disaster Recovery Guide

*April 1998

28