VMware Communities : Thread List - Site Recovery Manager

VMware SRM 1.0 : failed to configure Array managers in SRM in secure mode.

justyouguess — Sat, 21 Nov 2009 03:39:41 GMT

In My VMware SRM setup. We are trying to do bidirectional SRM. Like Site I and SIte II will act as Protected and recovery site vice versa in failover. But it seems to me that when I keep my ESX Host which has solution enabler installed & windows SRM host which also has ENMC solution enabler installed ( Symclient). When I use non-secure mode to configure arraymanagers, I am able to add/configure array managers but when I chose secure mode it gives me error that Management system error while configuring array manager ( pls. see attached screenshot for details).

To change secure mode on ESX solution enabler host as well as windows Solution enbaler ( which I eventually installed on SRM host itself), I do as below.

On ESX solution enabler host: /var/symapi/config/options...changing secure mode to nonsecure and vice varsa.

On windows solution enabler host: C:\Program Files\EMC\SYMAPI\config\netcnfg ...changing secure mode to nonsecure and vice varsa.

But when I chose secure mode to configure array manager, it is giving me error as specified in screenshot, with non-secure mode. Array managers get configured.

Now I am confused what is wrong with secure mode in my setup ?

vCenter linkde mode and SRM problems

Witek Rolka — Tue, 17 Nov 2009 01:06:24 GMT

Hello

I'm in the process of deploying a vSphere environment with vCenter and SRM. I would like to utilize linked mode but am experiencing problems with SRM when it is enabled.

The problem that I'm having is when link mode is used between the production and DR vCenter servers, I experience communication and authentication issues between the two SRM sites.

When I try to configure Folder associations between the two sites, I get an login error into the DR vCenter through the SRM plugin, but the link mode between the two vCenter sites works fine. When I try to re-enter the DR site vCenter credentials after an authentication error occurs, i get repetitive authentication errors.

As soon as I disable linked mode between the vCenter servers, SRM work fine and I don't get any authentication or connection dropout problems.

It looks like there is a conflict with the credentials that are being used with vCenter linked mode and the SRM authentication. I have a dedicated AD account that is used for all vCenter functionality between the two sites.

Has anyone seen this before and is there a work around?

Kind regards
Witek

Question about SRM and vCenter

devnull1101 — Thu, 19 Nov 2009 23:07:07 GMT

My company is going to a VMware environment. We are looking at two different solutions from two different vendors. I'm getting conflicting information and need some help.

Vendor A assisted us with a virtualization assessment, and provided us with a solution for the vSphere Advanced acceleration kit for 6 sockets (VS4-ADV-AK-C), a copy of vCenter standard (for SRM site), and 4 SRM licenses (we're looking at 2 esx hosts at protected site and only doing srm one way). My understanding is this will allow for 2 esx hosts at protected site to allow one way failover to 1 esx host at DR site.

Vendor B: has suggested the same vSphere acceleration kit, and for SRM has suggested vCenter SRM v4 Acceleration Kit for vSphere
Advanced (VCSRM4AAK-C).

I've been told Vendor A's solution won't work but it looks like it will, so that is question #1. Is Vendor A's solution workable even if not best practice?

My main question however is the vSphere acceleration kit (VS4-ADV-AK-C) comes with vCenter Foundation. I can't find where I saw/read it but I was under the impression SRM required vCenter Standard (not Foundation) at both sites. Will SRM work with vCenter Foundation at one location and Standard at the other? If so which site (protected or DR) needs to have the vCenter Standard and which can use Foundation (if there's any difference). Or will we wind up having to purcase a vCenter Standard to replace the copy of Foundation in both Vendor's solutions?

Any input on this appreciated as I'm getting conflicting stories from both vendors..

VMware Site Recovery Manager Service will not start Error 1067

WAMTech — Wed, 18 Nov 2009 18:54:18 GMT

We have ESX 3.5 Update 4 and we are using SRM 1.01 Update 3.

For some reason after completly configuring SRM including the DR IP customizer I went on to create my Recovery plan and after that my SRM Service in the DR site does not want to start. There were a few things I noticed while finishing up the configuration. After running the DR IP Customizer script I checked the customization of some of the VMs and I noticed the customization for each VM was inserted correctly. After that I went ahead and ran through creating my recovery plan and after it finished I checked the customization section again and the customizations were gone. I can see them in the DR site VC but they are not associated with the correct VM as they were right after I ran the customizer script. Now I can't even start the SRM Service in the DR site.

Any help will be greatly appreciated.

vCenter configuration question

nbhms — Tue, 17 Nov 2009 19:03:44 GMT

I know you need two vCenters for SRM, one at the protected site and one at the recovery site. The question I have (and can't seem to find a clear answer to) is do these two vCenters need to be dedicated to SRM?

We currently have several clusters and stand-alone hosts in our current vCenter (no SRM). We would like to add a few new hosts protected by SRM . . . but the current hosts and clusters will not be part of SRM. Can the current vCenter server already in production be the "protected" site vCenter in addition to managing its current hosts and clusters that will not be protected by SRM? If a single vCenter server can manage both SRM and non-SRM hosts, do they need to be in separate "datacenters" within vCenter?

Thanks,

nbhms

SRM 4.0 and HP StorageWorks EVA Virtualization Adapter

esmarques — Wed, 28 Oct 2009 20:49:53 GMT

Hi, I installed SRM 4.0 and SRA StorageWorks EVA Virtualization Adapter for EVA 8xxx.

When i try to configure Array Manager in SRM, I receive the following error message "Failed to execute 'discoverarrays' command during SRA launch".

CA is working fine, and i tried to reinstall SRA but receive the same error message. The connection with command view is ok and the user used to login has the necessary privileges.

tks

Ernando

SRM Configuration

waydees — Tue, 17 Nov 2009 08:01:37 GMT

Hi Everyone,

I am new to this forum but hoping to get solutions of my issues. I am using VMware VSphere 4 with two sites, on for protection and the other for recovery. I have installed SRM on Sites for testing purpose.

I would like to know that I am not using any External storgae /Array like SAN or NAS and using the direct storage with ESX servers. When I am trying to setup tyhe Site Recovery I could not confiure Array becaue of the above reason.

When I try to create protection group, I couldnt do that as the create option is disabled

Therefore, When I create a recovery plan I couldnt find any protection group in the list.

The configuration I have made on Recovery sites are not reflected on Protection site and vice versa. while connection is configured successfully and showing connected.

I would appreciate if any of you can guide me in this regard ? as I am not sure whether I can use SRM with storage.

Regards
Waydees

SRM and Microsoft Clustering

sfortuna74 — Mon, 16 Nov 2009 21:47:57 GMT

Hello -

My team is in the midst of architecting a DR/Business Continuity solution for our organization, and the matter of VMs running Microsoft Clustering has come up. Could someone please tell me if SRM can successfully fail over virtual machines running Microsoft Clustering, specifically if the failover site is running a different ip scheme than the "production" datacenter?

Thanks very much for any help you can offer -

Steve

Running SRM with RecoverPoint Adapter when remote site is down

sunvmman — Fri, 13 Nov 2009 19:36:43 GMT

I have Prod and DR. If my prod servers and recoverpoint go down (power outage) , I run my recovery plan from DR.

Does anybody know what state my consistency groups will be on RecoverPoint.

The EMC adapter reverse replicates when it executes a failover. But when the Prod site is down what does it do.
I assume it puts it in direct access and stays there ?

would like someone who had this experience.

SRM 4 and ESX 3.5

Iwan Rahabok — Fri, 06 Nov 2009 13:10:24 GMT

Production Site: SRM 4, vCenter 4, ESX 3.5 U4. This is an existing setup, and we can't upgrade yet. Will do that after DR project.

DR Site: SRM 4, vCenter 4, ESX 4.0. This is a new setup, so we can implement vSphere.

I'v checked the official document on http://www.vmware.com/support/srm/srm_releasenotes_4_0.html#compatibility.

Both ESX versions are supported on the underlying FC array.

Any potential or known gotcha for doing the above combination?

Regards

How is SRM licensed?

JamesSykes — Fri, 13 Nov 2009 17:21:25 GMT

Just wondering how SRM is licensed. I can see it's per processor, does that mean every processor within both your primary/secondary sites needs to be licensed?

For example our existing site has 16 processors, we are setting up a secondary site with 8 processors. Do we need 24 SRM licenses?

SRA for IBM DS4000/DS5000 Not found in SRM 4 Downloads

XAAL — Wed, 11 Nov 2009 23:47:52 GMT

Hi,

anyone knows when it will available ?

thanks

SRM pairing

cef2lion — Fri, 06 Nov 2009 17:22:29 GMT

I have installed SRM into our Vsphere environment. I used credential authentication. SRM installed and started ok at both sites. I created a pairing between both sites. Each time I start VI and select SRM I get prompted for pairing credentials. I entered that information and the pairing switches to port 443. I have a case open with vmware on this issue. They looked at the logs and said the issue might be using FQDN and IP addresses on the SRM install. I uninstalled SRM and installed using just IP addresses for hosts. No luck. I uninstalled and used just FQDN. Same results. Waiting back to hear from support but wanted to put it out here as well.

Craig

SRM 4 and iSCSI connected volumes in Guest OS supported ?

vJerry — Tue, 20 Oct 2009 20:53:35 GMT

Hi there,

My customer wants to have volumes connected via the MS iSCSI initiator in the Guest OS, because of vss snaps etc. We using DELL EQL PS6000E and Host Intergration Tools of DELL.

Is this supported when we want to protect these VMs with SRM 4? I think the initiator config must be reconfigured at the recovery site also, with different target IP ?!

Hope there is an answer out there.

Thnx and greetings,

Jerry.

A Bunch of Useful SRM Links

Mike_Laverick — Fri, 29 Aug 2008 07:54:11 GMT

Like me you have probably found finding the storage vendors docs on SRM sometimes tricky to find. So I have been collecting and collating them...

Thanks to Lee Dilworth (Smoggy?) on the forums for handing me the EMC ones:

IF anyone here finds a doc which have found useful, please post it here:

LeftHand Networks SRA for VMware Site Recovery Manager
http://resources.lefthandnetworks.com/forms/VMware-LeftHand-SRA-Download

HP disaster tolerant solutions using Continuous Access for HP StorageWorks Enterprise Virtual Array in a VMware Infrastructure 3 environment
Document ID: 4AA1-0820ENW
http://h71028.www7.hp.com/ERC/downloads/4AA1-0820ENW.pdf

VMware Site Recovery Manager in a NetApp Environment
Document ID: TR-3671
http://media.netapp.com/documents/tr-3671.pdf

Disaster Recovery Using Dell Equallogic Ps Series Storage And VMware Site Recovery Manager
Document ID: TR1039
http://www.equallogic.com/uploadedFiles/Resources/Tech_Reports/TR1039-Dell-EqualLogic-PS-Series-SAN-and-VMware-SRM.pdf

Improving VMware Disaster Recovery with EMC RecoveryPoint
Document ID: H5582
http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/H5582-VMware_Site_Recovery_Manager_with_EMC_RecoverPoint_Implementation_Guide.pdf

Using EMC SRDF Adapter VMware Site Recovery Manager
Document ID: H5511
http://powerlink.emc.com/km/live1/en_US/Offering_Technical/White_Paper/H5511-using-emc-srdf-adapter-vmware-site-rcvry-mgr-wp.pdf

VMware Site Recovery Manager with EMC Celerra NS Series and Celerra Replicator Implementation Guide
Document ID: H5581
http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/H5581-VMware_Site_Recovery_Manager_with_EMC_Celerra_NS_Series_and_Celerra_Replicator_Implementation_Guide.pdf

VMware Site Recovery Manager with EMC CLARiiON CX3 and MirrorView Implementation Guide
http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/H5583-VMware_Site_Recovery_Manager_with_EMC_CLARiiON_CX3_and_MirrorViewS_Implementation_Guide.pdf
Document ID: H5583

Regards
Mike Laverick
RTFM Education
http://www.rtfm-ed.co.uk
Co-Author of the vi3book.com and author of a shortly to be released book on VMware's SRM

Error Creating Protection Groups: "Virtual machine could not be created on recovery site: Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other"

kweller — Mon, 08 Jun 2009 16:47:03 GMT

Thanks in advance for the help. I'm seeing the following message for each VM when trying to create a protection group: "Virtual machine could not be created on recovery site: Resource pool,
datastore and host specified for shadow virtual machine are not
compatible with each other" I have checked my inventory mappings and everything seems to be fine.

Environment: VC 2.5 / ESX 3.5U3 / SRM 1.0.1-128004

Note: My ESX hosts boot from SAN so from time to time the MAC address or the FC WWNs on the protected or recovery site will change. Should this matter?

SRM log excerpt below:

~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 verbose~~ Task created
~~2009-06-08 11:56:00.297 'SimpleTaskManager' 3336 verbose~~ Adding task com.vmware.vcDr.ReplicationGroup.AddVmTask-2
~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 info~~ State set to running
~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 verbose~~ Scheduling work item
~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 verbose~~ Task created
~~2009-06-08 11:56:00.297 'SimpleTaskManager' 3336 verbose~~ Adding task com.vmware.vcDr.ReplicationGroup.AddVmTask-3
~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 info~~ State set to running
~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 verbose~~ Scheduling work item
~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 verbose~~ Task created
~~2009-06-08 11:56:00.297 'SimpleTaskManager' 3336 verbose~~ Adding task com.vmware.vcDr.ReplicationGroup.AddVmTask-4
~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 info~~ State set to running
~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 verbose~~ Scheduling work item
~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3432 info~~ Running work method
~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3432 info~~ Work function yielded
~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 1064 info~~ Running work method
~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 1064 info~~ Work function yielded
~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3288 info~~ Running work method
~~2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3288 info~~ Work function yielded
~~2009-06-08 11:56:00.609 'PrimarySanProvider' 3448 trivia~~ 'Retrieved 4 properties of 1 objects of type 'vim.VirtualMachine'' took 0.046 seconds
~~2009-06-08 11:56:00.625 'PrimarySanProvider' 3448 trivia~~ 'Retrieved 1 properties of 1 objects of type 'vim.Datastore'' took 0.015 seconds
~~2009-06-08 11:56:00.625 'PrimarySanProvider' 3448 trivia~~ VM 'vm-181' has no snapshots
~~2009-06-08 11:56:00.625 'PrimarySanProvider' 3448 trivia~~ 'Retrieved 4 properties of 1 objects of type 'vim.VirtualMachine'' took 0 seconds
~~2009-06-08 11:56:00.625 'PrimarySanProvider' 3448 trivia~~ 'Retrieved 1 properties of 1 objects of type 'vim.Datastore'' took 0 seconds
~~2009-06-08 11:56:00.625 'PrimarySanProvider' 3448 trivia~~ VM 'vm-189' has no snapshots
~~2009-06-08 11:56:00.640 'PrimarySanProvider' 3448 trivia~~ 'Retrieved 4 properties of 1 objects of type 'vim.VirtualMachine'' took 0.015 seconds
~~2009-06-08 11:56:00.640 'PrimarySanProvider' 3448 trivia~~ 'Retrieved 1 properties of 1 objects of type 'vim.Datastore'' took 0 seconds
~~2009-06-08 11:56:00.640 'PrimarySanProvider' 3448 trivia~~ VM 'vm-652' has no snapshots
~~2009-06-08 11:56:00.640 'Replication' 3448 verbose~~ Protected VM 'vim.VirtualMachine:vm-181' device '4000' being mirrored
~~2009-06-08 11:56:00.640 'Replication' 3448 verbose~~ Protected VM 'vim.VirtualMachine:vm-181' device '2000' being mirrored
~~2009-06-08 11:56:00.656 'Replication' 3448 verbose~~ Protected VM 'vim.VirtualMachine:vm-189' device '4000' being mirrored
~~2009-06-08 11:56:00.656 'Replication' 3448 verbose~~ Protected VM 'vim.VirtualMachine:vm-189' device '2000' being mirrored
~~2009-06-08 11:56:00.656 'Replication' 3448 verbose~~ Protected VM 'vim.VirtualMachine:vm-652' device '4000' being mirrored
~~2009-06-08 11:56:00.656 'Replication' 3448 verbose~~ Protected VM 'vim.VirtualMachine:vm-652' device '2000' being mirrored
~~2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 verbose~~ Progress is unchanged
~~2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 verbose~~ Progress is unchanged
~~2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 verbose~~ Progress advanced to 90
~~2009-06-08 11:56:01.312 'Replication' 3480 verbose~~ Creation of shadow VM failed with error (dr.secondary.fault.WrongVmInventoryPlacement) {
1 dynamicType = <unset>,
1 resourcePool = 'vim.ResourcePool:resgroup-584',
1 datastore = 'vim.Datastore:datastore-625',
1 host = 'vim.HostSystem:host-585',
1 msg = "Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other."
1 }
~~2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 verbose~~ Error set to (dr.primary.fault.RemoteAddVmFault) {
1 dynamicType = <unset>,
1 remoteFault = (dr.secondary.fault.WrongVmInventoryPlacement) {
1 dynamicType = <unset>,
1 resourcePool = 'vim.ResourcePool:resgroup-584',
1 datastore = 'vim.Datastore:datastore-625',
1 host = 'vim.HostSystem:host-585',
1 msg = "Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other."
1 },
1 msg = ""
1 }
~~2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 info~~ State set to error
~~2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 verbose~~ Progress is unchanged
~~2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 verbose~~ Progress advanced to 90
~~2009-06-08 11:56:01.312 'Replication' 3480 verbose~~ Creation of shadow VM failed with error (dr.secondary.fault.WrongVmInventoryPlacement) {
1 dynamicType = <unset>,
1 resourcePool = 'vim.ResourcePool:resgroup-584',
1 datastore = 'vim.Datastore:datastore-625',
1 host = 'vim.HostSystem:host-585',
1 msg = "Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other."
1 }
~~2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 verbose~~ Error set to (dr.primary.fault.RemoteAddVmFault) {
1 dynamicType = <unset>,
1 remoteFault = (dr.secondary.fault.WrongVmInventoryPlacement) {
1 dynamicType = <unset>,
1 resourcePool = 'vim.ResourcePool:resgroup-584',
1 datastore = 'vim.Datastore:datastore-625',
1 host = 'vim.HostSystem:host-585',
1 msg = "Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other."
1 },
1 msg = ""
1 }
~~2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 info~~ State set to error
~~2009-06-08 11:56:01.531 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 1064 verbose~~ Progress advanced to 90
~~2009-06-08 11:56:01.531 'Replication' 1064 verbose~~ Creation of shadow VM failed with error (dr.secondary.fault.WrongVmInventoryPlacement) {
1 dynamicType = <unset>,
1 resourcePool = 'vim.ResourcePool:resgroup-584',
1 datastore = 'vim.Datastore:datastore-625',
1 host = 'vim.HostSystem:host-585',
1 msg = "Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other."
1 }
~~2009-06-08 11:56:01.531 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 1064 verbose~~ Error set to (dr.primary.fault.RemoteAddVmFault) {
1 dynamicType = <unset>,
1 remoteFault = (dr.secondary.fault.WrongVmInventoryPlacement) {
1 dynamicType = <unset>,
1 resourcePool = 'vim.ResourcePool:resgroup-584',
1 datastore = 'vim.Datastore:datastore-625',
1 host = 'vim.HostSystem:host-585',
1 msg = "Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other."
1 },
1 msg = ""
1 }
~~2009-06-08 11:56:01.531 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 1064 info~~ State set to error

Equallogic SRA discoverarrays error

jakejaya — Fri, 06 Nov 2009 14:35:45 GMT

Hi All,

I am installing a fresh install of vSphere/Site Recovery Manager w/ Dell Equallogic PS4000 SANs and am getting the following error when trying to add the SAN in the array manager screen

"Failed to authenticate with the array management system while executing 'discoverArrays' command."

Below is an excerpt of the logs at the time of the error.

0:17:32: ***** Dell EqualLogic SRA: Processing request discoverArrays *****
1 10:17:35: Connection to the server could not be established {ErrorLevel=4;Exception=rl.clbroker.RlError {Connection to the server could not be established;errorCode=0;};ExceptionType=5}
1 10:17:35: Failed to connect to the server xxx.xxx.xxx.xxx

1 10:17:35: Saving XML output in output file C:\DOCUME~1\xxx\LOCALS~1\Temp\vmware-xxx\dr-sanprovider220-0

~~2009-11-06 10:17:35.254 00220 info 'PrimarySanProvider'~~ discoverArrays exited with exit code 0
~~2009-11-06 10:17:35.254 00220 trivia 'PrimarySanProvider'~~ 'discoverArrays' returned <?xml version="1.0" encoding="ISO-8859-1"?>
1 <Response>
1 <ReturnCode>3</ReturnCode>
1 </Response>
~~2009-11-06 10:17:35.254 00220 info 'PrimarySanProvider'~~ Return code for discoverArrays: 3
~~2009-11-06 10:17:35.254 00220 error 'PrimarySanProvider'~~ The scripts returned an error, leaving the temporary file 'C:\DOCUME~1\xxx\LOCALS~1\Temp\vmware-xxx\dr-sanprovider220-0'
~~2009-11-06 10:17:35.254 00220 error 'PrimarySanProvider'~~ Invalid array management system credentials reported by the script
~~2009-11-06 10:17:35.254 00220 info 'ArrayManagerImpl.QueryInfoTask-Task'~~ Work function threw MethodFault: dr.san.fault.AuthenticationFault
~~2009-11-06 10:17:35.254 00220 info 'ArrayManagerImpl.QueryInfoTask-Task'~~ Fault:
1 (dr.san.fault.AuthenticationFault) {
1 dynamicType = <unset>,
1 faultCause = (vmodl.MethodFault) null,
1 command = "discoverArrays",
1 msg = "",
1 }
~~2009-11-06 10:17:35.254 00220 verbose 'PropertyProvider'~~ RecordOp ASSIGN: info.error, ArrayManagerImpl.QueryInfoTask-2
~~2009-11-06 10:17:35.254 00220 verbose 'ArrayManagerImpl.QueryInfoTask-Task'~~ Error set to (dr.san.fault.AuthenticationFault) {
1 dynamicType = <unset>,
1 faultCause = (vmodl.MethodFault) null,
1 command = "discoverArrays",
1 msg = "",
1 }

Any help would be greatly appreciated!

Jake

SRM 4.0 versus Symantec Pure Disk w/ VCB (or vSphere DR)

wallabyfan2 — Tue, 10 Nov 2009 08:54:53 GMT

Hello Community

Can anyone point me in the direction of resources which compare the advantages and disadvantages of VMware SRM 1.0/4.0 versus Symantec Pure Disk w/ VCB (or vSphere DR)?

I have a customer who is thinking of doing Symantec Pure Disk but I am encouraging not do based on the fact that SRM is an automated fail-over solution with granularity and ability to Test Recovery Plan.

What are the pros of Pure Disk? I'm not so sure Pure Disk will even scrape the surface of the functionality found in SRM.

Auto-Modify Virtual Machine Device Protection

ajames — Tue, 21 Jul 2009 17:41:58 GMT

Hi all,

I recently created my protection groups and configured protection for about 35 VMs. Ever since then, I get the task called "Auto-Modify Virtual Machine Device Protection" in vCenter every minute, relating to all the configured VMs. Is this normal behaviour?

Thanks

Adrian

Running recovery plan if Virtual Center on protected site is unavailable.

veli — Mon, 09 Nov 2009 10:08:33 GMT

I have SRM 1.0.1 and VC 2.5.0 both installed on virtual machine on protected host.

Question one is: Does recovery plan work normally when this protected host (and SRM and VC) is in down state?
Question two is: It is possible to run recovery plan automatically when protected host crashes or power off unexpectedly?

SRM 4 Failback

ServerMonkey — Tue, 03 Nov 2009 11:31:40 GMT

After having SRM 4 and RecoverPoint 3.2 up and running for a while now I decided to run a sample recovery plan to ensure everything was fine, the failover worked perfectly and only took a minute to run.

The problem is when I go to failback, its not working as I'd expect.

The first thing I did was confirm the host was up and running, then removed it from the protection group in production and removed the recovery plan that I used to run it.
I've logged into RecoverPoint admin to swap the replication around and I find that the system has done it for me, the diagram shows traffic flowing in the reverse direction already.

So at this point I've gone to reverse things and setup a protection group on the DR cluster so I can start the process of moving the system back onto the production array, the problem is I"m not able to click the create button as it's greyed out.

Doing a scan with the array manager results in the following warning "Unable to display datastore groups. Replicated devices could not be matched with datastores in the inventory" and not disks are listed.

Has anyone come across this problem before, any suggestions out there?

Thanks in advance.

Installation Error-Failed to create database tables

EddieH3 — Wed, 27 May 2009 22:59:36 GMT

During the installation of SRM, I receive the following error:

Failed to create database tables. Details: DB does not contain SRM schema: VdbError: Column name does not exist in table dr_product_info

The SRM documentation states the schema name must be the same as the DB user name which I have verified. Does anyone have a fix for this error?

Error running Recovery Plan - storage prep (IBM n / NetApp)

wackjunk — Wed, 12 Aug 2009 17:13:57 GMT

Hi, I'm getting an error when I try to test a recovery plan. I get it on any of the datastores I'm trying it on. It's an IBM n5200 (running NetApp OnTap). This worked at one point but there was a crash and after rebuild I get this error. What am I missing? Any help would be appreciated, thanks.

--2009-08-11 09:46:05.215 'SysCommandLineWin32' 3860 verbose-- Starting process: "C:
Program Files\\VMware
VMware Site Recovery Manager\\external\\perl-5.8.8\\bin
perl.exe" "C:/Program Files/VMware/VMware Site Recovery Manager/scripts/SAN/IBM_ONTAP/command.pl"
--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 info-- testFailover exited with exit code 0
--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 trivia-- testFailover's output:
<Response>
4 Starting script
4 Test-Failover-start
4 Collecting igroup information
4 skipping igroup since its ostype is not vmware
4 skipping igroup since its ostype is not vmware
4 skipping igroup since its ostype is not vmware
4 skipping igroup since its ostype is not vmware
4 skipping igroup since its ostype is not vmware
4 igroup DR_VMWARE has initiator 210000e08b9b300b and type FC
4 igroup DR_VMWARE has initiator 210000e08b9b1c0c and type FC
4 igroup DR_VMWARE has initiator 210000e08b9b330b and type FC
4 Checking existence of Lun /vol/SM_VMWARE_PROD2/Prod_VMFS2
4 Lun /vol/SM_VMWARE_PROD2/Prod_VMFS2 exists
4 Creating test Clone volume testfailoverClone_nss_v10745371_SM_VMWARE_PROD2
4 Mapping Lun /vol/testfailoverClone_nss_v10745371_SM_VMWARE_PROD2/Prod_VMFS2
4 No such LUN exists
4 Mapping Lun /vol/testfailoverClone_nss_v10745371_SM_VMWARE_PROD2/Prod_VMFS2 to DR_VMWARE failed
4 Test-Failover-start completed with errors
4 Generate EMS event in filer
4 Generating EMS event in filer succeeded
4 </Response>
--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 trivia-- 'testFailover' returned <?xml version="1.0" encoding="UTF-8"?>
4 <Response>
4 <ReturnCode>4</ReturnCode>
4 </Response>

--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 info-- Return code for testFailover: 4
--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 error-- The scripts returned an error, leaving the temporary file 'C:\WINDOWS\TEMP\vmware-SYSTEM\dr-sanprovider0'
--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 error-- Unknown error encountered by the script
--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 error-- No shadow LUNs found in testFailover/start output
--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 verbose-- Deleting lun snapshots

Error adding array manager - VSphere 4, SRM 4 and Dell Equallogic

maytrix — Fri, 06 Nov 2009 15:29:17 GMT

I've built a new 2003 VSphere 4 server and have installed SRM on it along with a Dell Equallogic SAN. I am at the point of configuring the array manager. After I enter in the information and click connect, I get the following error:

Error Occured: XML Document is Empty

I've tried running the setup again with the repair option and removed and re-added the SRA with no luck.

Any help is appreciated.

Issue with DNS_Update.cmd not deleting the A record

damianpb — Fri, 06 Nov 2009 17:33:53 GMT

I have configured the servers with the necessary tools. I have written a batch file with call to the cmd and all the necessary switches. When you run the batch file it executes the dns_update command. As you watch it the syntax reports that the A record is deleted and then added and the command completes successfully. However, when you go check the forward lookup zone in DNS the old A record remains while the new a record has been added as well as the reverse lookup. Not sure why it tells me the old record has been deleted when it hasn't. Has anyone seen this issue?

SRM and HP XP20000 Array

Icoda - DC — Mon, 08 Dec 2008 09:56:10 GMT

Hi i found this document from HP,

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=120&prodSeriesId=499896&prodTypeId=18964&objectID=c01493767

However the XP range of storage is not mentioned. Can anyway tell me whether it is a supported SAN solution when deploying SRM?

TIA,

what's TCP port for SRM connect to EMC Celerra ?

chaoyuan — Fri, 06 Nov 2009 10:05:04 GMT

Dear All,

Could you help to point out which ports need to open throught firewall?

I guest following direction need to define:

1. (VC+SRM) ---> local site Celeraa

2. (VC+SRM) ---> local ESX

3. remote (VC+SRM) --> remote ESX

4. remote (VC+SRM) --> local ESX

note: VC and SRM are the same computer

Thank you for any input

SRM Customization Specifications

rmagoon — Thu, 05 Nov 2009 05:51:22 GMT

I have a few questions regarding customization specifications for SRM. The documentation doesn't thoroughly address this subject. Based on the fragmented documentation, I can only gather that the recovery site customization specification is required and retains only the IP information. The rest of the fields are ignored (name, department, license key, etc). If the dr-ip-customizer tool is used to export a new customization specification on the recovery SRM server, the only fields specified are IP related fields. The rest of the fields within the customization specification would be missing. How can the mini setup wizard actually reconfigure the VM with those fields missing? Also, do the sysprep files need to be installed on the recovery vCenter server?

Thanks in advance.

Rick

How do customization specifications work in SRM?

rmagoon — Thu, 05 Nov 2009 16:47:16 GMT

We're trying to use the customization specifications to re-IP with SRM. I'm trying to get a clear understanding on what the process is for successful re-IP operations when SRM fails over to the recovery site. This particular environment doesn't use any customization specifications when deploying VMs. They utilize a custom Windows Server build ISO to deploy new VMs. If no customization specifications exist, and SRM only cares about the IP information when failing over, this is where my confusion lies. My understanding of sysprep (or the mini setup process) is that the answer file needs to have valid user, organization and license key to process without interuption. If SRM only cares about the new IP information, where are the other fields coming from if no customization specifications exist.

Thanks in advance,

Rick

Active Directory Domain Controller for SRM Test

ServerMonkey — Fri, 09 Oct 2009 04:00:42 GMT

Hi Group,

I'm sure this question has come up before but I haven't been able to find much discussion of it in the forums.

Basically I have created a new domain controller at the recovery site and am using standard Active Directory replication to keep this host up to date. To enable testing of systems in the SRM Recovery Plan I need a copy of this domain controller in the test network, obviously this will provide the test systems with a source of authentication, name resolution etc.

My first thought was to use a SRM command call-out to a powershell script, it would initiate a clone of the VM and then another script to seize the FSMO roles etc.

Not a bad idea but I was interested to hear what others in the group are doing to achieve similar results or if anyone had a better idea.

Thanks in advance.

SRM 4 and Equallogic SRA

cdickerson — Tue, 27 Oct 2009 17:27:08 GMT

So, confused on the SRA for the Equallogic. On the VMware site it lists an SRA for Equallogic to be used with SRM 4. But, the SRA is the old 1.0.1 version that was used with SRM 1. Dell doesn't list a SRA on their site. When I talk to Dell, they say they haven't released an SRA yet, that there is a bug with SRM 4 and they are waiting for it to be fixed. So, has anybody tried the 1.0.1 SRA with SRM 4, does it work? thanks

-Craig

dr ip customization

udaykumar-blr — Wed, 28 Oct 2009 03:19:44 GMT

has anyone tried using dr ip customizser to automate the MSCS cluster servers for a failover and attaching to create customizations for vms.

I have searched all over to automate IP and DNS mapping for Microsoft cluster VM servers where in, it has 2 or more NICS. however in vain. This did not work. Anyone has an idea?.

If anyone require a working script for Vms with one vNIC, i am happy to help and also setting up SRM with hp storage.

Test plans stops with "Array with key 'BB0050569F23260000-null' not found" error

asmolenko — Wed, 21 Oct 2009 18:06:56 GMT

Dear Gurus, I hope someone can help me with my issue.
My SRM 4.0 lab:

two vCenter v.4 servers + SRM 4.0 + EMC_Celerra_Replicator_SRA
two VSA Celerra with working replication
two ESXi 4 servers connected to the vCenter servers

When I'm trying to execute a Test recovery plan, I've got the error "Array with key 'BB0050569F23260000-null' not found".
I assume that is someting with recovery VSA, but can't move further, since I am beginner in storaging.
I have attached screenshot from "Configure Storage Arrays" diag box, maybe it will help.
Thanks in advance!

Automatic Failover

HamR — Thu, 15 Oct 2009 02:30:19 GMT

In a tightly controlled environment where very little changes - the Protection Groups are static and the single Recovery Plan is well-defined - is it possible to automatically execute the Recovery Plan if the appropriate instantiating conditions can be measured/quantified? With PowerShell for instance?

I know there are risks with this approach and the Business Vs Technical war to define and meet RTOs will be waged in due course.

I'm just interested to know if it's possible and how it might be achieved. Incidentally, a virtualized storage layer is not an option.

TIA,

HamR.

SRM Database Install Error

MicahelMenne — Tue, 03 Nov 2009 15:31:36 GMT

Hopefully this will help soemone else until VMware releases and official one. I ran into several databse install problems when I tried to install vSRM 4 for the first time..

As I went through the install, I had all of my ODBC connections correct, all of my credentials were correct. As it was installing, I came up with this error during the install. I tried and tried and tried to get around it using new databases, re-installing ,changing the db username password, changing the ODBC driver . Nothing helped. If I tried to re-install without first deleting the databse, I got other database errors (Failed to Install Certificate was one of them).

I opened a case with VMware and finally got this response from them:

This error
occurs when the user who is connecting to the SRM database is not the owner of
the database.

As a
result, the user does not have the privileges to view some columns in the
table.

If you
change the owner of the database to the user that you are using to connect to
the SRM database,

then you
should be able to complete the installation.

After I changed the owner of the databse to the SQL user defined in my ODBC connection, everything went through smoothly.

how to change db owner:

1) make sure the specified user is not already assigned rights to the database (it will fail otherwise).

2) run this script:

Use VMvSRM
Go
EXEC sp_changedbowner 'vmservices'
Go
3) Install SRM

Voilla.. all is good to go (from a db perspective).

I asked them to file it as a bug, but they said they were not going to. They said engineering was aware of the issue and they would be releasing a KB article instead.

SRM 4 WSDL

dmedvitz — Tue, 03 Nov 2009 15:26:19 GMT

I've been attempting to use the WSDL that came with SRM4 to create some powershell scripts to automate recovery plan testing. When I use the standard MS tools to compile the .NET class, everything appears to work as expected. When I attempt to create an instance of the SrmBinding, however, it hangs forever. I've also attempted to import the wsdl file into a workflow app that I have with no success (it throws an invalid index error).

I created a .Net class with the old SRM WSDL file, and it works great, so far.

Has anyone had any luck with the WSDL from SRM4?

Thanks

Dave

HP EVA and VMware SRM 1.0 Update 1, Patch 4

wallabyfan2 — Fri, 30 Oct 2009 10:39:26 GMT

Quick Question:

If I create an HP EVA DR Group for CA Repilication and add multiple vDisk members, only one vDisk is detectable by the HP SRA via SRM in vCenter.

I've tried multiple times by deleting and re-creating, same error.

If I create multiple DR Groups for CA Replication, each vDisk added individually to each DR Group, all detected OK.

Odd.

SRM 4.0 on HDS9990 and VMs consistency

germoles — Mon, 26 Oct 2009 13:33:26 GMT

Hi all,

this post is an attempt to better understand the inner workings of SRM 4.0 with respect to VMs consistency (which is our main goal).

Our farm is going to be upgraded from ESX 3.5 Upd 3 to vSphere, and we do need to implement a DR solution which will be entirely based on an HDS9990 storage solution.

What is not clear to us is whether or not SRM 4.0 is ***THE*** best product we can integrate in our environment in order to guarantee VMs consistency or not.

From the SRM 4.0 documentation it seems that a SRM 4.0's based DR solution should suite our needs.

Our question are: does SRM always guarantee VMs consistency?

Does it only relies on HW-based storage replication mechanisms? What is the role of the storage vendor's Replication Adapters?

Wouldn't it be better to rely on a snapshot-based solution (i.e. one build on VMware Consolidated Backup technology), instead?

Thank you very much in advance for your help.

Best regards,

Salvatore

SRM 1.01 Licensing

bigtrev3 — Wed, 28 Oct 2009 11:03:44 GMT

Having been burnt by the licensing requirement for SRM that each protected host must have a license for each CPU socket the following questions come to mind

1. If you do not want/need to protect all of your hosts in a data center because only a subset of VMs need to be protected for DR how are the licenses allocated, particularly if you have multiple HA/DRS clusters.

2. What does the '*The SRM Feature: SRM_PROTECTED_HOST is overallocated by xx licenses*.' mean?

In our environment we have a cluster of 6 x 4 socket hosts which runs all of the 'protected' VMs - thus we purchased 24 x SRM 1CPU licenses (it seemed a bit expensive at the time). In addition there is a test cluster of 2 x 4 socket hosts and another 'high performance' cluster of 3 x 2 socket hosts. This adds up to 38 sockets.

Every 15 minutes we get the following *'The SRM Feature: SRM_PROTECTED_HOST is overallocated by 20 licenses*'

Does this mean we have purchased 20 too many SRM licenses?

The number of 20 is not the difference between the 24 sockets we have purchased and the 38 actually managed by this vCenter or License server. My theory is that since HA on the 'protected' cluster is indicating that all VMs could actually be run on a single 4 socket host (failover capacity is 5 in a six host cluster) then only four licenses are needed. This is even more complex than I had thought but implies that we could have bought SRM in 4 socket batches as the utilisation of the clusters increase.

BTW - The SRM failover cluster consists of 5 x 4 Socket Hosts to the same spec as the protected cluster.

vCenter Server Site Recovery Manager Licensing - Tricky Scenario

wallabyfan2 — Tue, 27 Oct 2009 20:54:18 GMT

Hello Community -

Currently on a site doing a SRM to protect Virtual Machines and Platespin Protect (from Portability Suite) protecting physical machines.

All has gone smoothly over the 2 days. Back tomorrow for final day. All is good but one fact.

The customer was advised to purchase 5 SRM (1-CPU) licenses only as there are only 9/10 Virtual Machines which will require fail-over from PROD site to DR site.

This makes IP customisation a simple with the new IP Customisation tool, but SRM licensing tricky.

In the past I've put SRM in 10-12 hosts clusters, licensing covered up to 24-CPUs since the each host was two socket, dual/quad core...simple right.

But this is different.

The Cluster is made up of 12 hosts, a majority are single socket, some dual socket. Total Virtual Machines is around 200. Only 10 of these virtual machines require protection services from SRM.

I have 5 licenses. Each VM has 1 vCPU.

How do I approach this scenario? Is there a way to tie SRM licensing to a single socket on a particular host? Is there a way to specify only some hosts get the protection and other do not?

Will we need to create a separate Cluster? Or maybe use DRS rules to prevent some Virtual Machines from moving between hosts.

This is helpful, but not the high-level organisational stance I'm looking for: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010979

The final solution might be to allocate 4-CPU SRM licenses to 2 Hosts with dual-sockets, then pick one of the single socket Hosts and allocate the remaining 1-CPU SRM licenses.

This would give greater coverage than the 10 Virtual Machines, not a problem.

The question then is: How to ensure these Virtual Machines will always live on these 3 ESX Hosts?

SRM for vSphere 4.0 and NetApp

theblackknight — Thu, 29 Oct 2009 23:11:44 GMT

Does anyone out there have SRM implemented in a ESX 4.0 and NetApp environment?

If so, how's it working?

Protection Group missing VMs

cswaters1 — Mon, 26 Oct 2009 05:37:38 GMT

Hi,
I've successfully completed a failover without any issues, I'm now at the point where I start the failback procedure.

I've unregistered the protected VMs at the old protection site,
I've removed the protection groups that have been implemented at the old protection site,
I've removed the placeholder VMs at the local non-replicated LUNs at the old recovery site,
I've reconfigured my array (CLARiiON with MirrorView/S),
I rescan the array and all disks are present and accounted for,
My Invetory Mappings are reversed,
I now come to create the protection groups, but some of the VMs are not listed in the datastore group, they're just missing...

Any suggestions??, I have about 2-3 VMs which are never visible when I create the protection group, they look fine, they are on the correct Datastores, they don't have any CD-ROMs attached, nothing is obviously wrong... I've tried rebooting/restarting the VC / SRM servers/services but no change.

Can anyone suggest a resolution?

Thanks,

Craig.

SRM with EMC Clariion & Mirrorview: Is EMC Snapview needed?

enetics — Fri, 30 Oct 2009 08:59:00 GMT

Hi,

I am new to SRM and trying to understand the setup of an SRM installation with EMC storage. I found the setup guide for SRM with EMC CX and Mirrorview at the viops.vmware.com - site. This document talks about the setup of Mirrorview and Snapview for the use with SRM.

Is the SnapView SW for the CXs mandatory needed? As I understand, SRM needs the snapshots for the test scenarios. Are they being used for other tasks (failover,...)?

Thanks for your replies.

EMC Symmetrix and SRM 1.0.1

neo_italy — Thu, 29 Oct 2009 10:17:12 GMT

Hi all,

scenario:

-DMX-4 on prymary site. DMX-4 on secondary site

-one lun (R1) replicated via srdf(to R2)

group created and assigned a BCV for the test on the replicated lun

mapped R2 and BCV to the hosts of secondary site

There is a differnce in our implementation from the symmetryx guide with srm, we have installed the symapi srver on the srm server that access directly the storage, but the esx luns are not even mapped to srm server, is right?

When i try a test i get the following error:

--2009-10-29 10:21:28.301 'SecondarySanProvider' 2832 verbose-- Adding mount path '/vmfs/volumes/4addb18a-084d4d28-73a6-001a64dcf548/' for datastore 'datastore-191' on host 'host-26'
--2009-10-29 10:21:28.301 'SecondarySanProvider' 2832 verbose-- Adding mount path '/vmfs/volumes/4ab102d0-14838020-9f2f-001a64dcf28a/' for datastore 'datastore-29' on host 'host-26'
--2009-10-29 10:21:28.301 'SecondarySanProvider' 2832 verbose-- Adding mount path '/vmfs/volumes/4ae95e06-c3994fc6-9650-001a64dcf288/' for datastore 'datastore-381' on host 'host-26'
--2009-10-29 10:21:28.317 'SecondarySanProvider' 2832 trivia-- 'Prepare VM 'shadow-vm-5182' for test' took 0 seconds
--2009-10-29 10:21:28.317 'SecondarySanProvider' 2832 warning-- Failed to prepare shadow vm for recovery: (dr.san.fault.RecoveredDatastoreNotFound)

Any help will be appreciated

Many Thanks

shadow datastore not found, while testing

neo_italy — Thu, 29 Oct 2009 16:02:08 GMT

Here it is the error:

~~2009-10-29 10:21:28.286 'SecondarySanProvider' 2832 warning~~ Shadow datastore for datastore 'sanfs://vmfs_uuid:4ae70694-5ce765e3-9ce0-001a64dcf0a8/' not found

and test stops with failure

What is the shadow datastore?

Thanks

vSRM VLAN consideration ?

Funtoosh — Wed, 01 Apr 2009 10:06:56 GMT

I am planning to start POC for vSRM using ESX3.5 U2. I have done demo and it went through but could not show all the functionality. Currently for POC purpose I need to design VLAN.

My question what kind of approach should I take for VLAN. Shall I use "streached VLAN's" as few/NetApp says or shall I re-ip those machine?

If someone can point me to understand from pros/cons as well as "How To" that would be great help.

Thanks

Funtoosh

Microsoft SQL Server and SRM

dbdave — Tue, 27 Oct 2009 14:15:06 GMT

Hello Group,

I've got a question regarding SQL Server, the server data files, and SRM. I'm new to vSphere however our hosting company Rackspace will be rolling out vSphere4 + SRM very soon. I'd like to virtualize my big sql servers, 300-400 GBs, but even Rackspace is not sure exactly how to spec out the hardware to accomodate this.

The main issue is to rely on SRM to move VMs from one data center to the other. Rackspace things they can use NetApp disk devices plus SRM to move these. Do you have any advice on this configuration? Will this work? Is there anything better to move large SQL Server VMs?

Thanks for any help,

David S.

London

Initial (and probably the most common) Disaster Recovery question about SRM and private networks

jnevans — Mon, 26 Oct 2009 15:33:05 GMT

Hi,

Can anyone share best practices from the field in regards to my network archiecture question:

As per the SRM admin guide: SRMs at both Protected and Recovery sites need access to the same private network (makes sense).

We will have both Protected and Recovery sites located on the same property but both are located away from each other on separate sides of the campus and there is network connectivity between the sites.

What are several ways we can get two separate sites to share a private network? What is the best practice?

1) Direct fiber cables between the sites using Layer 2 switches? Any potential problems with switching over a distance?

2) MPLS with Layer 2 VPN? Mature enough to handle the traffic and failover/failback scenarios?

3) Is there any SRM work around to make a Layer 3 routed solution possible?

Running a customized script in the VM after initial boot up

WAMTech — Tue, 27 Oct 2009 14:49:24 GMT

Hi all I am working with SRM 1.0.1 Update 3 with ESX 3.5 U4 and VC 2.5 U4. I have successfully configured SRM and ran a few test, now I want to try to see if I can run a few VBS scripts during the Post power on steps of the recovry process. There area a few application specific changes that must be done in order for our application to work on our DR environment. Basically I have a few websites that need a URL to point to a differnt server. I tried adding the script in the post power on steps but it failed. Iread somewhere and I can't find it again for the life of me, that the scripts on the Post Power On Stesps execute on the Virtual Center, but I want the scripts to run from each of the virtual manchines to make the appropriate change. Does anybody have any idea or recommendations?

Thanks in advance.

MSCS and SRM

nymike — Tue, 20 Oct 2009 17:06:42 GMT

Has anyone tried failing over a 2-node windows cluster using SRM? I tried searching but couldn't find anything that matched what I was looking for.. Thanks!

SRM + Virtualcenter

hardingp — Mon, 14 Jul 2008 16:43:34 GMT

It seems that SRM has around the same hardware requirements as the Virtual Center Server.

Is it ok to place these both on the same server. Has anyone tried this? Are there any implications involved?

SRM and Snapdrive (Netapp)

kboeckx — Wed, 19 Aug 2009 14:27:51 GMT

Hi,

When I want to run a recovery plan of a vmware machine that has a FCP RDM and snapdrive (netapp application to manage rdm's) installed on it, I've the problem that snapdrive has to be told to connect to the new virtual center server in the disaster site.

Has anyone experience with this issue.

Greetings,

Kris Boeckx
Pidpa

Installation failed on "Failed to install certificate"

asmolenko — Wed, 14 Oct 2009 10:54:05 GMT

Hi,

I am trying to install SRM 4.0 for evaluation purposes, but can't move further than installation of certificates.
The installer gives me the error box (see the screenshot in the attachment).

I use the Microsoft MSDE database default instance (VCENTER4\SQLEXP_VIM) as a target for the SRM's database.
It did work with SRM 1.0, but failing with SRM 4.0.

Where I am wrong? Please, help.

Andrey

Unable to generate .csv file with dr-ip-customizer tool

EddieH3 — Tue, 13 Oct 2009 16:39:42 GMT

Hello SRM experts,

I am having trouble generating the .csv file with the dr-ip-customizer tool. The error states that the host name used for the connection does not match the subject name on the host certificate. It then asks me if I trust the server and then prompts me to enter a username and password. We are using credential based certificates, so the same username and password that was used to setup srm and establish reciprocity is the same username and password that is entered at the prompt which ultimately fails.

The executable is run from the recovery site srm server. Below is the environment and attached is the output from the executable.

ESX 3.5 U4 and VC 2.5 U4 at each site. NetApp v6080 at protected site and FAS6080 at recovery site both running ontap 7.3.1.1P3. Using SRM 1.0.1 patch 4 with NetApp SRA 1.0.1.

Looking forward to your responses. Thanks.

SRM and EMC Mirrorview/S recovery plan failed

veli — Wed, 21 Oct 2009 19:56:46 GMT

Hello!

I have 2 servers, one with ESX 3.5 fU1 Foundation as protected site server and other ESX 3.5 U3 in evaluation mode on recovery site.

Clariion CX4-120 with FLARE 4.29 on both sites with fibre mirror conection enabled.

Virtual Center 2.5.0 (evaluation mode), SRM 1.0.1 (evaluation mode) and EMC MirrorView SRA 1.4.0.15 are installed on both servers.

I have virtual machine on Mirrorview/s replicated LUN and SRM connection, array managers, inventory mappings and protection group configured on protected site.

Recovery plan is configured on recovery site and when this plan is testing or running - error occured (error on picture and log attached).

Can you help me? May be some steps are missing.....hm....

SRM, EMC CLARiiON SRA Test Failover snapshots missing

cswaters1 — Mon, 19 Oct 2009 05:13:56 GMT

Hi,

I've set up a simple test environment with a single VM, datastore etc which worked fine, I'm now testing a failover with about 19 LUNs and about 50 VMs.

vCenter 1.01 patch 4
SRA Clariion v1.3.0.4
2 x VCs servers
2 x SQL servers
2 x CLARiiON SANs

Mirrorview configured and SANs replicated,
Snapview configured for each LUN with VMWARE_SRM_SNAP

Setup looks fine, My problem is that when I hit test, the storage gets mounted to my recovery site, but about 5 of the LUNs are missing...?

SRM conifiguration looks fine...

Any suggestions? I've uploaded the logs and look forward to your response.

Thanks,

Craig.

Update DB Credentials in SRM

BobbyTPI — Mon, 19 Oct 2009 02:12:52 GMT

Hi,

Can anyone tell me how to update the DB credentials for an SRM database? I had to move the SRM database to a new SQL Server, so I detached it from the old SQL server and attached it to the new server. I updated the DSN on the SRM server (not the same server as VC). But the SRM service fails to start and when I generate logs I get the following: (note the username should NOT be "vmware" anymore, and the DSN is updated and successfully connects)

Log for VMware Site Recovery Manager, pid=236, version=1.0.1, build=build-128004, option=Release, section=2
~~2009-10-19 12:03:57.790 'App' 3104 warning~~ Failed to create console writer
~~2009-10-19 12:03:57.790 'App' 1792 info~~ Set dump dir to 'C:\Documents and Settings\All Users\Application Data\VMware\VMware Site Recovery Manager\DumpFiles'
~~2009-10-19 12:03:57.790 'App' 1792 info~~ Intializing the DBManager
~~2009-10-19 12:03:57.962 'Vdb' 1792 error~~ Connection: Could not connect to database: -1
~~2009-10-19 12:03:57.962 'App' 1792 warning~~ DBManager error: Could not initialize Vdb connection: ODBC error: (28000) - Microsoft SQL Native Client SQL ServerLogin failed for user 'vmware'.
~~2009-10-19 12:03:57.962 'App' 1792 error~~ Application initialization error: Could not initialize Vdb connection: ODBC error: (28000) - Microsoft SQL Native Client SQL ServerLogin failed for user 'vmware'.
~~2009-10-19 12:03:57.962 'App' 3068 info~~ serviceWin32,414 vmware-dr service stopped

Can anyone help? Thanks.

'Auto' Network when testing

jftwp — Mon, 19 Oct 2009 18:26:39 GMT

We have finished our initial config/setup of SRM (1.0 U1) and we're almost ready to run our first test. On page 61 of the SRM Admin Guide, it states:

"Select the network to use during recovery plan tests, or select Auto to create an isolated network from the Test Network drop‐down menu. If the recovery plan includes virtual machines that run Linux and are DHCP clients, be sure that the test network includes a DHCP server. If your VI cluster at the recovery site uses VMware HA, you must create and use use a test VLAN that spans ESX hosts. HA clusters do not work correctly on other test network configurations."

My recovery site resources are indeed using HA. Does this mean I CANNOT use the 'Auto' network to create/use an isolated network for running RP tests? Why? The guide doesn't really elaborate any further about this.

If I do need to create my own isolated network, then I take it I just need to create a new vswitch (with no physical NICs in it) across all ESX hosts at my recovery site, and use that network instead of the built-in SRM 'Auto' network? Thanks for any clarification/explanation regarding this.

SRM Batch-IP Script is not populating the Custom Specification, suggestions.

CrisRobinson — Wed, 21 Oct 2009 15:41:53 GMT

All -

We have encountered an interesting issue with the custom ip batch program. Essentially we run the process, and the customer specification CSV looks good and when we browse the custom specifications they are there. We notice however when we look at the protection group and the specific VM the custom specification is empty. The enclosed screenshot shows the empty custom spec. If we Browse we see all the custom specs for all the VM's.

we have done this numerous times before at other customers without issue.

We are on SRM UPdate 1 patch 3 ( 1.0.1.2587)

Thanks

Cris

How do you test SRM?

BjornJohansson — Tue, 06 Oct 2009 16:41:21 GMT

Hello all!

I would like to know how you guys out there test DR plans with SRM. Of course, all runs their plans in test mode. But is this enough for your disaster recovery policy?

We are discussing a full fail over of all Protection Groups. Sounds a bit dramatic but we want to test the whole infrastructure at the DR site. There are some business critical systems that will be very hard to get into the testbubble network. We want to make sure that we are actually able to work on our DR-site if the poo hits the fan. We have SLA on one hour for some systems.

How do you test your recovery plans? How do you manage failback if you are doing a planned fail over?

Please post!

Cheers!

/Björn

HP SRA and EVA4400 firmware

BjornJohansson — Thu, 17 Sep 2009 09:20:07 GMT

Hi all!

Ok, we have two HP EVA4400, one at each site replicating with continous access. We also have ESX 3.5 on both sites so Site Recovery Manager was the obvious choice.

I read in HP Storage Replication Adapter (SRA) readme that only certain firmware and Command View Eva. We are running a higher version on our EVA4400 than supported and probably have a mandatory firmware upgrade coming up.

Would be hard to believe that all SRM customers are not upgrading EVA firmware because of SRA support. Especially on 4400 that has huge firmware issues (check fixes in latest firmware update readme)

Any word on this? Is it safe to upgrade firmware and command view eva? I rather run SRM with a unsupported (but working) configuration than my SAN on un-stable firmware...

Please advice.

Thanks!

/Björn

Devices supported
• HP StorageWorks 8100 EVA Storage System (Firmware XCS v.6.2xx, 6.110)
• HP StorageWorks 8000 EVA Storage System (Firmware XCS v.6.2xx, 6.110)
• HP StorageWorks 6100 EVA Storage System (Firmware XCS v.6.2xx, 6.110)
• HP StorageWorks 6000 EVA Storage System (Firmware XCS v.6.2xx, 6.110)
• HP StorageWorks 4400 EVA Storage System (Firmware XCS v.6.2xx, 6.110, v.9.0xx)
• HP StorageWorks 4100 EVA Storage System (Firmware XCS v.6.2xx, 6.110)
• HP StorageWorks 4000 EVA Storage System (Firmware XCS v.6.2xx, 6.110)

VMs with snapshots "not supported"?

jftwp — Fri, 16 Oct 2009 17:13:51 GMT

I've been sifting through my piles of product documentation, whitepapers, release notes and so forth to find exactly where I could have sworn I read something to this effect, but cannot. Is anyone aware of any limitation of VMs (on protected site) that have 1 or 2 snapshots within them, and having those snapshots within the recovery site as well?

We don't keep snapshots for more than a day or so as a good-little-admin best practice (delta files left alone for a while never a good thing). Just wondering about this----I SWEAR I read something, somewhere, about VMs (protected site) that have snapshots within, NOT being supported with SRM 1.x.

(We're about to configured the array managers, and before our first 'test' I wanted to tie up a few loose ends/questions and this is one of them --- my remaining questions are array vendor specific... thanks!)

SRA adapter for EMC recoverpoint SRM 4.0

sunvmman — Mon, 12 Oct 2009 17:12:55 GMT

I do not see the EMC recoverpoint SRA release for srm 4.0

anybody know when that will be released ?

Error: Failed to execute 'failover' command during SRA launch.

mircmm — Thu, 15 Oct 2009 14:27:32 GMT

Testing SRM, everything is installed in test enviroment on one location:

Config on protected and recovery site is:

1 x ESXi 4.0.0-164009

FalconStor NSS VA v.6.00 build 6086

vCenter Server 4.0.0.7797

Site Recovery Manager 4.0.0.3008

FalconStor SRA 1.10.111

One Protection Group on protected site, one Recovery Plan onrecovery site

When I Test the Recovery plan everything is OK, but when I Run it (the real failover) SRM reports

2. Prepare Storage	Error: Failed to execute 'failover' command during SRA launch.	00:00:03
2.1. Attach Disks for Protection Group "PG_falcon1"	Error: Failed to execute 'failover' command during SRA launch.	00:00:03

I searched for explanation but found nothing, any ideas anybody ?

Sincerely Mirc

inquiry about SRM Licensing

russ_givens — Wed, 16 Sep 2009 22:36:45 GMT

I'm looking at setting SRM up for our primary datacenter. Looking at some docs for SRM I see that you need to license each processor in the ESX host for SRM that will fail virtual machines over to a failover site. If I want those vm's to come back to the primary datacenter after the disaster has occurred and everything is back to normal do I need to license the ESX servers in the failover site for SRM also?

Where is the SRM 4 compatible SRA for Lefthand?

c_shanklin — Thu, 08 Oct 2009 03:44:31 GMT

There's no SRA listed for Lefthand on the SRM 4 download page, I'm guessing it's not supported yet, anyone know when that might become available? Or if older versions have any chance of working and where they might be found?

Thanks,

=====
Carter Shanklin
Read the PowerCLI Blog
Follow me on Twitter

Celerra replicator adapter version 1

zenariga — Wed, 14 Oct 2009 11:20:33 GMT

Hello,

I try to create a test environment using VMWare SRM but I have a VI3 environment. I can download the SRM 1.0.1 but I can't download the Celerra Replicator Adapter version 1. I try to use the version 4 but return a error.

Anyone have a Celerra Replicator Adapter version 1 to send me?

Thanks,

Compatibility between SRM1, SRM4, VC and ESX versions

frederic.bailly — Wed, 14 Oct 2009 07:33:10 GMT

Hello,

Is someone able to answer if we can mix ?

SRM1 server with SRM4 server (either source or destination for both)

VC2.5 with SRM4

ESX 3.x under VC4 with SRM4

Thanks

SRA/DSA for NetApp for SRM 4.0

jcw248 — Tue, 06 Oct 2009 15:28:55 GMT

Does anyone have any information on this? I have been searching all morning and cant find anything.

Creating vNIC with multiple IP addresses using DR-IP-CUSTOMIZER? Duplicate IP address error.

MatthewCEvans — Fri, 22 May 2009 22:08:01 GMT

We have one Windows 2003 server that has multiple IP addresses on a single vNIC that we are using with SRM. So far I'm not able to import the customization specification .CSV file with multiple IP addresses on a single NIC. Adding it with a single IP address and multiple DNS servers works, but multiple IP address does not work. Here's my .CSV file snippet:

VM ID,VM Name,Adapter ID,MAC Address,DNS Domain,Net BIOS,Primary WINS,Secondary WINS,IP Address,Subnet Mask,Gateway(s),DNS Server(s),DNS Suffix(es)
shadow-vm-5765,SERVER1,0,,,,,,,,,,
shadow-vm-5765,SERVER1,3,,domain.com,enableNetBIOS,10.30.2.13,10.30.2.10,10.30.2.13,255.255.255.0,10.30.2.1,10.30.2.13,
shadow-vm-5765,SERVER1,3,,,,,,10.30.2.25,255.255.255.0,10.30.2.1,10.30.2.10,
shadow-vm-5765,SERVER1,3,,,,,,10.30.2.26,255.255.255.0,10.30.2.1,,

Here's the tail end of the output of the command:

--2009-05-19 23:09:16.401 'drCustUtil' 8000 verbose-- Creating CsvAdapterMapping for Shadow VM with ID 'shadow-vm-5765'.
--2009-05-19 23:09:16.416 'drCustUtil' 8000 info-- DR Connection: Logging out session EBE4EF39-ADDE-4E87-8F97-89274DCDF5AA
--2009-05-19 23:09:16.447 'drCustUtil' 8000 info-- DR Connection: Logged out session EBE4EF39-ADDE-4E87-8F97-89274DCDF5AA
--2009-05-19 23:09:16.447 'drCustUtil' 8000 verbose-- VC Connection: Logging out session 81FC9109-AC97-4F7A-AE1B-E72BE380161F
--2009-05-19 23:09:16.479 'drCustUtil' 8000 verbose-- VC Connection: Logged out session 81FC9109-AC97-4F7A-AE1B-E72BE380161F
Error on line '4' for VM with ID 'shadow-vm-5765': Duplicate IP Address entry.

Should this work? Do I have something wrong in my .CSV syntax?

Matthew Evans
Kraft & Kennedy, Inc.
360 Lexington Ave.
New York, NY 10017
Direct: 212.692.5608
email: evans@kraftkennedy.com

"Message exceeds database maximum string length."

adublin — Tue, 13 Oct 2009 14:22:36 GMT

We're trying to run a test but keep running into this issue. The support person we spoke to said that there is something in our configuration/naming convention that is too long.

However; I found posts saying this error is harmless and not really the cause.

Any insight we be much appreciated.

Separate Databases for SRM?

OUHSC — Thu, 08 Oct 2009 15:41:37 GMT

With SRM 4.0 out now, we're moving forward with our install in our DR site but I was needing to clear some things up.

Do you need to have 4 separate DBs? (2 vCenter DB's, one for each vCenter and then 2 SRM databases, one for each site)?

I ask because our SQL 2008 server is clustered with servers here at the production site and the DR site already so we're not using any local DBs.

SRM fails to delete Snapshots at the conclusion of Testing a recovery plan

houghtonj — Mon, 12 Oct 2009 19:38:01 GMT

Environment is as follows:

HP EVA 4400 replicated to HP EVA 6100
ESX 3.5 U4
SRM 4.0

The production ESX environment is housed on the EVA4400 which is replicated to the 6100 via continuous access. All recovery plans (testing and execution) function as expected when moving from the 4400 to the 6100.

After performing the failover via SRM to the EVA6100, and all steps noted in the SRM Admin Guide were performed to prep for a failback using SRM to the EVA4400. The recovery plan tests executed without any problems, however if run a second time would fail. After looking at the EVA, it was apparent that SRM did not delete the snapshots which it created during the first test. The SRM logs indicated that it was successful however when looking at the EVA adapter log, and at the EVA itself, it was noted that the snapshot could not be deleted as the LUN was presented to a host.

As I mentioned, there were no issues with running the test plans going the other way and snapshots were created, presented, unpresented, and deleted without any problems by SRM. There isn't much to configuring the EVA adapter or SRM down to this detail so I'm not sure of where to go from here. I'm not an EVA expert but would assume that there may be a problem on the 4400 that is preventing the SRM XML scripts from completing, or perhaps there are are some incompatibilities between the scripts that SRM is using with the 4400?

Any ideas would be appreciated. Below is the excerpt from the hpsrmeva.log.

~~10/06/09 - 15:00:02~~ CHsvElementManager::GetApi:GetAPI indicates support for CV
~~10/06/09 - 15:00:02~~ CHsvElementManager::GetApi:In GetApi m_pCVApi is00858290
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendCommand:The retry count is set to 20
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:CVCReturnCode OF CVAPI_CommandEx is[0]
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:CVAPI_CommandEx returns success and response is valid
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:Response buffer received from CV: START
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:<?xml version="1.0" encoding="UTF-8"?><Envelope><Header><embuild>090413</embuild><emversion>9.00.01</emversion><platform>HBM</platform><version>8.00</version></Header><Body><NsaServerOperationResponse><object><objectid>08000710B4080560B7840E000060000000000300</objectid><objectname>EVA4400</objectname><objecttype>storagecell</objecttype><objectwwn>5001-4380-04C5-D600</objectwwn><objecthexuid>6005-08b4-000e-84b7-0000-6000-0003-0000</objecthexuid><uid>08000710B4080560B7840E000060000000000300</u
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:d><operationalstate>good</operationalstate><operationalstatedetail>initialized_ok</operationalstatedetail><licensestate>good</licensestate><comments/><hexuid>6005-08b4-000e-84b7-0000-6000-0003-0000</hexuid><objectparentuid>0000000000000000000000000000000000000000</objectparentuid><objectparenthexuid>0000-0000-0000-0000-0000-0000-0000-0000</objectparenthexuid><objectparentid>0000000000000000000000000000000000000000</objectparentid><controllertime><day>06</day><month>10</month><year>2009</year><ho
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:r>15</hour><minute>00</minute><second>01</second></controllertime><systemtype>HSV300</systemtype><totalstoragespace>18089.37</totalstoragespace><usedstoragespace>7769.28</usedstoragespace><availablestoragespace>10320.09</availablestoragespace><osunitid>0</osunitid><deviceadditionpolicy>manual</deviceadditionpolicy><volumereplacementdelay>60</volumereplacementdelay><firmwareversion>09501200</firmwareversion><nscfwversion>CR13DFlep-09501200</nscfwversion><basiclicensed>true</basiclicensed><drmlice
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:sed>true</drmlicensed><snaplicensed>true</snaplicensed><statestring>0,27,0,41,26,0,0,21,8,5,10,8</statestring><managementhostname>SMA</managementhostname><managementhostip>10.1.1.75</managementhostip><storagesystemcontrollercachememory>1787</storagesystemcontrollercachememory><storagesystemcontrollermemory>4096</storagesystemcontrollermemory><storagecellconnections><storagecell><objectid>08000710B40805604194060000C0000000000200</objectid><connectionstatus>good</connectionstatus><objecthex
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:id>6005-08b4-0006-9441-0000-c000-0002-0000</objecthexuid></storagecell></storagecellconnections></object><status><statuscode>0</statuscode><statusdescription>Command completed successfully.</statusdescription><nsatrace/><trace><entry>XMLInterfaceTransaction::Initialize(string) - XML string set.</entry><entry>NsaXMLInterface::ExecuteXMLCommand - XML validated.</entry><entry>NsaXMLInterface::ExecuteXMLCommand - Command built.</entry><entry>NsaXMLInterface::GetProperties - Object Properties fetched
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:</entry><entry>NsaXMLInterface::ExecuteXMLCommand - Bridge command executed.</entry></trace><statistics><totaltime>156</totaltime><parsetime>0</parsetime><bridgecommand>110</bridgecommand><buildresponse>0</buildresponse><commandmap>0</commandmap></statistics></status></NsaServerOperationResponse></Body></Envelope>
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:Response buffer received from CV: END
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendCommand:returned with statusCodehttp://0 - Command completed successfully.
~~10/06/09 - 15:00:02~~ CHsvStorageCell::UpdateStateRefreshTable:EVA4400: Current State 0,0,0,0,0,0,0,0,0,0,0,0
~~10/06/09 - 15:00:02~~ CHsvStorageCell::UpdateStateRefreshTable:EVA4400: New State 0,27,0,41,26,0,0,21,8,5,10,8
~~10/06/09 - 15:00:02~~ SrmTestFailoverStop::deleteOldSnapshots:Info: previously created SRM snapshot found
~~10/06/09 - 15:00:02~~ SrmTestFailoverStop::deleteOldSnapshots:Info: Snapshot belongs to input LUN \Virtual Disks\1\VMFS\ESX02
~~10/06/09 - 15:00:02~~ SrmTestFailoverStop::deleteOldSnapshots:Info: Deleting \Virtual Disks\1\VMFS\ESX02\HP_SRM_SNAP-LUN-06Oct09 14.55.56
~~10/06/09 - 15:00:02~~ CHsvElementManager::GetApi:GetAPI indicates support for CV
~~10/06/09 - 15:00:02~~ CHsvElementManager::GetApi:In GetApi m_pCVApi is00858290
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendCommand:The retry count is set to 20
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:CVCReturnCode OF CVAPI_CommandEx is[0]
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:CVAPI_CommandEx returns success and response is valid
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:Response buffer received from CV: START
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:<Envelope><Header><embuild>090413</embuild><emversion>9.00.01</emversion><platform>HBM</platform><version>8.00</version></Header><Body><NsaServerOperationResponse><status><statuscode>600019</statuscode><statusdescription>Error cannot delete object.</statusdescription><nsatrace><entry><statuscode>42</statuscode><statusdescription>Logical disk Presented</statusdescription></entry></nsatrace><trace><entry>XMLInterfaceTransaction::Initialize(string) - XML string set.</entry><entry>NsaXMLInterface::E
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:ecuteXMLCommand - XML validated.</entry><entry>NsaXMLInterface::ExecuteXMLCommand - Command built.</entry><entry>NsaXMLInterface::DeleteObject - Storage Object Broker delete object failed.</entry></trace><statistics><totaltime>31</totaltime><parsetime>0</parsetime><bridgecommand>31</bridgecommand><buildresponse>0</buildresponse><commandmap>0</commandmap></statistics></status></NsaServerOperationResponse></Body></Envelope>
~~10/06/09 - 15:00:02~~ CHsvCVClientAPI::SendAPICommand:Response buffer received from CV: END
~~10/06/09 - 15:00:02~~ CHsvVirtualDisk::Delete:returned StatusCodehttp://600019 - Error cannot delete object. -- NsaStatus42 - Logical disk Presented
~~10/06/09 - 15:00:02~~ SrmTestFailoverStop::deleteOldSnapshots:Error: Could not delete \Virtual Disks\1\VMFS\ESX02\HP_SRM_SNAP-LUN-06Oct09 14.55.56. Aborting testFailover operation

SRM License question

thomps01 — Thu, 11 Jun 2009 11:15:43 GMT

I have 3 x ESX hosts in my recovery site each with 4 CPU sockets (12 total). These all reside in the same cluster.

I have only purchased 8 SRM licenses as the resource requirements for the protected VM's is fairly low.

To ensure I'm within my license tollerance I am only presenting the replicated storage containing the protected VM's to 2 of the ESX hosts.

However, I see in the event log the following message:

"The SRM Feature SRM_PROTECTED_HOST is over allocated by 4 licenses"

So my question is: How does SRM know which ESX hosts to license within a cluster?

Newbie question: Do you have to have 2 vCenter servers for SRM?

AndyShine — Thu, 08 Oct 2009 12:46:17 GMT

We've been running ESX for a couple of years and have just started the process of implementing SRM.

I have one (virtual) vCenter server which manages both my production and DR datacenters. It usually runs on my Production cluster though can run on my DR cluster. It can manage all the ESX hosts and see all the iSCSI storage (ie both the production san and the DR san)

Do I have to have a second vCenter server to implement SRM?

The documentation seems to demand it

Thanks

Andrew

Clariion Consistency Group name - length limitations bug - See here for info

steve31783 — Mon, 05 Oct 2009 15:15:25 GMT

Test failover ran fine.. actual failover "failover of luns failed"..

Noticed in the logs that the name of the CG assigned seems to be cutoff...

1 002828 003828--10/05 10:48:10 327----Failover.cpp @000070 PromoteConsistancyGroups-- CG_for_LUN235_VM_SATA_30B_Mirro(Array:APM000) normal promote failed. Error Details: The Mirror Group name specified cannot be found

1 002828 003828--10/05 10:48:10 327----Failover.cpp @000075 PromoteConsistancyGroups-- Waiting for 50734 ms before another normal promote

1 002828 003828--10/05 10:49:01 063----Failover.cpp @000077 PromoteConsistancyGroups-- Trying another normal promote for Consistancy Group CG_for_LUN235_VM_SATA_30B_Mirro

Is this a function of logging, or is there a maximum # of characters for the name of the CG?

Will SRM 1.0.1 U1 support ESX4i?

vJerry — Wed, 07 Oct 2009 23:42:07 GMT

Hi There,

I wonder, will SRM 1.0.1 support ESX4 / vSphere ?

I must commit to this version because off the DELL SRA 1.0.1 is not supported by SRM 4 following the comp. matrix.

Please if anyone has some internal news, help me.

Greets Jerry.

SRM 4.0 and vCenter 4.0 Linked Mode

Erik Bussink — Wed, 07 Oct 2009 11:27:27 GMT

I checked the Release Notes and the documentation for SRM 4.0, but I can't seem to figure out if SRM 4.0 can work on vCenter 4.0 that are configured in a Linked Mode configuration.

Installing SRM 4.0 on each vCenter 4.0 should not be an issue, but having the VI Client get the SRM configuration from two or more Linked Mode vCenter might be an issue.

Error when recomputing datastore groups

NetJnkie — Mon, 05 Oct 2009 15:56:11 GMT

When vCenter/SRM tries to recompute the datastore groups it fails and SRM doesn't show any LUNs/datastores being replicated. We are using EMC RecoverPoint appliances for replication. Here is the error information from the SRM log:

~~2009-10-05 11:46:47.086 'SanConfigManager' 3756 trivia~~ 'Computed LUN groups for array 'array-7706' with ID 'RecoverPoint-Production'' took 1.765 seconds
~~2009-10-05 11:46:47.086 'com.vmware.vcDr.San.RecomputeLunGroups-Task' 3756 info~~ Work function threw std::exception: Not initialized
~~2009-10-05 11:46:47.086 'com.vmware.vcDr.San.RecomputeLunGroups-Task' 3756 info~~ Fault:
(dr.fault.InternalError) {
dynamicType = <unset>,
reason = "Not initialized",
msg = ""
}
~~2009-10-05 11:46:47.086 'com.vmware.vcDr.San.RecomputeLunGroups-Task' 3756 verbose~~ Error set to (dr.fault.InternalError) {
dynamicType = <unset>,
reason = "Not initialized",
msg = ""
}
~~2009-10-05 11:46:47.086 'com.vmware.vcDr.San.RecomputeLunGroups-Task' 3756 info~~ State set to error
~~2009-10-05 11:46:47.086 'SanConfigManager' 3756 trivia~~ No pending requests for lun groups computation
~~2009-10-05 11:47:15.195 'LocalSiteStatus' 3096 verbose~~ Free disk space: 1355 Mb
~~2009-10-05 11:47:15.195 'LocalSiteStatus' 3096 verbose~~ CPU usage: 21 %
~~2009-10-05 11:47:15.195 'LocalSiteStatus' 3096 verbose~~ Available memory: 156 Mb
~~2009-10-05 11:47:27.539 'SimpleTaskManager' 3920 verbose~~ Scanning for tasks to reap
~~2009-10-05 11:47:27.539 'SimpleTaskManager' 3920 verbose~~ Task com.vmware.vcDr.ServiceInstance.AddRemoteSite-2 marked as complete
~~2009-10-05 11:47:27.539 'SimpleTaskManager' 3920 verbose~~ Task Array.Synchronize-3 marked as complete
~~2009-10-05 11:47:27.539 'SimpleTaskManager' 3920 verbose~~ Task com.vmware.vcDr.San.RecomputeLunGroups-4 marked as complete

BMR from Physical to VM

Odurasler2 — Tue, 06 Oct 2009 17:35:28 GMT

Hello,

Not sure if i'm in the right community, but i wanted to see if anyone has successfully restored a physical machine that was backed up by Netbackup or Backup Exec to a newly created virtual machine? If so, what extra steps (if any) did you have to take to ensure the VM came up properly after the restore?

Many to one possible?

paulmack — Wed, 09 Sep 2009 12:46:24 GMT

Hi,

I've tried searching to find this info with no success. Is it possible using SRM to have multiple primary sites with multiple vcenters all failing over to one recovery site?

Cheers

Paul

SRM 4.0 Available for Download

hkrishnan — Tue, 06 Oct 2009 00:26:42 GMT

We are excited to announce general availability of SRM 4.0 today which includes vSphere 4.0 as well as NFS support. Thanks for your patience and support.

You can download SRM 4.0 from http://www.vmware.com/download/srm/

More information on release is available at

http://www.vmware.com/products/srm/resource.html

http://www.vmware.com/support/pubs/srm_pubs.html

Here are links to VMware blog posts on SRM 4.0 general availability, quick tour of new features as well as upgrading to SRM 4.0.

http://blogs.vmware.com/uptime/2009/10/srm-40-get-it-now.html

http://blogs.vmware.com/uptime/2009/10/a-quick-tour-of-srm-40.html

http://blogs.vmware.com/uptime/2009/10/srm-40-is-here-the-wait-for-vsphere-and-nfs-support-is-over.html

Site Recovery Manager's vSphere support

germoles — Mon, 28 Sep 2009 15:44:47 GMT

Hi all,

we currently host two ESX 3.5 Upd.3 production farms in one of our Company's site, and we are planning to build a new and much powerful vSphere 4 based farm. Finally, we'll upgrade the older two farms to the new product, too.

At the very end we'll also need to enable two of our production farms for Disaster Recovery with another remote Company's site (at one point this need will become bidirectional).

That's why we are trying to understand if the VMware vCenter Site Recovery Manager is the right product to suite our needs or not.

Unfortunately it seems that the vCenter SRM is not yet able to manage a vSphere 4 farm: does anybody precisely know anything sure about the release date for the new SRM version (vSphere enabled)?

And also, Am I wrong in suspecting that the fact that SRM's full name includes a reference to vCenter (vCenter SRM) may suggest that an upgrade from our current Virtual Center 2.5 Upd. 3 to the newer vCenter Server version would be forcibly required in order to install and use the SRM product even against an ESX 3.5 based farm?

Thank you very much for your help.

Best regards,

Salvatore

SRM vSphere support

gboskin — Wed, 06 May 2009 09:18:38 GMT

i recently read somewhere that the release of vSphere will of course be available with vCenter for basic management and automation tasks but the rest of VMware's great product suite is not supported in the initial release of vSphere.

So there won't be support for:

VMware vCenter Site Recovery Manager

Can someone please confirm when SRM will be supported by vSphere.

Will There Ever Be SRM for vSphere 4.0?

joeervolino — Wed, 16 Sep 2009 16:18:15 GMT

So.... Does anyone have a clue as to when there might be a new version of SRM? 2009? 2010? Ever?

NFS or ISCI for vSRM1.0.1

Funtoosh — Tue, 01 Sep 2009 13:16:41 GMT

I had a discussion last week along with VMware and Netapp representative. NetApp told me that there are some patch which will make SRM1.0.1 to support NFS.

My current customer is very much interested to go NFS route since someone from NetApp told him that you can have privilege of Data Deduplication.

I know that SRM V4 does support NFS but current VMware environment has not yet reached there yet.

Can someone share their experience implementing SRM with NFS?

What all advantage and disadvantage we will have if we implement SRM over NFS?

Which one is better NFS or ISCSI to implement SRM and why ?

This will help us to convince my current client with SRM. Network link is the major issue because of which my customer has chosen NFS as a mean for SRM but I really don't have much insight how. I read TR-3671 but it never talk about NFS/ISCSI . I am currently running POC for the same.

Protecting VMs with RDMs

EddieH3 — Fri, 02 Oct 2009 18:34:10 GMT

I've been reading through some of the older discussions about replicating and protecting RDMs and I haven't read any good news yet.

I have one volume on a v6080 cluster replicating with snapmirror to a fas6080 cluster. I have verified that the luns are replicated and are mapped to the recovery site esx hosts. I re-scanned on both sides and verified that the luns are presented through the VC on both sides. I have one VM with a VMFS lun and 3 RDM luns (RDMs were created with SnapDrive 6.0). When I go to configure protection for the VM, the VMFS lun state is "replicated" for the recovery location, but the 3 RDMs show as "not configured". My only 2 options are to detach (which won't allow me to recovery those RDMs) or to browse a datastore on the recovery site and locate a .vmdk, .dsk, or .raw which won't exist because the replicated luns are read-only. Right?

What am I missing? Has anyone had success replicating and failing over RDMs attached to a VM?

Looking forward to your responses. Thanks.

Eddie

SRA Adapter HP is compatible with SRM 4

PetervandenBosch — Mon, 05 Oct 2009 14:53:30 GMT

Hallo,

it is always a long search to find the right software in the HP site. I found the SRM 4.0 SRA Adapter withsome nice updates! Support for Command View EVA 9.1 so also the LUN shrinking possibility is available!

http://bit.ly/21uZdf

regards, Peter van den Bosch

Usefull? award me a few points

IPv6 and SRM

Timothy@Corismo — Mon, 05 Oct 2009 08:02:53 GMT

Hi all,

One of our customers is asking about ipv6 support in SRM. I couldn't find anything in the official guide nor unofficially (giyf). It also seems a problem in changing the ip on the fly cause you can add them in the customization specifications. So what are your thoughts?

Thanks in advance,

Timothy

Running scripts/commands on guests

luisarnauth — Mon, 28 Sep 2009 17:33:47 GMT

Hello all,

AFAIK the "Command Step" only runs at the SRM Server where the recovery plan is being executed. This commands (bat, cmd, vbs, ps1, whatever) are run in the context of the SRM service account, ie, LocalSystem.

By default, this account as no network access, so I asked:

How can I run some kind of script/command on the guest server?
Is it supported to change the SRM service account to a domain/local account?

Does anybody as a suggestion?

Thank you in advance,

Luis Arnauth

Email Alerts - anyone got it working?

Mike_Laverick — Mon, 01 Sep 2008 19:22:00 GMT

I've been trying to get email alerts working...

Tried in the Beta/RC nothing doing, and now I'm have little success with the GA...

THe alarm does work. I've configured it send out a MS net send message - which does get sent & recieved with the event (VM added)... also email for general VC alerts work as well. Tested with a power on/off email alert on a virtual machine - I recieve the email.

I've edited the extension.xml file to make sure to match the email address I use to send out my alerts...

How does SRM send out emails - does it use the general settings from VC - or does it have its own unique settings?

I've got alarms working for scripts and SNMP - but I've never seen a smtp delivered message...

Regards
Mike

SRA setup with multiple NetAPP filer FAS30XX

Funtoosh — Wed, 30 Sep 2009 17:38:48 GMT

We have tested SRM successfully between FAS3050 and FAS3070. Now we are into second phase and test the scenario where our VM's are spread across multiple volume and multiple filer (All NetApp FAS30XX). My queries is how can I setup replication with multiple filer to one filer? Because when we configure SRA adapter we provide source IP which is protected site filer and then recovery IP which is recovery site filer and then we are able to see replicated array. But in the situation where you have multiple source how can SRA will configured?

Thanks for your response

Connection Pair is grayed out

Funtoosh — Thu, 24 Sep 2009 11:02:14 GMT

We have renamed and re-ip our SRM box at recovery location. Now I am not able to break the pair and change the pair VC name. How to resolve this.