Product Documentation

Synchronizing GSLB Static Proximity Database

Apr 08, 2014

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

Synchronizing GSLB static proximity databases synchronizes the files in the /var/netscaler/locdb directory across the slave nodes. During the synchronization process, the master node fetches the running configuration from each of the slave nodes and compares it to the configuration on the master node. The master GSLB node uses the rsync program to synchronize the static proximity database across the slave 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 slave site, to master site Site1. The administrator enters the sync gslb config command on Site1:

sync gslb config -nowarn  
Sync Time: Feb 24 2014 14:56:16  
Retrieving local site info: ok  
Retrieving all participating gslb sites info:   
0 bytes in 0 blocks  
ok  
site1[Master]:  
        Getting Config: ok  
site2[Slave]:  
        Syncing gslb static proximity database: ok  
        Getting Config: ok  
        Comparing config: ok  
        Applying changes: ok  
 Done