Attach to the node on which the TSM server instance is currently
active.
| Attach to a third, non-clustered system on which an additional instance
of the TSM server is active.
|
This configuration allows high performance backup and restore.
However, it is not entirely automated. Operator intervention is
required to service a failover where repair delays take more than 2
days.
| This configuration may not be acceptable in installations with low
bandwidth communications between the servers in the cluster and the tape
device controller server.
|
Define enough disk-based data volume space to keep more than 2 days worth
of average data.
| Define enough disk-based data volume space to keep more than 2 days worth
of average data.
|
Set up a storage pool hierarchy so that data is migrated efficiently to
the tape device.
| Use the virtual volumes to enable migration of the data from the local
disk volumes to the tape device.
|
When a failover occurs, manually disconnect the tape device and reattach
it to the node on which the server was newly active.
| When a failover occurs, no operator intervention is required; the
newly active server continues to use the virtual volumes as before.
|