Configuring a tape library for NDMP operations

You can configure a tape library to back up a network-attached storage (NAS) device to tape.

Complete the following steps to set up tape libraries for NDMP operations:

1. Connect the library and drives to be used for NDMP operations.
   1. Connect the SCSI library. Before you set up a SCSI tape library for NDMP operations, determine whether you want to attach your library robotics control to the IBM Storage Protect server or to the NAS file server. See Tape libraries and drives for NDMP operations. Connect the SCSI tape library robotics to the IBM Storage Protect server or to the NAS file server. Refer to your device manufacturer documentation for instructions.

      If the library is connected to IBM Storage Protect, make a SCSI or Fibre Channel connection between the IBM Storage Protect server and the library robotics control port. Then, connect the NAS file server with the drives.

      If the library is connected to the NAS file server, make a SCSI or Fibre Channel connection between the NAS file server and the library robotics and drives.

   2. Connect the ACSLS Library. Connect the ACSLS tape library to the IBM Storage Protect server.
   3. Connect the 349X Library. Connect the 349X tape library to the IBM Storage Protect server.
2. Define the library for your library device by issuing the DEFINE LIBRARY command. The library must be a single device type, not a mixed device.
   Issue one of the following commands to define the library depending on the type of device that you are configuring:

   SCSI Library

   define library tsmlib libtype=scsi

   ACSLS Library

   define library acslib libtype=acsls acsid=1

   349X Library

   define library tsmlib libtype=349x

3. Define a device class for your NDMP device by issuing the DEFINE DEVCLASS command.
   Tip: A device class that is defined with a device type of NAS is not explicitly associated with a specific drive type, for example, LTO. However, the preferred practice is to define a separate device class for different drive types.

   In the DEFINE DEVCLASS command, use the following parameters and values:

   • Specify DEVTYPE=NAS.
   • Specify MOUNTRETENTION=0. It is required for NDMP operations.
   • Specify a value for the ESTCAPACITY parameter.
   For example, to define a device class that is named NASCLASS for a library that is named NASLIB with an estimated capacity is 40 GB for the media, issue the following command:

   define devclass nasclass devtype=nas library=naslib mountretention=0
    estcapacity=40g

4. Define a storage pool for NDMP media by issuing the DEFINE STGPOOL command. When NETAPPDUMP, CELERRADUMP, or NDMPDUMP is designated as the type of storage pool, managing the storage pools that are produced by NDMP operations is different from managing storage pools that contain media for traditional IBM Storage Protect backups. IBM Storage Protect operations use storage pools that are defined with a NATIVE or NONBLOCK data format. If you select NETAPPDUMP, CELERRADUMP, or NDMPDUMP, NDMP operations require storage pools with a data format that matches the NAS file server and the selected backup method. Maintaining separate storage pools for data from different NAS vendors is optimal, even though the data format for both is NDMPDUMP.
   For example, to define a storage pool that is named NDMPPOOL for a file server, which is not a NetApp or a Celerra file server, issue the following command:

   define stgpool ndmppool nasclass maxscratch=10 dataformat=ndmpdump 

   To define a storage pool that is named NASPOOL for a NetApp file server, issue the following command:

   define stgpool naspool nasclass maxscratch=10 dataformat=netappdump 

   To define a storage pool that is named CELERRAPOOL for an EMC Celerra file server, issue the following command:

   define stgpool celerrapool nasclass maxscratch=10 dataformat=celerradump 

   Attention: Ensure that you do not accidentally use storage pools that are defined for NDMP operations in traditional IBM Storage Protect operations. Be especially careful when you assign the storage pool name as the value for the DESTINATION parameter of the DEFINE COPYGROUP command. Unless the destination is a storage pool with the appropriate data format, the backup can fail.
5. Optional: Define a storage pool for a table of contents. If you plan to create a table of contents, you must also define a disk storage pool in which to store the table of contents. You must set up policy so that the IBM Storage Protect server stores the table of contents in a different storage pool from the one where the backup image is stored. The table of contents is treated like any other object in that storage pool.
   For example, to define a storage pool that is named TOCPOOL for a DISK device class, issue the following command:

   define stgpool tocpool disk 

   Then define volumes for the storage pool.

   For more information about defining volumes, see Configuring random access volumes on disk devices (version 7.1.1).

   For more information about defining volumes, see Configuring random access volumes on disk devices (version 7.1.1).

   For more information about configuring libraries, see Configuring libraries for use by a server.