IBM E16RMLL-I - Tivoli Storage Manager, Implementation Manual

Page: 484 / 828

454
IBM Tivoli Storage Manager Implementation Guide
14.1 Exporting server to server
In this section we cover the facility to export and import data directly between
servers using TCP/IP.
Before Tivoli Storage Manager V5.2, you could export to media, physically move
the media onto another server, then import. Often, this tended to be problematic
and slow. With the new export function, you can export and import between
servers directly.
Here we review the export process, and later in the chapter we describe an
example scenario.
Tivoli Storage Manager server export and import processing supports the
following functions:
򐂰 Direct server export to server import via TCP/IP between two servers of the
same or differing platforms. Using the network eliminates the need for
compatible sequential device types between servers for data movement.
򐂰 Merging of imported data into existing client file spaces on the server.
򐂰 Ability to export client file data based on a date and time specification,
allowing maintenance of duplicate copies of client data on two or more
servers.
You can still use the previous version of the export and import commands,
specifying a sequential access deviceclass. For details, see the “EXPORT
NODE -- To Sequential Media” section of the chapter “Administrative
Commands” in the Administrator’s Reference for your server operating system
platform.
14.2 Exporting data directly to another server
You can export all server control information or a subset of server control
information when specifying one or more of the following
export commands:
򐂰 export admin
򐂰 export node
򐂰 export policy
򐂰 export server
When you export data to a target server, you must specify the server name that
will import the data.