ADC

Synchronize GSLB static proximity database

Synchronizing a global server load balancing (GSLB) static proximity database requires that one of the sites be identified as the parent GSLB node. Any site in the topology can be designated as the parent node. The rest of the GSLB nodes are automatically designated as child nodes.

Synchronizing GSLB static proximity databases synchronizes the files in the /var/netscaler/locdb directory across the child nodes. During the synchronization process, the parent node fetches the running configuration from each of the child nodes and compares it to the configuration on the parent node. The parent GSLB node uses the rsync program to synchronize the static proximity database across the child nodes. To speed up the synchronization process, the rsync program makes only enough changes to eliminate the differences between the two files. The synchronization process cannot be rolled back.

The following example synchronizes Site2, which is a child site, to parent site Site1. The administrator enters the sync gslb config command on Site1:

sync gslb config -nowarn
Sync Time: Dec 19 2024 8:55:8
Retrieving local site info: ok
Retrieving all participating gslb sites info: ok
gslb_site1[Master]:
        Getting Config: ok
gslb_site2[Slave]:
        Getting Config: ok
        Comparing config: ok
        Syncing gslb static proximity database: ok
        Syncing inbuilt gslb static proximity database: ok
        Applying changes: ok
 Done
<!--NeedCopy-->
Synchronize GSLB static proximity database

In this article