Solved

Migrating vCenter machine fails - why?

Posted on 2016-08-24
16
24 Views
Last Modified: 2016-09-28
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
0
Comment
Question by:huntson
  • 10
  • 6
16 Comments
 
LVL 119
ID: 41769513
are you migrating a replica copy, which is supposed to be "in step" "in sync" with the parent ?

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.
0
 

Author Comment

by:huntson
ID: 41769515
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.
0
 
LVL 119
ID: 41769555
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!).
0
Three Reasons Why Backup is Strategic

Backup is strategic to your business because your data is strategic to your business. Without backup, your business will fail. This white paper explains why it is vital for you to design and immediately execute a backup strategy to protect 100 percent of your data.

 

Author Comment

by:huntson
ID: 41772281
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?
0
 
LVL 119
ID: 41772372
Are we referring to the replica which has been created ?
0
 

Author Comment

by:huntson
ID: 41772381
Yes indeed.  I can't migrate it as it keeps failing with the error mentioned above.
0
 
LVL 119
ID: 41772385
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
0
 

Author Comment

by:huntson
ID: 41772392
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.
0
 
LVL 119
ID: 41772413
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 ?
0
 

Author Comment

by:huntson
ID: 41772437
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.
0
 

Author Comment

by:huntson
ID: 41772451
What information can I provide so you can better understand what the potential problem is?
0
 

Author Comment

by:huntson
ID: 41772460
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/
0
 
LVL 119
ID: 41772578
logs, escalate  to VMware Support.
0
 

Author Comment

by:huntson
ID: 41773024
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!!
0
 

Accepted Solution

by:
huntson earned 0 total points
ID: 41813055
Turns out it was related to the NAS crashing (Synology) under iSCSI load
0
 

Author Closing Comment

by:huntson
ID: 41819415
Found answer
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In this article, I will show you HOW TO: Suppress Configuration Issues and Warnings Alert displayed in Summary status for ESXi 6.5 after enabling SSH or ESXi Shell.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
This video shows you how easy it is to boot from ISO images for virtual machines with the ISO images stored on a local datastore on the ESXi host.

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question