Table of Contents
Advertisement
14.2.3 Exporting client node information to another server
When you issue the export node command, the server exports client node
definitions. Each client node definition includes:
User ID, password, and contact information
Name of the policy domain to which the client is assigned
File compression status
Whether the user has the authority to delete backed up or archived files from
server storage
Whether the client node ID is locked from server access
You can also specify whether to export file data. File data includes file space
definitions and authorization rules, as well as the file objects themselves. You
can export file data in any of the following groupings of files:
Active and inactive versions of backed up files, archive copies of files, and
space-managed files
Active versions of backed up files, archive copies of files, and
space-managed files
Active and inactive versions of backed up files
Active versions of backed up files
Archive copies of files
Space-managed files
Tip: When you specify a list of node names or node patterns, the server will
not report the node names or patterns that do not match any entries in the
database. Check the summary statistics in the activity log to verify that the
server exported all intended nodes.
Example 14-2 shows the export node process in preview mode.
Example 14-2 Exporting a node
tsm: ATLANTIC>export node paris filedata=all toserver=lochness
ANR0609I EXPORT NODE started as process 9.
ANS8003I Process number 9 started.
tsm: ATLANTIC>q pr
Process Process Description
Number
-------- -------------------- ----------------------------------------------
9 EXPORT NODE
Status
ANR0648I Have copied the following: 1 Nodes 1
Filespaces 3895 Backup Files 547429051 Bytes
Chapter 14. Advanced operations
457
Advertisement
Table of Contents
