U2, SRM and SRA vCenter 6.0 compatibility

Similar Questions

• vCenter upgrade from 5.0 to 5.5 for the new machine, SRM and dvswitch

  Anyone know if it is possible to do a upgrade to vCenter from a machine under windows server 2008 on a new computer server 2012? The database is located on an external computer. All I can see in the upgrade doc is that there is a tool for migrating data with earlier versions, but not when moving to 5.5.

  Also - what implications are there if there's a dvswitch in the site?

  Thank you very much

  Hello

  I guess you run ESXi and vCenter 5.1?

  If it were me, I'd do the following:

  -Install a new instance of vCenter on a new Server R2 2012

  -Turn off the old server vCenter on 2008.

  -Save the remote SQL database vCenter.

  -Install a new instance of the Web, the inventory Service and SSO client. I remind vCenter to use the SQL remote database existing and chose to 'upgrade' when installing vCenter.

  Then you'd be in vCenter server 2012 R2 with a new facility and using your old database that will get upgraded. You will always retain so your dvSwitch information. I'm not sure of SRM, you probably need to reconfigure it to use the new vCenter Server (unless you use IP records or that you can easily return?).

  There are a few things to think about when you really do. Can you afford any downtime on vCenter? What of SRM and your RPO/RTO? The complexity is your configuration of SSO? Use you things like tags in web client (they would get lost in the reconstruction of the inventory service)? What confidence you are on the side of things RS? It is possible to save these configurations, but I'm not sure restore them on 5.5.

  The main thing to consider is the database really. Worst case, you can restore it and turn back on your old vCenter 2008.

  Happy to be told I'm wrong or answer your questions. If in doubt, contact VMware technical support and ask for help.

  Kind regards

  Ryan

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

• Long distance vmotion and cross-vcenter vmotion are incompatible, with MRS?

  We plan our updates of 5.5 to 6.0. Two sites have involved SRM. We would like to be able to deploy to make long distance and cross-vCenter vMotion possible in the future. However it seems that these may be incompatible with MRS.

  Cross-vCenter vMotion requires enhanced link mode. Improved link mode requires the vCenters using the same PSC. A dependency between the protected site and recovery site that would be created by putting the two SRM vCenters in bound mode is a non-starter. You must be able to connect to your vCenter site recovery if the protected site is swept away by a tornado.

  The answer is maybe; Cross-vCenter vMotion is not compatible with SRM unless you create the deployment model with PSC servers redundant load balancing. Locate a CFP that is geographically separated from the protected site. Even in this scenario, it is clear to me if you would have to re-pointer the vCenter site disaster recovery. Again, I think that increased vMotion requires literally the 2 vCenters to be directed to the * same * PSC, CSP not only in the same SSO domain.

  I have a box to open with VMware and I'll share the results if it is useful. The two protected site site and recovery use our company Active Directory as an identity source, but I don't think it will help us if we are in bound mode and lose a PSC.

  Well, the weakness of my logic is in bound mode extended vCenters must point to the * same * PSC.  At least in SRM 6.1 there is some good news here.

  Thank you Federal VMware supported;

  Site Recovery Manager 6.1 Documentation Center

• SRM point again vCenter

  We have decided to take our guests to a new vCenter and don't want a lot with SRM (it is installed on its own virtual machine in the environment and use a MRD).

  To have a quick glance I think I should be able to do a repair on the existing installation of the SRM and point to the new vCenter, during repair I suppose it will ask the IP address of the new vCenter? As a result, I hope to be able to upgrade to 5.0 5.5.8, could I possibly do the upgrade and repoint at the same time?

  I saw the article, but I guess I won't need to follow if the installation program updates the IP for me?

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 2008033

  Thank you very much!

  I think the best option is to do a fresh install, because if you plan to switch to version 5.8, this upgrade path is not supported, take a peek: upgrade of Site Recovery Manager

  Important

  The upgrade of Site Recovery Manager 5.0.x Site Recovery Manager 5.8 is not supported. Upgrade of Site Recovery Manager 5.0.x to a release of Manager5.5.x of Site recovery before upgrade you to Site Recovery Manager 5.8. See upgrading of Site Recovery Manager in the documentation of the Site Recovery Manager 5.5 for more information on the upgrade of 5.0.x to 5.5.x.

  And see what are the documents tells a new installation of vCenter and the MIS upgrade: Types of upgrade that supports Site Recovery Manager

  Type of upgrade	Description	Support
  Update the Site Recovery Manager on-site	The easiest way to upgrade. This path is to upgrade instances of server vCenter Site Recovery Manager-related before the upgrade of Site Recovery Manager server. Run the new version of the Site Recovery Manager installer on the Recovery Manager Server host computer, connect to the existing database of existingSite.	Yes
  Site Recovery Manager with migration update	This path includes improving the vCenter Serverinstances associated with Site Recovery Managerbefore the upgrade of Site Recovery Manager server. To migrate the Site Recovery Manager to a different host or a virtual machine as part of the upgrade of Site Recovery Manager, stop the existing Site Recovery Manager server. Do not uninstall the previous version of the Site Recovery Manager Server and make sure you keep the contents of the database. Run the new version of Site Recovery Manager installer on the new host or virtual machine, connect to the existing database.	Yes
  New vCenter Server installation with migration ofSite Recovery Manager	Create new facilities of vCenter Server and migrate these new instances of server vCenter Site Recovery Manager Server.

  N ° you cannot migrate the Site Recovery Manager Server to a new installation of vCenter Server. Site Recovery Manager requires a single object on the server vCenter Server identifiers that are not available if you are using a new Serverinstallation vCenter. To use a new Serverinstallation vCenter, you must create a new Site Recovery Manager Server installation.

• SRM and HP EVA 8400/6400 error

  SRM with HP EVA-8400/6400 returns an error when you run a test:

  Error - Failed to create snapshots of the replica devices. SRA command 'testFailoverStart' failed. Unable to create snapshot Action to create a shot Snapshot failed because of an error on the table cannot create snapshots of the replica devices. SRA command 'testFailoverStart' failed. Unable to create snapshot Action to create a shot Snapshot failed because of an error on the table cannot create snapshots of the replica devices. SRA command 'testFailoverStart' failed. Unable to create snapshot Action to create a tour Snapshot failed because of an error on the table.

  Response from HP:

  It seems that EVA communicates very well with the Sra So. now, you need to scan for the SRA in SRM and then try to perform the replication again. If she fails to perform replication with the SRM then you will need to contact the VMware team, because that would be a problem with the SRM and not a problem with the EVA contacting the SRA.

  Not sure what Miss us here. I work with the administrator of storage without result.

  We found the problem, it was because of the permission on the user account for the table. Need to be added to the storage administrators group.

• 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

• SRM and vCSHB

  Hi all

  VCSHB is supported with MRS? And if so, what are the advantages and disadvantages?

  See you soon,.

  Rob

  Hello

  Heart rate may not protect SRM:

  Using vCenter Heartbeat with SRM 4.0

  In addition, it found in one of the PDF files:

  Q: how vCenter Heartbeat works with Site Recovery Manager? Heart rate can protect the Site
  Recovery Manager?
  A: currently, vCenter heartbeat cannot protect Site Recovery Manager. However, vCenter Heartbeat can protect the vCenter Server associated with a particular instance of the Site Recovery Manager. According to this scenario, SRM must run on a separate server than vCenter Server. If a vCenter failover occurs while the SRM is the execution of a workflow of recovery plan,

  Michael.

• What is Oracle SRM and why is it used?

  Hello

  What is Oracle SRM and why is it used?

  Thank you

  POOJA

  Hi Pooja,

  SRM is used to combine social networks for businesses that use them for advertising.

  SRM Oracle documents are available on:-https://docs.oracle.com/cloud/social/index.htm

  Kind regards

  eDynamic Experts Eloqua

• Two horizon view infrastructure and a vcenter

  Hi guys,.

  I have not found the information in the guide to validate this installation (installation of two horizon and a vcenter)

  Only indication is for the composer, where it is suggested to use a vcenter for a composer, but in my idea I have no delivery VM with the composer.

  No idea how to find trust information this configuration?

  Thank you.

  Fabio

  Hello Fabio.

  What do you mean by "Installation of two horizon."

  Do you mean multiple connections servers or really 2 different environments.

  I'm making an assumption you mean 2 different environments.

  Yes it is possible I think to use 2 composers with 1 vcenter.

  Just install the composers on a different machine than Virginia and I advice to use different accounts.

  Keep in mind the limits of the composer vmware VMware Documentation Library not to overload your vcenter

  Is it supported any idea that I should advice he not except for a migration and even then, I'll ask the support vmware for more information.

  If you want hard confirmation I would suggest opening a ticket with vmware support VMware - how to file a support request online | United States of America.

  Kind regards

• Move cluster configured with replication SRM and Vsphere

  All,

  We go 2 groups in the near future to achieve a geographical distance between the 2 sites.

  A cluster is equipped with VMware 5.0 replication SRM and vSphere and the other cluster running VMware 5.5 and SRM in combination with replication of vSphere.

  What is the best way to move these clusters, I must stop the replication or interrupt the replication process and are these action to perform on SRM or we need to perform any action on the virtual machine itself?

  I read that a stop is setting the State to not configured including destroy all files in the target directory.

  Does anyone have an experience by physically moving a cluster managed by SRM (and replication of vSphere)

  Any help is welcome

  Thank you

  Gerbert Coolen

  Just pause replication before stop you the VR device on the site target/DR. stop vs break with vSphere replication - VMware vSphere Blog - Articles from VMware

• 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

• Using NetApp SRA with vSphere SRM and suspension

  Hello!

  My understanding is that SnapMirror is no suspension, so as a result, you will only get consistent backups fail?

  My question is, when you use the NetApp storage replication adapter in Site Recovery Manager, you now get supported in standby, as MRS can work alongside the matrix to orchestrate the recovery correctly?

  See you soon,.

  Bilal

  Necessary for suspension of application with NetApp NetApp SnapManager.

  SRM does not add any capabilities of demand for NetApp mise en veille (or another provider of table). SRM monitoring, can trigger and in some cases reverse replication, but it is not change/impact how replication is running.

  If you perform a scheduled migration (or a failover of DR and MRS can communicate with servers SRM & vCenter protected site), SRM will replicate storage, turn off the system VMs graciously and then happen again so it is not necessary in these cases of app-compatible replication.

  Does that answer your questions?

• Using CA signed CERT on 5.5U2 device and SRM 5.8 vCenter (vPostgres)

  Updated all our vCenters to 5.5U2.  Also upgraded to the latest Vsphere replication as well. No problems.  Everything works fine.

  Tried to (re) install with 5.8 SRM components

  A site uses Windows vCenter, and upgrade went well, using P12 CA cert signed during installation.

  Another site using Vcenter device.  When you install SRM 5.8 and p12 cert, receive the following:

  ---

  Could not validate the certificate:

  Details:

  VMware vCenter Site Recovery Manager of the customer are not approved by vCenter Server.

  ---

  and unable to continue

  Tried to install the intermediate certificate on the host Windows SRM.  Also tried to add the intermediate certificate in the P12 cert but the message on the cert is not wrong.

  Think it's something to do with the intermediate cert not given on the server vCenter, so unable to completely validate the cert chain.  Do not know if this can be installed on vCenter device is able to validate the string in this way.

  Recorded a call about that, but I was wondering if anyone has encountered this and that she might have a work around.

  Hi Joel,

  To put done SRM trust certificates in vCenter Server, you must do the following:

  1 copy the cert CA (not sure if only the intermediary would be enough or the entire string) file in/etc/ssl/certs in Vcenter device

  2. run c_rehash in Vcenter device console

  Kind regards

  Asen

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