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

Recovering from primary volume failure on the RCU, on the new Continuous Access Synchronous S-VOL

Page 56 highlights

7. If using RAID Manager and changing the Continuous Access Synchronous pair to a n ESAM pair, complete this step on the primary storage system. If using RWC, go directly to the RWC step. 1. Reverse the relationship of the pair by running the following RAID Manager command on the new Continuous Access Synchronous S-VOL: horctakeover 2. Split the Continuous Access Synchronous pair by running the following command: pairsplit-r 3. Change the Continuous Access Synchronous pair to an ESAM pair by running the following command: pairresync 8. If using RAID Manager to again create the ESAM pair, do the following: 1. On the secondary storage system, when the copy operation is completed, release the Continuous Access Synchronous pair by running the following command: pairsplit -S 2. On the primary storage system, perform a paircreate to create an ESAM pair. 9. If using RWC, do the following: 1. On the secondary storage system, when status is PAIR, release the Continuous Access Synchronous pair. 2. On the primary storage system, create the ESAM pair. 10. On both systems, make sure that Type shows ESAM. 11. Using multipath software, vary the owner path online. 12. Restart I/O. Recovering from primary volume failure on the RCU This failure occurs after automatic system failover switches host I/O to the primary volume on the RCU due to a failure of the primary volume on the primary storage system. Because both systems have volume failures, all host I/O stops. Recovering the volume from this failure involves releasing the pair, clearing the failure (and any failures on the primary storage system), recreating the pair, restoring the original relationship of the volumes, and restoring normal host I/O. NOTE: If the failed volume is an external volume, contact the HP Support Center for assistance clearing the failure. You use multipath software and RWC to complete this task. 1. Make sure that I/O is stopped. 2. Using multipath software, vary the non-owner path offline. 3. On the secondary storage system, release the ESAM pair by running the Pairsplit-S command on the P-VOL. 4. Clear the failure in the secondary storage system P-VOL. 5. If using RAID Manager, on the primary storage system, run the paircreate command to create the ESAM pair. 6. If using RWC, on the primary storage system use a Paircreate (ESAM) window to create the ESAM pair. 7. Clear any failures on the primary storage system so that it can accept I/O. 8. On the primary storage system, create the pair (Paircreate(ESAM)). 9. On both systems, make sure that Type shows ESAM. 10. Using multipath software, vary the owner and non-owner paths online. 11. Restart host I/O. 56 Disaster recovery

  • 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

7.
If using RAID Manager and changing the Continuous Access Synchronous pair to a n ESAM
pair, complete this step on the primary storage system. If using RWC, go directly to the RWC
step.
1.
Reverse the relationship of the pair by running the following RAID Manager command
on the new Continuous Access Synchronous S-VOL:
horctakeover
2.
Split the Continuous Access Synchronous pair by running the following command:
pairsplit-r
3.
Change the Continuous Access Synchronous pair to an ESAM pair by running the following
command:
pairresync
8.
If using RAID Manager to again create the ESAM pair, do the following:
1.
On the secondary storage system, when the copy operation is completed, release the
Continuous Access Synchronous pair by running the following command:
pairsplit -S
2.
On the primary storage system, perform a paircreate to create an ESAM pair.
9.
If using RWC, do the following:
1.
On the secondary storage system, when status is PAIR, release the Continuous Access
Synchronous pair.
2.
On the primary storage system, create the ESAM pair.
10. On both systems, make sure that
Type
shows
ESAM
.
11.
Using multipath software, vary the owner path online.
12.
Restart I/O.
Recovering from primary volume failure on the RCU
This failure occurs after automatic system failover switches host I/O to the primary volume on the
RCU due to a failure of the primary volume on the primary storage system. Because both systems
have volume failures, all host I/O stops. Recovering the volume from this failure involves releasing
the pair, clearing the failure (and any failures on the primary storage system), recreating the pair,
restoring the original relationship of the volumes, and restoring normal host I/O.
NOTE:
If the failed volume is an external volume, contact the HP Support Center for assistance
clearing the failure.
You use multipath software and RWC to complete this task.
1.
Make sure that I/O is stopped.
2.
Using multipath software, vary the non-owner path offline.
3.
On the secondary storage system, release the ESAM pair by running the
Pairsplit-S
command on the P-VOL.
4.
Clear the failure in the secondary storage system P-VOL.
5.
If using RAID Manager, on the primary storage system, run the
paircreate
command to
create the ESAM pair.
6.
If using RWC, on the primary storage system use a Paircreate (ESAM) window to create the
ESAM pair.
7.
Clear any failures on the primary storage system so that it can accept I/O.
8.
On the primary storage system, create the pair (Paircreate(ESAM)).
9.
On both systems, make sure that
Type
shows
ESAM
.
10. Using multipath software, vary the owner and non-owner paths online.
11.
Restart host I/O.
56
Disaster recovery