Microsoft Windows Server 2003 Cluster Server Integration

Load Balancing at Failover
If a failover causes a move of applications to that system where the Data Protector Cell Manager is
running, it can result in a very high load on that system. Therefore, it might be necessary to abort
running backup sessions in order to have enough system resources for the applications.
It is possible to:
• Abort all running backup sessions.
• Abort specific running backup sessions.
• Inhibit the Data Protector cluster Cell Manager for a specific timeframe.
The belonging feature is provided by the command line utility “omniclus.exe”.
Autoconfiguration of Backup Devices
The autoconfiguration wizard enables easy and automatic configuration of libraries in cluster
environments. The devices are configured as virtual and floating drives.
Floating drives are devices that are configured on a virtual host, using virtual hostnames. Floating
drives should be configured for the backup of cluster-aware applications. This ensures that no matter
on which node in the cluster the application is currently running, Data Protector always starts a media
agent on that same node.
Before executing Autoconfigure:
• Verify that drive hardware paths are identical on every node.
• Autoconfigure runs only on the active node without checking the inactive nodes. Therefore, drive
hardware paths are only determined on the active node.
During execution of Autoconfigure:
• Choose the appropriate virtual hostname.
• Select required devices.
• Enable option “Automatically discover changed SCSI address”, which could help in case of
changed backup device paths (this is a well known problem in Windows environments, which can
be detected by Data Protector).
After execution of Autoconfigure:
• A failover test is imperative for checking that all paths are matching.
11