So the status of your Hyper-V replica shows that replication health is critical and if I click resume replication, it says replicating changes >> and after a few moments >> failed.
There is no other option to fix this issue. Try these steps:
(I use Hyper-V manager for this procedure)
1. From the primary site, remove replication using “remove replication” option.
This will leave the replica VM on the DR site intact.
2. Now, on the DR site, remove replication.
If you look at this replica VM inside VMM, you will see that now it has become a regular VM. It looks like a regular server instead of a server with a shadow behind it. (you may have to refresh VMM)
3. On the primary site, right click on the VM and choose enable replication.
4. Go through the wizard, (next-next) until you come to the “Choose initial replication” page. On that page, choose the option “Use an existing virtual machine on the replica server…”
5. Click finish and it shows “sending initial replica (progress percentage).
Don’t worry, it is not really all the data, it is synchronizing with the data already there at the DR site.
That’s it folks! I hope it helps someone.
I ran into a situation where a large VM had its replication enabled, and the initial replication (IR) sent to a USB drive. Then IR was imported on the DR site. Everything was fine but later on, for one reason or another, the replica was deleted. At this point you have the option of recreating another IR to a USB drive, sending that USB drive to your DR site, importing the new IR again. All that, of course, will take quite a lot of time.
The alternative is to import the same old IR on the USB drive (assuming it is still there at the DR site) and letting the replication sync up the changed bits.
Here is how to do that.
Continue reading “How to re-sync replication with an old initial replica on USB drive”
While creating a Hyper-V replica broker in my HV cluster, I came across a problem. No matter what workaround I tried, my broker wont work. I tried pre-staging the computer account etc, as mentioned here but for my particular environment, it did not work. I read this:
Here is how I resolved it :
- I deleted the pre-staged computer account in AD, (which I had created manually, earlier for the replica broker)
- Configured the role in FCM, no errors while creation
- After that… yes, I got errors in the log (ignore for a minute)
- Then I recreated the AD computer name by hand and gave full control over that new account to the cluster’s computer account
- Went to FCM > cluster name > roles
- Noticed the HV replica role there (but it was in red, stopped)
- clicked “start role” on the right side action menu
- The role came online in a few seconds.
Now I can even ping the virtual IP address of this Hyper-V replica broker role!
I guess, for whatever reason, (at least in some environments) FCM cannot really use a “pre-staged” account for this role.
So after scratching my heard for the most part of two hours, I found out the solution to my problem. The problem started happening after I had to restore the DB of my VMM 2012 R2 onto a new installation. I kept on getting Error 20552 when refreshing any server in VMM.
I finally resolved it by re-entering the password for the “run as account” for the VMM service in control panel.
PS: I had tried resetting the password inside VMM’s settings > Security > run as account > my host admin account. But that was not taking, throwing an error saying that the account was not found in the domain or something 🙁
Do you know that System Center Virtual Machine Manager (VMM) lets you create an identical clone of a running VM?
Yes! you do not even have to shut down a VM . How cool is that!
1) While going through the cloning process wizard in VMM, choose to leave the NIC disconnected
If you do not leave the NIC connected, you will have duplicate IP addresses on the network, when the cloned VM boots up.
2) After the cloning process completes, remember to run sysprep.
Yes, there have been some reports that VMM runs sysprep when it creates a clone, but I have confirmed myself (using psgetsid utility) that the clone and the original have the same SID and have the same hostname. They are virtually identical. So, you MUST run sysprep.