NOTE:
The difference with the previous example is that each of the cluster nodes has a Data Protector Media Agent installed. Additionally, you need to use the Data Protector load balancing functionality. Include both devices in the backup specification. With load balancing set to min=1 and max=1, Data Protector will only use the first available device.
The following is the expected backup behavior under this configuration.
Table 4 Backup behavior
Condition | Result |
Failover of the node before a backup starts | Successful backup due to automatic device |
| switching (load balancing) |
Failover of the node during backup activity | 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 need to be |
| backed up again by restarting the session |
| manually. |
| Application backup: The backup session fails. |
| |
| The session needs to be restarted manually. |
IMPORTANT:
If a failover during backup activity occurs in such a configuration, the MA may not be able to properly abort the session. This results in the corruption of the medium.
Cell Manager installed in a cluster, devices connected to the cluster nodes
In the environment depicted below:
•The Cell Manager installed in a cluster.
With regard to the Data Protector application integrations, there are two possible ways of configuring Data Protector and an application in such a configuration:
•The Data Protector Cell Manager is configured to run (both during the normal operation and during the failover) on the same node as the application - the
Concepts guide | 87 |