000016730 - How to move a 5.x Database to a new Server for RSA Archer GRC

Document created by RSA Customer Support Employee on Jul 4, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000016730
Applies ToRSA Product Set: Archer
RSA Version/Condition: 5.x
IssueThe Archer database needs to be moved to a different server. What is the procedure for doing that?
 
CauseDatabase needs to be moved because of hardware upgrade or other reason.
Resolution
Procedure for moving database

  1. Open the Archer Control Panel and navigate to the Job Engine Manager
  2. Check the box labelled “Discontinue processing new jobs” and click Save.
  3. Return to the Job Engine Manager page and ensure that there are no jobs listed in the “Running Jobs” window. If there are, refresh periodically until all currently executing jobs have completed.
  4. Close the Archer Control Panel.
  5. On each Archer Web and/or Archer Services server, stop IIS and Archer Services in the following order:
    1. World Wide Web Publishing Service
    2. Archer Services – Job Engine
    3. Archer Services – Queuing Service
    4. Archer Services – Configuration Service
  6. Backup the Archer Instance and Configuration Databases.
  7. Restore the Archer Instance and Configuration Databases on the new server.
  8. Verify SQL Accounts as DB_OWNER to the Archer Instance and Configuration Databases on the new server.
  9. Run the following two scripts on the Archer Instance Database on the new server:
    delete from tblSearchMessageContent
    delete from tblSearchMessageQueue

  10. On each Archer Web and/or Archer Services server, open the ArcherTech.Services.ConfigurationService.exe.config file for edit.  (Typically installed in C:\Program Files\RSA Archer\Services)
  11. Find/verify the <connectionStrings> node in the configuration file and ensure/change (according to your scenario)  the SQL Connection from the old server to the new server. 

Note:  this will be the connection string for the Archer Configuration Database, NOT the Archer Instance Database. 
For example, change:

add name="SqlDB" connectionString="Server=myoldserver;Database=myoldconfigurationdatabase;UID=myolduid;PWD=myoldpwd;" providerName="System.Data.SqlClient" />

To this:

<add name="SqlDB" connectionString="Server=myNewServer;Database=myNewConfigurationDatabase;UID=myewuid;PWD=mynewpwd;" providerName="System.Data.SqlClient" />


Windows Integrated connection string example:

<add name="SqlDB" connectionString="Server=myNewServer;Database=myNewConfigurationDatabase;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />


  1. Save the changes to the ArcherTech.Services.ConfigurationService.exe.config file.
  2. On each Archer Web and/or Archer Services server, start Archer Services
    – Configuration Service only.
  3. On each Archer Web and/or Archer Services server, start the Archer Control Panel and verify that your instance is displayed in the Instances List.
  4. Close the Archer Control Panel on all but one of the Web/Services servers.
  5. On the one server with the Archer Control Panel still open, navigate to Instances -> [YourInstance]->Database.  Enter the new connection information for the instance database.
  6. On each Archer Web and/or Archer Services server, restart Archer Services – Configuration Service.
  7. On each Archer Web and/or Archer Services server, start the remaining Services
    in the following order:
    a.) Archer Services – Queuing Service
    b.) Archer Services – Job Engine
    c.) World Wide Web Publishing Service
  8. Navigate to the Archer Login page and verify that you can now login to the Framework.
  9. Open the Archer Control Panel and navigate to Plugins > Job Engine Manager.
  10. Uncheck the box labelled “Discontinue processing new jobs” and click Save.
  11. Use the script provided with the Archer Installer to deploy the RSA Archer Database Maintenance Jobs. The "jobDeployScript.sql" file is typically located in C:\Program Files\RSA Archer\Tools or wherever Archer was installed.
 
Legacy Article IDa60205

Attachments

    Outcomes