FlashCopy image considerations for backup and restore

When you make a FlashCopy® image, the .flashcopy subdirectory is created as read-only. The client backup application typically backs up the .flashcopy subdirectories along with all other directories or files. At restore time, however, the same backup application attempts to copy the original files back into the same subdirectories and fails. (You would not want the subdirectories there because they would appear to be valid FlashCopy images from the client perspective, when in reality, the metadata needed for the original FlashCopy images would be missing.)

One consequence of this process is that there is no way to restore your original FlashCopy images if you have lost your metadata in a disaster scenario. Only the original files are restored. However, if your backup application has the ability to restore files to a directory other than the files' original location (that is, to the grandparent directory two levels above the ./.flashcopy/flashcopy_name directory), then you have all the ingredients for a highly efficient backup, which leverages the FlashCopy image feature.

Tip: Periodically create FlashCopy images. They are the most efficient method for quickly backing up and restoring files in scenarios where the metadata is still available.

Parent topic: Backup and restore

Parent topic: Planning the backup and restore strategy

Library | Support | Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.
IBM TotalStorage SAN File System v2.2