huntson
asked on
Migrating vCenter machine fails - why?
When I migrate a backup of my vCenter machine it keeps failing. I tried live first and when that didn't work I setup another vCenter instance and tried migrating while the original was shut down and I keep getting the attached image of non descriptor errors. Any clue where I can look? vCenter and ESXI 6.
Screen-Shot-2016-08-24-at-6.18.55-PM.png
Screen-Shot-2016-08-24-at-6.18.55-PM.png
ASKER
I'm using Nakivo to replicate. I messed up the primary one and renamed the replica. I'd like to migrate it to the primary ESXi store so it retains the same name as what I renamed it to.
So, use Nakivo to failover, or break the replication.
There are procedures to follow, just rename-ing and carrying on is not the correct procedure. (as you've experienced!).
There are procedures to follow, just rename-ing and carrying on is not the correct procedure. (as you've experienced!).
ASKER
I'm a bit confused. You're saying that the virtual machines that Nakivo creates aren't able to be moved around like normal virtual machines? Can you elaborate?
Are we referring to the replica which has been created ?
ASKER
Yes indeed. I can't migrate it as it keeps failing with the error mentioned above.
Where is the replica at present ?
where do you want to migrate to ?
is the original VM still present ?
Have you failed over to this new VM, and then fail it back ?
Nakivo does create normal VMs, which can be manipulated in the same way as any other VMs, BUT.....there are Jobs, which allow you easily to Failover to new VM (replica) and then Fail it back! so you don't have to complete any manually manipulation, or rename and migrate
where do you want to migrate to ?
is the original VM still present ?
Have you failed over to this new VM, and then fail it back ?
Nakivo does create normal VMs, which can be manipulated in the same way as any other VMs, BUT.....there are Jobs, which allow you easily to Failover to new VM (replica) and then Fail it back! so you don't have to complete any manually manipulation, or rename and migrate
ASKER
Sorry if I've been vague. I had a VM that I've been replicating. I have two datastores of the same size connected via iSCSI so all my primary VMs are on one and my replicas are on the other. I messed up my primary VM and wound up deleting it.
In order to restore it I tried migrating the replica and it keeps failing; I tried migrating as this is what I am familiar with and most comfortable with. I will explore restore via Nakivo in the future.
In order to restore it I tried migrating the replica and it keeps failing; I tried migrating as this is what I am familiar with and most comfortable with. I will explore restore via Nakivo in the future.
Okay, so now failover.....using Nakivo.
This is a vCenter Server VM, so vCenter Server is down ? So how are you migrating ?
This should be standard VM, and standard VM rules apply, can you power it on ?
This is a vCenter Server VM, so vCenter Server is down ? So how are you migrating ?
This should be standard VM, and standard VM rules apply, can you power it on ?
ASKER
I've tried restoring via Nakivo and it takes 5 seconds, says it has restored and nothing changes. I have a tech support ticket open with them. I'd like to see what is up with my ESXi installation and why things aren't moving as vmotion tasks on other machines are also failing.
ASKER
What information can I provide so you can better understand what the potential problem is?
ASKER
This seems to be my exact problem but I'm not comfortable going through with all that work
http://the-orbit.net/lousycanuck/2014/12/17/vmware-vm-cant-be-cloned-moved-or-backed-up-no-problem/
http://the-orbit.net/lousycanuck/2014/12/17/vmware-vm-cant-be-cloned-moved-or-backed-up-no-problem/
logs, escalate to VMware Support.
ASKER
I figured that's what would be next. Unfortunately I do not have a support contract with them currently so I'm here hoping for an alternative solution. I was quite sure that no ISOs were mounted and the files weren't being used by other machines.
Some folks referenced deleting or consolidating the snapshots - that's what worked!!
Some folks referenced deleting or consolidating the snapshots - that's what worked!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Found answer
why are you messing with the replica....it should be left alone, until required.
otherwise break the replication....if you want to play with it and do other stuff.
Your not migrating a Backup, you are Migrating a Replica, there is a big difference between the two, if you were allowed to mess with it, replication would break, and then it would not be in sync with the Parent Production VM.