Attaching an existing installation of the Symantec Critical System Protection [SCSP] management server to a Database [DB] where the name and/or location has been moved.

book

Article ID: 158140

calendar_today

Updated On:

Products

Critical System Protection

Issue/Introduction

You have moved your development DB to a production DB (Server name or instance has been changed) and now need to attach the SCSP management server to it.

 

Resolution

A full migration of the DB must be performed before the following steps are performed.

 

 

Steps to attaching an existing installation of the SCSP Management Server to a Database where the name and/or location has been moved:

1. You will need to modify the server.xml. You can find the server.xml> c:\program files\symantec\critical system protection\server\tomcat\conf\server.xml

2. Stop the SCSP service and modify the server.xml as shown below to reflect the new DB location and name;

OLD
<Resource name="Database-Console"
                    auth="Container"
                    type="javax.sql.DataSource"
                    url="jdbc:jtds:sqlserver://127.0.0.1/SCSPDB;instance=SCSP"
 
<Resource name="Database-Agent"
                    auth="Container"
                    type="javax.sql.DataSource"
                    url="jdbc:jtds:sqlserver://127.0.0.1/SCSPDB;instance=SCSP"
 
NEW
 
<Resource name="Database-Console"
                    auth="Container"
                    type="javax.sql.DataSource"
                    url="jdbc:jtds:sqlserver://192.168.2.24/SCSPDB;instance=SCSPA"
 
<Resource name="Database-Agent"
                    auth="Container"
                    type="javax.sql.DataSource"
                    url="jdbc:jtds:sqlserver://192.168.2.24/SCSPDB;instance=SCSPA"
 
3. Restart the SCSP service.

Applies To

SCSP