This topic describes how to perform SAN File System backup operations using the LUN method. LUN backup requires that all transactions are stopped during the process.
The LUN method of backup is only available to SANs comprised of storage subsystems with built-in copy services. SANs without such service must use the file-based (API) method of backup.
Because the LUN method deals with data at the byte level, it is an all-or-nothing approach for backing up and restoring your entire SAN File System. In particular, it provides no ability to restore individual files (because it has no concept of files); you have to save and restore all the data — metadata and file data — or none of it. Restoring a previously saved FlashCopy® image is the best method for recovering a subset of SAN File System data. Therefore, the LUN method is best employed as part of a disaster recovery situation.
/usr/tank/admin/bin/sfscli quiescecluster -state full
This procedure also locks out any subsequent new input and output from the clients or metadata servers.
/usr/tank/admin/bin/sfscli resumecluster
For additional information about restore procedures, including commands, refer to the IBM® TotalStorage® SAN File System Maintenance and Problem Determination Guide, on the publications CD that came with your metadata servers.
Parent topic: Backing up the SAN File System
Related concepts
Backup and restore
Engines
FlashCopy images
Clients
Related reference
Managing disaster recovery
quiescecluster
resumecluster