Recovery from Clone Volumes

For recovery from clone volumes, use the mmrecov command, as described in "Using the mmrecov Command".

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 17  22:21 1996  mars's Backup bootstrap information Page 1
date    time       level  ssid       file  record   volume 
6/14/96 23:46:13   full   17826163    48       0   mars.1 
6/14/96 23:46:13   full   17826163    12       0   mars_c.1
6/15/96 22:45:15      9   17836325    87       0   mars.2 
6/15/96 22:45:15      9   17836325    24       0   mars_c.2
6/17/96 22:20:25      9   17851237    52       0   mars.3
6/17/96 22:20:25      9   17851237     6       0   mars_c.3

After mmrecov recovers 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.

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 are not online, mmrecov attempts 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.1 and mars_c.3 volumes both need to be online. If the mars_c.3 volume is the only one online, mmrecov also requests mars.1.