vCenter SRM 5.5

Similar Questions

• Testing failover with VMware vCenter / SRM and SQL on protected volume.

  OK, MRS. works well in test mode, although we would like to test a failover / then backspace over the weekend...

  We run SQL 2012 on a virtual machine as well as vCenter/SRM on another virtual machine, both on the protected volumes.

  If the failover stops all VM, makes a new replication then turns on the virtual machine on the DR site, it would fail because we had SQL and SRM on a protected volume?  I can understand moving protected site vCenter / SRM VM to another volume, but SQL Server is also used for other data bases we want protected.  My guess is that MRS is not smart enough to not stop SQL server last.  What should do?  What is everybody doing?

  Thanks in advance.

  You need a RS and SRMDB on both sites. The SRM on the site of DR will manage the entire process and not the vcenter/srm on the production site.

  BTW. a Microsoft SQL Server 2008 Express (R2 SP1) - 64-bit is supportet to SRMDB. Check partnerweb.vmware.com/.../interop_matrix.php

  Kind regards

  Joerg

• Point at the new vcenter SRM

  Here's a little history.  We have tried to update our existing 5.5 vCenter server, however we met a ton of SSO issues and could not go beyond the SSO 5.5 upgrade.  VMware offers a new server vCenter.  OK, so we did it, however I must now get pointed to this new server vCenter SRM.  This new vCenter Server uses the existing DB vCenter.  We have a separate server (5.1) SRM and SRM SQL server.

  My question is, can I point my existing to the new server vCenter SRM Server AND update to 5.5?

  I just wanted to update this in case someone else still has the same problem.  Contacted support VMware SRM.

  They have referenced this KB http://kb.vmware.com/kb/2008033 - but they know that I don't "try this at home" without their help.  Their solution worked great however.

• vCenter SRM VM + VM + vNDS vShield

  Hi guys,.

  Just want a few comments or feedback from the experts here. FYI, my team is going to be implemented later above solution and my design choice will be: -.

  
  * vCenter + SRM runs on a virtual machine
  * vShield Zones (MSM & vSA) will protect 3 x group of ports (SZ1 and SZ2 DMZ) and no network management separated.
  * Virtual Network Distributed Switch (vNDS) will be used

  
  In my class vSphere 4.1 office (vCenter VM + vShield VMFN) installation, I noticed that this configuration can produce some time some hiccups. The VM connection will be revoked if vShield sitting inside the same ESX agent fails. vShield now another addiction to my virtual network.

  So, my question now:

  • This configuration will work fine, and is there any place that I need to focus more?
  • When VM grave vCenter fails (vNDS), network connection will resume again as normal right?
  • What is the correct order, then I'll raise my virtual infrastructure [ESX-> VM-> SRM VM vCenter-> MSM-> AUV-> other VM]
  • For vShield 4.1.0 u1, do we still need install vShield and create the vNDS manually instead of using port group Assistant? I don't find it in the current document.

  At this point if that's your only choice, I would say that sticking with vShield Zones 1.0.

• upgrade to vCenter/SRM to 6.1

  All,

  We have recently updated our server vCenter 5.5 Update 2 to 6.0 Update1b.  All thanks to the improvement of the PSC and vCenter went to the wonder.  The problem we run into is with MRS.  We have improved 5.5.1 to 6.0 SRM that crossed successfully.  However, whenever connect us to vSphere Web Client and run SRM we get the following message when you click sites:

  Cause:

  Connecting to remote servers to SRM Server to https:// < IPofLocalSRMServer >: 9086, vcdr, vmomi, sdk needs to be reconfigured.

  I can't find anything on this error and have waited for hours for the VMware support call.  Any ideas?  We get this message with the SRM Server (remote and the).

  I suspect it is a certificate problem, but I can't identify where.  When you go to https://srmhost:9086 , I get the following:

  Local connections

  -------------------- --------------------------------------------------------------------------------
  Service com.vmware.cis.cs.inventory
  URL https:// < vCenter Server >: 443/invsvc
  Unknown thumbprint
  Status connected
  -------------------- --------------------------------------------------------------------------------
  Service com.vmware.cis.vcenterserver
  URL https:// < vCenter Server >: 443/sdk
  Unknown thumbprint
  Status connected
  -------------------- --------------------------------------------------------------------------------
  Service com.vmware.cis.cs.inventory
  URL https:// < vCenter Server >: 443, invsvc, vmomi, sdk
  Unknown thumbprint
  Status connected
  -------------------- --------------------------------------------------------------------------------
  Service com.vmware.cis.cs.lookup
  URL https:// < vCenter Server >: 443/lookupservice/sdk
  Unknown thumbprint
  Status connected
  -------------------- --------------------------------------------------------------------------------
  Service com.vmware.cis.cs.identity
  URL https:// /SSO-AdminServer/SDK/vsphere.local < vCenter Server >
  Unknown thumbprint
  Status connected
  -------------------- --------------------------------------------------------------------------------
  Service com.vmware.cis.cs.authorization
  URL https:// < vCenter Server >: 443, invsvc, vmomi, sdk
  Unknown thumbprint
  Status connected
  -------------------- --------------------------------------------------------------------------------
  Service com.vmware.cis.cs.license
  URL https:// < vCenter Server >: 443/ls/sdk
  Unknown thumbprint
  Status connected
  -------------------- --------------------------------------------------------------------------------

  Thank you!

  Hello

  after upgrade, you must reconfigure the pairing between sites or fix the connection from one site to the other. This should be a time effort and it is necessary to renew the certificates information in SRM products improved after all.

  You can find more useful information in our documentation - Site Recovery Manager 6.1 Documentation Center

  Procedure

  1	In the Web Client vSphere client, select Site Recovery > Sites, right-click on a site and select reconfigure matching to reconfigure the connection between sites Site Recovery Manager.

  Hope that this is sufficient,

  Daniel G.

• Redundansy vCenter by SRM

  Hello!

  I have vCenter VM on the ESXi host. I can create redundancy by MRS vCenter?

  For example, if ESXi host with vCenter server VM failure, can SRM start VM vCenter on another ESXi?

  Thank you.

  All first use SRM you will need a vCenter Site recovery too, and on recovery in protected site vCenter, SRM will be repeated this virtual machine on the recovery as a normal VM site.

• spend 5.0u1 + RS 5.0.2 to vCenter vCenter 5. 1 b + SRM 5.1.0.1 really not possible?

  Hello

  I vSphere business with vCenter SRM 5.0.2 on two sites (SRM for two protected volumes and two recovery volumes on NetApp file on every site server) and 5.0u1 and I guess its time for the 5.1 branch. But in the documentation for the MRS it is explicitly stated that MRS. upgrade to 5.0.2 5.1 is not possible. Is this really true? This means that I need

  d ' being stuck to 5.0 versions forever?

  -to completely uninstall RS, remove from its database, install 5.1.0.1 and create 5.1 SRM and set it up from scratch on each site?

  Or should I just wait for the next version of SRM 5.1 (5.1.0.2?) - if so, when it comes out?

  Thank you

  David

  Hi David.

  SRM 5.0.2 was released after 5.1, there is no built-in 5.1 code that knows the way to upgrade to 5.0.2.

  Good news, it is that there should be a 5.1.1 new releases in the next 24 hours that will have this ability... so your upgrade path is now directly from 5.0.2 to 5.1.1.

  You will probably spend a lot more time on the upgrade to vCenter with every new bit it to with SRM upgrade - it's pretty simple.

  Hope that it took you time before you rebuilt.

• 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

• 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

• SRM 5.1.1 - multiple entries of plugin

  Hi all -

  I recently deployed a multi-site SRM 5.1 configuration.  (2) sites are tipping toward a recovery site.  All sites seem to be running OK - VM reserved spaces are on the DR site and I don't see any problems.  However, on the site of production (1), (2) plugin entries appear when I try to load the plugin SRM.  Here's what it shows:

  

  When I load either of the SRM IDs, it loads the same SRM site.  I tried to restart the server vCenter, SRM server and uninstall and reinstall the extension of the SRM on the vCenter server that did not help.  I would like to somehow remove the < default > option of entry when I charge RS.  Is it possible to do this easily?  Thank you!

  Guy-

  I ended up having to find the invalid extension of the SRM and the deletion in the article below.

  VMware KB: Removal of the unwanted plugins to vCenter Server

• Replication of hot Site DR with SRM

  Hi gurus,

  I am designing the SRM solution to a client.

  The customer needs to reproduce some vm from main Site to the Site of DR.

  Some other vm of the DR Site to the primary Site.

  In my opinions we can do with 2 packs of SRM for each site.

  I need your advice on how to the vCenter will identify the protected Site and recovery at the same time.

  This is a fairly common scenario.

  You install RS on both sites, configure replication for necessary VMs and / or LUNS in the desired direction, in case of array level replication install and set up authorities in securities on both sites and then set up groups for protection and recovery for your VMS protected plans.

  You need not necessarily "2 packs of SRM for each site. Usually you just need a single vCenter SRM and unique example in each site.

  Suppose we have A with VMs vmA1, vmA2, and vmA3 and site B with VMs vmB1, vmB2 and vmB3. Are being replicated virtual machines from site A to site B and vice versa.

  For protection:

  -protection for their virtual machines are managing vCenter-a and RS - A, SRM - B holds for VMs vmA1, A2 and A3 recovery plans

  -protection for virtual machines B are managing vCenter-B and RS - B, RS - A holds recovery for VMs vmB1, B2, and B3 plans

  If customer policy explicitly states that extracted protected site of the VMs should not be started under vCenter even (i.e. If site B fails and VMs vmB1, B2 and B3 must be restarted to site A, customer does not want to live under vCenterA for a reason any) then this would require 2 vCenter and 2 instances of MRS server in each site. Normally, you should be able to avoid this, because that increases the cost and complexity of managing (thinking of buying 2 licenses vCenter for each site). If there are strict insulation requirements, in general, you should be able to satisfy them by using two pools of resources, different vSwitches / exchanges, proper network segmentation, different data stores and possibly multiple clusters.

  I hope this helps.

  WBR

  Imants

• 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.

• The best location for vcenter VM and placeholder data warehouses

  Hello

  I have an SRM installation with 2 sites.  The sites are separated by metro trunk of layer 2 ethernet between the sites.

  Site has

  1 EqualLogic PS6100

  2 ESX servers configured as cluster

  There is a single data store volume over the San with all virtual machines in this cluster

  There is one instance of vCenter to this place located in the same data as the other virtual machines store

  There are also a few other volumes on the SAN used for the RDM disks in virtual machines

  I also created a small volume of 1 GB as a VMFS data store and have it mapped in SRM to use as a placeholder for a data store

  What are your thoughts on that?  Is this the best way?  I could use the local storage on the ESX servers?  Main VM can be used for fictional settings or my data store?

  SRM is installed on the same VM as vCenter

  MRS. uses SQL Express on the local vCenter VM

  vCenter also uses SQL Express

  Site B

  1 EqualLogic PS4100

  1 ESX Server, so no clustering

  There is a single data store volume over the San with all virtual machines running on ESX Server

  According to the requirements of the SRM, there is a separate instance of vCenter operating as a virtual machine, and it is not in bound mode.  Should it be? / Should it be?

  The number of volumes on the SAN and their goals is the same Site A, the only difference is the size of the volume is smaller because less machines virtual running on this site.

  Replication has been implemented and verified the bi-directional working.

  We use replication on Bay

  OK, here's the problem... When I do a recovery expected, the process stops all the virtual machines on this site that includes the server vCenter/SRM.  I guess that to happen because it's on the same database as my other virtual machines?

  If I run the recovery in emergency mode, vCenter is then moved to the other site and power.  Because the sites are layer 2 and on the same vlan, MRS. watch sites are connected by 2 instances SRM can meet eventhough they are now running on the same site.  This does not seem right to me.

  Can someone suggest a better configuration?

  Thank you

  Brian

  Hello

  There is one instance of vCenter to this place located in the same data as the other virtual machines store

  What are your thoughts on that?  Is this the best way?

  In addition to vCenter VMS residing on the store of data replicated, it's OK.

  I could use the local storage on the ESX servers?

  I think that you can, but it is not recommended, because it creates dependency on the availability of the single ESX host.

  Main VM can be used for fictional settings or my data store?

  I would not recommend this. This will create a mess on the data store. Continue to 1 GB placeholder data store you created and do not replicate.

  MRS. uses SQL Express on the local vCenter VM

  vCenter also uses SQL Express

  Consider that SQL express is adapted to the environment of very small size (don't remember the numbers now). Make sure that you do not exceed the limits.

  1 ESX Server, so no clustering

  There is a single data store volume over the San with all virtual machines running on ESX Server

  This host has sufficient capacity to run all the virtual machines together (Site A and Site B)?

  I recommend having two hosts for prallele and accelerate the recovery process (multiple virtual machines can be powered on simultaneously).

  According to the requirements of the SRM, there is a separate instance of vCenter operating as a virtual machine, and it is not in bound mode.  Should it be? / Should it be?

  You don't have to configure them in bound Mode. This is for ease of management only (license, roles and inventory)

  OK, here's the problem... When I do a recovery expected, the process stops all the virtual machines on this site that includes the server vCenter/SRM.  I guess that to happen because it's on the same database as my other virtual machines?

  Yep, do not put vCenter VM on the VMS data store and reproduce at all.

  If I run the recovery in emergency mode, vCenter is then moved to the other site and power.  Because the sites are layer 2 and on the same vlan, MRS. watch sites are connected by 2 instances SRM can meet eventhough they are now running on the same site.  This does not seem right to me.

  Do not replicate vCenter / SRM VM and that will not happen.

  Michael.

• SRM Server regenerate - certificates

  Hello

  I had to rebuild a recovery site SRM server. There was no backup. The database, the DSN and the application install fine however, when I connect to my server protected site vcenter SRM, I get a certificate error

  Failed to connect to the SRM 'DC' primary server in Server SRM "Secondary Site. SRM "DC" primary server cannot validate the «recovery site srm server.com:8095» Server SSL certificate The certificate of the remote host has these problems:

  Certificates to host television is not complete. Reason.MSG

  On the recovering VC site when I try to configure, I get the following site.

  Call 'DrRemoteSiteManager.ProbeDrConnection' to object 'DrRemoteSiteManager' on the server 'sdsrm01.gbn.com' failed.

  I read somewhere that if MRS is not uninstalled cleaning you will have problems to connect to a new server.

  How can I remove old certificates SRM of the recovery and the protected site of virtual centres?

  Thank you very much!

  Hello

  AFAIK, if one of the servers SRM is lost and no backup is available - you must reinstall both SRM and re-create the configuration from scratch.

  It's not just about certificates, DBs SRM on the two sites must be synchronized.

  Michael.

• Best method for SRM

  With 5 guests and replication of VM 75 which method is preferred for best practices

  (1) deploy vCenter SRM

  (2) deploy SRM in dedicated VM (uses vCenter, database)

  (3) deploying MIS in dedicated VM (separate database)

  Hello

  Second option is the best option that is deployed in dedicated SRM VM (uses vCenter Database) because

  The MRS Server works as an extension to the vCenter Server on a site server. Because the MRS server depends on vcenter Server for some services, you must install and configure vCenter Server on a site before you install SRM.

  SRM benefits of vCenter services, such as storage management, authentication, authorization, and personalization of comments. MRS also uses the standard set of vSphere administrative tools to manage these services.