Backing up using the file-based (API) method

This topic describes how to perform SAN File System backup operations using two variations of the file-based (API) method.

Prerequisites

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.

Context

You have two possible options when using the file method of backup. Which method you choose depends on the characteristics of the backup application in your existing environment.
  • If your existing backup application allows you to selectively choose subdirectory branches for backup, and allows you to restore files to the directory two levels above their original location, follow this optimized procedure for SAN File System file-based backup:
    1. Stop or pause all SAN File System client applications. Because this task is application-specific, refer to the application documentation for details on performing this step.
    2. Create FlashCopy® images of each fileset.
      /usr/tank/admin/bin/sfscli mkimage -fileset fileset_name
      -dir  directory_name Flashcopy_image_name
      Tip: Consider using the SAN File System console. It allows you to create multiple FlashCopy images quickly and easily. See Saving a FlashCopy image of a fileset and accessing it.
    3. Restart the client applications using the specific procedures for those applications.
    4. From the master metadata server engine, save the most recent metadata to accompany the FlashCopy images.
      /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).

    5. On each metadata server, back up additional operating system and SAN File System administration configuration files.
      /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.

    6. Use the backup application to back up the .flashcopy directories. Also, back up the file containing the metadata (the file created by the mkdrfile command) and the *tar.gz file created by setupsfs -backup.
      Attention: Back up Microsoft® Windows® filesets only from a Windows client; back up AIX® filesets only from an AIX client.
  • The enhanced method allows you to re-enable client applications more quickly. Creating FlashCopy images is much quicker than backing up the real files to tape.

    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:

    1. Stop or pause all SAN File System client applications. Because this task is application-specific, refer to the application documentation for details on performing this step.
    2. From the master metadata server engine, save the most recent metadata.
      /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).

    3. Use the backup application to backup all fileset_name/directory_name subdirectories and their contents, to your backup medium (usually tape). If possible, exclude all .flashcopy subdirectories and their contents because they are not of any use during a subsequent restore operation.
    4. On each metadata server backup additional operating system and SAN File System administration configuration files.
      /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).

    5. Restart the client applications using the specific procedures for those applications.

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

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