HP XP RAID Manager Software - Manual (Page 192)

Recommended action Condition
Restart of HORCM is required if the storage system configuration is changed (e.g., microcode
exchange, cache memory install/uninstall). Maintenance
Continuous Access Synchronous only: In the case of an error (e.g., single error in cache
memory) which made the pair volume is accompanied by maintenance work, the
pairresync
or paircreate command cannot execute copy rejection.
Each Continuous Access Synchronous/Business Copy command is executed by issuing a
command to the command device. The Continuous Access Synchronous/Business Copy Command device
command is read or written from/into the specific block area of the command device.
Therefore, the command device cannot be used. In addition, this device must not belong
to an LVM volume group. For Windows systems, do not assign a drive letter to the command
device to prevent utilization by general users.
If the P-VOL and S-VOL are on the same server, alternate path from P-VOL to S-VOL cannot
be used. Use of SCSI alternate path to a volume pair is limited to among primary (secondary)
volumes. Alternate path using Path Manager (Safe Path) is limited to primary volumes. SCSI alternate path
restrictions
When executing horctakeover on a standby server manually, I/O on the active server
must be stopped. When the package software goes for a standby server a failover by HA
software, the HA software must guarantee an I/O insulation of the active server. horctakeover
(Swap-Takeover)
After a new system has been constructed, a failure to activate HORCM may occur due to
improper environment setting and/or configuration definition. Refer to the HORCM activation
log, and correct the setting(s). HORCM failure to activate
Refer to the command log file and HORCM log file to identify the cause of the error. If a
command terminates abnormally because of a remote server failure, recover the server Abnormal termination of
command
from the failure, then re-execute the command. If HORCM has shut down, restart HORCM.
If an unrecoverable error occurs, obtain the log files and contact HP Technical Support.
Continuous Access Synchronous only: If an error occurs in duplicated writing in paired
volumes (i.e., pair suspension), the server software using the volumes may detect the error Error in paired volume
operation
by means of the fence level of the paired volume. In such a case, check the error notification
command or syslog file to identify a failed paired volume.
The system administrator can confirm that duplicated writing in a paired volume is suspended
due to a failure and the system runs in regressed state using the error notification command
of the Continuous Access Synchronous. HORCM monitors failures in paired volumes at
regular intervals. When it detects a failure, it outputs it to the host’s syslog file. Thus, the
system administrator can detect the failure by checking the syslog file. Concerning the
operation of the RAID storage system, the failure can also be found on Remote Web Console
(or SVP) provided.
Issue the Continuous Access Synchronous commands manually to the identified failed paired
volume to try to recover it. If the secondary volume is proved to be the failed volume, issue
the pair resynchronization command to recover it. If the primary volume fails, delete the
paired volume (pair splitting simplex) and use the secondary volume as the substitute volume.
RAID Manager uses “/var/tmp” or “/usr/tmp” as the directory for the UNIX domain socket
for IPC (Inter Process Communication), and makes the directory and files as
“/var/tmp/.lcm*” in RAID Manager version 01-16-06 or before. About “/var(usr)/tmp”
directory
Caution: This “/var/tmp/.lcm*” should not be removed while HORCM is running.
On Red Hat Linux, Cron executes the following “/etc/cron.daily/tmpwatch” file as default:
----------------------------------------------
/usr/sbin/tmpwatch 240 /tmp
/usr/sbin/tmpwatch 720 /var/tmp
for d in /var/{cache/man,catman}/{cat?,X11R6/
cat?,local/cat?}; do
if [ -d "$d" ]; then
/usr/sbin/tmpwatch -f 720 $d
fi
done
----------------------------------------------
192 Troubleshooting