Hi,

We're going to put in a "active/active" SRM 5.1 deployment (half the protected VMs on each site - using the opposite site as their recovery site).

The vSphere 5.1 environment will be brand new too - so there is no SSO installed yet.

It seems that we need to use multisite SSO so that we can use "linked mode" vcenter servers with the C# client, and also add both vcenter servers to the Web Client environment. We don't want to have to authenticate to seperate vcenter servers for each site ;-)

Is anyone actually using multisite mode for SSO? I know you have to sync the SSO servers manually, but after initial configuration, nothing is really going to change with this. Also - it seems to me that the individual SSO servers are not even aware of each others existence - which makes the multisite environment not a whole lot different from a basic setup at each site. (functionally)

I know that a basic setup won't let me use linked mode for vcenter servers (with C# client) and I don't think you can add the "site B" vcenter server (with a basic SSO install) to the "site A" vcenter/sso server/web client enviornment.

So it sounds like multisite SSO is really the only option, when using multiple vcenter servers for SRM - and when a "single pane of glass" is required for managing the environment.

Does this sound right?

Hello,

Is it possible to test SRM recovery plan with vSphere replication (like Array based replication)  ?

If yes, How it works ?

The vsphere replication is automatically stopped, and after the VMs replicas are invertoried and the VMs started  or something else ?

Thanks for your answers

Regards

Philippe

Hi all

I am currently creating a protection group for SRM.

I have created a test cluster at our protected site which has 2 hosts, 1 datastore and a folder called Protected

I have then created a test cluster at our recover site which has 2 hosts, 1 datastore and folder called Recoverd

I have 3 test servers in the protected site and in the datastore and protected folder.

As far as I can see I have configured the folder mappings correctly, the recourses, placeholder datastores and network mappings on both sites.

When I create my protected group it comes back with the error againist each VM saying "Placeholder VM creation error: Unable to access file [SRM BAS Reocver Datastore01]"

Then on the vCentre at recovery site it says "unable to access file [SRM BAS Recover datastore01]

I have attached screenshots of the errors.

Can provide what extra information required.

Any help would be great.

Thanks!

Austin.

I have just discovered that you can only add steps to a recovery plan either in the recovery or test steps. The Add Step option is greyed out for both the reprotect and cleanup steps.

I want SRM to run powershell scripts to readd the NFS export back on our NetApp SAN and readd the datastores back onto the hosts of the protected site. This, logically, has to be done during the reprotect phase and not as part of the recovery phase especially if it is after an unplanned failover where the original protected site is not available at the recovery stage.

Does anyone know why this is or how you can get around it?

I'm attempting to test a recover plan. There is an issue with one of the vms on the datastore. It has a drive attached from a non replicated volume.

When I run the plan it logs the error below for all active steps after "Suspend Non-critical VMs at Recovery Site".

Error - Virtual machines "VM name" that
are not protected by this protection group use datastores "Volume Name"
that are in this protection group.

I understand that I can't protect that particular vm. The question is whether it will prevent other vms from being recovered or is something else going on?

Hi All

Production Site:

IBM Storwize V7000 and FW level: 6.4.1.4

SRM ver: VMware-srm-5.1.1-1082082

SRA : IBMSVCSRA_v2.2.0.130422

IP: 192.168.70.50

vCenter 5.1 U1

DR Site:

IBM Storwize V7000 and FW level: 6.4.1.4

SRM ver: VMware-srm-5.1.1-1082082

SRA : IBMSVCSRA_v2.2.0.130422

IP: 192.168.70.60

vCenter 5.1 U1

When I try to add array then this error occurred

SRA command 'discoverArrays' failed. Invalid Array ID.

Refer to IBM SAN Volume Controller troubleshooting

And SRM log is attached.

But I see this part of the logs.

Sorry for bad English.

-->   <Name>discoverArrays</Name>

-->   <OutputFile>C:\Windows\TEMP\vmware-SYSTEM\sra-output-12-119</OutputFile>

--> <StatusFile>C:\Windows\TEMP\vmware-SYSTEM\sra-status-13-225</StatusFile>

-->   <LogLevel>verbose</LogLevel>

-->   <LogDirectory>C:\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs\SRAs\IBMSVC</LogDirectory>

-->   <Connections>

-->     <Connection id="primary">

-->       <Addresses>

--> <Address id="spA">192.168.70.50:5989</Address>

--> <Address id="spB">192.168.70.60:5989</Address>

-->       </Addresses>

--> <Username>***</Username>

--> <Password>***</Password>

-->     </Connection>

-->   </Connections>

--> </Command>

2013-06-20T14:34:33.395+03:00 [02020 verbose 'SysCommandWin32' opID=258F28AC-0000001A] Starting process: "C:\Program Files\VMware\VMware vCenter Site Recovery Manager\external\perl-5.14.2\bin\perl.exe" "C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/IBMSVC/command.pl"

2013-06-20T14:34:33.395+03:00 [02020 verbose 'SraCommand' opID=258F28AC-0000001A] Resetting SRA command timeout to '300' seconds in the future

2013-06-20T14:34:33.395+03:00 [02020 verbose 'SraCommand' opID=258F28AC-0000001A] Listening for updates to file 'C:\Windows\TEMP\vmware-SYSTEM\sra-status-13-225'

2013-06-20T14:34:33.395+03:00 [02020 verbose 'PropertyProvider' opID=258F28AC-0000001A] RecordOp ASSIGN: info.progress, dr.storage.StorageManager.createArrayManager1

2013-06-20T14:34:33.441+03:00 [02444 verbose 'DrTask' opID=258F28AC-0000001A] Created VC task 'com.vmware.vcDr.dr.storage.StorageManager.createArrayManager:task-3901'

2013-06-20T14:34:34.065+03:00 [01496 info 'SraCommand' opID=258F28AC-0000001A] discoverArrays's stdout:

--> discoverArrays

--> Per Haz 20 14:34:33.909:[Info]Executing Module[ Constant ]Inatall Path: [C:\Program Files\VMware\VMware vCenter Site Recovery Manager\storage\sra\IBMSVC\]

--> Per Haz 20 14:34:33.909:[Info]Executing Module[ Constant ]SRA Name: [IBM System Storage SAN Volume Controller Adapter for VMware vCenter Site Recovery Manager] uuid: [38295F72-F7D0-4A0F-B8D4-FF9821AB2675] version: [2.2.0.130422]

--> Per Haz 20 14:34:34.19:[info]Executing Module[ SRARunner ]commandName file: [discoverArrays]

--> Per Haz 20 14:34:34.19:[verbose]Executing Module[ SRARunner ]logLevel: [verbose]

--> Per Haz 20 14:34:34.34:[verbose]Executing Module[ SRARunner ]outout file: [C:\Windows\TEMP\vmware-SYSTEM\sra-output-12-119]

--> Per Haz 20 14:34:34.34:[fatal]Executing Module[ SRARunner ]Command not supported : [discoverArrays]

-->

2013-06-20T14:34:34.065+03:00 [01496 error 'SraCommand' opID=258F28AC-0000001A] discoverArrays's stderr:

--> com.ibm.cstl.hsg.sra.svc.SRAException: Command not supported : [discoverArrays]

-->          at com.ibm.cstl.hsg.sra.svc.SRARunner.execute(SRARunner.java:100)

-->          at com.ibm.cstl.hsg.sra.svc.SRARunner.main(SRARunner.java:173)

-->

2013-06-20T14:34:34.065+03:00 [01496 verbose 'SraCommand' opID=258F28AC-0000001A] Stopped listening for updates to file 'C:\Windows\TEMP\vmware-SYSTEM\sra-status-13-225'

2013-06-20T14:34:34.065+03:00 [01496 verbose 'SraCommand' opID=258F28AC-0000001A] Cancelling SRA command timeout

2013-06-20T14:34:34.065+03:00 [01496 info 'SraCommand' opID=258F28AC-0000001A] discoverArrays exited with exit code 0

2013-06-20T14:34:34.065+03:00 [01496 verbose 'SraCommand' opID=258F28AC-0000001A] discoverArrays responded with:

--> <?xml version="1.0" encoding="UTF-8"?>

--> <Response xmlns="http://www.vmware.com/srm/sra/v2">

-->     <Error code="4"/>

--> </Response>

I have site recovery manager installed, everything is working just fine though 2 virtual machines at the main site show

the (butterfly) sign which should appear on vms at the DR site not on vms at the main site.

only those two vms show this sign, I checked of the plan for those two vms need to (Reprotected) but they were with (Recovery) sign only, which means they already reprotected.

is there any explanation for this ?!

Thanks for Advanced.

Hi all,

I installed a DR infrastructure as follow :

protected site:

1 VM vCenter 5.1 with SQL Express 2008 R2 SP1

HP SRA on the vCenter server for EVA storage

1 VM SRM 5.1.1 with SQL Express 2008 R2 SP1

recovery site exactly the same:

1 VM vCenter 5.1 with SQL Express 2008 R2 SP1

HP SRA on the vCenter server for EVA storage

1 VM SRM 5.1.1 with SQL Express 2008 R2 SP1

SRA is configured.

I downloaded the plugin, configured SRM (mappings, recovery groups, recovery plan), tested the recovery plan and everything  worked...

BUT

The day after, when connecting to the vCenter, SRM was not available in Home ==> Inventory ==> Solutions and Applications...Plugin was not installed anymore but in the available plugins

When I tried to reinstall the plugin, I had an error "SRM plugin is already installed"...

And here is the tricky part. I uninstalled the plugin on each vCenter rebooted it and tried to install it again and got the same error "SRM plugin is already installed"...

I uninstalled and installed again the 2 SRM servers. Same error...

I don't know what to do next...If someone has an idea, it will be very appreciated

Hi,

I'm new to vmware, so I'll ask maybe a basic question.

My company wants to move from physical to virtual system. We are over 20 servers with different roles (DC, Exchange, SQL, File Servers...), and we want to virtualize in the HQ, and in the same time create a DR site in another place. I would be very grateful if someone can help me to build a list of hardware, and software we need to achieve this:

1. In  the HQ, we would like to have 2 Storages mirroring with each other, and 3 servers connected there to run VM machines so in case one craches, system doesn't need to start working in DR site. Is it possible, and if yes what we would need to buy (SAN license, special vmware license)

2. In the DR site to install 2 servers, and only one storage, and replicate with mirroring storages in HQ. Is this possible, and again ,what licenses we need (for storage, and wmware side).

Thank you in advance for your reply, and I hope I'm not asking to much.

Hi,

I have deployed vmware srm 5 based on array.

It could automatically run the recovery plan when it detects a drop in storage or servers? or it must be done manually when we detect the fall?

thanks!

Has anyone else seen this error with VRMS?

I have two sites setup in SRM5.

Each site has a VRM server deployed, configured, and connected.

Each site has a single vSphere Replication server deployed and registered as well.

Summary tab shows them as connected via IP (did not use DNS due to other problems I had read), one site shows 2 source VMs, datastore mappings are correct, permissions are correct (run as admin).

So when I try and tell it to "synchronize" I receive a "HmsGroup.OnlineSync" for object "GID...." on Server "xxx.xxx.xxx.xxx" failed. An unknown error has occurred."

Anyone else run into this or could give me some pointers on how to troubleshoot from here?

Thanks.

Hi,

I'm setting up SRM and did a successful planned migration to the recovery site. Now I want to do a reprotect and do a recovery in the opposite direction.
The reprotect fails with the following error: Error - Failed to reverse replication for failed over devices. Cannot process device 'sync-Mirror_LUN_viR-205R' with role 'target' when expected device with role 'promotedTarget'

There is now also an error with the array manager on the recovery site: Duplicate device 'sync-Mirror_LUN_viR-205R' found in SRA's 'discoverDevices' response.

This is all running on version 5.1 for ESXi and SRM and we are using a VNX for storage on both sites.

I was wondering if anyone had similar issues and were able to resolve them.

vCentre 4 connected to a CX4 using Recoverpoint SE.

We have the consistency groups configured as we want, but SRM is grouping the consistency groups together when attempting to create protection groups. This means they are always in error.

Has anyone else experienced this?

Dear People From The Future: Here's what we've figured out so far: (http://xkcd.com/979/)

We are installing a vCenter Site Recovery Manager system, and having a deuce of a time on one vCenter deploying the OVF Template for the VR Appliance. Error message is "This OVF package uses features that are not supported. Unsupported section '{http://www.vmware.com/schema/ovf}vServiceDependencySection' (vCenter Extension vService Dependency)"

vCenter A is Protected and has successfully completed connection, mapping, and created Placeholders with vCenter B (Offsite). When I go to the vSphere Replication step 1 to Deploy the Appliance, the OVF template shows the correct location of my vCenter server, and both of the SRM servers for A and B are configured the same (physical SRM with SQL 2k8, virtual vCenter appliance).

I can force it to use the OVF template straight from my SRM server, but then the vSphere Replication process won't go past step 2 (Reconfigure the VR Appliance).

Also, I don't see a "VMware VirtualCenter Management Webservices" service on either vCenter server A or B so I don't think that's the issue.

Thoughts?

Victor.

Can anyone advise how I can find out where the SRM database is installed? I’ve looked under ODBC System DSN but there’s nothing there as there is with VCenter which shows the SQL instance or server?

Many thanks if you can help.

Upgrading from SRM 5.0.1 to 5.0.2 and received the attached error. Selecting to accept the thumbprint allowed the install to progress but failed with a message advising the install was interrupted and to try again another time. Nothing in the logs so far to assist deducing where the trust issue lies. Has anyone experienced  this issue themselves or have any initial fault finding advice?

My setup is as follows:

• ESXi 5.1
• vCenter 5.1a running on a VM
• SQL 2008R2 running on separate VM from vCenter
• Separate VM for running SRM
• Above config is replicated on DR site
• vCentres are not in Linked mode
• Separate SSO databases for each site

When I installed SRM it got right to the end and then gave the service failed to start message.  Eventually, after clicking Retry several times, the installation completed.  However the SRM service was stopped.

The service can be started, but it stops immediately without leaving any errors in the Windows logs.  The only hint of information that may be helpful is in the SRM installation log:

VMware: Srm::Installation::Utility::LaunchApplication: INFORMATION: Executable finished executing. Result code=1

VMware: Srm::Installation::VMUnregisterSrmService: ERROR: LaunchApplication() failed. Executable=D:\Program Files\VMware\VMware vCenter Site Recovery Manager\bin\vmware-dr.exe, Parameters=-u "D:\Program Files\VMware\VMware vCenter Site Recovery Manager\config\vmware-dr.xml", Code=1

VMware: Srm::Installation::Utility::LaunchApplication: INFORMATION: Launching executable. Command line="D:\Program Files\VMware\VMware vCenter Site Recovery Manager\bin\vmware-dr.exe" -r "D:\Program Files\VMware\VMware vCenter Site Recovery Manager\config\vmware-dr.xml"

VMware: Srm::Installation::Utility::LaunchApplication: INFORMATION: Waiting for child process to complete

VMware: Srm::Installation::`anonymous-namespace'::ReadFileCompleted: INFORMATION: Asynchronous callback status: 109

VMware: Srm::Installation::`anonymous-namespace'::ReadFileCompleted: INFORMATION: Asynchronous callback status: 109

VMware: Srm::Installation::Utility::LaunchApplication: INFORMATION: Child process stdout:

I have tried looking up Result code=1 but without any success.  Some KB articles talk about the System DSN, but that is 32 bit and the test connection is successful.

I have the same problem on both the Production DC SRM and DR DC SRM.

Any ideas gratefully received!!

I have an issue in my Host Based replication setup.  Since it’s a host based setup I have to use VR servers for the replications. My issue is that these VR servers will throw alarms as being disconnected.

[VMware vCenter - Alarm alarm.hbr.primary.NoConnectionToHbrServerEvent] No connection to VR Server for virtual machine

I have a ticket with VMware Support and they are saying that my virtual center server on the destination side is not a supported configuration for SRM since the VC is a VM. Which to me doesn’t make sense and is ironic in the that a VM is the preferred method according to VMware.

At first support had me make sure that all the FQDN settings were correct on both sides. That didn't help.

I was wondering if anyone had similar issues and were able to resolve them.

This is all running on version 5 for esxi and SRM. Not the update 1 either.

Thanks

Jason

The SRM 5.1 install guide says that SRM can work the stand alone version of vSphere Replication:

" If you installed the standalone version of vSphere Replication 5.1 and then installSRM 5.1, all existing pairings and replications are immediately accessible through the SRM user interface"

http://pubs.vmware.com/srm-51/index.jsp?topic=%2Fcom.vmware.srm.install_config.doc%2FGUID-E8859207-0D9D-414E-8A2A-CEAC0FCA76A3.html

However, SRM 5.1 does not detect it at all.  When I go to the vSphere Replication page in SRM it looks as if no VR appliance has been deployed, as if it still wants me to deploy them from SRM.

How do you get SRM 5.1 to detect the existing VR appliance and all of it's replications?  Thanks.

I’ve got to failback an upgrade of SRM 5.0.2 to 5.0.1 due only one of the upgrades being successful at the protected and recovery sites so one is at 5.0.1 and one is at 5.0.2 and I need it all back working on the earlier version until I can resolve the issue. I’ve got a backup BAK file of the external SQL DB and I’ve snapshot the SRM VM before the upgrade.

The plan I thought would be:

1. Shut down the upgraded SRM VM
2. Rollback to before the upgrade
3. On the SQL server, right click the DB select tasks and restore the DB from the BAK file
4. Start the SRM VM back up

I’m concerned there will be issue with VCenter (5.0) though as surely the successful SRM upgrade would have made changes there also for example there is the updated SRM plug-in visible in the VI client and that would still be remaining surely if I performed the above action. Any thoughts?