How to redirect the SQL Database connection for Data Protection
Article ID: 115233
Updated On:
Products
CA Security Command Center
CA Data Protection (DataMinder)
CA User Activity Reporting
Issue/Introduction
There may be some scenarios where it becomes necessary to host a CA Data Protection SQL database on a different physical server. For example, where old hardware is being decommissioned or the hosting architecture is being upgraded. This article outlines the steps required to redirect the Database connection?
Environment
CA Data protection 15.x
Resolution
The following steps assume the following:
(a) The server hosting the CMS\Gateway is remaining unchanged other than the Database it connects with is being reloacted and
(b) the database Name remains the same on its new host machine.
1. Stop the CA Data Protection Infrastructure on the CMS\Gateway server.
2. Back up the Database in its original location.
3. Restore the Database to its the new location.
4. Ensure the Data Protection Database User names for the Primary (default WGNUser) and Search (default WGNSearch) users exist on the new Database machine with the respective Username, Password, User Mappings and Server Roles being the same as the originating system.
5. Backup the ‘startup.properties’ files located in the %wgninstalldir%\System directory
For example:
C:\program Files (x86)\CA\CA DataMinder\system\
6. Edit the ‘startup.properties’ file updating the information relating to the new database host in the sections highlighted below:
[Database]
db.jdbcDriver=com.wgn.jdbc.sqlserver.SQLServerDriver
db.jdbcDatabase=jdbc:wgn:sqlserver://<newDBserver:port>;database=<DBname>
db.shareConnections=True
db.Machine=<newDBserver>
db.SchemaName=<DBname>
db.SchemaLocation=<DBname>
db.DataLocation=<path>
For Example:
[Database]
db.jdbcDriver=com.wgn.jdbc.sqlserver.SQLServerDriver
db.jdbcDatabase=jdbc:wgn:sqlserver://SQLServer:1433;database=WGN_15SQL
db.shareConnections=True
db.Machine=SQLServer
db.SchemaName=WGN_15SQL
db.SchemaLocation=WGN_15SQL
db.DataLocation=C:\\ProgramData\\CA\\CA DataMinder\\data\\
Note:
If using an SQL Server hosting more than one instance the format differs please see below.
[Database]
db.jdbcDriver=com.wgn.jdbc.sqlserver.SQLServerDriver
db.jdbcDatabase=jdbc:wgn:sqlserver://<newDBserver:port>;database=<DBname>
db.shareConnections=True
db.Machine=<newDBserver>\\<DBInstance>
db.SchemaName=<DBname>
db.SchemaLocation=<DBname>
db.DataLocation=<path>
For Example:
[Database]
db.jdbcDriver=com.wgn.jdbc.sqlserver.SQLServerDriver
db.jdbcDatabase=jdbc:wgn:sqlserver://SQLServer:1433;database=WGN_15SQL
db.shareConnections=True
db.Machine=SQLServer\\DLP
db.SchemaName=WGN_15SQL
db.SchemaLocation=WGN_15SQL
db.DataLocation=C:\\ProgramData\\CA\\CA DataMinder\\data\\
7. Edit the registry:
HKLM\SOFTWARE\Wow6432Node\ComputerAssociates\CA DataMinder\CurrentVersion\Properties
DatabasePort: <port>
DatabaseServer = <newDBserver>
For Example
DatabasePort: 1433
Database Server SQLServer
If using an SQL Server hosting more than one instance the format differs please see below.
DatabasePort: <port>
DatabaseServer = <newDBserver>\<DBInstance>
For Example
DatabasePort: 1433
Database Server SQLServer\DLP
8. Restart the CA Data Protection Infrastructure on the CMS server.
9. Check the Activity logs (locate in %wgndatadir%\logs) to ensure that the CA Infrastructure service is starting correctly.
(a) The server hosting the CMS\Gateway is remaining unchanged other than the Database it connects with is being reloacted and
(b) the database Name remains the same on its new host machine.
1. Stop the CA Data Protection Infrastructure on the CMS\Gateway server.
2. Back up the Database in its original location.
3. Restore the Database to its the new location.
4. Ensure the Data Protection Database User names for the Primary (default WGNUser) and Search (default WGNSearch) users exist on the new Database machine with the respective Username, Password, User Mappings and Server Roles being the same as the originating system.
5. Backup the ‘startup.properties’ files located in the %wgninstalldir%\System directory
For example:
C:\program Files (x86)\CA\CA DataMinder\system\
6. Edit the ‘startup.properties’ file updating the information relating to the new database host in the sections highlighted below:
[Database]
db.jdbcDriver=com.wgn.jdbc.sqlserver.SQLServerDriver
db.jdbcDatabase=jdbc:wgn:sqlserver://<newDBserver:port>;database=<DBname>
db.shareConnections=True
db.Machine=<newDBserver>
db.SchemaName=<DBname>
db.SchemaLocation=<DBname>
db.DataLocation=<path>
For Example:
[Database]
db.jdbcDriver=com.wgn.jdbc.sqlserver.SQLServerDriver
db.jdbcDatabase=jdbc:wgn:sqlserver://SQLServer:1433;database=WGN_15SQL
db.shareConnections=True
db.Machine=SQLServer
db.SchemaName=WGN_15SQL
db.SchemaLocation=WGN_15SQL
db.DataLocation=C:\\ProgramData\\CA\\CA DataMinder\\data\\
Note:
If using an SQL Server hosting more than one instance the format differs please see below.
[Database]
db.jdbcDriver=com.wgn.jdbc.sqlserver.SQLServerDriver
db.jdbcDatabase=jdbc:wgn:sqlserver://<newDBserver:port>;database=<DBname>
db.shareConnections=True
db.Machine=<newDBserver>\\<DBInstance>
db.SchemaName=<DBname>
db.SchemaLocation=<DBname>
db.DataLocation=<path>
For Example:
[Database]
db.jdbcDriver=com.wgn.jdbc.sqlserver.SQLServerDriver
db.jdbcDatabase=jdbc:wgn:sqlserver://SQLServer:1433;database=WGN_15SQL
db.shareConnections=True
db.Machine=SQLServer\\DLP
db.SchemaName=WGN_15SQL
db.SchemaLocation=WGN_15SQL
db.DataLocation=C:\\ProgramData\\CA\\CA DataMinder\\data\\
7. Edit the registry:
HKLM\SOFTWARE\Wow6432Node\ComputerAssociates\CA DataMinder\CurrentVersion\Properties
DatabasePort: <port>
DatabaseServer = <newDBserver>
For Example
DatabasePort: 1433
Database Server SQLServer
If using an SQL Server hosting more than one instance the format differs please see below.
DatabasePort: <port>
DatabaseServer = <newDBserver>\<DBInstance>
For Example
DatabasePort: 1433
Database Server SQLServer\DLP
8. Restart the CA Data Protection Infrastructure on the CMS server.
9. Check the Activity logs (locate in %wgndatadir%\logs) to ensure that the CA Infrastructure service is starting correctly.
Additional Information
Please note the direction of the slashes in the syntax below (forwards / and backwards \) is contextually correct and should be used as verbatim.
Feedback
Yes
No
Powered by
