Tivoli Header

Administrator's Guide


Moving Data by Node

You can move data located in a sequential-access storage pool for one or more nodes, or a single node with selected file spaces. In contrast to previous sections that discuss moving volumes using the MOVE DATA command, for the following sections you need to use the MOVE NODEDATA command. For this command the data can be located on either a primary or copy storage pool. When the source storage pool is a primary pool, you can move data to other volumes within the same pool or to another primary pool. When the source storage pool is a copy pool, data can only be moved to other volumes within that pool.

Notes:

  1. You can only move data by node if the data resides in a storage pool whose data format is NATIVE or NONBLOCK.

  2. If you are moving files within the same storage pool, there must be volumes available that do not contain the data you are moving. That is, the server cannot use a destination volume containing data that will need to be moved.

Task Required Privilege Class
Move data by node System, unrestricted storage or restricted storage

Moving Data for All File Spaces for One or More Nodes

Moving data for all file spaces on one or more nodes is useful:

Note:
You should avoid movement of data into, out of, or within a storage pool while MOVE NODEDATA is concurrently processing data on the same storage pool.

To move all file spaces for a single node named ACCOUNTING where the data is in storage pool ACCTPOOL and the destination storage pool is BACKUPPOOL enter:

+--------------------------------------------------------------------------------+
|move nodedata accounting fromstgpool=acctpool tostgpool=backuppool              |
+--------------------------------------------------------------------------------+

Moving Data for Selected File Spaces for One Node

Moving data for selected file spaces for a single node is useful:

For example, consider moving data for a single node and restricting the data movement to files in a specific non-Unicode file space (for this example, \\eng\e$) as well as a specific Unicode file space (for this example, \\eng\d$ ). The node name owning the data is ENGINEERING and it currently has data stored in the ENGPOOL storage pool. After the move is complete, the data is located in the destination storage pool BACKUPPOOL. To move the data enter the following:

+--------------------------------------------------------------------------------+
|move nodedata engineering fromstgpool=engpool                                   |
| tostgpool=backuppool filespace=\\eng\e$ unifilespace=\\eng\d$                  |
+--------------------------------------------------------------------------------+

Another example is to move data for a single node named MARKETING from all primary sequential-access storage pools to a random-access storage pool named DISKPOOL. First obtain a list of storage pools that contain data for node MARKETING, issue either:

+--------------------------------------------------------------------------------+
|query occupancy marketing                                                       |
+--------------------------------------------------------------------------------+

or

+--------------------------------------------------------------------------------+
|SELECT * from OCCUPANCY where node_name='MARKETING';                            |
+--------------------------------------------------------------------------------+

For this example the list of resulting storage pool names all begin with the characters FALLPLAN. To move the data repeat the following command for every instance of FALLPLAN. The following example displays the command for FALLPLAN3:

+--------------------------------------------------------------------------------+
|move nodedata marketing fromstgpool=fallplan3                                   |
| tostgpool=diskpool                                                             |
+--------------------------------------------------------------------------------+

A final example shows moving both non-Unicode and Unicode file spaces for a node. For node NOAH move non-Unicode file space \\servtuc\d$ and Unicode file space \\tsmserv1\e$ that has a file space ID of 2 from sequential access storage pool TAPEPOOL to random access storage pool DISKPOOL.

+--------------------------------------------------------------------------------+
|move nodedata noah  fromstgpool=tapepool tostgpool=diskpool                     |
| filespace=\\servtuc\d$ fsid=2                                                  |
+--------------------------------------------------------------------------------+

Requesting Information about the Data Movement Process

To request information on the data movement process, enter:

query process

Figure 37 shows an example of the report that you receive about the data movement process.

Figure 37. Information on the Data Movement Process

+--------------------------------------------------------------------------------+
| Process     Process Description      Status                                    |
|  Number                                                                        |
|--------     --------------------     ------------------------------------------|
|       3     Move Node Data           Storage Pool 3590FC, Target Pool 3590FC Fi|
|                                       Moved: 0, Bytes Moved: 0, Unreadable Files|
|                                       Unreadable Bytes: 0. Current Physical Fil|
|                                       (bytes): 268,468,584                     |
|                                                                                |
|                                       Current input volume:                    |
|                                       DST308.                                  |
|                                                                                |
|                                       Current output volume:                   |
|                                       DST279.                                  |
|                                                                                |
+--------------------------------------------------------------------------------+

Preventing Incomplete MOVE NODEDATA Operations

There are various reasons why an incomplete MOVE NODEDATA operation can occur. The following are the most common reasons:


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