vCenter server recovery?

Similar Questions

• vCenter Server Recovery of Cluster has failed (Site A to Site B)

  Hello community VMWare,

  I was wondering if someone could help understand me the following scenario.

  I have two Sites, and each one has its own VMWare Cluster.

  Site A Cluster goes down, which hosts our vCenter Server.

  The vCenter Server contains all of its components, for example database.

  I want restore vCenter Site b, so as the SAN and the networks are online I could just connect to an ESXi host, browse the data store, import the vCenter Server and turn it on?

  The only thing I could think of who could stop me is a possible file lock.

  All guests will perform in ESXi 5.5.

  I tried searching google but couldn't really find this type of scenario.

  May I use the wrong search words so my apologies to advanced if I missed something obvious.

  Thank you.

  Power on this virtual machine to the other site won't be a problem.

  Since you will be reproducing original VM of the Site A to Site B, they're just files residing on the data store, no locks on them.

  But of the things to think about is, network setting the guest OS etc. If you use a different subnet to the recovery of the site (Site B in your case).

• Restore backups of data to different vcenter server recovery

  Hello

  We have separated closed vCenter in our society in different places, I'm just starting to use Vmware Data Recovery instead of VCB for backups. Is it possible to restore the backup of Vmware Data Recovery of Virtual Machines to a different vCenter Server?

  If you can, you could point me to documentation that shows how?

  Thank you

  Glenn

  You can create another device VDR with the same data from disk (or NAS share).

  Then connect to this device (you can also use the VDR plugin when you are connected to a host, not only when you are connected to vCenter) and wait until it import the backup catalog.

  André

• VMware Data Recovery 2 in a vCenter Server

  Hi all

  I need a base backup of VMS backup solution. I know that each camera VDR is bounded to vCenter server, you might not use vcenter several with one camera VDR. But in a sense the opposite? I use several VDR devices with a vCenter server? I know about the limits of the VDR and probably I can achieve limit of 2 TB and only solution in this case use another camera VDR, but I don't know if it is possible to use more than a VDR with a vCenter.

  You can use up to 10 of VDR with a VirtualCenter.

  Look at the "VMware Data Recovery Administration Guide" on page 16:

  Special data recovery Compatibility Considerations:

  Ten aircraft recovery backup of data for each instance of vCenter server.

  Paul

• VMware vCenter Site Recovery Manager Server services stop auto

  SERVER VMWARE VCENTER SITE RECOVERY MANAGER, service stops automatically.

  Section of VMware vCenter Site Recovery Manager, pid = 2084, version = 4.0.0 build = build-192921, option = released
  [2010-12-19 08:39:33.595 06868 WARNING "App"] Cannot create the writer console
  [2010-12-19 08:39:33.611 04220 info "App"] Set of dump dir "C:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Site Recovery Manager\DumpFiles"
  [2010-12-19 08:39:33.611 04220 info "App"] The initialization of the DBManager
  [2010-12-19 08:39:33.736 04220 info "App"] Current working directory: C:\Program VMware vCenter Site Recovery Manager\bin
  [2010-12-19 08:39:33.736 04220 verbose "ThreadPool"] TaskMax = 10, IoMin = 1, IoMax = 21
  [2010-12-19 08:39:33.736 04220 verbose "ThreadPool"] Definition of MTA COM threading model
  [2010-12-19 08:39:33.736 04220 info "App"] Try DrExternalRecoveryApi
  [2010-12-19 08:39:33.736 04220 verbose "App"] Plugin path 0: dr-external-recovery - api dll
  [2010-12-19 08:39:33.736 04220 verbose "App"] Absolute path of the plugin 0: C:\Program VMware vCenter Site Recovery Manager\bin\dr-external-recovery-api.dll
  [2010-12-19 08:39:33.736 04220 info "App"] Try RecoverySecondary
  [2010-12-19 08:39:33.736 04220 verbose "App"] Plugin path 1: dr-secondary - recovery.dll
  [2010-12-19 08:39:33.736 04220 verbose "App"] Absolute path of the plugin 1: C:\Program VMware vCenter Site Recovery Manager\bin\dr-secondary-recovery.dll
  [2010-12-19 08:39:33.736 04220 info "App"] Try SanProvider
  [2010-12-19 08:39:33.736 04220 verbose "App"] Plugin path 2: dr - san - provider.dll
  [2010-12-19 08:39:33.736 04220 verbose "App"] Absolute path of the plugin 2: C:\Program VMware vCenter Site Recovery Manager\bin\dr-san-provider.dll
  [2010-12-19 08:39:33.767 04220 'Local' info] Created from the ./locale/ locale subsystem with in default locale.
  [2010-12-19 08:39:33.783 04220 info "SrmServiceInstance"] DrExtApi Instance of Service is initialized.

  Post edited by: a.p. (VMware Community Manager)

  Moved to the 'Site Recovery Manager' forum and edited the object line to fix the formatting

  While I can't give you a solution, I can share that I had a similar problem with an SRM installation.  Like yours, mine was a working facility which, for some strange reason, began to exhibit the same symptoms.  Start the service, in a second or two, stopped service.

  I opened a ticket with VMware on the issue and in more than three months of back and fourth Exchange with various Tech support I have ever received a satisfactory answer on what caused it.  The 'solution' they gave me was to remove the database SQL RS and re - install SRM.  This 'solution' has worked, but if this question comes up, I'll probably have to back unpleasant, emphasizing the fact that they solve the problem.

  I wish I could be more help, but that's it.  I feel your pain.

• vCenter server password recovery?

  Hey guys,.

  I deployed a vmhost 3 with storage networking, about 3 weeks ago. I installed the unit of vcenter server and everything worked fine.

  Today, I am not able to connect to vcenter server at all... He told me the password is incorrect... nothing to my knowledge, and no one has changed the password... y at - it a way to recover it or reset it? Help, please

  Hello

  It is with a correct domain account?

  Take a look at

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

  and see if it helps.

  Many tx

• A vCenter Server failure recovery

  Hi all

  I'm relatively new to VMware and now find myself with a serious and perplexing problem.  We have a cluster of two ESXi hosts with approximately 20 mV for connections a DVS.  Recently, we noticed that the Server vCenter, who also works as a virtual machine has become inaccessible.  Using the VI Client I reached the host that the vCenter Server is running and found alive, but without a network connection.  Reviewing its network settings, I found that he was still the real network set up but it was not "connected".  I tried to check the 'connected', but would receive enigmatic "caused by 0" error message in the newspaper work.  Tried to restart the server vCenter Server, no change.  Tried to change the setting so that it is turned off, no change.  Finally, I made the tragic decision to remove the connection network altogether and try a new.  Although the deletion went beautifully, but as you can probably guess, I now can't add a network card!  In fact I can make any change for the network adapters from one of my virtual machines due, I guess, to the configuration of the DVS and that, even if they are fortunately pumping packages in and out through their 'data plan', the 'control plan' of the switch DVS is located somewhere in the bowels of the vCenter Server...

  My question is the best way to recover my vCenter Server without affecting my virtual machines.  Should I create a new server vCenter Server on a physical server and support clusters with its two hosts?  How this would affect my productions receive VMs? or y at - it an easier way?  What happens if, on the host where my vCenter VM is running, I had to remove one of the network adapters of the DVS back to the simple virtual switch - I was then able to use this network adapter to add to my vCenter Server and get it back up and communicates with the two hosts?

  As all my virtual machines are running without problem, I want to ensure I can retrieve my vCenter without negatively impacting on them or do something stupid (yet!).

  I am grateful for any light you can on this for me...

  see you soon,

  William

  Hello

  You can remove a NIC of the DVS and create a simple switch and change the virtual machine to configure to use this switch.

• vCenter Server

  In case the server vCenter Server has encountered a problem and needs to re-setup of vCenter, what happens to what follows? They will always work?

  1. high availability

  2 DRS (automatic)

  3. distributed switch connectivity

  4 vSphere replication

  5. Advanced vSphere of data protection

  6 site Recovery Manager

  7 cluster VSAN

  During the time where the vCenter server is unavailable.

  1. high availability - Yes, but the management of Cluster HA is possible only when your vCenter gets online

  2 DRS (automatic) - No.

  3. distributed communication switch connectivity - Yes, the VMs will not face questions, data flow is managed completely by ESXi hosts, but your DVS control plan is not available to change the Setup in it.

  4 vSphere replication - work should, don't know if.

  5 vSphere Data Protection advanced - should work, not too sure.

  6 site Recovery Manager - no.

  7 cluster VSAN - Yes, but the handling of the VSAN that we are using vSphere Web Client is going to be affected.

  and if you need to re - install server vCenter completely. so in this case, you need to take action based on how you re - install your vCenter. For example, if you have fresh installation complete you vCenter server then you need to start building your vCenter Server inventory and take steps to add your ESXi hosts in this new inventory.

  many different references

  Distributed failure vSwitches and vCenter, what's the problem?

  VMware KB: Spend an ESX/ESXi host with vDS to a vCenter Server to another

  VMware KB: Move a managed ESX ESXi host to a vCenter Server to a different Server vCenter

• vCenter Server Appliance error 6.0 #1009 after update

  Hi guys.

  A few days ago I updated my client vCenter Server device of vpx of b. 6.0 to 6.0 update works fine, but when I log in web client, I have error #1009.

  

  Journal

  

  I tried all the work arrounds:

  Stop the web client, clear the cache of serenity, start the web client and nothing.

  I disabled the Update Manager and web client and Site Recovery Manager plugins works very well. Then I reload Update Manager and Site Recovery Manager and fails again.

  Update Manager to update to the latest version and fails again.

  Any tips? Help? Wishes?

  I just opened a SR with Vmware, but I don't always have a solution or something. I want to wait for a solution before the restoration, but I can't live without feature Site Recovery Manager.

  Thank you

  Kerchief!

  VMware support solved this situation.

  My browser has settings to Spanish. So, I changed to English languaje of firefox, and the Vmware web client works very well!

  Greetings Vmware support.

• How to update 2 for 4.1 vSphere vcenter server?

  I have vcenter on a primary site and also a site of recovery (with SRM) and I also have VMWare update manager.  We have balance sheets quarterly internal vulnerability run and two servers vcenter came with high vulnerabilities with crossing of directories on the two ports 9087 and 9084.

  Here are the CVE Vulnerability:

  http://CVE.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4404

  We have installed 4.1 and in vSphere client if I do help > about it says 4.1.0 Build 491557.  How can I put it to U2?  I tried scanning with VMWare update manager, and he came to the top.  I downloaded the 4.1.0 - 493063 full blown vSphere which includes 2 update that is supposed to address this vulnerability in my opinion.  The issue is when I try to launch it on one of the vCenter servers it does not give me an option to upgrade.  When I run the installation of the vCenter server it gives me "edit mode configuration" linked or "Uninstall" I don't want to do either of these options... I just want to improve as I did from 4.0 to 4.1.

  Thanks for the help.  I just download the update 2 "patch" If there are so.

  If you perform the upgrade:

  You can download the SRM 4.1.2 here:

  https://my.VMware.com/Web/VMware/info/slug/datacenter_downloads/vmware_vcenter_site_recovery_manager/4_0

  Notes release & installation notes:

  http://www.VMware.com/support/SRM/srm_releasenotes_4_1_2.html

• VCenter Server installed as a virtual machine within a ESXi servers it manages?

  Hi all.  I'm new in the world of VSphere... still in my evaluation period.

  I have only a single ESXi server running at the moment but plans to add a second later for high availability, vmotion, increase general capacity, etc.  They are / will be ESXi running on the internal storage and the virtual machines running on a shared SAN.

  Today, I installed VCenter Server 4 on a server at bottom of range/Office that I was carrying around running XP Pro x 64.

  As I was installing I read the guide installation and to my surprise, it seems to recommend that I have installed VCenter Server 4 as a virtual machine on my ESXi host.

  Now maybe I just spent too much time setting up my without new Lefthand requiring a 'witness' during the failover of one SAN to another... but I was under the impression that VCenter Server is not designed simply to host configuration, but is also designed to act as a 'witness' or to take account of quorum whenever a failure scenario occurred on one of my ESXi hosts.  I also noticed the VCenter Server features of a port "heartbeat", which I suppose one would use for the ESXi server heartbeat, but perhaps it is used for "connected mode" with other VCenter servers (I was intending to use only one since it is a small scale installation) I also felt that it would be useful enough to restore a damaged or shot ESXi host.

  So my question is, if my ESXi host dies and it is where I have VCenter Server installed, then high availability will be unable to work?  I guess there are going to be other issues with me unable to access VCenter Server while I have an ESXi host shot, too, as a greater difficulty to get the ESXi up?

  Maybe I'm wrong understand the purpose of the VCenter server... maybe it's not something that's necessary for HA, recovery, etc. and acts only as a configuration tool until something is wrong?  Or maybe I misunderstood the installation guide and they recommend only installing VCenter Server on an ESX box... they don't want this ESX box to be part of the group that manages the server?

  Finally, if indeed they recommend I install this on a ESXi host manages... would I ideally be install this for local storage on the server (where I installed ESXi) or on the SAN (where all my other virtual machines are installed)... or is it just personal preference?

  Thank you!!

  When you add hosts an active hemagglutinin vCenter cluster HA agent is installed on it.  This agent is what is actually the HA.  While necessary to add new hosts in a cluster and configure some specific parameters of vCenter vCenter's agents HA are self-sufficient and can handle HA failover so vCenter is offline.

  You must install the vCenter VM on SAN storage, so that he can use the vMotion, sVmotion, DRS, HA, functions etc. that require a SAN.

  -MattG

  If you find this information useful, please give points to "correct" or "useful".

• VCenter Server (standard) useful with ESXi is free?

  Trying to decide what, if anything, to actually buy VMware.  The free ESXi product license is... enough.  I would really like to central management, backup or read/write capabilities with rcli (piracy without installation - I think I said that correctly).

  My question is this.  There is a VERY big jump in $$$ of the products beforehand essentials range or better (I think that the Standard line is unnecessary).  I currently have 5 VMware servers (2 under Server Linux 2.0 on server newish hardware, each, 2 ESXi 4 server about 4 VM running on old jobs as each House a unique VM (due to higher disk IO) and ESXi 3.5 server running on 32-bit with 1 VM hardware).

  In any case - with a mixture of mission critical production VM and VM little criticism that don't necessary not to live on a San and puff SAN bandwidth, I'm not sure I want to limit myself to 3 physical machines.  It would be probably enough for the next 5 to 10 years, but it would affect my SAN strategies and I have to buy at least 1 or 2 new costly servers.

  So I thought that maybe just get the vCenter Server for centralized management would work.  I always have 2 or 3 more enjoyable new servers ESXi 4 on the San with mission critical servers, while continuing to have 2-3 of older machines with individual local readers VM (I like to keep virtual for purposes of disaster recovery for) running.

  I can't find any information on knowledge if it would work, and it would offer benefits etc..

  You cannot add free ESXi to vCenter. Adding a host requires the inside the host vCenter Agent license.

  Sorry about that.

  Marcelo Soares

  VMWare Certified Professional 310/410

  Master virtualization technology

  Globant Argentina

  Review the allocation of points for "useful" or "right" answers.

• Unable to activate plugin vCenter data recovery

  I installed the plugin for vCenter Data Recovery and I went into the Pugins manage and it is listed as disabled. If I right click it nd select activate, nothing happens.  No error, but it does not either. Someone at - there experience this problem?

  -Daniel

  chiazynloo,

  Build numbers seem to be off - unlike the version numbers correct for Beta 2 or RC build recovery of data and vCenter Server 4.0 RC respectively.  Where did you got these bits?

• How to change the MOB OpenManage integration for vCenter Server registration

  A few months back, I've updated our installation of the vCenter for v2 plugin, now called OpenManage integration for vCenter Server. When you perform the upgrade, we have kept the old base done vs a new installation. During the upgrade process, we deployed the new device under a new name of the computer.

  Everything works well except that we noticed an annoying thing. Registration of the plugin is the former name of the server instead of the name of the new server-oriented. It is validated by looking at the web page MOB: http://vcenter Server/fmt drilling then down through:

  Content--> Extension Manager--> extensionList ["com.dell.plugin.OpenManage_Integration_for_VMware_vCenter"] --> server--> URL string

  The configuration of the appliamnce shows the correct new name of the device and the administration console is accessible via the new name for the device. The only place where we see the old name of the device is in the MOB config.

  We tried to remove the plugin and added, but still cannot change the value of server URL to reflect the new name of the device. Until we solve this problem, I work around the problem by keeping just the DNS entry for the old name of the server in DNS.

  Anyone know who to change the property MOB for the URL of the server?

  I solved the problem.

  I found the following article that shows how to upgrade the extension. I just cut and paste into my current values with the URL of update and now all is good.

  http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2060127&sliceId=1&docTypeID=DT_KB_1_1&dialogID=236869583&StateID=0%200%20236885165

• VMware vCenter Server service stops or restarts at the start of data collection

  VMware vCenter Server service stops or restarts at the start of data collection

  I am using vCenter Server 5.0

  Whenever I have begin to collect data, vcenter service stops or restarts, if I stop data collection and to disable the agent, vcenter service again and works well.

  Please any help!

  Thanks in advance

  It is a known issue, relating to the collection of historical data being enabled (nonzero) in the properties of the VMWare Agent on the Agent status screen.

  Change to 0 to disable/re-enable the agent and it should fix the problem.

  Please open a ticket of level 1 with telephone support if you need more help.