Professional Documents
Culture Documents
Vmware Vcenter Site Recovery Manager 5.X With Emc VNX Arrays & Mirrorview
Vmware Vcenter Site Recovery Manager 5.X With Emc VNX Arrays & Mirrorview
By Dave O’Sullivan
David.C.OSullivan@emc.com
- VNX Block
- CLARIION Block
- Pre-requisites
- Design
- Test Failover / Failover / Recovery [DEMO]
- Required Logs
- Troubleshooting
- VM’s !
- vCenter
- MirrorView A and S
- VNX / CLARIION Arrays
- SRA (s) ???
- ensures the simplest and most reliable disaster protection for all
virtualized applications.
- Site Recovery plans can be tested non-disruptively as frequently as
required to ensure that they meet business objectives.
- At the time of a site failover or migration, Site Recovery Manager
automates both failover and failback processes, ensuring fast and
highly predictable recovery point objectives (RPOs) and
recovery time objectives (RTOs).
http://
communities.vmware.com/servlet/JiveServlet/download/11547-1-32136/Install%20%26%
20Configure%20SQL%20Express%20for%20use%20with%20SRM4%20v1.3.pdf
- ….
- Next
http
://www.vmware.com/resources/compatibility/search.php?deviceCategory
=sra
.
EMC CONFIDENTIAL—INTERNAL USE ONLY 17
SRA [Storage Replication Adapters]
- These are the most current supported EMC SRA’s
• SRM
• VNX
• ESX
- Watch out for messages like this, customers could open cases based
on these errors alone…
LVM: 8452:00:00 queried disk ID: <type 2, len 22, lun 11, devType 0, scsi 0, h(id) 14674641011867526612>
LVM: 8459:00:00 on-disk disk ID: <type 2, len 22, lun 1, devType 0, scsi 0, h(id) 15441737393007327004>
LVM: 8452:00:00 queried disk ID: <type 2, len 22, lun 11, devType 0, scsi 0, h(id) 14674641011867526612>
LVM: 8459:00:00 on-disk disk ID: <type 2, len 22, lun 1, devType 0, scsi 0, h(id) 15441737393007327004>
LVM: 8452:00:00 queried disk ID: <type 2, len 22, lun 11, devType 0, scsi 0, h(id) 14674641011867526612>
LVM: 8459:00:00 on-disk disk ID: <type 2, len 22, lun 1, devType 0, scsi 0, h(id) 15441737393007327004>
LVM: 8452:00:00 queried disk ID: <type 2, len 22, lun 11, devType 0, scsi 0, h(id) 14674641011867526612>
LVM: 8459:00:00 on-disk disk ID: <type 2, len 22, lun 1, devType 0, scsi 0, h(id) 15441737393007327004>
1. Power Off Test VMs at Success 2012-10-09 14:46:24 (UTC 0) 2012-10-09 14:46:30 (UTC 0)
Recovery Site
1.1.1. Power Off Success 2012-10-09 14:46:24 (UTC 0) 2012-10-09 14:46:25 (UTC 0)
1.1.2. Reset Storage Success 2012-10-09 14:46:30 (UTC 0) 2012-10-09 14:46:30 (UTC 0)
1.2.1. Power Off Success 2012-10-09 14:46:24 (UTC 0) 2012-10-09 14:46:27 (UTC 0)
1.2.2. Reset Storage Success 2012-10-09 14:46:30 (UTC 0) 2012-10-09 14:46:30 (UTC 0)
3. Discard Test Data and Success 2012-10-09 14:46:30 (UTC 0) 2012-10-09 14:47:25 (UTC 0)
Reset Storage
3.1. Protection Group test7 Success 2012-10-09 14:46:30 (UTC 0) 2012-10-09 14:47:25 (UTC 0)
- Watch out for messages like this, customers could open cases based
on these errors alone…
- http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1009253
In the left pane, click Recovery Plans and select the Recovery Plan which had the issue.
Select the Plan Name which is showing an Error in the Result column.
On the Plan Name with the error click the Export action to generate the report for the failed Test Failover
or actual Failover.
Save the file to your desktop and upload this file with the SRM system logs.
- 2012-09-02T09
- The SRA log folder will be loaded full of many logs so I’m just going to focus
on the logs form Sept 02 2012
- The above error was received when trying to do a Test Failover.
- We need to check in the following log:
- sra_testFailoverStart_09-02-2012_08-42-09.811.log
- com.emc.mirrorview.platform.naviseccli.NaviseccliConnection
- This will show the actual navi commands that are being issued by the
SRA to the SP
- Command result:
- Dave@QQWWQQWW /cygdrive/c/Users/Dave/Documents.backup/Logs/SRM_LOGS_PPTX/Pandora
- $ grep SnapCopy "TRiiAGE_full_SPlogs.txt“
• http://kb.vmware.com/selfservice/microsites/search.do?
cmd=displayKC&docType=kc&externalId=1009253
1. Collect Logs
2. Check MirrorView & confirm it is actually working.
3. Have customer reconfirm DNS & IP connectivity is OK
1. all hosts should be DNS resolvable on both sites
2. All hosts / SP’s should have IP connectivity on same VLAN, all hosts /
SP’s should be able to ping each other…
4. Confirm Software requirements listed on Slide 7
5. Check error that is reported in Recovery Plan Export Log.html
6. Search in TRiiAGE_full_Splogs for any errors at the time reported
on the Recovery Plan Export Log.html
Search the whole folder of SRA logs as you will get hits on different files depending on the issue you
are having.
It would seem form the above that Naviseccli is not installed properly on SRM
host, check path!
2012-08-29 12:20:32,823 [com.emc.mirrorview.platform.naviseccli.NaviseccliConnection]: 10.64.29.83 Executing command: mirror -sync -info -systems
2012-08-29 12:20:34,102 [com.emc.mirrorview.platform.naviseccli.NaviseccliConnection]: 10.64.29.83 Command result: stdout(Remote systems that can be enabled for mirroring:
Remote systems that are enabled for mirroring:
Array UID: 50:06:01:60:C7:20:0A:2D
Status: Enabled on both SPs), stderr()
2012-08-29 12:20:34,102 [com.emc.sra.response.ReplicatedDevicesBuilder]: Attempted discovery of peer array:50:06:01:60:C7:20:0A:2Dfailed.
2012-08-29 12:20:34,102 [com.emc.mirrorview.platform.mirror.MirrorServiceImpl]:
************* SYNC MIRRORS ***************
2012-08-29 12:20:34,102 [com.emc.mirrorview.platform.naviseccli.NaviseccliConnection]: 10.64.29.83 Executing command: mirror -sync -list
2012-08-29 12:20:35,381 [com.emc.mirrorview.platform.naviseccli.NaviseccliConnection]: 10.64.29.83 Command result: stdout(MirrorView Name: Mirror of dellpr710-c.w2k8.emcvmw.ctc Datastore_1
MirrorView Description:
MirrorView UID: 50:06:01:60:BE:A0:39:93:03:00:00:00:00:00:00:00
Logical Unit Numbers: 0
Remote Mirror Status: Mirrored
MirrorView State: Active
MirrorView Faulted: NO
MirrorView Transitioning: NO
Quiesce Threshold: 60
Minimum number of images required: 0
Image Size: 125829120
Image Count: 2
Write Intent Log Used: YES
Images:
Image UID: 50:06:01:60:BE:A0:39:93
Is Image Primary: YES
Logical Unit UID: 60:06:01:60:9D:A0:2E:00:52:49:31:9F:C9:D7:E1:11
Image Condition: Primary Image
Preferred SP: A
In the above example, I did not have the correct Snapview enabler installed on the VNX, there is a
new one for INYO.
Reference Slide 7
Both of the above errors were experienced when I did not have the Reserved Pool setup.
http://10.241.217.72/vmdecoder/index.php