This article describes the recommended procedure to move the ePO database from one SQL Server to another.

IMPORTANT: Before you begin the process explained in this article, you must back up your ePO server. See the following KB articles for more information:

• KB87976 - Overview of the ePolicy Orchestrator 5.x Disaster Recovery Snapshot feature
• KB66616 - ePolicy Orchestrator server backup and disaster recovery procedure

NOTES: The account used by ePO to access SQL must have the minimum needed permissions on the new server for ePO to function correctly. See KB75766 - SQL permissions needed to install and use ePolicy Orchestrator for details.

IMPORTANT: In ePO 5.10 and later, threat event information is split into its own database. Carry out the actions on both the main database (default name ePO_<ePO server name>) and the events database (default name ePO_<ePO server name>_Events).

Overview
To move the ePO database, follow the steps below in the order they’re listed:

1. Stop the ePO services.
2. Move the database.
3. Configure ePO and verify connectivity.
4. Start the ePO services.
5. Extra steps for extra Agent Handlers.
6. Optional: Remove service dependencies.

1 – Stop ePO services:
Before you make any changes, you must stop ePO services to prevent anything from accessing the database:

1. Click Start, Run, type services.msc, and click OK.
2. Right-click the following services and select Stop:
   
   On the ePO server:

2 – Move the database:

1. Make sure that the new database instance has the same collation as the old one.
   For details, see KB73717 - ePolicy Orchestrator supported SQL Server collation types.

2. On the current SQL Server, take a full backup of the ePO database using SQL Management Studio.
   If you’re unfamiliar with this process, see KB52126 - How to back up and restore the ePolicy Orchestrator database using SQL Server Management Studio.
   
   When complete, you have a backup (.BAK) file.
    
3. Copy the (.BAK) file to the new SQL Server.
4. Restore the backup file to the new server using SQL Management Studio.
   For details, see KB52126 - How to back up and restore the ePolicy Orchestrator database using SQL Server Management Studio.
   
   After the restore completes, the ePO database is visible in Management Studio on the new SQL Server.

3 – Configure ePO and verify connectivity:

1. On the ePO server only, start the McAfee ePolicy Orchestrator Application Server service.
2. Open a web browser and navigate to the core/config-auth database configuration page (https://localhost:8443/core/config-auth by default).
   
   NOTE: If needed, adjust the host name and port to match your custom configuration.
    
3. When you see the logon prompt, log on using an ePO Global Administrator account.
   
   The 'Configure Database Settings' page displays.
    
4. Type the details for the new SQL Server.
5. Click Test Connection.
   
   "The database connection was tested successfully" message displays.
   
   If any errors display, verify and correct the new SQL Server details until the connection test succeeds.
    
6. When the connection test is successful, click Apply.
   
   A prompt to restart the server displays.
    
7. Restart the McAfee ePolicy Orchestrator Application Server service.

4 – Start ePO services:

1. Click Start, Run, type services.msc, and click OK.
2. Right-click the following services and click Start:
   
   McAfee ePolicy Orchestrator Event Parser
   McAfee ePolicy Orchestrator Server

5 – Extra steps for extra Agent Handlers:
If you have more Agent Handlers, you must provide each one with the new SQL Server details by rerunning the initial setup wizard. Perform the following steps on each Agent Handler:

1. Open the folder where you extracted the contents of the ePolicy Orchestrator software installation package.
2. Copy the Agent Handler folder to the Agent Handler server system and double-click Setup.exe.
   
   The McAfee Agent Handler InstallShield wizard appears.
    
3. Click Next, click Modify, and then click Next again.
4. Type the details for the ePO server and click Next.
   
   The Database Information page appears.
   
   NOTE: The Database Server field already contains the name of the new SQL Server. If it doesn’t, correct the name.
    
5. Type the new SQL Server connection credentials.
   
   NOTE: The Database Name field already contains the correct database name. If it doesn’t, correct the database name.
    
6. Click Next, and then click Install.
   
   The Agent Handler is now reconfigured to use the new SQL Server.

The database migration is complete, and ePO now uses the new SQL Server.

You can safely delete the database copy from the old server, if:

• Your organization requires it
  Or
• You need to free up disc space on the old server

6 – Optional: Remove service dependencies:
IMPORTANT: You need to perform this step only if the ePO database was previously hosted on the ePO server itself. That is, the SQL Server was installed on the ePO server computer alongside ePO. If you moved the database from one remote SQL Server to another, you can safely ignore this step.

If the ePO database was hosted on the ePO server, ePO services have dependencies on the SQL Server services. These dependencies mean that you’re unable to stop the SQL services or uninstall SQL without affecting ePO. You must remove the dependencies from the services by editing the registry:

CAUTION: This article contains information about opening or modifying the registry.

• The following information is intended for System Administrators. Registry modifications are irreversible and could cause system failure if done incorrectly.
• Before proceeding, Technical Support strongly recommends that you back up your registry and understand the restore process. For more information, see the Microsoft Windows registry information for advanced users article.
• Do not run a REG file that is not confirmed to be a genuine registry import file.

1. Click Start, Run, type regedit, and click OK.
2. Navigate to each of the following registry keys and remove the dependencies using the following steps:
   
   HKEY_LOCAL_MACHINE\SYSTEM\Current ControlSet\Services\MCAFEEAPACHESRV
   HKEY_LOCAL_MACHINE\SYSTEM\Current ControlSet\Services\MCAFEEEVENTPARSERSRV
   HKEY_LOCAL_MACHINE\SYSTEM\Current ControlSet\Services\MCAFEETOMCATSRVXXX
   
   Where XXX is the version of ePO
    
   1. Double-click the DependOnService value.
   2. From the value data, delete the line reading MSSQLServer.
   3. Click OK.
       
3. Restart the ePO Server computer.
   
   NOTE: It isn’t mandatory to restart, but the old dependency settings remain in effect until a restart completes. If you can't restart the ePO Server computer now, plan for a restart as soon as possible.