This topic describes how to perform SAN File System backup operations using two variations of the file-based (API) method.
The file method of backup is used for SANs consisting of storage subsystems that do not offer built-in copy services. SANs that do offer copy services can use the LUN method of backup.
/usr/tank/admin/bin/sfscli mkimage -fileset fileset_name -dir directory_name Flashcopy_image_name
/usr/tank/admin/sfscli mkdrfile most_recent_metadata_file_name
A text file is created in /usr/tank/server/DR. Copy the resulting file onto your backup medium (usually tape).
/usr/tank/admin/bin/setupsfs -backup
A tar file called DRfiles-metadata_server_name-timestamp.tar.gz is created in /usr/tank/server/DR/ (by default). Copy the resulting tar file onto your backup medium (usually tape). The list of files to be backed up is specified in /usr/tank/admin/config/backup.list. You can customize the contents of backup.list to save any files of your choosing into the DR tarball.
However, if your existing backup application does not provide the features required for the enhanced method, follow this procedure for SAN File System file-based backup:
/usr/tank/admin/bin/sfscli mkdrfile most_recent_metadata_file_name
A text file is created in /usr/tank/server/DR/. Copy that file onto your backup medium (usually tape).
/usr/tank/admin/bin/setupsfs -backup
A tar file called DRfiles-metadata_server_name-timestamp.tar.gz is created in /usr/tank/server/DR/ (by default). Copy the resulting tar file onto your backup medium (usually tape).
For additional information about restore procedures, including commands, refer to the IBM® TotalStorage® SAN File System Maintenance and Problem Determination Guide, provided on the publications CD that came with your metadata servers.
Parent topic: Backing up the SAN File System
Related concepts
Engines
FlashCopy images
Clients
Related reference
Managing disaster recovery
mkdrfile
mkimage