LAN-free client-data backup: Scenario
Tape and file media to be used for client backup data is stored in a storage pool that uses a device that is shared on a SAN. A library manager sends the location to a storage agent. Backup data goes directly to the device over a SAN.
A typical scenario for LAN-free data movement consists of the following steps:
- The backup-archive client begins a backup operation. The server reports policy information to the client, including whether a destination is LAN-free. As the client assigns policy settings for files during backup processing, it sends the data, using LAN-free data movement, when the destination for that policy is LAN-free enabled.
A storage pool is a LAN-free destination when the storage pool uses a device that is shared on a SAN. That device must also have a defined path to the storage agent.
- The storage agent receives data for those files that are backed up by the client and assigned to policy settings that use a LAN-free enabled storage pool. The storage agent sends a request for a volume mount to the library manager server. In external libraries, the storage agent contacts the external library manager, using the path to the executable file.
- A request is made to the storage device to mount the appropriate media.
- The library manager notifies the storage agent of the location where the mounted media resides. In external libraries, the storage agent is informed of the device location by the external library manager.
- The client, by use of the storage agent, writes the backup data directly to the device over the SAN.
- The storage agent sends metadata information to the IBM Storage Protect server, and the server stores the information in its database.
Restriction: LAN-free data movement takes precedence over client-side data deduplication. If LAN-free data movement occurs during client-side data deduplication, client-side data deduplication is turned off, and a message is issued in the error log.