Verifying that the clone is complete before doing a point in time rollback
NetBackup initiates clone creation on the array. For large source devices, clone creation may take a long time to complete. The Symmetrix array, however, makes the new clone immediately available for normal restore. This availability allows individual files or directories to be restored as soon as the NetBackup Activity Monitor marks the job as finished, even if the clone has not been fully created.
Although you can restore individual files or directories before the clone is completely copied, you cannot perform a point in time rollback. Clone creation must be complete before a point in time rollback can succeed.
If a point in time rollback begins before the clone is finished, the restore fails without a failure notification in the Activity Monitor. In this case, the bpfis log contains the phrase Invalid clone state, cannot restore from device-ID to device-ID, where the first device ID is the source and the second is the clone.
To verify that the clone is complete before doing a point in time rollback
- Create a temporary file that contains only the source and target device IDs separated by a space.
For example, if the source device ID is 0050 and the target (clone) device ID is 0060, the temporary file should contain the following:
0050 0060
- Check the status of the clone with the symclone command. For example:
symclone -sid 58 query -file /tmp/0050_0060.txt
where 58 is a short version of a Symmetrix ID ending in 58, such as 000187910258, and /tmp/0050_0060.txt is the temporary file.
- In the output, look for Copied under the State column. When the clone pair is in the copied state, it is ready for point-in-time rollback.
More Information