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 KB87976 for details of the Disaster Recovery Snapshot process, and KB66616 for details of the manual backup procedure.
NOTE: 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 for details.
Overview
To move the ePO database, follow the steps below in the order that they are listed:
- Stop ePO services.
- Move the database.
- Configure ePO and verify connectivity.
- Start the ePO services.
- Extra steps for extra Agent Handlers.
- Optional: Remove service dependencies.
Stop ePO services
Before you make any changes, you must stop ePO services to prevent anything from accessing the database:
- Click Start, Run, type services.msc, and click OK.
- Right-click the following services and select Stop:
On the ePO server:
McAfee ePolicy Orchestrator Application Server
McAfee ePolicy Orchestrator Event Parser
McAfee ePolicy Orchestrator Server
If you have any additional Agent Handlers, stop the following services on all Agent Handlers:
McAfee ePolicy Orchestrator Event Parser
McAfee ePolicy Orchestrator Server
Move the database
NOTE: Make sure that the new database instance has the
same collation as the old one. See
KB73717 for details
- On the current SQL Server, take a full backup of the ePO database using SQL Management Studio. If you are unfamiliar with this process, see KB52126.
When complete, you have a backup (.BAK) file.
- Copy the (.BAK) file to the new SQL Server.
- Restore the backup file to the new server using SQL Management Studio. See KB52126 for this process, if needed.
After the restore completes, the ePO database is visible in Management Studio on the new SQL Server.
Configure ePO and verify connectivity
- On the ePO server only, start the McAfee ePolicy Orchestrator Application Server service.
- 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.
- When the logon prompt is shown, log on using an ePO Global Administrator account.
The 'Configure Database Settings' page appears.
- Type the details for the new SQL Server.
- Click Test Connection.
"The database connection was tested successfully" message appears.
If any errors are appear, verify and correct the new SQL Server details until the connection test succeeds.
- When the connection test is successful, click Apply.
A prompt to restart the server displays.
- Restart the McAfee ePolicy Orchestrator Application Server service.
Start ePO services
- Click Start, Run, type services.msc, and click OK.
- Right-click the following services and click Start:
McAfee ePolicy Orchestrator Event Parser
McAfee ePolicy Orchestrator Server
Extra steps for extra Agent Handlers
If you have more Agent Handlers, each one must be provided with the new SQL Server details by rerunning the initial setup wizard. Perform the following steps on each Agent Handler:
- Open the folder where you extracted the contents of the ePolicy Orchestrator software installation package.
- Copy the Agent Handler folder to the Agent Handler server system and double-click Setup.exe.
The McAfee Agent Handler InstallShield wizard appears.
- Click Next, click Modify, and then click Next again.
- 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 does not, correct the name.
- Type the new SQL Server connection credentials.
NOTE: The Database Name field already contains the correct database name. If it does not, correct the database name.
- Click Next, 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
Optional: Remove service dependencies
IMPORTANT: You need to perform this step
only if the ePO database was previously hosted on the ePO server itself. Meaning 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 are 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: http://support.microsoft.com/kb/256986.
- Do not run a REG file that is not confirmed to be a genuine registry import file.
- Click Start, Run, type regedit, and click OK.
- 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
- Double-click the DependOnService value.
- From the value data, delete the line reading MSSQLServer.
- Click OK.
- Restart the ePO Server computer.
NOTE: It is not 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.
