KSS failover setup

To enable rapid switchover if the primary KSS fails, you will need to preload the backup key onto a second server instance. Once this is complete, you need only to start the Atakama application on the backup server at the time of the switchover.

Backup server setup

Shut down Atakama on the primary server.
Perform all steps defined in the “Recovery Procedure” on the backup server.
Recommended: use a KSS client to verify the functionality of the backup server.
Shut down Atakama on the backup server.
Restart Atakama on the primary server.

Switchover procedure

If the primary KSS is temporarily offline (e.g., unplanned Windows update):

Confirm that Atakama is not running or connected to the Internet on the primary server.
Start Atakama on the backup server.

If the primary KSS dies (e.g., hard drive failure):

Start Atakama on the backup server, which will now take over as the primary KSS.
Add additional devices and recovery word sets so there are two mobile devices and two recovery word sets.
Repeat the steps from the “Backup Server Setup” (above) to set up a new backup server.

Notes:

Do not restart Atakama on the primary server until off-hours. Shut down the backup server before or as soon as possible after the primary server is started.
At no point should multiple instances of Atakama with the same ID (the primary and the backup) be running at the same time. This would cause client requests to fail.

Ensure the backup server is shut down when the primary server is brought back online.
Do not configure the backup server to launch Atakama on startup.

Throttling quotas are separately maintained on each server; data is not synchronized.
Profile changes (adding, replacing, and removing devices) should not be performed on the backup server instance.