Loading

×Sorry to interrupt
CSS Error

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

Skip to main content

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

Creating snapshots in a different location than default virtual machine directory for VMware ESXi and VMware ESX (1002929)

Last Updated: 10/14/2019Categories: How toTotal Views: 325885Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

27 like this article

Subscribe to get an email
newsletter with new updates

27 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Details

In ESX/ESXi 3.x and 4.x, all files comprising snapshots are created in the virtual machine's working directory. By default, the working directory is the same directory as that of the virtual machine (.vmx) configuration file. If the virtual disk (.vmdk) file is located on a different datastore than that of the virtual machine, the virtual disk redolog (-delta.vmdk or -sesparse.vmdk) files are created along with the virtual machine's (.vmx) configuration file instead of the virtual disk (.vmdk) file.

In ESXi 5.0 and later, virtual disk redolog (-delta.vmdk) files for snapshots are placed in the same directory as the parent virtual disk (.vmdk) file.

You may want to change the location (new directory on the same or alternative datastore) where virtual disk redolog (-delta.vmdk) files are created, to:

Create snapshots but do not have enough space on the VMFS volume.

Power on a virtual machine when does not have enough space to create a swap file on the VMFS volume.

This article provides steps to change the default virtual machine working directory location used for snapshots on ESX/ESXi 3.x and later.

Solution

To change the default virtual machine working directory location for snapshots (to a new directory on the same or alternative datastore):

Note: To proceed you need the UUID of the target datastore. You can run the esxcli storage filesystem list command in an SSH session to generate a compact list of the LUNs currently connected to the ESXi host, including their UUIDs and VMFS version. For more information see Identifying disks when working with VMware ESXi/ESX (1014953).

ESX/ESXi 4.1 and earlier

Power off the virtual machine.

Open the virtual machine's .vmx configuration file using a text editor. For more information, see Tips for editing a .vmx file (1714).

Add a line to the .vmx configuration file of the virtual machine, specifying a full path to the directory on a datastore for the workingDir option:

workingDir = "new_path_location"

Example:

workingDir = "/vmfs/volumes/46f1225f-552b0069-e03b-00145e808070/vm-snapshots"

This ensures that subsequently created snapshots cause new virtual disk redolog (-delta.vmdk) files to be created in the defined directory. In this example, the redolog files are created in the vm-snapshots directory.

When a virtual machine is powered on for the first time, a new swap file is created in the working directory of the virtual machine. By default, the virtual machine writes the swap file in the same directory as the.vmx configuration file. If you would like to change this location, add the new location to this line in the.vmx file:

sched.swap.dir = "path_to_vm_directory"

Note: This step is optional. Adding the new file location ensures that the swap file is created in the working directory.

Save the changes and close the virtual machine's .vmx configuration file.

Reload the virtual machine configuration by unregistering and re-registering it in the inventory. For more information, see Registering or adding a virtual machine to the inventory (1006160).

Power on the virtual machine.

ESXi 5.0 and later

Power off the virtual machine.

Open the virtual machine's .vmx configuration file using a text editor. For more information, see Tips for editing a .vmx file (1714).

Add these lines to the .vmx configuration file of the virtual machine, specifying a full path to the directory on a datastore for the workingDir option:

workingDir = "new_path_location"
snapshot.redoNotWithParent = "true"

Example:

workingDir = "/vmfs/volumes/46f1225f-552b0069-e03b-00145e808070/vm-snapshots"
snapshot.redoNotWithParent = "true"

This ensures that subsequently created snapshots cause new virtual disk redolog (-delta.vmdk) files to be created in the defined directory. In this example, the redolog files are created in the vm-snapshots directory.

Note: In ESXi 5.5, if the virtual disk is larger than 2TB in size, the redolog files will be -sesparse.vmdk format rather than -delta.vmdk.

When a virtual machine is powered on and the memory allocated to the virtual machine is greater than the memory reserved for it, a new swap file is created in the working directory of the virtual machine. By default, the virtual machine writes the swap file in the same directory as the.vmx configuration file. If you want to change this location, add the new location to this line in the.vmx file:

sched.swap.dir = "new_path_location"

Note: This step is optional. Adding the new file location ensures the swap file is created in the chosen directory. You might want to do this to keep the swap file with the virtual disk files, for example, or in a separate path from the original VM folder.

Save the changes and close the virtual machine's .vmx configuration file.

Reload the virtual machine configuration by unregistering and re-registering it in the inventory. For more information, see Registering or adding a virtual machine to the inventory (1006160).

Power on the virtual machine.

Notes:

Thesnapshot.redoNotWithParentoption in 5.x/6.0 can also be added from the vSphere Client. For more information, see Changing the location of snapshot delta files for virtual machines in ESXi 5.x (2007563).

If you are performing a storage vMotion or storage migration of a virtual machine that has its working folder set to a location other than the virtual machine directory, this change is not maintained and you must reconfigure it as necessary.

If you are performing a storage vMotion or storage migration of a virtual machine that has its working folder set to a location other than the virtual machine directory, the operation might fail with the error:

Cannot complete the operation because the file or folder already exists.

Additional Information

For translated versions of this article, see:

Español: Crear instantáneas en una ubicación distinta al directorio predeterminado de la máquina virtual (2055255)

Português: Criando snapshots em outra localização que não o diretório padrão da máquina virtual para o VMware ESXi e o VMware ESX (2144430)

日本語: デフォルトの仮想マシン ディレクトリとは異なる場所でのスナップショットの作成 (2079326)

简体中文: 在默认虚拟机目录以外的其他位置创建快照 (2075634)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

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 vSphere ESXi

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant