|Administrator activities for Tivoli Data Protection for NDMP include |managing: |
|You can update, query, rename, and remove NAS nodes. For example, |assume you have created a new policy domain named NASDOMAIN for NAS nodes and |you want to update a NAS node named NASNODE1 to include it in the new |domain. You might first query the node.
|query node nasnode1 type=nas
|Then you might change the domain of the node with the following |command:
|update node nasnode1 domain=nasdomain
|To rename the NAS node named NASNODE1 to NAS1 you must: |
|rename node nasnode1 nas1
|Attention: When defining a new data mover for a node that you |have renamed, ensure that the data mover name matches the new node name and |that the new data mover parameters are duplicates of the original data mover |parameters. Any mismatch between node names and data mover names or |between new data mover parameters and original data mover parameters can |prevent you from establishing a session with the NAS file server.
|To delete the NAS node, first delete any file spaces for the node. |Then delete any paths to the data mover before finally deleting the data |mover. Then you can enter the following command:
|remove node nas1
|You can update, query, and delete the data movers you define for NAS file |servers. For example, if you shut down a NAS file server for |maintenance, you might want to take the data mover offline. To do this, |first query your data movers to identify the data mover for the NAS file |server you want to maintain.
|query datamover nasnode1
|Then issue the following command to make the data mover offline:
|update datamover nasnode1 online=no
|To delete the data mover, you must first delete any path definitions in |which the data mover has been used as the source.
|delete datamover nasnode1
|Attention: If the data mover has a path to the library, and |you delete the data mover or make the data mover offline, you disable access |to the library.
|Managing tape libraries and drives used for NDMP operations is similar to |managing hardware used for traditional Tivoli Storage Manager |operations. One exception is that you may want to reallocate Tivoli |Storage Manager libraries and drives for NDMP operations.
|You can change a definition for a drive you are using for Tivoli Storage |Manager operations when you want to dedicate the drive to NDMP |operations. Remove server access by removing the device name from the |drive definition. To update the drive, you can issue the following |command:
|update drive naslib drive0 device=""
|Updating the drive with the DEVICE="" parameter removes any |existing device name specification for the drive. The Tivoli Storage |Manager server is then unable to access the drive. However, the drive |may be available for NDMP operations. See Step 6. Defining Tape Drives for NDMP Operations.
|You can query, update, and delete the paths between data movers and tape |libraries and drives. For more information, see Tivoli Storage |Manager for Windows Administrator's Reference.
|Attention: If you delete the path to a library or make the |path to a library offline, you disable access to the library.
|Managing device classes for tape libraries used with Tivoli Data Protection |for NDMP is essentially the same as managing device classes for other |devices. See Chapter 8, Defining Device Classes for information about updating device |classes.
|Managing storage pools for Tivoli Data Protection for NDMP backups is |different from managing storage pools containing media for traditional Tivoli |Storage Manager backups. You can query and update Tivoli Data |Protection for NDMP storage pools. You cannot update the DATAFORMAT |parameter.
|You cannot back up a storage pool that has a data format of |NETAPPDUMP.
|The following DEFINE STGPOOL and UPDATE STGPOOL parameters have no meaning |when working with Tivoli Data Protection for NDMP storage pools because |storage pool hierarchies, reclamation, and migration are not supported for |these storage pools: |
MAXSIZE
NEXTSTGPOOL
LOWMIG
HIGHMIG
MIGDELAY
MIGCONTINUE
RECLAIMSTGPOOL
OVFLOLOCATION |
|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.