Upgrade SRM

Similar Questions

• Upgrade SRM question

  I'm trying to upgrade the SRM 5.1.1 to 5.1.2. I am invited by the installer as to if I want to overwrite the current record with Vcenter.

  It is not that I have any other choice. I guess that this normal for an upgrade, is that correct?

  Yes, here is the documentation: upgrade the server without Migration of SRM

• VR SRM 5.1 VRM Server vs. device

  Hi guys,.

  I am fairly new MIS program and decided to install SRM 5.1 but I'm not able to find the installation instructions step by step and I noticed a few differences in the terminology I hoped to clarify.

  In SRM 5.0 basic in the Startup tab configuration was:

  1. deploy the VRM Server

  2 configure the VRM Server

  3. configure the connection VRMS

  4 deploy the server of VR

  5 register servers VR

  The terminology for SRM 5.1 configuration in the Startup tab is:

  1. deploy the VR device

  2 reconfigure the VR device

  3 set up the RV connection

  4 deploy an additional server VR

  5. save servers VR

  Although the terminology has changed everything is the same under the hood?  Is there a real difference between a VRM server and a VR device?

  Thank you

  Duncan.

  Hi Duncan,.

  You can find detailed installation and setting instructions to level for MRS 5.1 in the docs of SRM 5.1, here:

  http://pubs.VMware.com/SRM-51/topic/com.VMware.ICbase/welcome/welcome.html

  For more information about the differences between RV in 5.0 and 5.1 SRM SRM, see the following in particular: http://pubs.vmware.com/srm-51/topic/com.vmware.srm.install_config.doc/GUID-E8859207-0D9D-414E-8A2A-CEAC0FCA76A3.html

  For instructions on upgrading SRM and VR 5.0 to 5.1, see http://pubs.vmware.com/srm-51/topic/com.vmware.srm.install_config.doc/GUID-E506E898-D72A-4F21-B24D-30F0F0291847.html.

  For instructions on performing a new installation of MIS 5.1, see http://pubs.vmware.com/srm-51/topic/com.vmware.srm.install_config.doc/GUID-437E1B65-A17B-4B4B-BA5B-C667C90FA418.html.

  For instructions on performing a new installation of VR with MRS 5.1 5.1, see http://pubs.vmware.com/srm-51/topic/com.vmware.srm.install_config.doc/GUID-BDBF1B7C-C1EE-4598-B92D-F824524F386D.html.

  Hope this helps,

  Stuart

  Documentation for VMware SRM

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

• I'm looking for help to share best practices to upgrade the Site Recovery Manager (SRM), if someone can summarize the preparatory tasks?

  I'm looking for help to share best practices to upgrade the Site Recovery Manager (SRM), if someone can summarize the preparatory tasks?

  Hello

  Please check the content below, you may find useful.

  Please refer to the URL: Documentation VMware Site Recovery Manager for more detailed instructions.

  Important

  Check that there is no cleanup operation pending on recovery plans and there is no problem of configuration for the virtual machines that protects the Site Recovery Manager.

  1 all the recovery plans are in ready state.

  2 the protection status of all protection groups is OK.

  3 the status of the protection of all the individual virtual machines in the protection groups is OK.

  4 the recovery of all groups of protection status is ready.

  5. If you have configured the advanced settings in the existing installation, note settings you configured before the upgrade.

  6 the vCenter local and remote server instances must be running when you upgrade the Site Recovery Manager.

  7 upgrade all components Server vCenter Site Recovery Manager on a site until you upgrade vCenter Server and Site Recovery Manager on the other site.

  8 download the setup of Site Recovery Manager file in a folder on the machines to be upgraded the Site Recovery Manager.

  9 make sure no other facilities-\no updates windows restarts done shoud

  Procedure:

  1. connect to the machine on the protected site on which you have installed the Site Recovery Manager.

  2. backup the database of Site Recovery Manager by using the tools that offers the database software.

  3. (optional) If you upgrade of Site Recovery Manager 5.0.x, create a 64-bit DSN.

  4 upgrade the instance of vCenter Site Recovery Manager server that connects to vCenter Server 5.5.

  If you upgrade a vCenter Server and Site Recovery Manager 4.1.x, you upgrade the instances of vCenter Server and Site Recovery Manager server in the correct sequence until you can upgrade to Site Recovery Manager 5.5.

  a upgrade vCenter Server 4.1.x to 5.0.x server.

  b Update Site Recovery Manager of 4.1.x to 5.0.x.

  c upgrade server vCenter Server 5.0.x to 5.5.

  Please let me know if it helped you or not.

  Thank you.

• 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 upgrade rollback

  I've got failback, an upgrade of MRS. 5.0.2 to 5.0.1 only success on sites protected and recovery improvements due if one is 5.0.1 and 5.0.2 is and I need all the back working on the previous version until I can solve the problem. I have a BAK file backup of the external SQL DB and I saw MRS VM before the upgrade.

  The plan that I thought would be:

  1. Stop the VM SRM upgrade
  2. Return to the upgrade
  3. The server of SQL, right-click the DB, select tasks and restore the DB in the BAK file
  4. Start the VM SRM upward

  I'm afraid that there will be problems with VCenter (5.0) if as surely the successful SRM upgrade would have made changes here too for example it is the update plugin MRS. visible in the VI client and who would still probably stay if I performed the action above. Any thoughts?

  Hello

  The official literature suggests the following procedure:

  To return to an earlier version, uninstall the current version of the SRM of the protected server and the recovery sites.

  uninstall the plug-in of MRS and restore the database SRM for the backup that you made before you updated the

  SRM server. You can then install the previous version and use the restored database.

  You can find more information on page 40 in the Administrator's guide.

  IMO your plan should work. But you probably need to run the installer SRM in mode "Change" (same page 40 in the Administrator's guide) to repair the connection to vCenter.

  Michael.

• shared recovery of SRM - upgraded site

  I would like to ask communities how others deal with the vSphere / SRM / new in the version of the SRA. We have a number of clients who are matched with ourselves. All of us are in version 5.0 (vSphere + RS)... Us v4.1 and EVERYONE upgraded to v5.0 when we had a new client came on board who needed v5.0 (as you know)... Now we have a number of customers who would also like to use this service and vSphere 5.1. This would mean that we would need to upgrade to everyone and ourselves to 5.1.

  For me the shared recovery site becomes unmanageable for these reasons... An administrative nightmare of site VMware release new versions on a regular basis that are shared recovery.

  Am I missing something?

  Hello

  It is not problem, but unfortunately there is currently no plan to this address. At least not in the near future.

  Consider opening a feature request. As more customers will request this feature, most likely it will be addressed in the future provided.

  http://KB.VMware.com/kb/1002123

  Michael.

• Upgrade from 5.1 to 5.5 with SRM

  Currently I have VC 5.1 installed and have set up a RS. If I'm on 5.5 VC, will always work SRM or I will have to install and configure a new version of it?

  If his 1082082 it would be 5.1.1.

  It will work only with vCenter 5.1 and 5.1 U1, not 5.5.

  

• Terminal srm command no longer works

  Since Apple has removed the installation Secure Empty Trash, I have used to safely remove files via the Terminal using the m srm or the srm - rf commands.

  I just upgraded to El Capitan for OS X Sierra, and this command seems to no longer exist?

  Anyone know what happened?

  I have not yet updated, but you can install it using the Homebrew (http://brew.sh/).

  %> brew install srm

• Upgrade to vSphere 5.0

  Hello

  We intend to upgrade our infrastructure to vSphere 5.0 (approximately 30 guests and 3 vcenters) 5.5 or 6.0.

  Few of my friends suggested to upgrade to 5.5, because they think this is the stable version. But personally, I'd rather spend to 6.0.

  What are the issues involved in the upgrade to 6.0. The update will affect my VMs after hardware upgrade.

  Or should I get with 5.5?

  Background information:

  We have the following tools:

  • Current VCenter don't use SSO. What are the issues involved in upgrading this vCenter for vCenter SSO based.
  • My data stores are based FC.
  • I have the following tools:

    • VMware vCOPS

    • VMware LogInsight

    • VMware SRM

      Thanks in advance

      Kind regards

      Nithin

  Hello

  First check the compatibility. This means that you must validate your solution backup, storage and physical servers are compatible with your target (vsphere 5.5 / 6.x and SRM vsphere).

  For the vCenter 6, I don't think that there is some sort of in place update since version 5.0.

  This means that you may go your vCenter to version 5.5, and then to version 6.

  What I recommend with your vCenter number is to have different PSC. Instead of using a full vCenter, external use PSC is the best way for your architecture.

  You can install the new vCenter too and re - import the esxi inside too...

  Kind regards

  Jeremiah

• U2, SRM and SRA vCenter 6.0 compatibility

  Hi all

  We currently have vCenter 5.5 Update 2 with SRM 5.8.1 and SRA for EMC VNX (EMC VNX SRA with MirrorView Enabler for 5.0.39 VNX) and want to upgrade to vCenter 6.0 Update 2.

  In the table below (from VMware interoperability matrices):

  VMware Site Recovery Manager	6.1	6.0	5.8.1
  VMware vCenter Server 6.0 U2	THERE
  VMware vCenter Server 6.0 U1	THERE	THERE
  VMware vCenter Server 6.0		THERE
  VMware vCenter Server 5.5 U2			THERE

  I see that vCenter 6.0 U2 only supports 6.1 SRM.

  I looked here:

  Download VMware Site Recovery Manager for disaster recovery and planned migration

  For the SRA that I need (EMC VNX SRA with MirrorView Enabler for VNX) and couldn't find it there.

  This is a chart of the VMware Compatibility Guide:

  Name of the partner	Name SRA	Version SRA	SRM version (s)
  EMC	EMC VNX SRA with MirrorView Enabler for VNX	5.0.2 / 5.0.39.139	5.8 SRM | SRM 5.1 Update3 | SRM 5.5 Update1. SRM 5.5 | SRM 5.1 UPDATE 2 | SRM 5.1 Update1 | SRM 5.1
  EMC	EMC VNX SRA with MirrorView Enabler for VNX	5.0.2.77/5.0.39.149	SRM 6.0 | 5.8 SRM | SRM 5.5 Update1. SRM 5.5

  According to this, there is no SRA for MRS 6.1.

  My questions are:

  1 MRS. 6.0 works with vCenter 6.0 U2 (I know that it is not taken in charge with respect to the interoperability of VMware)?

  2. for employees of VMware - do you know if there is an adapter (for EMC VNX) to version 6.1?

  Bottom line: I am looking for EMC VNX SRA with MirrorView Enabler for VNX SRM 6.1 (which is the only currently taken SRM supported by vCenter 6.0 Update 2).

  
  

  Thank you!
  

  Hello Daniel

  Your questions:

  1 MRS. 6.0 should work with vCenter 6.0U2, but as you mentioned, it is not supported by VMware.

  2. as far as I know, such a DSM is underway. I suggest you speak with your EMC representative to confirm that and give you an ETA.

  Best regards

  Stefan

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

• ESXi 5.1 to 5.5 upgrade

  Hi all

  I intend to spend any esxi 5.1 5.1 to our newly built 5.5 vCenter vCenter army.

  We not have distributed switches, SRM, Vmware view etc...
  Not also concerned historical data in vCenter 5.1

  What is the best way to do it?

  Here is my planned approach

  • Create new cluster on vCenter 5.5 that will even
    as cluster in vCenter 5.1.
  • Disconnect hosts in vCenter 5.1 and register
    ESXi host to vCenter 5.5
  • I guess when I do this standard will all be
    always available as it is esxi host specific not vcenter.
  • We have 5 guests clustered, so I intend to
    remove a host both the cluster and esxi 5.1 to 5.5 upgrade using Update Manager
    5.5 the new vCenter.
  • Given that I don't update facility, I'm not sure will
    switch support will be always there after upgrade. We use iscsi for storage
    and it uses a standard switch. If it is not available I can recreate after upgrade.
  • Anything that suggests on pit fall that I need attention in this plan, please suggest.

  Thank you...

  I did these migrations several times in the past and that you are having problems.

  What I usually do in such cases is to:

  • Disable HA in two groups (the current/old as well as new)
  • Make sure you of EVC is configured correctly to the new cluster (if necessary)
  • disconnect and remove all hosts (one by one) from the old server vCenter Server and add them to the new cluster
  • configure settings like HA cluster, DRS...
  • Once everything works as expected begin the upgrade of the host

  Be sure to reconfigure your backup software (and any other 3rd party software and Add-ons) after migrating to the new vCenter Server hosts.

  André

• vCenter 5.1. Update 3 has no upgrade path?

  The path to upgrading Solution of the matrix of interoperability shows that there is no way to upgrade available in a vCenter Server 5.1 updated 3 or ESXi 5.1 update 3.

  I'm having a hard time to believe that the latest patch for the 5.1 versions cannot be upgraded.  Normally a reconstruction would do the trick, but there are built-in replication and SRM and I need to upgrade in place.   Anyone upgraded the 3 to 5.5 5.1 update update 2 or whatever it is between the two?  I really hope it's just a bug in the interoperability matrix.

  Indeed, this seems odd. However, from the date where the 5.1U3 has been provided (5.1U3 in 12/2014 - 5.5U2 09/2014) there is a good chance that 5.1U3 already contains code that is not integrated in the 5.5U2 yet, but might come with 5.5U3.

  André