Redundansy vCenter by SRM

Similar Questions

• Licensing vCenter with SRM

  Hi all

  I seem to be going round in circles with this question - I have read the documentation and recorded a call with the service the customer on this subject, and the answers are contradictory to say the least...

  We seek to implement a SRM solution in a new infrastructure - essentially a management cluster will use SRM failover management of virtual machines to a domain protected to a DC recovery in another city controller.  The DC recovery will be dark for normal operations, only more direct when MRS. failover occurs and will not host virtual machines.

  The question I have vCenter licenses of MRS. The documentation states that, during failover of a vCenter server from a site protected for a recovery site hosting any other virtual machines, only 1 vCenter license is required. However the VMware licenses team said the 2 licenses are required for automatic restoration of VMs for the protected site of origin once he recovered.

  So, who is? Any thoughts anyone (who is not a dealer or someone trying to sell me licenses)? Happy qualify points if necessary to answer the question...

  See you soon.

  Jeremy.

  the vcenter in Dominican Republic must be put under tension and linked with the SRM server of the RD, in this scenario, it's actually light and 2nd license is necessary.

• Updated vCenter, now SRM service does not start.

  We have put SRM implementation.  We have vcenter, SRM servers on separate boxes.  We have updated our vcenter since version 4.0 to 4 Update 1 servers.  Somewhere in there the VMwarevCenter Site Recovery Manager Server service has stopped.  Now, when we try to start it, it starts and stops again.  Any help would be greatly appreciated.

  In the face of problems always get your eyes on the newspapers.  I just go to the start menu for 'generate the site recovery manager newspaper bundle' or something like that...  Try to start your service, newspapers will turn, generate a bundle and after the last log.  The most common cause for this problem is a lack of database connectivity, but it could really be a lot of things.  Let's see these newspapers!

  Tim Oudin

• Moving VMs to different vCenter using SRM + RecoverPoint

  I need to spend 5 virtual machines to a different data center permenetly. The good news is these virtual machines are already protected by 3.4 SP1 RecoverPoint and Site Recovery Manager 5.0, because we already have replicate them I'm working on a way to swing these VMs, reverse the RecoverPoint replication and pretty much swap around, so they are replicated to the initial data center.

  I just installed SRM 5.0 so we continue to use its latest features, but I assume that what I said above is actually possible? Perhaps he might not be as clean I hope, but at least I wouldn't be able to do the following? Keeping in mind, if this fails, we would just go back to how it was.

  1. run the failover plan that will recover virtual machines to the new data center

  2 reverse replication in RecoverPoint, making the new primary data center

  Is this possible?

  The old production VMs is converted into placeholder VMs. The point behind this conversion is that identity of the virtual machine does not change when you cycle complete (failover from A to B, Reprotect to B, B to A failover). It should all work modulo any RecoverPoint questions and / or ODA I mentioned. Incidentally I have never worked with RecoverPoint SRA, so that part is purely speculative.

  -Remy

• SRM starts does not after migration to vCenter

  Hi all

  We are moving some things regarding the vCenter and SRM.  vCenter and SRM are on separate servers, remain like this once all the moves are complete.  I currently work in a test environment in order to eliminate the process.  Moreover, all this is actually in 4.1 U 2.

  The vCenter and SRM databases are moved to new servers.  vCenter also moved to a new server.  SRM will not move.

  So far, the migration went well.  Everything worked fine after the vCenter and SRM databases have been moved.  vCenter worked well after being re-installed on a new server.   However, now I have problems with MRS after the modified vCenter (hostname/ip).  It won't start (or at least it is in a perpetual state start) and the log file is similar errors to: could not establish a connection to VMware vCenter.

  This makes sense since the vCenter hostname/ip just be changed.  To try to find a way to solve this problem, I was looking for to http://kb.vmware.com/kb/2008033.  I tried to adjust the database, but now he complains about host certificates.  I'm starting to think about a re - install MRS. from scratch may be the best option. 

  Y at - it an easier way, or am I missing something?

  Thanks for your help...

  Hello

  The Ko, you mentioned suggests to re - install RS, so I think it is necessary, and there is not another way.

  Michael.

• SRM and Datacenters in VCenter

  Hello gurus,

  SRM limited to a virtual data center only or may, once the MRS server be used for failover of multiple data centers in an instance of VCenter? Also, is it possible to manage different virtual centers within one instance of VCenter by SRM difference? Basically can we have only a single instance of MRS. manage a VCenter? Also if there are any other limit of SRM that one should be aware of?

  Hi, you can have more than one data center in a SRM config.

  Each SRM is asociated with only Vcenter, you can have different SRM asociated with a Vcenter or various Vcenter with an SRM.

• SRM and VCenter on the same server?

  I was just by reading the documentation and I saw that I need to have vCenter in both places in my SRM deployment. Now I'm on a server. SRM and vCenter co-exist on the same server? Is it still a good idea. I don't have a problem with the purchase of another server if I need to.

  I have a follow-up question on the vCenter licenses. Do I need to purchase a second license for the recovering site vCenter?

  -Patrick

  SRM and VCenter can coexist on the same server.  You will see a performance impact when you test your disaster recovery plan.  I think that a lot of achievements have vCenter and SRM on the same server.  If you do not want to take the risk of a performance hit on your vCenter server you might move RS for its own box, but I advise to use a virtual machine instead of another physical server.

  I think that you need a license of vCenter to each site.  If your recovery site hosts only the DR then you can use your existing licenses for ESX.  If your DR will site also its own VM produciton is then you will need full license.

• Add vCenter fails with CertificateChainValidator - vCO 6.0.3

  I had a running off vCO 5.5 self-service portal using a bunch of users.  I deployed a 6.0.3 vCO device VM and imported the config.  I finished the configuration, and all radio buttons are green on the site Configuration port 8283.  When you try to add vCenter using the workflow 'Add an instance of vCenter server', it does not immediately in the workflow "Import a certificate" with "ReferenceError: 'CertificateChainValidator' is not defined."  I have imported the SSL certificate of the vCenter and the PSC under Network-> SSL Trust Manager.   All certificates are self-signed because MRS. 6.0 would not work with CA Cert on vCenter has signed at the time where we deployed SRM.  I have not touched the CERT on vCO 6.0.3... trying to take the path of least resistance to maintain vCenter and SRM running and get the vCO online.  I checked vCenter MOB and there are no extensions of vCO.  How can I get vCO 6.0.3 is registered correctly with vCenter?  My vCenter is a VCSA and 6.0 build 2656761.

  VMware support was able to understand this.  For some reason, not all the workflow was available even though I deployed a new 6.0.3 camera and imported the config of my old 5.5 instance.  So we went into the Web of Orchestrator Configuration page-> troubleshooting and click 'Reset the current Version' for plug-ins.  Bounced, she and the missing workflow was there.  Back then in the Web Configuration Orchestrator page-> vSphere Configuration under general and enter IP address of our vCenter PSC and [email protected] used.  The appearance of the data worked, I checked most of the boxes and could see vCenter in vCO thereafter.

• SRM appear in web client

  So I've been reconfiguring our server VCenter and SRM.  I replaced the VCenter server with a camera and set up a new server in each site to perform the Manager Update and SRM.  Configuration was fine and I was making each site in parallel most of the time.

  I ran into an issue now but where SRM is in service webclient on the production site, but it does not appear in the vcenter for our recovery site.  I put in place the same sites so it seems strange that I would have a question. I also watched the event on the client log web vcenter in the Dr site and it does not list SRM and using 0 75 licenses, so we see it clearly, but I have no option for this.

  Thoughts?

  Thank you!

  Hello

  Probably just wishful thinking on my end, but have you tried to restart the Web Client vSphere? You can do it in the management UI (VAMI) unit of vCenter Server.

  Thank you

  Stefan

• Permissions not reflecting only not in the SRM console

  When I check the console SRM (5.1.2), the recovering site is not reproduce the permission that is present in the vCenter permissions tab. The result is, I want to use a service account for connecting sites SRM, however on the basis of this problem when I try to link to the site using the designated service account, it does not work on the protected site, but when I have a pair from the recovery of the site he pairs no fault.

  Has anyone encountered this problem?

  Posted shears vCenter & permissions SRM console.

  Hi shantanu27

  You've paired the sites successfully before or is this the first time?

  Try to manually add the permission to the service account in the recovering Site.

  Connect to vCenter Site Recovery > Home > Site Recovery > Sites > Permission > right click on the white space (under the username) and add the authorization > choose CORP domain > add SVC-BNL-VCENT... as an administrator.

  See screenshot below

  

  After you have added the user SVC, try to pair again.

  Thank you

  Bayu

• SRM 5.5 - the remote server returned an error: (503) server unavailable, could not create SSL/TLS secure channel

  Design:

  2 vCenter VMs version 5.5 on new W2k12. x. related and the same use facilities key SSO (default installation)

  2 x fresh install of the SRM VMs version 5.5

  20 + hosts vSphere 5.5 with DR/HA configured and working. Two dvSwitches (one per site) configured with the groups of port / VLAN work

  Question:

  Installation goes well until I needed to activate the Plugin SRM in vCenter.  Plugin called "Plug-ins available" and I click on the link 'download and install '.

  I had two separate fouls on both servers vCenter, both with same errors if it is compatible.

  Errors:

  (attached file viclient-3 - 000.log)

  The request has been aborted: could not create SSL/TLS secure channel.

  (attached file viclient-3 - 000.log)

  The remote server returned an error: (503) server unavailable

  I guess that the two are linked and probably something with SSO.  Post installation on each server vCenter vCenter, at the level of the vCenter, I added the "Domain Admins" AD Group with all permissions and then properly connected and built the group with this set of credentials.

  I need help to debug this further.

  Thank you

  ************

  < < Updated > >

  Seems the features and functions are NOT present so you don't not sign in as '[email protected]' (SSO account by default for this "basic" configuration)

  But even with this connection, I have noticed that there is NO option in the webclient service, to perform the installation of a vCenter plug-in.  It does not appear in the vSphere Client (see images).

  I also found it weird that the web client to vCenter illustrates SRM roles but the traditional client does not work.

  Maybe it's a clue to the root cause of...

  Post edited by: ArrowSIVAC 2013-10-07 to provide more details and attachments

  Post edited by: ArrowSIVAC, this is related to the case of support for vmware 13384832210 This problem is solved.  Several pieces here. (1) vCenters were installed secretly with local account as own databases, and this is how I usually do things (2) MRS. servers were built as separate virtual machines, VMWare vs guides guess and documents in anticipation of your SRM installation on the same server as vCenter Documentation / Installer is not clarified that you MUST use domain for MRS accounts in the multiplayer linked site facilities and if you do not, the installation is completed without error, but resources will not work. Errors have for client plugin does not work. It was the symptom, the reason was that the SRM service did not work.  The service would not start and only an error in the Windows event log is 'vmware-dr stopped service' is because the connectivity issue of MRS to vCenter hosted the new SQL instance database SRM. The SRM database has been installed on the instance of vCenter server as vCenter database.  And just like the installation of default vCenter I chose localhost\administrator for database owner.  The database was filled with tables, but SRM has connectivity problems.   The fix for this was to add "domain\user" (called mine SRMAdmin and added as a member of domain admin), add this user in SQL in the list of database users and then promoted as the owner of SRM database and define the rights on DBO. This fixed the first issue. Second issue was that SRM installation set the DSN system identification information, but does not specify that they must also be domain based accounts.  The installation program is not not clear here and should only allow user domain\username when installing. After several attempts because of the root and installation methods different tried, how to get the installation complete and properly configure was to log on to the system AS the example domain account: domain\srmadmin = > Configuration System DSN by selecting "How should SQL Server verify the authenticity of the login ID?"  "with integrated Windows authentication', and then the installation of SRM to the"Enter Database user credentials"value"domain\srmadmin ".  Then and communication services to the vCenter SRM hosted DB database will work correctly. < See images attached benchmarks >

  attached files

• vCenter/Single Sign - on design recommendation

  Hello

  We would like to do a new install of our 2 virtual centres.

  The vCenters looks like this

  ----------------------------------------------------------------------------

  1 vCenter main Site (source vCenter for SRM)

  1 vCenter Site Backup (target vCenter for SRM)

  The current running configuration has a problem with SINGLE sign-on. If the primary vCenter is down you can't connect on the second, which should be the backup vcenter.

  My question is, how to configure the vCenters with SSO as the two vCenter are not affected by another (related modes and MRS. should also work).

  Somebody has experiences with this or has a few recommendations for me?

  Thanks so far

  Simon

  5.5 you will want to install the first VirtualCenter and create a new SSO domain.  Then when you install the second vcenter, you must also install SSO, but tell him to join an existing domain. This will cause the two bodies SSO replicate, but each vcenter has its own copy of the SSO database. In this way when the primary vcenter disconnects, the vcenter backup can still login with SSO and all the data you need.

  I'm not familiar enough with SSO s 5.1 - we skipped this upgrade (and boy, I'm happy). My advice would be to spend 5.5 with a clean if possible install and configure these organizations on both sides with replication.

• SRM and vReplication need help

  Hi all.  We're new here and desperately need help with SRM and vReplication.  We had a case open with VMware, but apparently we are a large enough customer because we've been down for more than 3 weeks with limited (and very limited) contacts with VMware.  Us running vSphere 5.0.1 with self signed certificates and try to install the SRM and vReplication.  After you have reinstalled completely vCenter Server both protected and recovery sites, we have installed SRM in both places.  Currently, we are trying to install and configure VRMS.  Even if we deploy VRMS and are able to connect to the server, the Summary tab never displays the name of the server and the VRM will not accept self signed certificates generated by vCenter and SRM.  Anyone (nothing to do with VMware) can help us.

  Hello

  The message to the attached screenshot - "local and remote servers use certificate methods of trust. ' is generated by the MIS servers due to the different configuration on both sites. I guess that SRM can be modified to use only digital fingerprint matching, but I've not done this before.

  If the VRM servers are configured differently, so that the message would be "method of trust Incompatible certificate used on the server" Server: port ".» Two VRM servers must use the same method to trust certificate. ».

  Kind regards

  Martin

• vCenter server SRM2 is not a pair of vCenter server SRM1

  Hello

  We install two sites with vCenter 5 and 5.01 SRM (two VM) and the link between the two sites using vCenter with SRM, good plugins, then accidentally delete vCenter and SRM to the site servers, then recreate us these servers and attempt a new connection of vCenter, then came the aims of the error that the server is not a pair of vCenter SRM to the main site. How can we clean up the remains of connection on the main site and make this connection again? Thank you for your help. Aquiles.

  Hello

  You must also reinstall SRM on the main site.

  Michael.

• SRM plugin has me re - authenticate each time after I have logged in vSphere client?

  After I authenticate the client vSphere and then proceed to the section of Site recovery, I wonder to be re - authenticate the vCenter recovery.

  Is it possible to store my credentials, so I sign in twice now when I need for activities of MRS?  Once for vsphere client, and then back to recovery vcenter as SRM is plugged.

  Thank you.

  This is a normal activity and there is not yet a cache for the other site identification method, would be awesome to have device assuming that the remote site is located in the area of trust or A.D. even.

  Tim Oudin