Hyper-V Replication Question

Hello,
I just completed watching some YouTube videos and reading some helpful websites but still had a quick question. I have a .110 network in LocationA and a .60 network in LocationB.
Both locations use static IP addresses. I can ping both locations from each other. If I want to replicate a VM from the .110 network or LocationA to the .60 network which is LocationB would this be possible since both locations have different networks? If
I want to replicate from the .110 network, would my .110 network settings on the VM still be configured on the VM in the .60 network? If this is the case then when I turned on the replicated VM it would not be able to join the network without modifying the
NIC settings. I was hoping someone could explain this process a little better or more in-depth so I have an idea of what I'm doing.
On a different note as long as your two host servers are Server 2012 R2, can you replicate Server 2003 and Server 2008 systems or is it only for 2012 R2 VMs? Any and
all information is helpful. Thank you!
Pat

Hello Pgrantland,
I was checking some documents about this wonderful feature and I found this:
2.3 To enable replication for a virtual machine
9. A dialog box appears indicating that replication was successfully enabled. In this dialog, click the Settings button
and provide settings to configure the network that the virtual machine will connect to on the Replica server. The Replica virtual machine does not automatically connect to any network on the Replica server (after a failover) by default,
so these settings are important. You can configure the network settings so that the virtual machine will connect to a different network after a failover to the Replica server than it used when it was on the primary server.
Step 2: Enable Replication
https://technet.microsoft.com/en-us/library/d5d9e9f2-0f21-4d82-aa90-45e194de5ac9#BKMK_2_3
These steps are configured before you finish the wizard to enable Hyper-V replica on a VM.
Regarding the other question as far as I know a VM is just a VM from the Hyper-V side, the replica does not look what OS you are running.
The only thing is that if you a re planing a VM to be replicated check that the hardware elements configured on the settings of you VM are able to be replicated.
There are scenarios on which hardware configured on a VM makes that the VM is not supported for replica and you cannot replicated as long as those elements are configured on the VM.
For example "Fibber Channel adapter" (Virtual SAN) and "Virtual hard disk sharing" are not supported to replicate.
Hope this information help you to reach your goal. :D
5ALU2!

Similar Messages

Hyper-V Replication Implementation question

I have two Hyper-V 2012 servers. I want to setup replication between them but I wanted to clarify a few things. My plan is to put 3 VM's on each Hyper-v Server and then replicate them to the other servers. So Server A has 3 VM's and Server B has
3 VM's. In case of a server failure the servers on Server A will failover to Server B and vice versa. This also applies to the VHD's. I want everything to replicate between the two. And I need to make sure that the process is automatic so if storage fails
the vm's will fail over. I just want to make sure the Hyper-V Replication will work in this way.
Vincent Sprague

I need the storage replication aspect, I currently have the two servers in a cluster and the vm's failover but storage is my problem, our shared storage solution is junk and I need to find a way to get around that.
Vincent Sprague
1) For Hyper-V Replica you don't need to have shared storage as Windows will replicate source VHDX with some minor delay to a destination VHDX.
2) You may also take a look @ Storage Replica (part of the upcoming Windows Server 10) as it may do a better job for you because of the synchronous nature. See:
Storage Replica and Hyper-V
http://www.starwindsoftware.com/blog/storage-replica-with-microsoft-failover-cluster-and-clustered-hyper-v-vm-role-windows-server-technical-preview/
Good luck :)
P.S. Looks like you've already asked similar question before:
https://social.technet.microsoft.com/Forums/projectserver/en-US/c19b08aa-b395-49e0-9bf7-52981118b820/server-2012-r2-vm-replication?forum=winserverhyperv
StarWind Virtual SAN clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Will Hyper-V Replication Manager move a VM without shutting it down?

Scenario
Let say I have two sites (Primary And DR). I have my production VM's running on my Primary Site. If I protect them with Hyper-V Replica the VM is replicated and I can bring the VM up manually in the DR site. So I know that process work. I am trying
to minimize the outage of an app and the time it takes to bring the VM up and running. I have a database server in the primary site. I want to be able to move the VM hosting the database server to the secondary site without shutdown or with minimal downtime.
Question
Can I use Hyper-V Replication Manager to migrate the VM with the database from the Primary Site to the DR site without downtime for the SQL server? When I mean downtime for the SQL server is that clients can continue to connect to the database and access
the data in the database while I am migrating the VM.
This is needed to maintain availability during DR testing of the Production environment.
Thanks,
Carlos

Hi Carlos,
For DR drills you can use the test failover. A
test failover can spin up a test virtual machine for the production virtual machine. This VM can run in an isolated environment and does not affect the production environment. Your SQL server will have no outage while DR testing.
A test failover can be executed on an individual virtual machine or a recovery plan. This can orchestrate the drill as close to a real failover which recovers the application in a planned manner.
Hope this pointer helps.
More detailed tutorials are available at http://msdn.microsoft.com/en-us/library/windowsazure/dn440569.aspx

Hyper-V Replication over Dedicated LAN and "is alive" checks over Corporate LAN

I am testing Hyper-V replication to see if it will be a suitable replacement for the ArcServer RHA product. One thing I am struggling with is configuring the replication to use the dedicated LAN, but still have the host servers verify over the corporate
LAN.
I have seen the blogs on how to use a dedicated route and editing the hosts file to get replication to use the dedicated LAN, but that also changes the LAN in which the host servers communicate. It seems to me that if the corporate LAN were to go down
on the master server, I wouldn't be able to fail over the virtual machines to the replica server without first having to connect into the master server through the dedicated LAN of the replica server to shut down the virtual machines.
I need to be able to fail over to the replica server if the corporate network connection on the master server drops without having to go through the extra steps of connecting into the master server first.
Is it possible for the two items to be separated? Can I tell Hyper-V to replicate using one specific IP destination on the dedicated LAN and have the replica server check to see if the master is live over the corporate LAN?

Hi Telrick,
>> It seems to me that if the corporate LAN were to go down on the master server, I wouldn't
be able to fail over the virtual machines to the replica server without first having to connect into the master server through the dedicated LAN of the replica server to shut down the virtual machines.
I want to say that there are "planned fail over" and "unplanned fail over " , the latter applies the primary server crashing (you can select "failover" on "replica server " then the VM will start up ,after the primary
server online again you can do "reverse" )
The point is that you can not use hyper-v replica as a backup (it will lost little data which have not yet been replicated to replica server when "unplanned fail over" happens )
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-v replication Error Hyper-V received a digital certificate that is not valid from the Replica server 'burstingreplica'. Error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp"

Hi,
When trying to initiate hyper-v replication from the main server i'm getting this error in the event logs.
Hyper-V failed to enable replication for virtual machine 'RECADemo': A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. (0x800B0101). (Virtual Machine ID 561591B6-567C-...)--I'm using certificate based auth and cert is installed/recognized on both machines.Please help.Thanks,Jaffer
Jaf

Hi,
This error occurs because the Microsoft Certificate Trust List Publisher certificate expired. A copy of the CTL with an expired signing certificate exists in the CryptnetUrlCache
folder. Please try to renew the Trust List Publisher certificate.
The related KB:
Event ID 4107 or Event ID 11 is logged in the Application log in Windows and in Windows Server
http://support.microsoft.com/kb/2328240
How to Renew the Site Server Signing Certificate (Microsoft Certificate Services)
http://blogs.technet.com/b/configmgrteam/archive/2009/02/11/how-to-renew-the-site-server-signing-certificate-microsoft-certificate-services.aspx
Manage Trusted Publishers
http://technet.microsoft.com/en-us/library/cc733026.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

DPM 2012 R2 and Hyper-V Replication, huge conflict and failure to backup

I have recently created new 2012 R2 servers with DPM 2012 R2 in attempts to upgrade an environment.
When attempting to create Protection Groups for Hyper-V VM, DPM will consistently omit any VM that happens to have Hyper-V Replication enabled, whether that server is the primary VM instance or a replica VM instance. ALL other Hyper-V VMs are listed,
only those with Replication enabled are omitted. This happens on both DPM 2012 R2 servers, exactly the same results - all VMs without Hyper-V Replication enabled are listed, none of the VMs with replication enabled are visible in the list.
Obviously we need to be able to backup VMs with Hyper-V replication since replication is only a tiny portion of a DR strategy, it doesn't cover ANY recovery scenario other than the loss of the primary VM - it doesn't allow for restoring any missing or damaged
files or undoing any other changes to the VM.
The DPM 2012 R2 server have the latest update rollup (#4) applied and the protection agents have also been updated.
Looking for some hints since DPM 2012 R2 is supposed to support backing up both the primary and replica VMs, especially when the Hyper-V host if Server 2012 R2.
Might have to use Windows Server Backup or Veeam's free Hyper-V backup since aside from enabling Hyper-V replication to keep a couple snapshots, DPM isn't a viable backup options in combination with Hyper-V replication.

As per the following blog:
http://blogs.technet.com/b/dpm/archive/2014/04/25/backing-up-of-replica-vms-using-dpm.aspx
you should be able to backup Hyper-V VMs even if they are replica VM.
When you configure DPM to protect both primary and recovery hosts, VM will appear on any of the Servers as it will have the same GUID.
So, protect primarya nd recovery hosts using different DPM or if you want to protect both primary and recovery using same DPM, make sure that you check both servers so as to discover VM.
Regards, Trinadh [MSFT] This posting is provided AS IS with no warranties, and confers no rights. If you found the reply helpful, please MARK IT AS ANSWER. Looking for source of information for DPM? http://blogs.technet.com/b/dpm/ http://technet.microsoft.com/en-in/library/hh758173.aspx

Windows Server 2008 Standard 64 bit edt support Hyper-v replication

Dear Team.
Windows Server 2008 Standard 64 bit edt support Hyper-v replication or not.
If my primary physical server down so my secondary server act as primary server.

Hi,
Windows Server 2008 Hyper-V do not Support Hyper-V replica.
This is a new Feature in Hyper-V for Windows Server 2012.
http://technet.microsoft.com/en-us/library/hh831410.aspx#BKMK_Replica
Regards
Sebastian

Limit Hyper-V Replication Data Transfer Rate

Hello,
i need to limit data transfer rate for Hyper-v replication because between two Datacenter have bandwidth limitation.
Please suggest

You can use the New-NetQoSPolicy cmdlet to set the throttling limits -
http://technet.microsoft.com/en-us/library/hh967468.aspx. Based on the destination port (the port on which the replica server has been configured to receive replication traffic - maybe it's port 80 in your case) or the destination subnet, you can specify
a throttling value (-ThrottleRateActionBitsPerSecond) or assign a weight (MinBandwidthWeightAction).
Eg: New-NetQosPolicy "Replica traffic to 8080" –DestinationPort 8080 –ThrottleRateActionBitsPerSecond 100000
or check the link to Thomas blog
http://www.thomasmaurer.ch/2013/12/throttling-hyper-v-replica-traffic/

Hyper-V Replication Certificate Question

Hi,
Possibly a common question so apologies if it's simple.
My main server is HV1.company.local
My second server will be cloud based and standalone in a workgroup, let's call it hv2 and for arguments sake I'll add the DNS entries of hv2.mydomain.co.uk
and a certificate for this address.
Certificates will obviously need to be internet facing so will go for HV1.companydomain.com for the first server.
Do I just use internal DNS to sort out the fact that the server name is .local?
Anyone with experience in this set up with best practice and any gotcha's would be much appreciated,
Cheers,
JJ

Hi Sir,
>>My second server will be cloud based
Based on my understanding of your case , first you may ensure two hosts can access the IP of each other directly (whatever dns or hosts file ).
If the network prerequisite is met , then we can think of it as a workgroup environment and build certificate-based replication for two hyper-v host :
https://social.technet.microsoft.com/Forums/en-US/c3e309b6-1d5d-4e52-b859-cf36bd5af47d/forum-faq-how-to-implement-hyperv-replica-in-workgroup-environment?forum=winserverhyperv
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V Replication - Subnet Configuration Between Datacenters?

I'm designing a DR solution in a geographically separate datacenter which will use Hyper-V 2012 R2 Replication to replicate several of our VMs to another Hyper-V cluster. The VMs will run a mix of Linux and Windows, with the Windows servers being Exchange,
SharePoint, WSUS, etc.
I currently have a static IP assigned to all servers and VMs, i.e. I'm not using static DHCP reservations.
I have the ability to extend the private LAN subnet (let's call it 192.168.1.1) between the two datacenters over the public Internet using my firewall's VPN capability, but I'm wondering if there is a recommended best/better practice for this?
Is it okay to extend the subnet so in a fail-over scenario I can just power the VMs on in the DR datacenter without much manual intervention? Or would it be a better idea to configure my servers with a static DHCP reservation, so when they come up in the
DR datacenter they can pull an IP on a unique subnet?

Hello Matt,
The answer is yes for Hyper-V 2012 R2, however this feature was available only for Windows Guest OS'es in Hyper-V 2012.
This works only on synthetic network adapters, not legacy network adapters, and it requires Windows XP SP2/Windows Server 2003 SP2 and newer OS'es to be running on the virtual machine to work. This
also works with Linux virtual machines that are running the latest Linux distributions.
As a good practice is to complete the failover TCP/IP configuration on the primary virtual machine with its normal IP configuration. In that way, if the replica is ever activated, replication is
reversed, and the virtual machine is then failed back to what was the primary, and the correct IP address for the primary location can automatically be put back.
Hope this help.
Regards,
Charbel Nemnom
MCSA, MCSE, MCS, MCITP
Blog: www.charbelnemnom.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial
to other community members reading the thread.
This is incredible. We are running Hyper-V 2012 R2 with the latest CentOS 6.5 and synthetic network adapters. Thank you so much.
Oh, hey! I read your blog! :)

Hyper-V replication across versions (2012 to 2012 R2 and vice versa)

Does Hyper-V support cross-version replication? In other words, can Windows Server 2012 Hyper-V replicate to Windows Server 2012 R2 Hyper-V server? Vice versa? I tried looking for documentation or blog posts about this but couldn't find any.

Hi,
Base on my test, the Hyper-V 2012r2 can't replicate to Hyper-v 2012.
Additional, the following similar thread may will helpful of your question.
Windows 2008 HyperV Replica in Windows 2012 HyperV
http://social.technet.microsoft.com/Forums/windowsserver/en-US/f92b1af2-d3cd-4a5e-a850-dadf0c33d2a1/windows-2008-hyperv-replica-in-windows-2012-hyperv?forum=winserverhyperv
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Multi-master replication questions for iPlanet 5.0, gurus out there?

hi:
I'm using iPlanet Dir Server 5.0 and I note that many gurus out there has
been able
to get this to work, that's good, but I have yet to. I have several
questions, maybe
someone can spend a few minutes and save me hours...
I have a suffix called dc=calient,dc=net. I followed the suggestions in
the
iPlanet install guide and created 2 directory servers
a) suffix o=NetscapeRoot, at some arbitrary port, 4601
b) suffix dc=calient,dc=net, at the usual port 389.
All my searches/create/delete work fine. However, when I try to replicate
with multi-master between 2 machines, I keep getting into problems.
Here's one set of questions...
Q1: do people out there really split their tree from the o=NetscapeRoot
tree?
Q2: The admin guide says the the unit of replication is a database, and
that each replication can only have 1 suffix. Is this true? Can
a replicated db have more than 1 suffix?
Q3: If I also want to replicate the o=NetscapeRoot tree, I have to set
up yet 2 more replication agreements. Isn't this more work? If
I just lump the 2 suffixes together, wouldn't it be easier? But would
it work?
Q4: I followed the instructions to enable replicas on the masters.
But then I tried to create this cn=Replication Manager, cn=config
object.
But what is the object class of this entry? An iPlanet user has uid
as its RDN... I tried a person object class, and I added a password.
But then I keep getting error code 32, object not found in the error
log. What gives? such as
WARNING: 'get_entry' can't find entry 'cn=replication
manager,cn=config', err 32
Q5: Also, are there any access control issues with this cn=Replication
Manager,
cn=config object? By this I mean, I cannot seem to see this object
using
ldapsearch, I can only see cn=SNMP, cn=config. Also, do I have
to give all access via aci to my suffix dc=calient,dc=net? Also,
given the fact that my o=NetscapeRoot tree is at a different port (say
4601),
not 389, could this be an issue?
Q6: when replication fails, should the Dir Server still come up? Mine does
not anymore
which is strange. I keep getting things like this in my log file
[08/Nov/2001:21:49:13 -0800] NSMMReplicationPlugin - Could not send consumer
mufasa.chromisys.com:389 the bind request
[08/Nov/2001:21:49:13 -0800] NSMMReplicationPlugin - Failed to connect to
replication consumer mufasa.chromisys.com:389
But why shouldn't the dir server itself come up even if replication
fails?
steve

Hi Steve,
First, please read the 'Deployment Guide'. I think that is easier to
understand when you want to setup multi-master replication. The
'Administrator's Guide' gives you step-by-step instructions, but it may
not help you to understand how to design your directory services.
Stephen Tsun wrote:
I have a suffix called dc=calient,dc=net. I followed the suggestions in
the
iPlanet install guide and created 2 directory servers
a) suffix o=NetscapeRoot, at some arbitrary port, 4601
b) suffix dc=calient,dc=net, at the usual port 389.
All my searches/create/delete work fine. However, when I try to replicate
with multi-master between 2 machines, I keep getting into problems.I don't understand something: which backend do you want to replicate?
The one holding 'o=NetscapeRoot' or the one holding 'dc=calient,dc=net'?
Do you want to setup replication between these two instances of the
directory server (i.e. between port 4601 and 389 in your example)?
Q1: do people out there really split their tree from the o=NetscapeRoot
tree?If you have multiple directory servers installed in your environment, it
is probably worth dedicating (at least) one directory server for the
o=netscaperoot tree.
Q2: The admin guide says the the unit of replication is a database, and
that each replication can only have 1 suffix. Is this true? Can
a replicated db have more than 1 suffix?Well, it is normal, since in iDS 5.x you have 1 suffix per database.
You can, however, replicate multiple databases.
Q3: If I also want to replicate the o=NetscapeRoot tree, I have to set
up yet 2 more replication agreements. Isn't this more work? If
I just lump the 2 suffixes together, wouldn't it be easier? But would
it work?You can't lump the 2 suffixes together, because each backend has 1
suffix associated with.
Q4: I followed the instructions to enable replicas on the masters.
But then I tried to create this cn=Replication Manager, cn=config
object.
But what is the object class of this entry?Usually, it is organizationalperson or inetorgperson. In most of the
cases you want an objectclass which can have userPassword attribute.
An iPlanet user has uid
as its RDN... I tried a person object class, and I added a password.
But then I keep getting error code 32, object not found in the error
log. What gives? such asYou must have misconfigured something. Or perhaps, it is not
cn=replication manager, cn=config, but 'uid=replication manager,cn=config'
Q5: Also, are there any access control issues with this cn=Replication
Manager,
cn=config object? By this I mean, I cannot seem to see this object
using
ldapsearch, I can only see cn=SNMP, cn=config.The configuration tree is protected by ACIs, so you can not see them
using anonymous BINDs. Try binding as 'directory manager' and you will
find your entry.
Also, do I have
to give all access via aci to my suffix dc=calient,dc=net?For what purpose? For replication, it is enough to set user DN in the
replication agreement and this user can update the replicated backend.
Q6: when replication fails, should the Dir Server still come up?Yes.
Bertold

Bi-directional replication question..

I configured database A & database B for two-way replication.
Basically, I configured from A to B without any problem, before runs "Start_Capture", I export & import the tables with rows=n.
Question is, Now I need to configure from B to A. Do I need to export from B and import to A with rows=n before running "Start_Capture" on B? or just simply runs "Start_Capture" on B?? thanks..

You can do this on B for instantiating table on A
DECLARE iscn NUMBER;
BEGIN
iscn := DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER();
DBMS_APPLY_ADM.SET_TABLE_INSTANTIATION_SCN@A(
source_object_name => 'schema.table',
source_database_name => 'B',
instantiation_scn => iscn);
END;
BEGIN
DBMS_CAPTURE_ADM.PREPARE_TABLE_INSTANTIATION(table_name => 'schema.table');
END;

CAD replication question- IPCC enterprise

IPCC enterprise, 2 cad servers version 7.2. One CAD server was down for more than four days causing replication between the primary and secondary CAD's to stop. Ran postinstall.exe to restore the LDAP replication and same for recording and statistics , both showed successful but only LDAP seems to have taken. when looking at the SQL database in CAD (using enterprise manager), the publication/subscription shows as deactivated for cra_agent_pub publication.
question: Can someone look at there server and let me know if the subscription is supposed to show as deactivated? (using enterprise manager, it is the listed as the publication on the primary CAD server) if not, does anyone know if it is as easy as reinitializing the subscription?
thanks

Possibly you have two separate issues, but let's address the replication issue first.
1. Make sure that both RASS databases are well under the 2GB limit imposed by MS SQL Desktop Engine. Hit the 2GB limit and the DB will be deactivated. Go too far and it can even appear as "Unknown".
2. Login as the local administrator and remove replication using PostInstall
3. Use Enterprise Manager to ensure that all aspects of replication have been removed. All aspects!
4. Again, using PostInstall apply replication again
5. Check with Enterprise Manager that replication has been applied - all those red Xs should be gone - obviously .
Regards,
Geoff

Hyper-V Replication stops working (General Access Denied)

For a customer we have a MAIN/DR solution based on Hyper-V and Replicas.
Main is equipped with 2 x Windows 2012 in a cluster, DR has one host standalone with Hyper-V.
The whole shebang is managed via SCVMM 2012 and we have replication enabled for around 4 VM's going from MAIN to DR.
Everything is working ok for a while and then all of a sudden we're getting events in our NOC about the fact that the replication has stopped. Upon further investigation we found a couple of events stating:
"Hyper-V failed to open the file 'C:\ClusterStorage\Volume1\VP-SCSQL01\VP-SCSQL01_E.vhdx' for replication in primary server for virtual machine 'VP-SCSQL01': General access denied error (0x80070005). (Virtual Machine ID B7020EE9-A781-4F50-B387-E781FC7F2315)"
When we recreate the replication (so really deleting everything and setting the VM replication up from scratch) it starts and works fine. Resuming replication does not work.

Hi Bart,
Have you tried to enabled hyper-v replica broker for hyper-v cluster ?
If you have enabled hyper-v replica broker , please try to use cluster manager to reproduce this issue and check if there is any useful event log .
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V Replication Question

Similar Messages

Maybe you are looking for