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

My Subscriptions

Loading

Knowledge Base

Forcing replication between ADAM databases (1021805)

Last Updated: 1/16/2023Categories: How toTotal Views: 110806Language:
Chinese (Simplified)KoreanJapaneseEnglish

8 like this article

Subscribe to get an email
newsletter with new updates

8 people found this helpful Please provide article feedback:

Symptoms

Connection broker pool information between main and replica brokers is out of sync.

Newly created pool on one broker does not show on the Admin page of its replica broker.

Event logs on the Connection Brokers show that ADAM was unsuccessful in replicating with at least one other server for several hours.

The ADAM Windows Event viewer has entries similar to:

Error,"1864","05/12/2010 10:48:55","ADAM [VMwareVDMDS] Replication","5","NT AUTHORITY\ANONYMOUS LOGON","This is the replication status for the following directory partition on this directory server. Directory partition: CN=Configuration,CN={F8BD78C6-ACF1-47B6-96B5-2E4320461172} This directory server has not recently received replication information from a number of directory servers.

Resolution

Local Adam Database:
Run this command on all Connection Brokers in the same ADAM instance to show the replication neighbors and the last time they replicated

repadmin.exe /showrepl localhost:389 DC=vdi,DC=vmware,DC=int

Run this command on all Connection Brokers in the same ADAM instance to force the replication:

repadmin.exe /replicate localhost-FQDN:389 remote-host-FQDN:389 dc=vdi,dc=vmware,dc=int

Note: Replace localhost-FQDN to FQDN of the local server and remotehost.-FQDN with FQDN of the destination server.

For example:

repadmin.exe /replicate CS1.domain.local:389 CS2.domain.local:389 dc=vdi,dc=vmware,dc=int

This command will check to ensure replication is not disabled.

repadmin /options localhost:389 -DISABLE_OUTBOUND_REPL -DISABLE_INBOUND_REPL

Cloud Pod Architecture - Global ADAM DB:

Note: Ports (22389) and the location of the DB (vdiglobal) differ.

Check replication neighbours:

repadmin.exe /showrepl localhost:22389 dc=vdiglobal,dc=vmware,dc=int

Check replication is not disabled:

repadmin /options localhost:22389

(Note: results should be: Current DSA options: (none))

Ensure replication is not disabled:

repadmin /options localhost:22389 -DISABLE_OUTBOUND_REPL -DISABLE_INBOUND_REPL

Force replication:

repadmin.exe /replicate localhost:22389 remote-host-FQDN:22389 dc=vdiglobal,dc=vmware,dc=int

Related Information

Run this command to ensure that replication is not disabled:

repadmin /options localhost:389 -DISABLE_OUTBOUND_REPL -DISABLE_INBOUND_REPL

ADAM データベース間でレプリケーションを強制する
强制在 ADAM 数据库之间执行复制

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)KoreanJapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon

Related Versions:

VMware Horizon 8

VMware Horizon 7

Take Our Survey

Support Assistant