Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

aux.xml file retained on datastore after VM Migration

Posted on 2015-01-05
3
Medium Priority
?
3,435 Views
Last Modified: 2015-01-14
Hi there,

I successfully migrated a couple of VMs from the local host datastore to shared storage.
However after migration, i see there is a '-aux.xml' file that has remained on the local datastore for each VM that was migrated. I want to use the local datastore for Backup To Disk jobs.

A quick google search reveals that this file is used to track changes occurring during snapshot activities?
 I just need clarity on whether if i delete these files, there will be big issues? (VM failures/errors).
Or should i just manually move the file and add it to the VM folder at it's new location?

Thanks
0
Comment
Question by:Pyrex Visuan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 123

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 40531184
There should be no issues in removing the file.

We always move the file, and check after a few days, if there are any issues, before finally removing from the datastore.
0
 

Author Comment

by:Pyrex Visuan
ID: 40531270
Thanks Andrew
0
 
LVL 123
ID: 40531296
no problems
0

Featured Post

Simple, centralized multimedia control

Watch and learn to see how ATEN provided an easy and effective way for three jointly-owned pubs to control the 60 televisions located across their three venues utilizing the ATEN Control System, Modular Matrix Switch and HDBaseT extenders.

Question has a verified solution.

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

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.
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…

704 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