10. Replication

The handle server allows for automatic replication of handles to one or more mirror servers. These mirror servers can be used to provide redundancy for resolution or simply as backup for disaster recovery. It should be noted that mirror servers cannot be used for handle administration.

Setting up a Single Mirror Handle Server

See 5. Advanced Server Configuration, for details on the configuration settings outlined below.

• Run SimpleSetup. as explained in the 'INSTALL.txt' file.

• Modify the mirror's config.dct:
  • server_admins
  • this_server_id (if more than 1 server in HS_SITE)
  • replication_authentication

• Modify the primary server's configuration:
  • Add the replication public key value(`replpub.bin') to the handle specified in replication_authentication.
  • Add that handle to the primary server's replication_admins group in its `config.dct' file.
• ONLY if mirror servers are under the same HS_SITE save the naming authority's second site (`siteinfo.bin' for both mirrors) into each mirror server's directory

The `txnsrcsv.bin' file is the `siteinfo.bin' file from the primary server.

The `txnstat.dct' file will be created once the server has replication information to store. When the mirror server is first started, the server has to "dump" all of the handles from the primary server. When that process is done, the mirror server creates and saves the `txnstat.dct' file with the current transaction ID from each primary server.

Setting up a Second Mirror Handle Server

If the 1st mirror server's db file is relatively large, before starting the second mirror server, it may be necessary to copy the `handles.jdb', `nas.jdb', `txnstat.dct' files to the second mirror's directory before starting it. Be sure the 1st mirror server is shut down while copying the files.

Additional notes

When servers are in the same site the handles for that service are distributed evenly across the site. Mirrors should be able to replicate from either the primary or existing mirrors.