How to Move the OperationsManagerAC Database in Operations Manager 2007
Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1
For various reasons, it might be necessary to move the Audit Collection (OperationsManagerAC) database from its original server to another server.
This procedure can result in data loss if it is not performed correctly and within a reasonable length of time. Ensure that you follow all steps precisely, and without unnecessary delays between steps.
The high-level steps for moving the OperationsManagerAC database are as follows:
Stop Operations Manager Audit Collection Service (ACS) to prevent updates to the OperationsManagerAC database during the move.
Back up the OperationsManagerAC database.
Delete the OperationsManagerAC database on the original Audit Collection database server.
Restore the OperationsManagerAC database to the new Audit Collection database server.
Configure SQL Server permissions on the new Audit Collection database server.
Configure the Audit Collection Server to point to the new Audit Collection database server.
Restart Operations Manager Audit Collection Service.
OperationsManagerAC Database Relocation Procedure
Use the following procedure to move the OperationsManagerAC database to a new Audit Collection database server.
To move the OperationsManagerAC database
On the original Audit Collection database server, stop Operations Manager Audit Collection Service.
On the original Audit Collection database server, use Microsoft SQL Server Management Studio to back up the OperationsManagerAC database (default name) to a shared folder on the server. It is recommended that you also back up the associated master database.
On the original Audit Collection database server, delete the OperationsManagerAC database as follows:
In SQL Server Management Studio, navigate to Databases.
Right-click OperationsManagerAC, and then select Delete.
In the Delete Object dialog box, ensure that the Delete backup and restore history information for databases and the Close existing connections options are both selected.
On the new Audit Collection database server, use SQL Management Studio to restore the OperationsManagerAC database backup. Access the database backup by copying the backup file to a local drive or by mapping a local drive to the folder that contains the backup.
On the new Audit Collection database server, use SQL Management Studio to create a login for the Audit Collection Service server. Use the format <domain\computername$> in SQL Logins (where computername is the name of the Audit Collection Service server).
On the new Audit Collection database server, add the correct permission for the login of the computer on which the ACS Service is running, as follows:
In SQL Server Management Studio, navigate to Security and then to Logins.
Right-click the account that corresponds to the computer on which the ACS service is running (use the <domain\computername$> format). Select Properties, and then select User Mapping.
Select the box in the Map column that corresponds to the OperationsManagerAC database, and then select db_owner in the Database role membership for: OperationsManagerAC list.
On the computer hosting Audit Collection Service, locate the registry key HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI\OpsMgrAC. Double-click the value Server, and set it to the name of the new Audit Collection Service database server.
On the server on which the ACS service is running, start Audit Collection Service.
Verify that the database move was successful by checking the OperationsManagerAC database for entries in the most recent dtEvent_<GUID> table that have a date/time stamp that is more recent than when the service was restarted in the previous step.