Configuring tape devices for full cluster backups

If you plan to back up all volumes in a NetApp cluster to a directly attached tape device, you must configure the tape device.

Before you begin

Ensure that you completed the steps in Configuring full cluster backups to directly attached tape devices.

Procedure

  1. Configure a tape library by following the instructions in Configuring a tape library for NDMP operations.

    If you plan to share drives between the Tivoli Storage Manager server and the NAS file server, configure the drives to be directly attached to the Tivoli Storage Manager server first. Then, use the drive serial numbers to identify the device names on the NAS file server as described in step 2.

    If you plan to connect a library device to the NAS file server, identify the device name and physical node to which the library device is attached:
    1. On the NAS file server, issue the following Data ONTAP command:
      storage tape show-media-changer
    2. Review the command output to find the serial number of the library device and the node of the cluster to which the library device is attached. The same stanza includes the device name, for example, mc0, mc1, or mc2.
    3. Define a single path from any of the data movers that are associated with the physical node on the cluster to the library device that will be used for NDMP backup operations. On the Tivoli Storage Manager server, issue the following command:
      define path data_mover library_name srct=datamover
      desttype=library device=/data_mover_name/device_name
    For the device_name value, use the value that you obtained in step 1.b. For instructions about specifying the other parameters, see DEFINE PATH (Define a path when the destination is a library).
  2. For each tape drive that is attached to the cluster, identify the device name and the physical node to which the drive is attached:
    1. On the NAS file server, issue the following Data ONTAP command:
      storage tape show-tape-drive
    2. Review the output to find the serial number of the tape drive, and the node of the cluster to which the drive is attached. The same stanza includes the device name, for example, st1, st2, or st3.
  3. Define a path from the data mover that is associated with the physical node on the cluster to each tape drive that will be used for NDMP backup operations. On the Tivoli Storage Manager server, issue the following command:
    define path data_mover drive_name srct=datamover
    desttype=drive libr=library_name device=/data_mover_name/device_name
    For the device_name value, enter the device name that you identified in step 2, but add an r to the beginning of the device name. Append an l, m, h, or a at the end. For example, the device name st1 becomes rst1l.

    For information about specifying the other parameters, see DEFINE PATH (Define a path when the destination is a drive).

    Tip: You can follow this example to define paths. In the example, the cluster includes two nodes, and each node has a single drive attached. The data mover is named CLUSTERA. Data movers that are named CLUSTERA-01 and CLUSTERA-02 were automatically created to connect to the physical nodes of the same name that were discovered in the cluster.
    The output of the Data ONTAP command indicated that the drive that is named DRIVE1 is connected to the node CLUSTERA-01 and is assigned the device name ST1. The drive that is named DRIVE2 is connected to the node CLUSTERA-02 and is assigned the device name ST1. The following Tivoli Storage Manager commands are used to define paths:
    define path clustera-01 drive1 srct=datamover destt=drive
    libr=lib1 device=/clustera-01/rst1l
    define path clustera-02 drive2 srct=datamover destt=drive
    libr=lib1 device=/clustera-02/rst1l
  4. Configure a Tivoli Storage Manager policy so that you can manage NAS image backups. Follow the instructions in Configuring a Tivoli Storage Manager policy for NDMP operations.
  5. Check tapes into the library and label them.
    AIX operating systemsHP-UX operating systemsLinux operating systemsOracle Solaris operating systemsLabel the tape volumes by using the LABEL LIBVOLUME command. For example, to check in a tape volume that is named HR2015 to the scratch pool of a library that is named LIB1, issue the following Tivoli Storage Manager command:
    label libvolume lib1 hr2015 checkin=scratch
    Windows operating systemsLabel volumes by using the LABEL LIBVOLUME command and specifying the CHECKIN parameter. For example, to check in a tape volume that is named HR2015 to a private pool of a library that is named LIB1, issue the following Tivoli Storage Manager command:
    label libvolume lib1 hr2015 checkin=private

    For more information about checking tapes into libraries, see LABEL LIBVOLUME, DEFINE LIBRARY, and UPDATE LIBRARY.

  6. Optional: Identify the volumes in the cluster, and schedule backup operations for the volumes:
    1. On the NAS file server, identify the volumes in the cluster by using the following Data ONTAP command:
      volume show
    2. Schedule backup operations by following the instructions in Scheduling NDMP operations.

What to do next

To verify that volumes in the NetApp cluster are backed up, complete the following steps:
  1. On the Operations Center menu bar, click Clients.
  2. Double-click a NAS device client and click Volumes.
  3. To determine when the last full volume backup was completed, review the information in the Last Full column. To determine when the most recent differential backup was completed, review the information in the Last Differential column.

Optional: To set up copy storage pools for added data protection, configure the tape-to-tape function to back up data. For instructions, see Backing up data with the tape-to-tape function.

Optional: To move data from a previous tape technology to a new tape technology, configure the tape-to-tape copy function. For instructions, see Moving data with the tape-to-tape copy function.