NOTE:
Clusters do not support a SCSI bus with shared tapes. To bring high availability also to Media Agents, the Fibre Channel technology can be used as an interface to the device. The device itself is not
This configuration allows the following features:
•Customizable automatic restart of backups in case of failover of the Cell Manager.
The Data Protector backup specifications can be configured to be restarted in case of failover of the Cell Manager. Restart parameters can be defined using the Data Protector GUI.
•System load control at failover.
Sophisticated control is provided to define Data Protector behavior at failover. A special command, omniclus, is provided for this purpose. The Cell Manager allows the administrator to define what should happen in such situations.
•If the backup is less important than the application that just switched to the backup system, Data Protector can abort the running sessions.
•If the backup is more important or it is just pending, Data Protector continues the sessions.
The following is the expected backup behavior under this configuration.
Table 5 Backup behavior
Condition
Failover before a backup starts
Failover of the application and the Cell Manager during backup activity (Cell Manager runs on the same node as the application).
Result
Successful backup
Filesystem/disk image backup The backup session fails. The completed objects from the session can be used for restore, the failed (running and pending) objects are backed up again by restarting the session automatically.
Application backup The backup session fails. The session is restarted automatically.
IMPORTANT
To restart the session, the appropriate Data Protector option must be selected. For information on defining all possible Data Protector actions in case of failover of the Cell Manager, see the online Help index: "cluster, managing backups".
90 | Planning your backup strategy |