How to migrate Control Compliance Suite (CCS) databases to another SQL Server.

book

Article ID: 180678

calendar_today

Updated On:

Products

Control Compliance Suite Unix Control Compliance Suite Windows

Issue/Introduction

 

Resolution

 The CCS database migration steps assume the following:

  • CCS-SQL-A = current SQL Server (source).
  • CCS-SQL-B = new SQL Server (destination).
  • User is migrating CCS databases from CCS-SQL-A to CCS-SQL-B.
  • CCS-SQL-A and CCS-SQL-B are in the same domain or child domain.
  • Both CCS databases are the same version.
  • User performing the migration has access to SQL Management Studio.
  • User has sysadmin rights on both SQL Servers.
Use the following steps to migrate CCS databases:
1. Begin by making note of the Application Server Credential used to connect to the database. In the CCS Console, go to >Settings >Secure Configuration >Application Server Credential and note the credential.
2. Close all CCS Consoles.
3. Stop the Symantec Application Server Service on computer with CCS Application Server role.
4. Open SQL Management Studio under the profile credential noted in Step 1 and connect to both SQL Server instances on CCS-SQL-A and CCS-SQL-B.
5. On CCS-SQL-A, right-click each of the following databases and select Properties:
  • for CCS 10.x databases: CSM_DB, CSM_EvidenceDB, and CSM_Reports.
  • for CCS 11 databases: CSM_DB, and CSM_Reports.
6. In each of the Properties windows select the Files page. In the Database files table scroll to the right to find the path for each of the listed files. Make note of the logical name and path for each file.
7. On CCS-SQL-A, right-click each of the databases and select Tasks >Take Offline.
8. On CCS-SQL-A, use Windows Explorer to find physical file locations of the mdf/ldf files noted in step 6.  Copy -- DO NOT DELETE OR MOVE -- all the CCS .mdf/.ldf/.ndf files to the server data location on CCS-SQL-B.
 
For Example: \Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA
CCS 11 database files
CSM_DB.mdf
CSM_DB_log.LDF
CSM_Queries.mdf
CSM_Reports.mdf
CSM_Reports_EvidenceStorage_<YYYYMMDD>.ndf (may be multiple files)
CSM_Reports_log.LDF
CCS 10.x database files
CSM_DB.mdf
CSM_DB_log.LDF
CSM_EvidenceDB.mdf (CCS 10.x)
CSM_EvidenceDB_log.LDF (CCS 10.x)
CSM_Reports.mdf
CSM_Reports_log.LDF
 
9. On CCS-SQL-A, right-click each CCS database >Tasks >Bring Online. Again those database are CSM_DB, CSM_Reports and CSM_EvidenceDB (in CCS 10.x only).
10. On CCS-SQL-B, configure SQL login, under Security>Logins, right-click and select New Login. Create a login for the account noted in Step 1. The Security login settings on CCS-SQL-B must mirror the login settings from CCS-SQL-A.
11. On CCS-SQL-B, right-click Databases >Attach... and Add… each of the CCS database mdf files copied in step 8. This will create an entry under Databases on CCS-SQL-B for each database.
12. On CCS-SQL-B, right-click each database >Tasks >Bring Online for all the CCS databases, CSM_DB, CSM_Reports and CSM_EvidenceDB (CCS 10.x).
NOTE: For this to work properly both sets of CCS databases, those on CCS-SQL-A and CCS-SQL-B, need to be online.
13. Start the Symantec Application Server Service on computer with CCS Application Server role.
14. Launch CCS console.
15. In CCS Console, go to >Settings >Secure Configuration >Production Database Connection, enter/select CCS-SQL-B computer and select Update button.
16. In CCS Console, go to >Settings >Secure Configuration >Report Database Connection, enter/select CCS-SQL-B computer and select Update button.
17. Close CCS console.
18. Launch CCS console.
19. In CCS Console, go to >Settings >Secure Configuration >Production Database Connection and verify connection to CCS-SQL-B computer.
20. In CCS Console, go to >Settings >Secure Configuration >Report Database Connection and verify connection to CCS-SQL-B computer.
21. It is now safe to ‘Take Offline’ and ‘Detach’ databases on CCS-SQL-A.