Quantcast
Channel: VMware Communities : All Content - Site Recovery Manager
Viewing all 2572 articles
Browse latest View live

HmsGroup.OnlineSync Fail - unknown error occurred

$
0
0

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.


Reprotect fails with error

$
0
0

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.

Datastore Groups Wrong?

$
0
0

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?

vSphere Replication Manager Appliance will not deploy

$
0
0

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.

vSphere Replication size limits

$
0
0

I've looked all around for specific  limits to the size of a VM that can be protected via SRM w/vSphere Replication, but I do not see such documentation. I did see the release notes of 5.0.2 stating being able to handle vmdks > 255G better now.

 

I originally used 5.0.1  and had a lot of problems trying to sync a 3TB Guest 2,  1.5TB vmdks but i finally go tit working, though it took days and multiple attempts to accomplish.

 

Now a customer is asking for 16TB to be protected. Not sure how the breakdown of VMDK's will be, but I came up with some rough numbers ranging from an initial sync ranging from 12-21 weeks.

 

anyone have any experince with large drives a vSphere Rpelication?

SRM Database Location

$
0
0

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.

VCenter Server certificate does not have a valid chain of authority error upon SRM upgrade

$
0
0

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?

Service starts and then stops during SRM 5.1.1 install

$
0
0


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!!


Host Based replication issue with VR servers.

$
0
0

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

SRM 5.1 does not detect existing standalone vSphere Replication 5.1 appliance

$
0
0

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.


 

SRA command 'queryInfo' didn't return a response

$
0
0


Hello all


Need another helping hand with SRM configuration.

I had got all the plugins installed and configured array managers for our protected site and recovery site.


I'm not to sure on what information to provide which can help getting your support with the current issue. I would attach the logs but not sure on where to find them.


I have attached the error I'm currently getting.


I have read through some of the articles and posts regarding people having the same issue but the fixes mentioned I had done already like .net 3.5 and services account admin rights and installing perl.


Please let me know if anymore information needed.


Thanks

Austin.

SRM upgrade rollback

$
0
0

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?

after doing a failover and failback -- replicated datastore

$
0
0

So I have a question of the state of the datastore where my vms are on after doing a array based failover and fail back.

 

I did a reocvery failover of a few vms, and then did a reprotect and finally failed the vms back to their original location.. So when I view the vms they are currently running on the original cluster before testing with SRM (as expected)

 

what I was not expecting is the datastore the vms are using has the prefix "snap" still.

 

I do not really think the datastore they are using is a snapshot, when I did a esxcfg-volume -l, nothing came up as far as snapshots.

 

So did it not just remove the "snap" prefix or am I missing something...

 

thanks!!!

SRA command 'queryInfo' didn't return a response

$
0
0

Hello,

 

Trying to install NetApp SRA in SRM.  SRA detected the NetApp controller at the remote site but I won't at the local site.  I always get this error message : Failed to load SRA from 'C:/Program Files (x86)/VMware/VMware vCenter Site Recovery Manager/storage/sra/ONTAP'. SRA command 'queryInfo' didn't return a response.

 

I have tried uninstall/reinstall SRM, SRA, Perl : nothing as changed.  If anyone have an idea about what could be the problem, it would be great to share it over here.

 

Thanks,

Anyone using multisite SSO with SRM 5.1?

$
0
0

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?


Design questions for vCenter 5.1, SSO and SRM

$
0
0

Currently running vcenter 5.0 U1 at primary and recovery sites.  These vcenter servers are currently in linked mode. In researching the upgrade to 5.1, I see a requirement that all vcenter servers in a linked mode group must be registered to the same SSO server. This seems like a requirement for a single point of failure if you want to use linked mode, if there is only one SSO server. I realize this applies to an environment without SRM as well. I bring this up in the SRM forum because I think it applies to most SRM environments.

 

My question is, how can I design for the recovery site to be independant of the primary site? Of course we want the recovery site to be available in a total loss of primary site scenario. In SRM 5.0 I believe linked mode is not required, but it is still recommended.

 

Maybe the answer is in SSO/vCenter design and I have not read enough about that yet. Just wondering if anyone has any thoughts...

SRM Install with Multiple VCs at Site

$
0
0

Question on SRM (5.1) install with multiple vCenters at site. I cant find a clear answer on this.  This is a classic Protected/Recovery DR design.  Two datacenters, Prime and "DR".  Question has to do with number of VC at the Prime Site. I have plenty of information on SRM datacenter locations with one vCenter each, but not multiple.

 

The Prime Datacenter has multiple vCenters representing different environments.  For SRM the two sites will match.  For every VC at PRIME, there will be one at DR.  However is on SRM that I have the issue:

 

  • Do I need to install SRM Instance for each VC at Prime location and its partner at DR location? Would this also mean each SRM instance needs its own DB?

 

OR

 

  • Can I install a single instance of SRM on its own server at each site to control the Prime site and all VCs located there and have the same at the DR site?  This would be very similar to SSO in that respect (one SSO server per location).

 

Consolidating the VC is not an option.  Company likes their environments to be separated even on the vCenter level.  One upside, all the VCs are linked.  Very nice single pane of glass way to review the all the VCs in the corporation.

 

Thanks,

 

Boston Tech Guy

DR-IP-Customizer on Shared SRM Instance

$
0
0

Getting an error when executing the DR-IP-CUSTOMIZER on the target vCenter server:

 

error:  unable to locate the srm extention on the vmware vcenter

 

Has anyone successfully run the tool with a shared SRM instance?

Different versions of SRM at sites

$
0
0

SRM 5.02 is installed at our Production site and our DR site.

I just got through upgrading the Vcenter server at our DR site to 5.1.

 

I need to upgrade SRM as 5.02 isn't compatible with Vcenter 5.1.

I  don't plan to update:the production Vcenter for a couple of weeks so the question:

 

Will SRM work with different version across the 2 sites?

 

I assume the answer is no but am hoping I'm wrong.

Failover Recovery Plan stuck

$
0
0

Hi all!

 

We our now in test phase for our SRM setup.

 

I created a protected group with 3 servers and then click on recovery to do a test.

 

It seemed like it recovered fine, but now when I try to do a clean up it won't work.

 

For the past 2 weeks now it has just been stuck at failover recovery plan 36%. I have looked at the recovery plan and it just says recovery in progress.

I am new to SRM and having trouble trying to find how and why it is stuck.

 

I have restarted all SRM services and virtual center server service.

 

We have 2 SRM servers and 2 vCentre servers.

 

I am not to sure on where the logs are that I can attach to this.

 

Any help would be greatly appreciated

 

Notes

We are using array replication and have an EMC san.

Viewing all 2572 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>