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”
OK so here is a tricky problem with an easy fix.
Sometimes, in SC VMM 2012 some of my VMs are shown as “missing”. I cannot do anything to them using VMM. An easy fix is to fire up FCM (Failover Cluster Manager) and live migrate or quick migrate the VM (depending upon whether the VM is running or not). After that VMM will immediately refresh the VMs state to the correct one….stopped or running.
From time to time, I run into this issue with our Hyper-V environment. No matter how many times I upgrade the VM additions, SCVMM still is not able to detect it. It always ends up saying “not detected”.
Eventually I noticed that one of the the 6 Hyper-V related services which are usually running on the VM was having some trouble – the heartbeat service. Hmmm…that makes sense!
If I tried to start this service, I got the following error:
Error 1083: The executable program that this service is configured to run in does not implement the service.
While doing some searching on the net, I found out the solution here !!THANK YOU!!
As mentioned by that guy, the two things I need to know are shown below:
So I open the registry and add vmicheartbeat to the bottom of this Multi-String entry, like this:
After I click OK and restart the VM, the heartbeat service starts without any problem (automatically). Just do a refresh in VMM and now I see the VM additions version number. Yeah baby!
Thanks a lot to Jeremy!
I noticed that one of my VMs (on Hyper-V 2012) was using a lot of RAM. Strangely, there was no application which was using that much RAM. It was using 14.2/16 GB RAM. At that time task manager showed this:
And this in the details tab:
Notice that Oracle was using only 1.8GB and that was the highest user. Even if I total everything, it still was nowhere near 14 GB used. What was using all that RAM?
Continue reading “What is Driver Locked memory?”