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

Usage of vSAN datastore unexpectedly increases after a planned migration with vSphere Replication (59396)

Last Updated: 7/30/2023Categories: TroubleshootingTotal Views: 4181Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

After a planned migration or test recovery with vSphere Replication is performed, the usage of the vSAN datastore increases unexpectedly under the following conditions:

The target datastore is a vSAN datastore in the target site for the target VMs.

Object Space Reservation > 0 is configured in the storage policies attached to the target VMs.

MPIT (Multiple points in time) snapshots are configured for the VMs.

For example, if Object Space Reservation in the storage policy is set to 100 (= 100%), the usage of the vSAN datastore by the target VM becomes double compared to the original VM.
If the vSAN datastore in the target site does not have extra space to accommodate the double sized VMs, a planned migration or a test recovery can fail.

Cause

This is an expected behavior of vSphere Replication.

With MPIT snapshots configured, a hbrimagedisk vmdk is created when a planned migration or a test recovery is performed.

The storage policy of a hbrimagedisk vmdk inherits its parents' storage policy. So a hbrimagedisk vmdk can consume the same amount of space as its parent's vmdk does.

Impact / Risks

This issue might cause unexpected vSAN datastore fullness. This issue can lead to a planned migration or a test failover to fail.

Resolution

Please remove the Object Space Reservation rule from the storage policy attached to the target VM's vmdk.
For example,

Open "VM Storage Policies" in the Web Client (Flex Client).

Select the storage policy that is applied to the VM.

Click "Edit" button

Remove "Object space reservation (%)" rule from the rule-set list.

Click "OK" to save the changes.

To remove the hbrimagedisk vmdk, please remove any snapshots of the target VM in the snapshot manager in the UI after a planned migration.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

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 Replication

VMware vSphere

VMware vSAN

VMware vCenter Site Recovery Manager

Related Versions:

VMware vSphere Replication 8.x

VMware vSphere Replication 6.x

VMware vSAN 6.x

VMware vCenter Site Recovery Manager 8.x

VMware vCenter Site Recovery Manager 6.5.x

VMware vCenter Site Recovery Manager 6.0.x

Take Our Survey

Support Assistant