Software configuration management process - Codematrix Software configuration management process - Codematrix Software configuration management process - Codematrix Software configuration management process - Codematrix Software configuration management process - Codematrix Software configuration management process - Codematrix Software configuration management process - Codematrix  
 
Codematrix - Navigation
 
 
Codematrix software configuration management
Configuration management software
SCM product info
SCM software downloads
Software version control and change management software
Configuration management software support
Training for software configuration management
Code Matrix Personal, Codematrix Professional, CodeMatrix Enterprise
Codematrix contact details
 
Home > Documentation
 
Download - Administrators Guide Administrator guide
 
Recovery

It is essential to implement a regular backup strategy, and procedures to recover the CodeMatrix database should a system failure occur. This section highlights issues to consider when implementing a recovery strategy.

Before restoring a CodeMatrix database the server must be stopped. See Stopping and starting the server for further information.

The saved database files should be copied to the original locations. NB the database structure uses cross linked files, therefore a partial recovery should not be attempted without discussing with CodeMatrix support.

Once the database is recovered the server should be started with the following command.

  cxs -recover <port>  

<port> should be a free port number on the server computer, but not the standard port. The server will start up and return the database to the backed up consistent state. Once complete it will allow a single client connection on the specified port. This allows a client to connect to examine the state before enabling the system. The client used for this operation should not be an active client with mounted workspaces. The client license validation is disabled in this mode so the client software may be installed on a different machine.

Once satisfied that the database recovery is successful the server should be stopped and restarted to re-enable the system. At this time the clients will reconnect and resynchronise their changes automatically if necessary.