Microsoft KB Archive/297771

= How to move a MOM 2000 OnePoint database to a new location =

Article ID: 297771

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Operations Manager 2000 Service Pack 1

-



This article was previously published under Q297771



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SUMMARY
This article explains how to move a Microsoft Operations Manager (MOM) OnePoint database to a new location if such a move becomes necessary.



Move involving only the OnePoint database from one SQL server to another
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

We do not recommend that you move the Microsoft Operations Manager OnePoint database.

Moving the MOM OnePoint database is not a standard maintenance procedure. However, you may need to move the OnePoint database for various reasons, including but not limited to:
 * Volume size restrictions.
 * Performance improvements, for example separating the database from the logs.
 * Relocation of the database to a fault-tolerant volume.

We recommend that you move the OnePoint database only if you must move it for one of these reasons. Moving the OnePoint database can cause serious problems that may necessitate a reinstallation of the server. Microsoft Product Support cannot guarantee that any resulting problems can be solved.

Note The following steps are for moving the MOM database from one SQL server to another. If your SQL server is also the MOM server (DCAM - Database Access Server, Consolidator and Agent Manager) then there may be a need to make additional modifications to the MOM server registry keys and/or database table modifications, which are discussed in the second section below - Move that involves also the DCAM server.  Install SQL server on new destination computer. Install MOM Database component by running MOM setup. Quit OnePoint service on the current database computer and stop the OnePoint service on all DCAMs. Backup the current OnePoint database to a file. On the new SQL server (installed in step 1 above), in SQL Enterprise Manager, under the Restore menu, use the From Device option to restore the OnePoint database, and then select the backup file created in step 4. On the DCAM server, start Regedt32 and change the following registry values from the current SQL server name to new SQL server name: <ul>  </li>  </li>  </li></ul>

For each of these keys, delete the current SQL Server value, and then create a new SQL Server name value. MOM will recreate DCAM Key(s) as needed under this new key once it restarts.</li> Navigate to the following registry key:

Change it from old SQL server name to new SQL server name.</li> On your Web Console computer, locate the Instal.stm file under the WebConsole folder wherever it is installed. (The default location is <%SystemDrive%>\Inetpub\Wwwroot\WebConsole. Change the old database server name in this file to the new database server name.</li> Restart OnePoint service on the DCAM server(s).</li> Make the same registry changes as above on each DCAM in this configuration group (except for the very last one preceding which you would make on all MOM admin console machines).</li></ol>

Note For information in the MOM 2005 Operations Guide about how to move the Microsoft Operations Manager 2005 database, visit the following Microsoft Web site:

http://www.microsoft.com/technet/prodtechnol/mom/mom2005/Library/faf19f47-facd-4467-9510-e7c84c671572.mspx?mfr=true

Move involving the SQL server that is also a DCAM server and/or MOM Web Console server
In addition to the changes discussed above on the SQL side, if the server you are moving also hosts either the MOM DCAM role or Web Console role, then there are additional changes to be made especially to the Configuration table in the OnePoint database. Also note that moving the DCAM server to a machine with a different name may have an effect on the managed nodes (servers running MOM agent) if this is the only DCAM in the configuration group. Please consult Microsoft Product Support Services first if that is the case.

If you are moving all the components of the Microsoft Operations Manager 2000 (MOM) server to a new hardware platform, you need to install the MOM server on the new platform. To do this:
 * 1) Perform a custom installation of MOM on the new computer.
 * 2) Type the Configuration Group name precisely as it appears on the existing MOM installation.
 * 3) Once MOM install is completed, start SQL Enterprise Manager.
 * 4) Right-click the Configuration table in the OnePoint database, click Open Table, and then click Return all Rows.
 * 5) Change all entries where DataCategory = URL to read DataCategory = , where   is the name of the new database computer.

Note The URL entries need to remain as they are with the exception of using the name of the SQL Server computer that you moved the database to. For example, if an existing entry in the table looks like this

http://MOMServer_OLD/OnePointOperations

or this

&quot;PropertySheet.asp?database=MOMServer_OLD&target=%1&t=alert&quot;

the corrected entry looks like this

http://MOMServer_NEW/OnePointOperations

or this

&quot;PropertySheet.asp?database=MOMServer_NEW&target=%1&t=alert&quot;

For more information about this topic, click the following article number to view the article in the Microsoft Knowledge Base:

917894 How to move the MOM 2005 OnePoint database to a new location

Keywords: kbinfo KB297771

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.