Tivoli Header

Administrator's Guide


Data Format for Server-Free Data Movement

Data that is transferred using server-free data movement must be stored in a different format than the format that has traditionally been used for Tivoli Storage Manager. The new data format is called NONBLOCK and must be specified when you define a data mover for server-free data movement, and when you define a storage pool that is used for server-free data movement.

Data that has been backed up or archived using server-free data movement, and stored in a storage pool with a dataformat of NONBLOCK, can be moved to other storage pools. Likewise, you can also move an uncompressed image object backed up by a client from a traditional storage pool to a NONBLOCK storage pool and restore it using server-free.

Server operations such as migration, move data, and storage pool backup can cause this data to be stored in storage pools that do not have a data format of NONBLOCK. If this occurs, it is no longer possible to restore the data by using server-free. The data can still be restored over the LAN or by using LAN-free data movement. For more information, see Server-Free Data Movement.


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