Tivoli Header

Administrator's Guide


Managing Tivoli Data Protection for NDMP

Administrator activities for Tivoli Data Protection for NDMP include managing:

Managing NAS File Server Nodes

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

Renaming a NAS Node

To rename a NAS node, you must also rename the corresponding NAS data mover; they must both must have the same name. For example, to rename NASNODE1 to NAS1 you must perform the following steps:

  1. Delete all paths between data mover NASNODE1 and libraries and between data mover NASNODE1 and drives. See Deleting Paths.
  2. Delete the data mover defined for the NAS node. See Managing Data Movers Used in NDMP Operations.
  3. To rename NASNODE1 to NAS1, issue the following command:
    rename node nasnode1 nas1
    
  4. Define the data mover using the new node name. In this example, you must define a new data mover named NAS1 with the same parameters used to define NASNODE1. See Step 4. Defining a Data Mover for the NAS File Server.

    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 a node name and a data mover name or between new data mover parameters and original data mover parameters can prevent you from establishing a session with the NAS file server.

  5. Define a path between the NAS data mover and a library only if the tape library is physically connected directly to the NAS file server. See Step 5. Defining a Path to a Library.
  6. Define paths between the NAS data mover and any drives used for NDMP operations. See Step 6. Defining Tape Drives and Paths for NDMP Operations.

Deleting a NAS Node

To delete the NAS node, first delete any file spaces for the node. Then delete any paths from the data mover before deleting the data mover. Then you can enter the following command:

remove node nas1

Managing Data Movers Used in NDMP Operations

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. Then issue the following command to delete the data mover:

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.

Dedicating a Tivoli Storage Manager Drive to NDMP Operations

If you are already using a drive for Tivoli Storage Manager operations, you can dedicate that drive to NDMP operations. Remove Tivoli Storage Manager server access by deleting the path definition with the following command:

delete path server1 nasdrive1 srctype=server desttype=drive library=naslib 

Managing Storage Pools Containing Tivoli Data Protection for NDMP Media

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 is used for NDMP backups.

The following DEFINE STGPOOL and UPDATE STGPOOL parameters are ignored for 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.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]