SRM point again vCenter

Similar Questions

• 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

• 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

• Best practice help to spend again vCenter with linked Clones

  Hello everyone

  I searched for days, but couldn't find a way clear of hover over our view 5.2 installation of a new vCenter.  The equipment was aging, and we decided to upgrade and move to 5.5.

  We have rebuilt and forwarded via our guests not VDI to the new vCenter 5.5 environment. I found a few documents, but nothing that tells us if it can be done actually.

  We tried to go in the service of the composer initially to the new instance of vCenter and maintenance, we do the DB on the old Victoria Cross, if it worked I émigrerait the DB above the new Victoria Cross

  We first tried these steps however VMware Documentation Library after removing the old VC service composer and installed on VC New (with ODBC connections mapped to the old VC) it wouldn't work.  We were moving to the VC 5.1 leaving guests ESXi running VDI attached to 5.1

  Then I did more research and discovered the related clones are all related to the database of the old VC and moving them is not possible per this KB KB VMware: workstations managed by moving between servers view vCenter is not supported

  I saw an article here that suggested dumping a bunch of DB and rebuild the new VC with the same name and IP address, but I can't do so because the new instance is already upwards and on a new host name / IP migrate view VCenter (with linked Clones) to new hardware

  I also found this where someone is in the same boat and suggested to recreate pools.  The discussion is not in the details so I wonder if someone can clarify this: migration View Composer and vCenter

  I have about 20 people on VDI in a combination of clones using 3 connected pools and personal drives.  Given that all the info from linked clone was linked to the former base of VC, it doesn't seem wise to move it to the wire.  This would be possible: I still have the base image with all the snapshots for each pool.

  • Persistent backup drives
  • Note the configuration of each pool
  • Disable the commissioning
  • Create DB on VC 55 composer vacuum
  • Create the ODBC connection for composer on VC 55
  • **
  • Do more ESXi hosts to 55 VC
  • Remove existing VMs (will be not able to connect to them at this point anyway)
  • Remove the old VC entry admin view / delete existing pools
  • Install the composer on 55, and then tap new ODBC
  • Create new instance vCenter in Admin 55-pointing mode
  • Recreate pools
  • Import and attach persistent disks (http://pubs.vmware.com/view-50/index.jsp?topic=/com.vmware.view.administration.doc/GUID-BDFCCEC8-682F-4421-8810-06108CBE8D20.html)
  • Recreate events empty DB on 55
  • Reconfigure the parameter DB events in Admin mode

  Any help would be greatly appreciated as I can't find an exact way to do

  Well, I'm pleased to say it worked! I had a few problems by removing existing pools. View repeated deletion but nothing happened. In the end I had to use ADSIedit to connect to the server to manually remove all the old discs VM and pool

  After the installation of the composer on the VC 5.5, I was able to create a login in admin mode and then start to re - create the pools.

  We were able to successfully reattach each disc persistent owners planned.  Did some spot checks and desktop users, bookmarks etc. all worked

  It is a tedious process, but it does not work. I hope that VMware can create an article for it.  God knows that I searched for days, I had to read a lot of things just for this plan.

• vRanger connection 7.1.1 migrate again vCenter

  Hello!

  I have to build a replacement vCenter server in a new physical data center and we are * not * re-use of existing vCenter DB, it will be a new database.

  I read a few forum messages:

  http://en.community.Dell.com/TechCenter/data-protection/f/4784/t/19555352

  The conflicts of the article above with Guide from Dell:

  https://support.software.Dell.com/vRanger/KB/82362

  The replacement vCenter server is already online, I just need help to plan my activities of migration in order to ensure the backup jobs/history will not be lost.

  Thank you!

  -Shaun

  While the support KB illustrates the method to directly modify the database connection vRanger table, I would recommend a case of pension to the best advice of opening.

  If you go down the road to edit the database, please note that incorrect updates or deletions to the data in the database can make it unusable. Please make a backup of SQL Server database or save the prior VM (using vRanger connection) vRanger connection for any changes.

  It is best to open a pension case.

  I will add a new element of the road map for vRanger connection consider whether we can allow editing of the address of vCenter.

• Migrate guests again vCenter without maintenance (vCenter 5.0 to 5.5) mode

  Greetings,

  I would like to move some 5.0 ESXi hosts that are in a cluster on 5.0 a 5.5 vCenter vCenter news without the guests off the power. Is this possible? I've read a lot about demanding in maintenance mode and then saw an old article (KB1002314) that describes simply disconnect them vcenter and adding them to the new vCenter (it was for v3.0 version). Maybe it can still be done? Article, "VMware recommends the removal of the VirtualCenter and VMware HA services management agent later." -j'imagine this would still need to happen.

  I also read this, which suggests the same thing is possible: http://www.yellow-bricks.com/2009/04/17/the-basics-moving-hosts-from-one-vcenter-server-to-the-other/

  
  Any help is appreciated,

  Rick

  As soon as the hosts are connected to the new vCenter Server, the required bits are updated on the hosts, and you should have no problem with that. I did with 4.1 hosts and guests 5.x and have any problems yet. What is important - and taken in charge in your case - is to always check the interoperability between products like ESX/ESXi hosts and vCenter Server to avoid the issue (see VMware product interoperability matrices)

  André

• pointing to vCenter Server Settings on 5.1

  It seems that we are unable to remove an erronious entry that has been added since the vSphere client heavy and clicking "Edit" on the "Advanced settings" area of the vCenter management zone in the Web Client results in a blank window.  Is it a good way to remove the keys from vCenter 'configure the Advanced Server settings?

  Thank you.

  monderick wrote:

  It seems that we are unable to remove an erronious entry that has been added since the vSphere client heavy and clicking "Edit" on the "Advanced settings" area of the vCenter management zone in the Web Client results in a blank window.  Is it a good way to remove the keys from vCenter 'configure the Advanced Server settings?

  Thank you.

  The parameter is visible in the vpxd.cfg file (located in C:\ProgramData\VMware\VMware VirtualCenter)?  It's a file in xml format.  If it is there, delete the entry associated with the parameter.  I think you must restart vCenter Server service for the change to take effect.

  As always, make a backup of the existing file, test, dililgence, etc, etc, etc.

• Pass vCops again vCenter

  Noticed that when I migrated all my hosts for the new vCenter 5.1 VAPP vCops does not. The virtual machine of the user interface and the virtual machine Analytics has migrated simply not vApp. Is it possible to export and then import the VAPP with powercli?

  Thank you

  Andy

  This seems to be an error in documentation PowerCLI 5.0.1. In PowerCLI 5.1 Release 2 this example uses the - location setting.

• Migrate guests again vcenter

  I have a new vcenter all configured. I can not just add hosts without removing them from the old Vcenter first? What a bad way to do it? I have only two hosts. I've set it to be the same as the old vcenter. I don't want to stop the virtual machines... I read the other thread on the displacement of the hosts, but I do not have active CVS.

  unplug and then remove and add the host in the new vCenter Server.

• Migration 4 and 3.5 ESX hosts again vCenter Server 4.0

  I'll put up a new vCenter Server 4.0 with an Oracle database to take the place of two vCenter using express databases included. They are both on the hosts recommended 5-50 VM for the Express database, oops.

  The first is vCenter 4.0 which uses the express database included is on a Dell 1950 server. ESX 4.0 hosts are on 2 groups on Dell blade servers that have 5 blades per cluster and are using storage arrays EqualLogic iSCSI for data warehouses. More there are a few individual Dell R900 and Dell R710 servers use local storage connected to the vCenter.

  The second is vCenter 2.5 that uses the express database included running on a Dell 2950 server with, like 20 other Dell running ESX 3.5 of 2950 using local storage.

  Looking for a vision a little and advise the host migration to the new server vCenter Server.

  Thank you... Jim Hurley

  I would say the easiest would be to create new vCenter new host OS (I would choose 64 bits that will put you in the conditions required for 4.1).  Once the new vCenter Server online, I then install a standalone license server for your VI3 hosts, then begin to disconnect and remove other environments and new hosts.

  Stand alone license server can be found

  http://downloads.VMware.com/d/details/esx_35_licenseserver_dt/dGViZGVoKmJqQA==

• SRM works with vCenter Foundation?

  I guess I'll just repeat the topic for this issue. =)

  Site Recovery Manager work with vCenter Foundation on the two sites, or require a full blown vCenter?

  Thank you!!!

  It of course works, Im using the Foundation on both sites.

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

• 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

• vCenter 5.1 U3 "embedded" Windows-> updated to 6.0 not embedded u2, appliances?

  Trying to find documentation, but you're not exactly what I'm looking for - in the hope that you just happen to know!

  I need to get a system for 6.0 vsphere vcenter u2 with the version of the device of vCenter and the PSC - currently 5.1 U1a with vcenter and components running on a single windows server SSO.

  I know (or believe) that I've upgraded to 5.1 U3 before I can move to 6.0 - but I'm not, of course, is if a 5.1 windows U3 can in fact be upgraded to a PSC embedded and vcenter?

  I need PSC upgraded to join an already existing domain of vsphere SSO (the existing system is autonomous).

  So is the path:

  updated 1) level up to 5.1 U3, then

  (2) upgrade to vcenter/sso embedded device, then

  install 3) new embedded device that has been installed in the existing field of vsphere, then

  (4) re-point the vcenter to newly created standards body?

  Tips/pointers/traps to know are all appreciated!

  I guess that is not easy and medium among the supported options to go to old windows vCenter to newer device via the process of upgrading (we usually upgrades).

  You should probably do a migration.

  I did something similar here a few months ago - had a Windows 5.1 VC and necessary upgrading to 6.0 device. Only in my case, the unit was supposed to have a built-in COPS. Anyway, after reading a lot of articles of migration, I ended up using the instant fling of the inventory: InventorySnapshot who doesn't have everything, however saved me a few hours of manual steps.

  Where you decide to go the same route (which probably isn't the only option), the General steps could be:

  (1) install a new device 6.0 running PSC

  (2) install a new vCenter1 Unit 6.0 running, add it to the domain SSO of PSC, created in step 1)

  (3) to migrate the objects of the inventory of the former vCenter again

  The instant fling of the inventory is not migrate / copy everything. AFAIR it cannot do things like tags and distributed switches (I could be wrong on some of these so check back) but in my case, I was more concerned with the structures of folders and for those that he save me a few hours. Don't me remember now how I moved customization specifications, however that was a script to export / import kind of thing as well. I also used RVTools to create a snap of the inventory before the migration information so that I could easily find all objects where they would get lost during the migration, however I did not.

  According to your complex infrastructure and vCenter in use inventory objects, you might have to do more research and work to make a difference to new vCenter. There are a lot of messages and even prepared scripts out there for the migration of vCenter.

  I hope this helps.

• vSphere WEB client falha ao try access o Serviço SRM

  Estou logando no vSphere Web client e e quando tento access o SRM appears uma falha atenticacao mensagem e os sites are offline. Very ja alterei a senha da conta do Serviço SRM e mesmo assim nao works.

  A conta pra instalar o e a mesma as esta utilizando atualmente SRM used? Caso afirmativo, o fato ter alterado senha pode ter glass o funcionamento do SRM, uma vez that essa senha armazenado fica na base RS, e para atualiza - e rodar o instalador SRM e again Chipre selecionar o option change.

  O bind a seguir mostra em details o principle: VMware KB: change the account to access the server vCenter Site Recovery Manager