Failure Scenarios; Hp-Ux; Windows Server 2003; Hp-Ux Failure Scenarios - HP StorageWorks 6100 - Enterprise Virtual Array User Manual

Failure scenarios

HP-UX

Table 56 HP-UX failure scenarios.
Fault stimulus
Server failure (host power-cycled)
Switch failure (SAN switch disabled)
Controller failure
Controller restart
Server path failure
Storage path failure

Windows Server 2003

Table 57 Windows Server 2003 failure scenarios
Fault stimulus
Server failure (host power-cycled)
Switch failure (SAN switch disabled)
Controller failure
Controller restart
Server path failure
Storage path failure
202 Single Path Implementation
Failure effect
Extremely critical event on UNIX. Can cause loss of system disk.
Short term: Data transfer stops. Possible I/O errors.
Long term: Job hangs, cannot umount disk, fsck failed, disk
corrupted, need mkfs disk.
Short term: Data transfer stops. Possible I/O errors.
Long term: Job hangs, cannot umount disk, fsck failed, disk
corrupted, need mkfs disk.
Short term: Data transfer stops. Possible I/O errors.
Long term: Job hangs, cannot umount disk, fsck failed, disk
corrupted, need mkfs disk.
Short term: Data transfer stops. Possible I/O errors.
Long term: Job hangs, cannot umount disk, fsck failed, disk
corrupted, need mkfs disk.
Short term: Data transfer stops. Possible I/O errors.
Long term: Job hangs, replace cable, I/O continues. Without cable
replacement job must be aborted; disk seems error free.
Failure effect
OS runs a command called chkdsk when rebooting. Data lost, data
that finished copying survived.
Write delay, server hangs until I/O is cancelled or cold reboot.
Write delay, server hangs or reboots. One controller failed, other
controller and shelves critical, shelves offline. Volume not accessible.
Server cold reboot, data lost. Check disk when rebooting.
Controller momentarily in failed state, server keeps copying. All
data copied, no interruption. Event error warning error detected
during paging operation.
Write delay, volume inaccessible. Host hangs and restarts.
Write delay, volume disappears, server still running. When cables
plugged back in, controller recovers, server finds volume, data loss.