In the event that an online initialization is not possible, the following steps can be used to initialize a server.
  1. From another server in the replication topology, backup the userRoot, adminRoot, schema, replicationChanges backends to the /bak directory. If encrypted attributes are present, then the encryption-settings backend should also be exported. One or more encryption settings IDs may need to be exported and imported.
    $ <source-server-root>/bin/backup --backendID userRoot -d bak/userRoot 
    $ <source-server-root>/bin/backup --backendID adminRoot -d bak/adminRoot 
    $ <source-server-root>/bin/backup --backendID schema -d bak/schema 
    $ <source-server-root>/bin/backup --backendID replicationChanges -d bak/replicationChanges 
    $ <source-server-root>/bin/encryption-settings export --id ID --output-file bak/exported-key
  2. Copy the bak directory to the new replica.
    $ scp -r <source-server-root>/bak <user>@<destination-server>:<destination-server-root>/bak
  3. Stop the server and restore the userRoot, changelog, adminRoot, replicationChanges backends. If the encryption-settings backend was exported, it should also be reimported.
    $ <destination-server-root>/bin/restore -d bak/userRoot 
    $ <destination-server-root>/bin/restore -d bak/adminRoot 
    $ <destination-server-root>/bin/restore -d bak/schema 
    $ <destination-server-root>/bin/restore -d bak/replicationChanges 
    $ <destination-server-root>bin/encryption-settings import --input-file bak/exported-key --set-preferred
         Enter the PIN used to encrypt the definition:
  4. Start the server using bin/start-server.