HP Surestore E Disk Array XP256 HP XP P9000 External Storage Access Manager Us - Page 59

Recovery from power failure, primary storage system recovery, horctakeover, pairsplit

Page 59 highlights

5. Perform one of the following operations: • If using the RAID Manager to change the Continuous Access Synchronous pair to an ESAM pair on the primary storage system: Run the RAID Manager horctakeover command on the S-VOL. This reverses the relationship of the pair. • If using RAID Manager to create an ESAM pair again, on the primary storage system, run the pairsplit command on the S-VOL and release the Continuous Access Synchronous pair. 6. If using RWC, from the secondary storage system, release the Continuous Access Synchronous pair. 7. On the primary storage system, delete the quorum disk ID. If the quorum disk ID cannot be deleted due to a disk failure, forcibly delete the quorum disk. 8. On the secondary storage system, delete the quorum disk ID. 9. On both systems, run the Disconnect External Volumes command on the quorum disk. If the connection to the quorum disk cannot be released due to the failure of the quorum disk, skip the Disconnect External Volumes operation. 10. Replace the quorum disk. 11. On both systems, run the Reconnect External Volumes command on the quorum disk. 12. On both systems, add the quorum disk ID. 13. Perform one of the following operations: • If using RAID Manager and changing the Continuous Access Synchronous pair to an ESAM pair: On the primary storage system, split the Continuous Access Synchronous pair by running the pairsplit-r command. After the system splits the pair, run the pairresync command to change the Continuous Access Synchronous pair to an ESAM pair. • If using RAID Manager and creating the ESAM pair again: On the primary storage system, run the paircreate command to create the ESAM pair. • If using RWC: On the primary storage system, use the paircreate(ESAM) dialog box to create an ESAM pair. 14. On both the primary and secondary storage systems, make sure that Type shows ESAM. 15. Use the multipath software to vary the owner path online. 16. Restart I/O. Recovery from power failure You can recover the primary storage system or secondary storage system from power failures that cause the system's backup batteries to discharge and cause the loss of differential data. The recovery process varies depending on the type of system. • "primary storage system recovery" (page 59) • "Secondary system recovery" (page 61) primary storage system recovery There are two procedures you can use to recover the system following a power failure that results in the initialization of the system memory. Which task you use depends on whether or not host I/O updates have stopped. You must use the correct procedure to ensure the recovery is successful. The tasks are: • "Recovering the system when the RCU is receiving host I/O updates" (page 60). • "Recovering the system when host I/O updates have stopped" (page 60). Recovery from power failure 59

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95

5.
Perform one of the following operations:
If using the RAID Manager to change the Continuous Access Synchronous pair to an
ESAM pair on the primary storage system: Run the RAID Manager
horctakeover
command on the S-VOL. This reverses the relationship of the pair.
If using RAID Manager to create an ESAM pair again, on the primary storage system,
run the
pairsplit
command on the S-VOL and release the Continuous Access
Synchronous pair.
6.
If using RWC, from the secondary storage system, release the Continuous Access Synchronous
pair.
7.
On the primary storage system, delete the quorum disk ID.
If the quorum disk ID cannot be deleted due to a disk failure, forcibly delete the quorum disk.
8.
On the secondary storage system, delete the quorum disk ID.
9.
On both systems, run the
Disconnect External Volumes
command on the quorum disk.
If the connection to the quorum disk cannot be released due to the failure of the quorum disk,
skip the
Disconnect External Volumes
operation.
10. Replace the quorum disk.
11.
On both systems, run the
Reconnect External Volumes
command on the quorum disk.
12.
On both systems, add the quorum disk ID.
13.
Perform one of the following operations:
If using RAID Manager and changing the Continuous Access Synchronous pair to an
ESAM pair: On the primary storage system, split the Continuous Access Synchronous
pair by running the
pairsplit-r
command. After the system splits the pair, run the
pairresync
command to change the Continuous Access Synchronous pair to an ESAM
pair.
If using RAID Manager and creating the ESAM pair again: On the primary storage system,
run the
paircreate
command to create the ESAM pair.
If using RWC: On the primary storage system, use the
paircreate(ESAM)
dialog box to
create an ESAM pair.
14. On both the primary and secondary storage systems, make sure that
Type
shows
ESAM
.
15.
Use the multipath software to vary the owner path online.
16. Restart I/O.
Recovery from power failure
You can recover the primary storage system or secondary storage system from power failures that
cause the system’s backup batteries to discharge and cause the loss of differential data.
The recovery process varies depending on the type of system.
“primary storage system recovery” (page 59)
“Secondary system recovery” (page 61)
primary storage system recovery
There are two procedures you can use to recover the system following a power failure that results
in the initialization of the system memory. Which task you use depends on whether or not host I/O
updates have stopped. You must use the correct procedure to ensure the recovery is successful.
The tasks are:
“Recovering the system when the RCU is receiving host I/O updates” (page 60)
.
“Recovering the system when host I/O updates have stopped” (page 60)
.
Recovery from power failure
59