Microsoft Windows Server 2003 Cluster Server Integration

Tape Devices and Failover
Tape devices connected to cluster nodes and its loaded media require additional attention after
failover.
Note: If a failover during backup activity occurs, the Data Protector may not be able to properly abort
the session. Data may not be completely written which results in the corruption of the medium. It is
highly recommended to restart the belonging backup session.
Cluster Database Restore
Two major problems are known:
1. The restore session of the cluster database fails because the ASR process restarts the cluster
services during the session.
When DP starts the cluster database restore, it calls the belonging Windows API. The API stops the
cluster services and with it DP session connections, before the restore session has finished.
2. The cluster database restore of a clustered Cell Manager may result in a failover.
Note: Before starting the restore of a cluster database, you should stop the cluster service on all
inactive nodes.
It is planned to fix this problems in the future. Please check the latest release notes and patches.
ASR and Windows RSM
The Windows Removable Storage Manager (RSM) is activated during ASR.
RSM is a service used for managing removable media (such as tapes and discs) and storage devices
(libraries). With RSM and SAN shared libraries, there are known issues.
RSM automatically scans system buses after reboot to determine if there are any removable storage
devices available for Windows to manage. This can interrupt backup and restores by doing a poll of
connected devices causing a SCSI reset on shared buses.
Additionally, there is a conflict of ownership for the removable storage devices. If the RSM service is
running, it captures library devices and maps them to Windows. The devices will be no longer
available for Data Protector.
Note: The RSM service should be manually disabled after the ASR process has finished (after the final
reboot). A solution will be provided in the near future. Please check the latest AUTODR patch.
ASR and Local Tape Devices
If the Data Protector Cell Manager together with local tape devices is installed cluster-aware, the ASR
process cannot access the local tape devices by its virtual hostnames.
ASR enters the local restore mode, starts a device autoconfiguration and sets the tape device
hostname temporarily to “machinename”, which does not match the name as described in the SRD-file
“recovery.srd”. Change in the SRD-file the system name specified with “–mahost” file to
“machinename” in order to avoid the local restore mode.
Please check in the HP OpenView Storage Data Protector 5.5 Administrator’s Guide chapter
Advanced Recovery Tasks how to edit the SRD-file.
If the SRD-file is not changed, the autoconfiguration process will determine any available tape devices
and offer it to the disaster recovery wizard. The devices and their hardware paths are displayed. You
must insert a tape into the device and choose the correct path in the wizard. This can be quite
complicated if the library is SAN-attached and drives are multiple displayed. In this case, the latest
26