Server Backup

SpecLog server stores all repositories in a central SQL server database.

Each client holds a local snapshot with a copy of the repository. However, not all commands that were received by the server are necessarily synchronized to all clients.

###State to backup for desaster recovery The following state has to be backed up regularly:

• repository data: the SQL sever database used by the SpecLog server instance

It is recommended, to additionally backup the following state after each configuration change from the server instance program directory (default: %programfiles%\TechTalk\SpecLog\Server)

• server configuration files: *.config files
• server binaries: can be also re-installed with simple file copy from another installation
• server admin token file: can be also re-initialized using SpecLog.ServerManager resetadmin (see SpecLog-ServerManager)
• user token files, as they are created: can be also recovered from the server using SpecLog.UserManager gettoken (see Server-Access-Management)

The following temporary state located in %ProgramData%\TechTalk\{SpecLogInstanceName} is not necessary to be backed up:

• \Snapshots: containing a snapshot cache file for each repository on the server
• \Plugins: containing a local repository for each repository/plugin active on the server

###Restoring the server The server can be restored using the following steps:

1. Restore the server binary folder with the configuration files and the server admin token file
2. Restore the SQL server database of the SpecLog server instance
3. Re-initialize the temporary state of the server calling: SpecLog.ServerManager update from the server bin directory. This will re-create the temporary snapshot files for the server and the plug-ins enabled on the server.
4. Clients should discard their local repository files after a restore, that were connected to the server, and download a fresh snapshot from the server using the "Connect to shared repository"Shared-Repository command.