Relocate DC using MRS?

Hi people,

Currently, my company has 2 data centers. One in New York and one in MY. A decision was made to close the data center of MY and I was instructed to get the virtual environment moves on the DC to NY. Some time, I would like to just physically move the ESXI hosts via UPS , the other decision that was made was to add new hosts esxi for the DC to NY. We will be upgrading the liaison network between the two sites.


My first thought and maybe a bad one, was to use the converter and try to V2V from one domain controller to another. Now, I wonder if perhaps SRM can do this? I know that is not the purpose of SRM, then perhaps that my hypothesis is far fetched. If MRS can be used, just can it with the host replication? I don't know if the array based replication is an option yet.

If I'm missing something and there is an easier way, please enlighten me

Thank you

-MN

Actually from vSphere 5.1, replication of vSphere SRM functionality was broken off SRM and is now provided with vSphere (all except Essentials license levels) as a stand-alone feature.  So, Yes, marknashe pouvez use 5.1 replication of vSphere functionality (assuming you are using vSphere 5.1?).   He works under the control of a single virtual circuit and does not need 2 VC (one on each site) as is the case with MRS. What is missing from this approach is automation for the migration process, the migration speed and a test feature (but maybe it's not important in this particular circumstance), however it does not cost anything and is a much better solution than V2V - ing your VMS, because downtime will be considerably reduced (VMs must be down to the final judgment & incremental synchronization).

Second, the planned migration of SRM workflow is designed to meet for exactly this datacenter migration use case.  Several of my clients have used it for exactly that.   Initially, VMware didn't want RS to make use of, but it turns out that about 1/3 of SRM clients exactly what were doing anyway.  So now, VMware has blessed this particular use case with its own workflow.  In fact, it's exactly as a failover, except priority #1 is the integrity of the data; If there is no problem in the case of virtual machines on the live site or if there are final data synchronization (assuming async) then the workflow paused to allow the issue to be addressed before proceeding.

Invest in RS is useful if you plan to operate in the future for DR automation... If not then vSphere 5.1 replication might be good enough.

HTH,

JD

Tags: VMware

Similar Questions

  • Protection of SQL servers using SRM

    Hi all

    I would like to know your thoughts around SQL Server VM protect using MRS.

    Is this something that is taken in charge and what someone doing this?


    I understand that MRS will bring the virtual machine in line, but SQL successfully fly into recovery mode and we would have to rely on the SQL backup to recover things.


    I am understood.

    Thank you very much

    Evan

    I did it in the past and the SQL Server starts as if she had just recovered from an unexpected shutdown.

    Basically you start the server with the data since the last replication.

    Several things to consider:

    1. turn your TempDB and page files on a different disk and do not replicate.  He will chew your bandwidth for very little reason.  You may need to add a disk to the start DR however on-site SQL to create a new TempDB when it comes to.

    2. make sure sure your MDF and LDF are replicated at the same point.  Having these replication on different calendars will cause you problems.

    3. consider your SQL maintenance.  Reindex your database will cause most of the blocks of data to change even if the data only.  This means a lot of replication traffic.

    I hope this helps.

  • Use SRM with Veeam for replication

    Anyone using Veeam to replicate the data of a site of Prod to a recovery site, also using MRS to create recovery groups and run then planned migration?  Is it still possible?

    No it's not possible - they are independent products - this white paper describes the product isolation - http://www.veeam.com/vmware-srm-veeam-backup-replication-complementing-tools.html

  • Import photos into lightroom on another machine and keep your changes.

    My hard drive has failed, but I could extract my lightroom with my pictures folder and place it on an external hard drive. Is it possible for me to import the photos in that folder in lightroom on a new machine and keep my changes I made?

    CHETNA response is good for running off LR the external drive.

    If you prefer to use an internal hard drive, simply copy the catalog and images to the new internal drive, then "relocate" images using the link of Claes.

  • SRM running in an active/active configuration

    Hi guys,.

    I'm curious about using MRS to protect virtual machines in 2 data centers that are both active.

    A data center has a bunch of virtual computers that must be replicated to the data center B using the replication table

    But B's data center has lots of different virtual machines that have reproduced more to A data center.

    Two data centers can sufficient spare to deal with a failure in the same place. I was wondering how this work with SRM as normally you would site just a source and a target?

    Can you have essentially a recovery plan, set up at the Site will a Site B and another stimulus plan set to Site B Site A with asynchronous replication.

    What are the implications of licensing and there documentation or links to such a facility?


    See you soon

    Bilal

    Hello

    Active scenarios are fully supported since SRM 5.0 (you need SRM 5.1 if you use vSphere replication). You can have PG a protection of virtual machines on the Site A and B PG protecting virtual machines on Site B. Then, you create two corresponding recovery plans.

    To license perspective on a few things - because of the asset, you now need active licenses for all the virtual machines on each site - that is, you need to have a license allocated on Site B for all the virtual machines that could be integrated from Site A (and vice versa). This can be avoided by using modes associated between Site A and Site B vCenter servers.

    Long story short - SRM supports your scenario. There is no documentation specific for this use case as it is for MRS. Central these days. You can check this page on docs SRM: Site Recovery Manager 6.0 Documentation Center

    Thank you

    Stefan

  • with vSphere replication to replicate vCenter Server in a VM

    Hi guys,.

    I am trying to find some info on this. I currently have vCenter 5.5 running on a Windows 2008 R2 VM server. I was wondering can I use replication to replicate it in some shared storage for backup purposes, and if I had to lose it could I recover and this and be good to go? He runs a database integrated. or is it as AD/SQL/Exchange and in general you shouldn't use replication or something of the sort for them.

    Also, if I have reproduced on the recovering site, I could pick it up and re protect him using MRS. and migrate to the main site once I had everything back up and restart? Is there a difference if I ran the vCenter device instead of the version of Windows inside a virtual machine?

    My apologies if this has been answered before that somewhere, it just went through my mind randomly and Googling gives me really a lot of results, so if its been answered somewhere, please point me in that direction.

    Hello

    vSphere replication requires vCenter to function, you cannot use VR to protect it that you wouldn't have a way to recover, unless it has been replicated on a different vCenter (whereby it might be recovered, but only inside the other vCenter) or if it has been managed by a different vCenter.

    If you are in the second option, where you have a vCenter management appliance RV, and you have an another vCenter, so yes, you can use RS in this model to protect and auto restore your internal vCenter.

    No difference in the functionality between vCA and windows version of vCenter.

    As for your statement: "or is it as AD/SQL/Exchange and in general you shouldn't use replication or something of the sort for them."

    -vSphere replication supports VSS suspension

    -I'm Okay I wouldn't recommend AD replication (SQL and Exchange or if you can use the built in replication at the application level)

    -If you can not however, most modern applications work very well in a consistent state of crash (VR normal replication) and the rest works with VSS

    Hope that answers your questions

  • On the replication SRM 5.5 and vsphere

    Hi guys,.

    using Mrs. 5.5 and replication of vsphere can I do a first replica of virtual machine with a manual copy or clone on the remote site and after synchronization with replication or srm vsphere virtual machine?

    Thanks in advance.

    Hello

    I assume that when the source of the VM is turned on, the disks (-flat.vmdk files) are locked and that's the reason to download drives while the virtual machine is turned off.

    The virtual machine can be powered on once the disc has been downloaded/copied.

    An alternative approach, if you have enough free space on the source website - you can clone the virtual machine, without any power off and download the clone disks.

    The clone operation may change the value of ddb.uuid in hard files. Make sure that it matches the value in the hard of source files and if not, change it manually. Another configuration of replication will fail if this value does not match.

    Kind regards

    Martin

  • With vSphere 5.5 replication disaster recovery test

    I have a few virtual machines in our site of DR using a 24-hour RPO.  We will test by recovering virtual machines remotely, without affecting the production of virtual machines on our local site by selecting the option 'recover with the latest available data.  My question is after the replication can I 'pause' instead of 'stop' the task of replication during this test, so that after our test, I can resume the replication tasks?  This would cause a problem?  I don't want something to happen to the production of virtual machines on the side of the source.

    Hello

    Currently Failover Test + Test cleanup function, without having to make a break or stop replication only works in VR, if using MRS. above it.

    RV without SRM, after failover, the only possible option is to stop replication. Perform the failover consolidates replica records in the target data warehouses and prepares the virtual machine configuration files.

    Yet after the replication is stopped, you can:

    -power off the virtual machine on the recovery after done with the test site

    -Remove the vCenter site recovery, leaving records in the target VM data stores

    -set up replication again and that it points to the existing disks in the warehouses of data target

    Although the UI will display 'Initial full sync', really VR calculates checksums and only changed disk blocks are transferred from the protected site.

    Kind regards

    Martin

  • You can replicate between 5.1 and 5.5?

    Hello

    I have two sites we will install vSphere replication and SRM, we're completely 5.5 and the other is 5.1.  Is there any problem with replication & using MRS. between the two versions?

    Thanks in advance

    Unfortunately you will not be able to reproduce in this use case. The problem is that we do not support replication between 5.1 and 5.5, and vice versa.

    You must have identical versions on both sites.

    Kind regards

    -Martin

  • Windows Server 2003 vmdk / blue screen / VMX missing

    Hello

    We come across a RAID failure that has had a number of machines with it. I'm trying to restore a particular machine that has replicated off-site using MRS. Unfortunately I can't recover the usual way as the Protection status is "not configured" and I can't restore because the connection state is "inaccessible". See below:

    Unable to protect VMS 'FTP' because of the status of the non-copyrightable connection "inaccessible".  The virtual machine must be properly connected before it can be protected.

    This machine has not been saved either. Lessons have been learned.

    So, I have since discovered that the VMDK for this machine is sitting in a folder on a store of data on the side of DR. However, there is no attached vmx file and I tried to recreate the virtual computer by using the standard virtual machine settings, but there bluescreening at startup:

    ftp.png

    Unfortunately, I'm unable to F8 for CHKDSK but I think it's more to do with a configuration problem on the side of the virtual machine rather than on the side of the BONE. Perhaps because of the machine version (which was 7) and we are now running 8 and higher, the CPU / RAM installation etc? I don't even know if it's an OS 32-bit or 64-bit.

    Is that what I can do to get this working?

    Everything is good!

    He joined a vm 2008 just if I could go down the files. Recreated the vm as 'typical' and handed over in place the VMDK and only, she went and booted up!

    Needless to say I took a snapshot and will get this saved mofo tonight.

    Thanks for the suggestion, if.

  • VADP recovery Issues for SRM protected VM

    We get the following error when you try to retrieve a picture VADP level backup to a virtual machine that has been protected using MRS:

    Configuration of the VM invalid or not taken care of.

    vSphere replication does not support change the length of a replicated disk.

    We have the SRM protection set up between two sites, but also have a third isolated site used for DR tests I need to restore the SRM protected computers. This site is an installation vCenter vanilla and 3 only vSphere hosts. I can recover backups VADP for unprotected MRS. fine of VM, however, trying to recover a virtual machine that has been protected using SRM in the production site, I get the error.

    We are running vSphere 5.0.1 and using EMC Networker 7.6 SP4 for backup and restore.

    I raised a call with VMware, but they seem uncertain. Has anyone seen this problem before?

    Thank you.

    Pete.

    Hello

    Just to provide an update for this problem incase anyone attempting the same process:

    VMware support reported:

    ********************************************************************************************************************************************

    It seems Networker following this process:

    -saves a copy of the VMX file during the backup (instead of obtaining the ConfigInfo to the virtual machine via the API)

    -during the restoration, it copies the VMX file to the data store (instead of creating/reconfigure the computer based on the registered ConfigInfo virtual).

    -register the VMX

    -Reconfigure the VMX recorded to create discs

    This will not work if the virtual machine is being restored to the same data store and has access to the original disks. If the virtual machine is being restored to another location where is has no access to the original disks, they create the disks but the VMX still has replication configuration entries that say that these discs are being replicated. When HBR checks the request reconfigures, he sees that the disk is 'change '. In this case, it checks if the length of old drive and the new drive is identical and fails reconfigures her request if the sizes don't match. But as the old records are no longer available, HBR does not find the old disk size and it may appear 0 in the ConfigInfo. So it fails the operation of education reconfigures.

    If he had followed the supported method for restoring the virtual machine by using the API to create, they would not run on this issue. However, I think that even in this case he might still have some problems in some scenarios where only some drives are restored (for example, the data store from one of the disks)
    is lost), but as long as partners of backup using the API, workaround for these rare cases would be to restore the entire VM.

    ********************************************************************************************************************************************

    I have raised this with EMC who said:

    ********************************************************************************************************************************************

    NetWorker has not qualified for SRM + Vshpere replication (which was confirmed by ENG_team). Eng-team approves then it will be open to support. In this case, we can have support call with VMware to solve the problem. Since it has not been tested with Networker, we cannot go further to discuss with VMware or troubleshoot.

    Yes you are right to say that, if networker VMware interviews there may be solutions to the problem you have. But unfortunately at the moment, it is not seems to be possible; While networker code was not prepared to support SRM + replication Vsphere.

    ********************************************************************************************************************************************

    EMC then referenced the following link:

    http://solutions.EMC.com/emcsolutionview.asp?ID=esg130882

    It seems that for the foreseeable future NetWorker will not support VADP image backups restore if the virtual machine is also protected by using VMware SRM.

  • Can do without the virtual online computer between 2 different vCenters with different Versions?

    Hi all

    I want to spend some VM to a vCenter to another without downtime. These 2 vCenters are different geographical locations.

    I have a vCenter with Version 4.1 and another in 5.1. I want to move the VM 4.1 Setup configuration 5.1 mode.

    Can we use SRM to move the machine between 2 data centers (allows for example between Richmond and Rockville)?

    Thanks in advance.

    -Isabelle

    No, it is not possible to move machines running using MRS, but it is an option if the possibility exists for downtime, also it will allow migration to predict.

  • SRM Test AD/DNS vs AD/DNS recovery failover recovery

    I read: http://communities.VMware.com/docs/doc-11517 and it seems that for a real failover SRM DDNS must manage VMS failover commissioning with a new IP (using MRS IP Customizer) using AD/DNS server that is running always on recovery (using built-in replication AD) site.

    Given that the bulk of failovers will actually failovers of test on the test network, how to make an AD/DNS server in the failover of the test?   Is it acceptable to replicate AD/DNS via SRM for purposes of test failovers?   If so, how would be to change the IP address on the test without problem AD/DNS Failover?  Also, I can create a test failover that includes VM AD/DNS and exclude the recovery plan even when to run in failover mode?

    Thank you

    -MattG

    By creating a script of MRS who clone the DC on the recovering site, then it adds to the bubble test VLAN for the stimulus plan.

    -MattG

  • Different material SRM to the DR site

    Dear people,

    I need clarification on below point.

    We have servers (a few years) running on the DC vSphere site. Now, we are planning for recovery by using MRS. site. But we intend to place newer materials to DR. Does make any incompatibility with MRS? (to my knowledge not as it should be compatible with only vSphere). Please let me know if I'm wrong.

    Thank you and best regards,

    Hari.

    To compute (server) resources compatibility is no need because the VMS failover has cold start.

    Because SAN paintings his most complex issue and to keep the replication health models the table must satisfy certain requirements of compatibility. You should check the compatibility charts.

    In any case, you can use SRM with vsphere replication in order to avoid any restriction of compatibility.

  • Protect the DHCP with SRM

    Hey guys,.

    We are in the middle of a project of DR and have come to the point that we want to have our service ready DHCP DR.  The idea of Split range (80/20) standard is an option we are looking at, but in a DR or even single server failure there is a bit of management that is necessary to ensure the secondary DHCP server can serve all the IP addresses of all scopes (before it's 20% fills).  So we have an idea to use SRM to protect DHCP.

    We have two sites, connected via the 3 layer, with two 10GB connections between the two (for fault tolerance and load balancing).  The DR site is a live environment; It is a branch across the city (such as 30 kilometers).

    The idea of the scope of Split we have DHCP running on a domain controller in each site with the server DHCP secondary (DR) serving 20% of the IP addresses of each field and the primary DHCP serving 80%.  This can be setup using the wizard of scope of Split that MS has the Server 2008.  In doing so we cover failure of the primary DHCP server (it is also a virtual machine so HA protects too), but also the Site as the secondary DHCP server failure will be in place.  If we have an extended outage of the primary DHCP server then we need to get to the secondary DHCP server and increase all scopes, ensuring that conflict detection is on.

    Our thinking is to move the DHCP on the domain controller and give it its own virtual server.  Then, we protect the service DHCP using MRS to move it on the DR site in a DR situation.  This will cause the DHCP server to get a new IP address, as the two sites are connected by Layer 3 - the same subnets cannot exist in both places.  And that's where our thought process is getting confused...

    What will happen with the DHCP service, if the server has a new IP address?

    What is the process for DHCP clients attempting to renew its IP address:

    one) to restart the computer?

    (b) to the mark 1/2 way of their lease?

    On the one hand, I think that MRS is the easiest way to protect not only the DHCP, but also to minimize the DHCP solution management.  The scope of Split idea help to ensure that any change to a DHCP server is replicated to the other server: scope changes, scope of options changes, reservation changes, etc...

    Has anyone analyzed the all around it?

    Thank you!!

    Gerald

    That is right.  DHCP server only cares about its own address.  As long as you subnet broadcast forwarders to two IP addresses of the DHCP server so that the request hits the server DHCP it matches just MAC address for reservations of IP / scopes etc. and will work.

    Only thing to check when it rises to the DR is if the DHCP server may need approval again before DHCP works. Do not remember how it works off the coast of the hand.

Maybe you are looking for