Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Taking Snapshots of Virtual Machines With Virtual Disks on Different Datastores Can Cause Datastores to Disappear From the VI Client (10043)

Last Updated: 4/9/2007Categories: Total Views: 22760Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

When a virtual machine is attached to two or more virtual disks (.vmdk files) where the disks are not on the same datastore and a snapshot is taken of the virtual machine (VM), a datastore might disappear from the Virtual Infrastructure (VI) Client for that VM and other snapshot functionality might break. For example, one possible scenario is that there is a VM with two .vmdk files, one on datastore1 where the .vmx file is also located and one on datastore2. When the snapshot is initiated, datastore2 disappears from the Virtual Infrastructure client view for that VM and you will be unable to delete the snapshot from that VM.

Solution

This is a known issue for ESX Server 3.0.1, VMware Consolidated Backup 1.0.2, <?xml:namespace prefix = st1 /><st1:place w:st="on"><st1:placename w:st="on">Virtual</st1:placename> <st1:placetype w:st="on">Center</st1:placetype></st1:place> 2.0.1 and all earlier versions of these products. The issue will be fixed in later versions of these products.

<?xml:namespace prefix = o />

This problem is not seen when the .vmdk files and .vmx are located on the same datastore. To work around this problem, move all .vmdk files onto the datastore on which the .vmx file (the virtual machine configuration file) is located before taking snapshots. The .vmdk files have to be renamed with vmkfstools –E before they can be moved to the same datastore.

Follow this procedure to rename one of the disks:

Make sure no snapshots of the virtual machine exist.

Note: If your virtual machine already has a snapshot, power off the virtual machine and delete the snapshot.

Power off the virtual machine.

Detach from the virtual machine the disk you plan to move, but do not delete the disk.

Log into the ESX Server system and use the following command to rename the disk:

vmkfstools -E <old_name> <new_name>

For example, to rename the disk foo.vmdk to bar.vmdk, enter vmkfstools -E foo.vmdk bar.vmdk.

From the VirtualCenter user interface (UI), add the renamed disk back to the virtual machine.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware Consolidated Backup

Related Versions:

VMware VirtualCenter 2.0.x

VMware Consolidated Backup 1.0.x

Take Our Survey

Support Assistant