VMware DR solution without Site Recovery

Similar Questions

• The goal of the "VMware-mount Service for Site Recovery Manager" Service?

  Hello

  We experienced a problem return to SAN replication recently after the maintenance of software packages. When we stopped all services SRM replication started. We could then restart RS and everything was fine. One of the services that we had to stop was the "VMware ride Service for Site Recovery Manager. This does not normally work however and the start is set to manual. I made several test stimulus plans last weekend and has never seen work. Anyone know what is this service?

  Thank you

  Mike

  There literally this name...?

  Normally, the Assembly in vCenter service is used by sysprep/deploy process...

  Sysprep is used by SRM as one of the methods for re-IP-ing a VM, I think we can assume the of the same kind of service, but for a different purpose...

  Concerning

  Mike Landry

  RTFM education

  http://www.RTFM-ed.co.UK

  Author of the book of MRS: http://www.lulu.com/content/4343147

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

• SRA order "matrices of discovery has not not" adv0408 file not found in VMware Site Recovery Manager.

  Hi all

  Can we add several table managers at sites in VMware SRM?

  How to record several managers of the group a table copy in SRA?

  "When I try to add new array manager of second table at one site I get the error message" SRA order "matrices of discovery has not not" adv0408 file not found in VMware Site recovery manager.

  Versions: VMware SRM 5.5

  Cruiser storage: Fujitsu Eternus SF v16.1, SRA 2.3

  Thanks in advance,

  RAMU Reddy

  [email protected]

  Thanks Stefan,

  I contacted my storage team. It was with License Manager (ACM) advanced copy number. After license ACM registry in SRA Database of SRM server, everything was fine and I was able to protect all remaining VM.

  Best regards

  RAMU Reddy

• deployment of Site Recovery Manager (SRM)

  If I want to deploy a DR solution with failover and failback, would I need a set (which is based on the sockets on a protected host) SRM license per site (a game for the DR site vCenter) and one for the production site vCenter?

  Hello

  Here you can get some info about the license per - VM model, supported with MRS 4.1:

  http://www.VMware.com/support/licensing/per-VM/

  In the two by VM and decision-making models, you can buy licenses only for your protected site. After a failover, you can reuse the same licenses to perform a backspace.

  http://www.VMware.com/products/site-recovery-manager/FAQs.html

  Plugin SRM is a client component that allows you to manage the SRM of vSphere client, install you on the machine that you are using vSphere client

  

  Michael.

• vSphere 4.1 and Site Recovery Manager

  I currently have vCenter 4.0 Update 1 and Site Recovery Manager 4.0.  Can I put vCenter 4.0 Update 1 to 4.1 without upgrading the Site Recovery Manager?

  According to http://www.vmware.com/pdf/srm_compat_matrix_4_x.pdf , you need improve SRM to 4.1.

  André

• vSphere and Site Recovery manager support

  recently, I read somewhere that the version of vSphere will be of course available with vCenter for simple tasks of management and automation, but the rest of excellent suite product of VMware is not supported in the initial release of vSphere.

  So there will be support for:

  • VMware vCenter Site Recovery Manager

  Can someone confirm please when SRM will rely on vSphere.

  and I feel your pain...

  im doing some projects at the moment involving SRM and to my surprise, client does not really hard to understand...

  Itzik Reich

  Solutions architect

  VCP, VTSP, MCTS, MCITP, MCSE, CCA, CCNA

  EMC²

  where the news concerts

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

• Application of site Recovery Manager

  Can someone shed light on the text following as cited in the SRM FAQ:

  "If VMware vCenter Site Recovery Manager is configured only to switch to virtual machines on the site protected on the recovering site, then VMware vCenter Site Recovery Manager licenses are required only for virtual machines protected on the protected site. " If VMware vCenter Site Recovery Manager is configured for the failover of a set of virtual machines to a protected site to a recovery site as it is configured to fail over to another set of virtual machines on the site of recovery on the protected site, VMware vCenter Site Recovery Manager licenses must be purchased for VMS protected on both sites '

  That's arrest with two datacenters 1 campus runs an active/active 'Production' site?

  Thanks in advance,

  not really

  Think of it this way, you can run the workloads of active production on BOTH sites, but have only a need to 'protect' vm is one of sites... for some reason, might simply as the workloads on the other website production are not classified as critical that you need to protect with replication to the other site. just because your sites are active / active does not always mean you must replicate in both directions at all times, yes it is a requirement common but not strict, but I digress... so says essentially that paragraph is you only need license keys available on the site where you intend to 'protect' the virtual computer If the other site will contain no protected vm you do not need srm for her license.

  When a failover occurs naturally licenses are reused just when you need to re-protected virtual machine that swung so that you can't miss their return.

  So just put SRM licenses are per-vm, you need that many licenses available as a virtual machine that you want to protect... site on which the virtual machine live on is not serious you can split licenses between sites or if linked using vCenter mode between sites simply assign the licenses to the pair of sites and the virtual machine will take on a license of the "pool" as it was.

• Site Recovery Manager - storage different

  Good afternoon all.

  Gostaria of sabre is o Site Recovery Manager mourned back dados em Doi/place of marcas diferent, mas replicacao as are dentro da HCL.

  I have a Clarion EMC Cx3-20 e um HDS (Hitachi) AMS2300, e pretendo develop o plano disastre em cima Kanada equipamentos.

  JA procurei nas HCLs da VMWARE, mas nao tem nada as fala em interoperabilidade back modelos dde storage.

  Obrigado a todos pela ajuda.

  To sua question faith respondida, por favor encerre o topico e atribua os pontos para as affect devidamente.

  Grato.

• VSphere of site Recovery Manager support

  Hi all

  We currently host two farms of ESX 3.5 Upd.3 in one of our company's website, and we intend to build a new and more powerful vSphere 4 based firm. Finally, we will upgrade two old farms for the new product, too.

  At the end we you will also need to activate two of our farms to resume with the company a remote site (at a given time that this need will become two-way).

  That is why we are trying to understand if the VMware vCenter Site Recovery Manager is produced following our needs or not.

  Unfortunately, it seems that the vCenter SRM is not yet able to manage a farm of vSphere 4: does anyone know precisely what to be sure of the release date for the new version of SRM (active vSphere)?

  And also, I am wrong in suspecting that the fact that the full name of the SRM includes a reference to vCenter (vCenter SRM) may suggest that an upgrade of our current Virtual Center 2.5 Upd. 3 to the most recent version of the vCenter server would be by the force required to install and use the SRM product even against a battery of ESX 3.5 based servers?

  Thank you very much for your help.

  Best regards

  Salvatore

  Salvatore,

  We shared that SRM will be compatible with vSphere 4 before the end of the year and preview of vSphere 4 + feature SRM at VMworld in San Francisco this month.  We have not yet made a public announcement on a more precise date, but stay tuned.

  The currently available version of SRM (SRM 1.0 U1) is compatible with vCenter Server 2.5 - you can see the details in the http://www.vmware.com/support/pubs/srm_pubs.htmlcompatibility document.  For what it's worth, 'vCenter' is a family name of products for our management of the add-on products (e.g. vCenter AppSpeed, vCenter Lifecycle Manager, vCenter Lab Manager, etc.).  The product formerly VirtualCenter is now called "vCenter Server.

  Once SRM is compatible with vSphere 4, you should not use vCenter Server 4 can use SRM with vSphere 4 servers because vCenter Server 2.5 is not compatible with vSphere 4.

  Hope that helps,

  Jon

• investigating the potential use of the Site Recovery Manager

  We are looking for site recovery manager.   We will use this as part of our DR solution for some virtual machines in our main data center.  I gather specifications on what equipment would be needed to the main data center and the data center of failover.  I was wondering if I could use the material of the Datacenter for failover as a development environment when nothing is failed over to it.  When there is a failover situation either of the tests or a real failover I would have built in that the development environment is stop so resources can be used for site recovery manager.

  Is that what a realistic configuration that I have not dug into the details of the Site Recovery Manager at this time.

  I can't control the LULU URL - so your best to use...

  http://www.RTFM-ed.co.UK/?page_id=7

  In addition, it goes down as a hit of RTFM, which contributes to advertising revenue...

  Concerning

  Mike Landry

  RTFM education

  http://www.RTFM-ed.co.UK

  Author of the book of MRS:http://stores.lulu.com/rtfm

  Free PDF or printed at price

• VMware HA installation without DRS.

  Hello

  Just out of curiosity, let's say I have 4 guests in a VMWare HA and 10 virtual machines per host. I don't have installation DRS that HA and an ESX host goes down.

  How/where VMware HA re - start the 10 mV in the nodes bore? Where the decision of initial implementation of the VMs done?

  
  
  Saludos,

  Jose Maria Gonzalez,

  -

  ---

  http://www.JmGVirtualConsulting.com

  http://www.josemariagonzalez.es

  VMware vExpert 2009

  Co-autor del Libro update1 VMware Site Recovery Manager 1.0

  -

  ---

  If you find this or any other answer useful please consider giving points by checking the answer useful or appropriate.

  ! http://feedproxy.Google.com/ElBlogDeVirtualizacionEnEspanol.2.gif!

  Yes, it starts with the first host in the list once it is out of resources that it moves to the next--until he started the machines it can or all of the if you have chosen to ignore the constraints of resources-

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Database of SQL 2005 with Site Recovery Manager

  Hello

  I want to install Site Recovery Manager.  I have a few questions about the configuration of database.  In my for the database installation steps

  I have the following:

  -

  ---

  For Microsoft SQL Server, the database must be configured as follows:

  1 schema name must be the same on behalf of the user, and you must have a default schema for the user account

  2 bulk insert of administrator privileges

  3. If Windows authentication is used, install the SRM service on a host that shares the same domain as the database server

  4. If SQL Server is installed locally, you may need to disable the network setting shared memory on the database server

  -

  ---

  I have almost 0 experience with SQL 2005.

  How to make sure that the schema name must be the same as the user name? My username is "vcadmin".

  How can you "Bulk insert administrator privleges.

  Thank you all...

  I'm not an expert SQL 2005 is... DB2 is my thing ahead of VMware

  CREATE SCHEMA vcadmin

  AUTHORIZATION vcadmin.

  GO

  will create the scheme of vcadmin with vcadmin be the owner. In SQL Server 2005, each user will have a default schema, and if no default schema has been assigned to a user, they will be part of the DBO schema.

  the format for the granting of insertion block is:

  GRANT ADMINISTER BULK OPERATIONS TO VCADMIN

  You can also just do your username VCADMIN the owner of the database when you create the database.

  see you soon

  Lee

• Site Recovery Manager and HP EVA5000 communication adapter

  I have a requirerment use SRM, HP EVA5000 and EVA4400 to connect a local and the site of DR. I'm having a hard time finding out if the communication

  adapter is based on the EVA5000. Anyone can offer the any insite?

  Gary,

  The matrix of compatibility of Site Recovery Manager posted to http://www.vmware.com/support/pubs/srm_pubs.html is the definitive reference for what is supported and not supported.  Inside, you will find a list of the models in table storage supported with each of the storage replication adapter.  If it is not there, it is not officially supported.

  -Jon