|Because Tivoli Data Protection for NDMP is a separately licensed product, |ensure that you register the license for the server before beginning the |configuration. See Licensing Tivoli Storage Manager.
|The following is a checklist to use for configuring Tivoli Data Protection |for NDMP: |
|Before setting up a tape library for NDMP operations, you should have |already determined whether you want to attach your library robotics control to |the Tivoli Storage Manager server or to the NAS file server. See Planning for Tape Libraries and Drives used in NDMP Operations .
|Connect the tape library robotics to the Tivoli Storage Manager server or |to the NAS file server. See the manufacturer documentation for |instructions. |
|Define the tape library to Tivoli Storage Manager based upon one of the |following configurations: |
|define library tsmlib libtype=scsi device=lb0.0.0.2
A DEVICE parameter is included in a library definition when the library
|robotics are connected to the Tivoli Storage Manager server.
|define library naslib libtype=scsi
No DEVICE parameter is included in a library definition when the library
|robotics are connected directly to the NAS file server. Instead, you
|include the DEVICE parameter when you define the path from the NAS data mover
|to the library (Step 5. Defining a Path Between a Data Mover and a Library Used for NDMP Operations).
||You must create a device class for NDMP operations. Specify the |following: |
|For example, to define a device class named NASCLASS with a library named |NASLIB, enter the following command:
|define devclass nasclass devtype=nas library=naslib mountretention=0 estcapacity=40g
|The storage pools you define for NDMP media are different from storage |pools you define for Tivoli Storage Manager media because they are defined |with different data formats. Tivoli Storage Manager operations use |storage pools defined with a NATIVE data format. NDMP operations |require storage pools with a data format that matches the NAS file server and |the backup method to be used. For example, to define a storage pool |named NASPOOL for a Network Appliance file server, enter the following |command:
|define stgpool naspool nasclass maxscratch=10 dataformat=netappdump
|Attention: Ensure that you do not accidentally use storage |pools that have been defined for NDMP operations in traditional Tivoli Storage |Manager operations. Be especially careful when assigning 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 will fail.
|Policy allows you to manage the number and retention time of NDMP image |backup versions. See Configuring Policy for Tivoli Data Protection for NDMP. |
|define domain nasdomain description='Policy domain for NAS file servers'
|define policyset nasdomain standard
|define mgmtclass nasdomain standard mc1
|assign defmgmtclass nasdomain standard mc1
|define copygroup nasdomain standard mc1 destination=naspool verexists=4
|Attention: Ensure that management classes used for NDMP |operations contain the name of a storage pool defined for NDMP |operations. Accidentally mixing storage pools used in NDMP operations |and those used in Tivoli Storage Manager operations will cause backups to |fail.
|activate policyset nasdomain standard
|The policy is ready to be used. Nodes are associated with Tivoli |Storage Manager policy when they are registered. For more information, |see Step 3. Registering NAS Nodes with the Tivoli Storage Manager Server. |
|When you use a client interface to initiate a backup, the policy is |affected by that client's own option file. To ensure that you |control the management classes that are applied to NDMP backups, you can use |client option sets. The option set can have an |include.fs.nas statement to specify the management |class for NAS file server backups. See Creating Client Option Sets from the Server for more information.
|Register the NAS file server as a Tivoli Storage Manager node. This |node name is used to track the image backups for the NAS file server. |For example, to register a NAS file server as a node named NASNODE1, with a |password of NASPWD1, in a policy domain named NASDOMAIN, enter the following |command:
|register node nasnode1 naspwd1 domain=nasdomain type=nas
|If you are using a client option set, specify the option set when you |register the node.
|You can verify that this node is registered by issuing the following |command:
|query node type=nas
|When you specify TYPE=NAS only NAS nodes are displayed.
|Define a data mover for each NAS file server in your Tivoli Data Protection |for NDMP environment. The data mover name must match the node name that |you specified when you registered the NAS file server to the Tivoli Storage |Manager server. For example, to define a data mover for a NAS file |server node named NASNODE1, enter the following command:
|define datamover nasnode1 type=nas hladdress=netapp2 lladdress=10000 userid=root |password=admin dataformat=netappdump |
|In this command: |
|For more information about the parameters, see Tivoli Storage Manager Data Movers and Paths Used with Tivoli Data Protection for NDMP.
|If you have defined the tape library with a DEVICE parameter (in Step 1, B. Define the Library for NDMP Operations), no path to the library is allowed.
|Define a path between the data mover and the library only if the library is |connected to the NAS file server. For example, to define a path between |a NAS data mover named NASNODE1 and a library named NASLIB, use the following |command:
|define path nasnode1 naslib srctype=datamover desttype=library device=mc0
|The value of the DEVICE parameter is the special file name for the tape |library as it is known to the NAS file server. See Obtaining Special File Names for Path Definitions.
|See Tivoli Storage Manager Data Movers and Paths Used with Tivoli Data Protection for NDMP for an overview of paths, as they are used in NDMP |operations.
|Define the tape drives that you want to use in NDMP operations.
|Depending on your hardware and network connections, you can use the drives |for only NDMP operations, or for both traditional Tivoli Storage Manager |operations and NDMP operations. For example, you have defined a library |named NASLIB and now want to define the drive with the name NASDRIVE1.
|To define the drive so that it can be used only for NDMP |operations, enter a command such as the following:
|define drive naslib nasdrive1 element=117
|No DEVICE parameter is specified for drives used only by the NAS file |server. Instead the DEVICE parameter is specified when you define a |path to a drive.
|To define the drive so that it can be used for both Tivoli Storage |Manager operations and NDMP operations, enter the following |command:
|define drive naslib nasdrive1 element=117 device=mt3.0.0.2
|The DEVICE parameter is specified for tape drive definitions when the |Tivoli Storage Manager server also accesses the drives.
|When you define SCSI drives to Tivoli Storage Manager, you must specify |element numbers for the drives when the library contains more than one |drive. Element numbers are available from device manufacturers. |Element numbers for tape drives are also available in the device support |information available on the Tivoli Web site at http://www.tivoli.com/support/storage_mgr/tivolimain.html.
|Define a path between the data mover and each drive that the data mover |will use. For example, to define a path between a NAS data mover named |NASNODE1 and a drive named DRIVE1 residing in a library named NASLIB, enter |the following command:
|define path nasnode1 drive1 srctype=datamover desttype=drive library=naslib device=rst1l
|The value of the DEVICE parameter is the special file name for the drive as |it is known to the NAS file server. To obtain the special file name, |see the following section.
|When you are creating paths, you must provide special file names for tape |libraries and drives. The value of the DEVICE parameter in the DEFINE |PATH command is the name by which the NAS file server knows a library or |drive. You can obtain these names, known as special file names, by |querying the NAS file server. For information about how to obtain names |for devices that are connected to a NAS file server, consult the product |information for the file server. For example, for a Network Appliance |file server, connect to the file server using telnet and issue the SYSCONFIG |command. To display the device names for tape libraries, use this |command:
|sysconfig -m
|To display the device names for tape drives, use this command:
|sysconfig -t
|You must label the tapes and check the tapes into the tape library. |These tasks are the same as for other libraries. See Labeling Media for more information.
|You can schedule the backup or restore of NDMP image backups by using |administrative schedules that process the BACKUP NODE or RESTORE NODE |administrative commands. The BACKUP NODE and RESTORE NODE commands can |be used only for nodes of TYPE=NAS. See Backing Up and Restoring NAS File Servers Using Tivoli Data Protection for NDMP for information about the commands.
|For example, to create an administrative schedule called NASSCHED to back |up all file systems for a node named NASNODE1, enter the following:
|define schedule nassched type=administrative cmd='backup node nasnode1' active=yes |starttime=20:00 period=1 perunits=days
|The schedule is active, and is set to run at 8:00 p.m. |every day. See Chapter 19, Automating Server Operations for more information.