IBM E16RMLL-I - Tivoli Storage Manager, Implementation Manual, Page: 496 / 828

466
IBM Tivoli Storage Manager Implementation Guide
SARAH Bkup \\sarah\c$ 1 DISKDIRS 2,714 0.75 0.75
SARAH Bkup SYSTEM 2 DISKDATA 1,810 242.84 242.84
OBJECT
Note that although Lochness appears to have more data for Sarah, we can see
that the extra data are in copy storage pools. The actual number of files and
directories, and the amount of data stored, is identical (including policy details).
After changing the destination server to Atlantic in Sarah’s dsm.opt file, the first
backup will only send its incremental (changed) files since the last backup
completed with Lochness.
The last step in the process is to delete the exported node from the originating
server (that is, delete Sarah from Lochness). Use
delete filespace to remove
Sarah’s data, then remove node once all the file spaces have been removed.
14.3.2 Moving a node’s metadata
There may be situations where you may require moving just a node’s metadata.
The metadata is all the details about the client node, but not the actual managed
data for that client. The command for this operation is shown in Example 14-12.
Note the parameter filedata=none.
Example 14-12 Exporting metadata only
tsm: ATLANTIC> export node paris domains=workstn filedata=none
toserver=lochness
ANR0609I EXPORT NODE started as process 888.
ANS8003I Process number 888 started.
After the export process, and changing the destination server in dsm.opt on
Paris, the node Paris will connect to Lochness exactly as it would after a full data
export. However, as there is no data on Lochness belonging to Paris, a complete
backup (initial incremental) will be performed.
14.4 Moving a node back to an originating server
Suppose that we exported the client Sarah from the server Lochness to Atlantic.
However, suppose also that we did not remove it, nor its managed backup data,
from Lochness. We then switched Sarah to do backups to Atlantic. Some time
passes, and we want to export Sarah back to the server Lochness, with all of the
data. Using the merge feature of the
export node
command, we can ensure that
the data originally on Lochness belonging to Sarah are brought up to date with