Server Backup

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

Each client stores a local snapshot with a copy of the repository. However, not all commands received by the server are synchronized with all clients.

Regular Backups (Disaster Recovery)

You should back up the following regularly:

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

You should also back up the following files in the server's program directory (default: %programfiles%\TechTalk\SpecLog\Server) whenever the server's configuration is updated:

• Server configuration files: *.config files
• Server binaries: You can also reinstall by simply copying the files from another installation
• Server admin token file: You can also recreate this file using SpecLog.ServerManager resetadmin (see SpecLog-ServerManager)
• User token files: Back these up as they are created. These files can be also recovered from the server using SpecLog.UserManager gettoken (see Server-Access-Management)

You do not need to back up the temporary state stored by SpecLog in %ProgramData%\TechTalk\{SpecLogInstanceName}, which includes:

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

Restoring the Server

To restore the server:

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 stored on the server by executing SpecLog.ServerManager upgrade from the server's bin directory. This re-creates the temporary snapshot files for the server and plug-ins enabled on the server.
4. Discard the local repository files on all clients after restoring the server. Download a fresh snapshot on each client by selecting using Connect to shared repository from the menu.