HP P4000 9.0 HP StorageWorks P4000 SRA for VMware SRM User Guide - Page 9

Array and volume discovery, Volumes recognized by the HP StorageWorks P4000 SRA

Get HP P4000 PDF manuals and user guides View all HP P4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 9 highlights

Array and volume discovery SRM gets information from the HP StorageWorks P4000 SRA about what volumes are being replicated by the SAN/iQ software. SRM then compares that list to the volumes it recognizes in a VMware environment. For normal SRM operation, a replicated volume needs to have a Remote Copy schedule with completed remote copies at a different HP StorageWorks P4000 SAN Solution management group under a remote volume that is not mounted at the remote site. This is a standard HP StorageWorks P4000 SAN Solution Remote Copy configuration. For instructions on how to configure Remote Copy schedules, see the Remote Copy User Manual which is installed in the Documentation directory of the HP StorageWorks P4000 Centralized Management Console program. The same information is available from the online help in the HP StorageWorks P4000 Centralized Management Console. Volumes recognized by the HP StorageWorks P4000 SRA Volumes must be configured with scheduled remote snapshots or they will not be considered for SRM by the SRA. The HP StorageWorks P4000 SRA recognizes the scheduled remote snapshots as replicated LUNs for SRM to manage. Volumes that are being remote copied only manually are not updated consistently enough to be useful for disaster recovery and SRM. If a volume has scheduled remote snapshots, and you create an ad hoc manual remote snapshot of that volume, then the HP StorageWorks P4000 SRA will recognize the manual remote snapshot along with the scheduled remote snapshots. Such ad hoc remote snapshots may be useful to test failover with a more recent copy than the schedule has, or to push the latest updates to the remote site before a foreseeable disaster occurs. Volumes ignored by the HP StorageWorks P4000 SRA Remote snapshots within the same HP StorageWorks P4000 SAN Solution management group are ignored. These snapshots are not considered disaster recovery copies since they are usually created to clone a volume in the HP StorageWorks P4000 SAN Solution, and copies that reside on the same SAN are not useful for disaster recovery. Testing failover at the recovery site SRM performs test failovers at the recovery site when requested. When test failovers are requested, the HP StorageWorks P4000 SRA will perform the steps listed. 1. Select the replicated volumes. 2. Identify the latest complete Remote Copy snapshot. 3. Delete any temporary writable space on that snapshot to ensure an unedited snapshot is presented to ESX servers. 4. Configure authentication for ESX servers to directly mount snapshots. 5. When testing stops, to conserve space on the SAN, delete the temporary writable space that was used during the test. P4000 SRA for VMware SRM user guide 9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
Array and volume discovery
SRM gets information from the HP StorageWorks P4000 SRA about what volumes are being replicated
by the SAN/iQ software. SRM then compares that list to the volumes it recognizes in a VMware
environment.
For normal SRM operation, a replicated volume needs to have a Remote Copy schedule with completed
remote copies at a different HP StorageWorks P4000 SAN Solution management group under a
remote volume that is not mounted at the remote site. This is a standard HP StorageWorks P4000
SAN Solution Remote Copy configuration.
For instructions on how to configure Remote Copy schedules, see the
Remote Copy User Manual
which is installed in the Documentation directory of the HP StorageWorks P4000 Centralized
Management Console program. The same information is available from the online help in the HP
StorageWorks P4000 Centralized Management Console.
Volumes recognized by the HP StorageWorks P4000 SRA
Volumes must be configured with scheduled remote snapshots or they will not be considered for SRM
by the SRA. The HP StorageWorks P4000 SRA recognizes the scheduled remote snapshots as replicated
LUNs for SRM to manage. Volumes that are being remote copied only manually are not updated
consistently enough to be useful for disaster recovery and SRM.
If a volume has scheduled remote snapshots, and you create an ad hoc manual remote snapshot of
that volume, then the HP StorageWorks P4000 SRA will recognize the manual remote snapshot along
with the scheduled remote snapshots. Such ad hoc remote snapshots may be useful to test failover
with a more recent copy than the schedule has, or to push the latest updates to the remote site before
a foreseeable disaster occurs.
Volumes ignored by the HP StorageWorks P4000 SRA
Remote snapshots within the same HP StorageWorks P4000 SAN Solution management group are
ignored. These snapshots are not considered disaster recovery copies since they are usually created
to clone a volume in the HP StorageWorks P4000 SAN Solution, and copies that reside on the same
SAN are not useful for disaster recovery.
Testing failover at the recovery site
SRM performs test failovers at the recovery site when requested. When test failovers are requested,
the HP StorageWorks P4000 SRA will perform the steps listed.
1.
Select the replicated volumes.
2.
Identify the latest complete Remote Copy snapshot.
3.
Delete any temporary writable space on that snapshot to ensure an unedited snapshot is presented
to ESX servers.
4.
Configure authentication for ESX servers to directly mount snapshots.
5.
When testing stops, to conserve space on the SAN, delete the temporary writable space that
was used during the test.
P4000 SRA for VMware SRM user guide
9