Disaster Recovery procedure for Symantec Critical System Protection (SCSP)

book

Article ID: 155954

calendar_today

Updated On:

Products

Critical System Protection

Issue/Introduction

You would like to know data to backup in order to be able to rebuild Symantec Critical System Protection (SCSP) Server in the case of a failure.

 

Resolution

How to make a full SCSP Server backup?

 
1) Stop "Symantec Critical System Protection Server" service
 
 
2) Make a database backup (http://msdn.microsoft.com/en-us/library/ms186289.aspx). As an example (your company DBA is the only person responsible for this), here is a way to do it on SQL Server 2008:
 
 - Login to SQL Server Management Studio
 
 - Browse Databases, and right-click on SCSP database
 
 - Click on Tasks > Backup, then configure the backup settings and run it
 
    
 
 
3) Make a copy of certificates and server settings (below are default paths on 32bit system):
 
     C:\Program Files\Symantec\Critical System Protection\Server\agent-cert.ssl
     C:\Program Files\Symantec\Critical System Protection\Server\server-cert.ssl
     C:\Program Files\Symantec\Critical System Protection\Server\ui-cert.ssl
     C:\Program Files\Symantec\Critical System Protection\Server\tomcat\conf\server.xml
 
 
4) Note all settings used during initial SCSP install: ports, database instance (SCSP by default), database name (SCSPDB by default), database account (scspdba by default) and password, install path.
Additionally, you may export SCSP database accounts/passwords from SQL Server database (http://support.microsoft.com/kb/246133/).
 
 
5) Start "Symantec Critical System Protection Server" service
 
 
 
 
 
How to recover SCSP Server?
 
 
IMPORTANT: it is necessary to reinstall SCSP Server on a machine with the same hostname/IP address to recover server-agent communication (see TECH116309 for more details).
 
 
 
Situation A - Database backup not available, but you want to recover at least Server-Agent communication
 
Follow article HOWTO42154 (http://www.symantec.com/docs/HOWTO42154)
 
 
 
Situation B - Only database content has been corrupted, database structure is still valid
 
1) Stop "Symantec Critical System Protection Server" service
 
 
2) Restore database backup
 
 
3) If any database account needs to be re-created, you can find below their default configuration:
 
   - scsp_ops in Security > Logins
 
    
 
    
 
    
 
   - scsp_ops in SCSPDB > Security > Users
 
    
 
   - scsp_plugin in Security > Logins
 
    
 
    
 
    
 
   - scsp_plugin in SCSPDB > Security > Users
 
    
 
  - scspdba in Security > Logins
 
    
 
    
 
    
 
"sp_change_users_login" can be used as well to fix orphan account issue (http://msdn.microsoft.com/en-us/library/ms174378.aspx).
 
 
4) If needed, reinstall SCSP Server as described in "Begin re-installation of the SCSP Manager, making sure to select TOMCAT only" section from HOWTO42154 article (steps 9 to 14 should not be required).
Otherwise, start "Symantec Critical System Protection Server" service.
 
 
 
Situation C - SCSP server database needs to be completely rebuilt
 
1) Reinstall SCSP Management Server choosing to recreate the database schema, using previous SCSP Server install settings
 
    
 
 
2) Stop "Symantec Critical System Protection Server" service
 
 
3) Restore SCSP Server database backup over the new database created in previous step
 
 
4) Replace all certificate files and server.xml by the ones you backup previously (below are default paths on 32bit system):
 
     C:\Program Files\Symantec\Critical System Protection\Server\agent-cert.ssl
     C:\Program Files\Symantec\Critical System Protection\Server\server-cert.ssl
     C:\Program Files\Symantec\Critical System Protection\Server\ui-cert.ssl
     C:\Program Files\Symantec\Critical System Protection\Server\tomcat\conf\server.xml
 
 
5) If any database account needs to be re-created, you can find their configuration above, and use as well "sp_change_users_login" (see above for more details).
scsp_ops password can be then set appropriately in SQL Server Management Studio by following steps 9 to 13 from HOWTO42154 article.
 
 
6) Start "Symantec Critical System Protection Server" service
 

Applies To

SCSP Server with SQL Server database.

 

Attachments