printer friendly

Moving the NSM 2.5.x for Active Directory Engine to another server


Last modified: 2010-Jun-21

Q: How do I move my NSM 2.5.x for Active Directory Engine server from one server to another?

A: If you need to move your NSM Engine to another server, follow the steps below:

Do not use this process to upgrade!!! Move first, then upgrade for best results.


Step 1

  1. Use NSMAdmin to document which servers are running the Event Monitor and Agent services as this information will be needed later when re-configuring these services to talk to the Engine in the new location.
  2. Using NSMAdmin de-register all Event Monitor and Agent services. These services will have to be updated via the nsmevent-config, and nsmagent-config utilities on their specific servers to point to the new location of the engine. If there are any event or agent servers you will not be using with the new engine installation, remove them at this time.
    * * * Warning * * *
    Please ask your administrators to hold off on object creates, moves, deletes, and renames, on managed objects, since all of the Event Monitors have been removed or deregistered.

    Note: Management Actions will have to be performed to get NSM to manage objects that changed while the Event Monitors are down.


Step 2

  1. Verify that there are no pending Eligible Events. (Best Practice, if possible)
  2. Stop the Engine service on the current server, along with any other local NSM components if still running.
  3. Uninstall the engine from the current server.

Step 3

  1. Run the NSM Install program for the currently installed version of NSM on the new server.
  2. Use the same proxy accounts that were used during the previous Engine installation. The installer will reset the passwords. Use the LICENSE.DAT file from the C:\Novell\Storage Manager\Engine folder on the old server.
  3. Stop the engine service.

Step 4

  1. Copy the following folders from the old server's installation directory (C:\Novell\Storage Manager\Engine) to the new server's installation directory (Overwrite ALL existing files):

    1. DBASE
    2. POLICY
    3. LOGS
    4. REPORTS (Optional)
    5. PROXYHOM (Optional) Only if its contents have been modified from the original.
    6. AUDITLOG (Optional)

  2. Check www.storagemgr.com for any updates to NSM components in the same version family.
  3. Start the Engine service on the new server

Step 5

  1. Use the nsmevent-config and nsmagent-config utilities to update the Event and Agent configurations to point to the newly installed Engine address.
  2. Use NSMAdmin to re-authorize NSM components on other servers.

Step 6

    Rename the old server's installation directory so that the old Engine cannot be accidently restarted on the old server without seeing that the directory has been renamed. We want it to be obvious that this directory is no longer in use. We recommend saving this directory for a day or two as a precaution. If everything runs correctly delete this old directory, and uninstall the Engine to remove the services properly.