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

Replication failures occur in VMware Database Management Essentials 1.0 (71175)

Last Updated: 1/30/2020Categories: InformationalTotal Views: 9546Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

An initial replication or full synchronization fails to complete.

Deltas fail to complete and DiskQueue is full errors may appear in the hbsrv.log from the VMware Database Management Essentials Snapshot Manager.

Cause

There are known issues currently affecting replication for VMware Database Management Essentials 1.0 on vSphere 6.7 GA and 6.7 U1.

First, there can be an issue where the replication appears to be in progress, but the checksum fails to complete. The replication fails to resolve until the host is rebooted.

Additionally, it is possible that more demand log chunks be scheduled for parallel transfer than the actual number that can be transmitted. If you are replicating a VM that is running on such a host and this coincides with a slow target host or temporary network errors, this might result in replication failure and DiskQueue is full errors.

Resolution

These Issues are resolved in vSphere 6.7 U2 and above.

Workaround

If the environment is encountering either of these issues, but cannot be updated to vSphere 6.7 Update 2 or above, the following steps can be used to work around the behavior and need to be applied to each affected ESXi host:

Migrate all VMs and power off the ones that cannot be migrated on the ESXi host.

Edit the advanced settings on the ESXi host and adjust the following items:

Set HBR.ChecksumUseChecksumInfo to 0

Set HBR.DemandlogTransferMaxNetwork to 63

Place the host in maintenance mode.

Reboot the ESXi host.

Confirm that the host is healthy, then remove the host from maintenance mode and reintroduce the workloads, as appropriate.

Please note, adjusting the checksum functionality can lead to the transmission of blocks that have not changed and it would be recommended to revert these changes after updating to a version that addresses the issues.

Related Information

For additional information regarding the configuration of the advanced settings on an ESXi host, please refer to the following:

Configuring advanced options for ESXi/ESX (1038578)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
如何使用 dbms_scheduler 程序启用/禁用在 Oracle 数据库中调度的作业 (71154)

KB
•
对于混合 vSAN 环境中的某些 I/O 工作负载，vSAN 层中可能会出现内存不足的情况，从而导致 I/O 失败，并且 vSAN 会将目标磁盘组标记为永久错误状态 (70827)

KB
•
移除智能卡时在 Ubuntu 18.4、16.4、SLED12SP3、SLES12SP3 和 SLED11SP4 上自动锁定屏幕 (71068)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Database Management Essentials

Related Versions:

VMware Database Management Essentials 1.x

Take Our Survey

Support Assistant