KB00010: Moving MessageMaster from one server to
another
Description
You've been running MessageMaster server on MMServerOld for a while now. However,
your message volume has now outgrown the capacity of this machine, and you
would like to move it to a faster machine - MMServerNew. Or you're reorganizing your
infrastructure, and would like to move some applications to different machines
to better distribute the processing load in your environment.
Resolution
These are the steps you will need to take to move MessageMaster from MMServerOld
to MMServerNew. This procedure will preserve your
message history, and no messages will be lost during the migration.
Furthermore, you do not have to perform this procedure off hours. And, there is
no down-time for the client machines; all messages generated during the
migration will be captured by the time you are done.
-
On MMServerOld, stop the MessageMaster Router and MessageMaster Delivery
services and disable them. From this point on, the clients will continue
sending messages to MMServerOld, but the messages will no longer be entering
the database on MMServerOld. They will be accumulating in the IncomingMessages
queue.
-
On MMServerOld, go to Scheduled Tasks, and disable the two ObjSoft tasks:
'ObjSoft Daily Tasks' and 'ObjSoft Retry Delivery' so they don't run on both
servers.
-
On MMServerOld, in SQL Enterprise Manager, right-click on the ObjectiveSoftware
database, and make a back up.
-
On MMServerNew, in SQL Enterprise Manager, restore from your backup to create the
ObjectiveSoftware database. You may need to adjust the location of the log and
full-text catalog if you have different drive letters on the new server.
Be sure to read the "What is the recommended hardware for MessageMaster server?"
article, referenced below, for important recommendations on SQL database and
log placement.
-
From SQL Enterprise Manager, go into Users under the ObjectiveSoftware database,
and remove the
ObjectiveSoftware user (its numeric ID from the old SQL Server will likely not
match the ID on the new server). Then go into Logins under Security, and add
back the user and assign it dbo rights to the ObjectiveSoftware database.
-
On MMServerNew, run MessageMaster Server setup. The database will be left
intact during the installation, preserving your message history.
-
On MMServerNew, run EventMaster Server setup and MessageMaster Client
setup Then run EventMaster Client setup if you intend to monitor the event
logs of MMServerNew.
-
Move the accumulated files in the IncomingMessages queue on MMServerOld
to the IncomingMessages queue on MMServerNew. Use the console's Monitor
page to ensure that the backlog is being processed efficiently.
-
Re-point your clients so that they start sending their messages to
MMServerNew. There is a registry entry under [HKEY_LOCAL_MACHINE\SOFTWARE\Objective Software\MessageMaster]
called "MessageMasterQueueShare". It needs to be set to \\MMServerNew\MessageMasterQueue$.
Currently, you'll need to find your own way to do this, but we have a planned enhancement
to provide a GPO Administrative Template that will allow you to set this entry using
your Active Directory.
-
Once everything is flowing smoothly on MMServerNew and all queued messages
have been moved over, you can stop sharing
MessageMasterQueue$ (the IncomingMessages queue) on MMServerOld.
Any straggling clients that have not been re-pointed to MMServerNew
will now cache their messages on their own hard drive until they are
re-pointed to MMServerNew;
again, no messages will be lost. Alternatively, you can keep the old
share, and examine the files that are still being sent there, in order
to identify which clients have not yet been re-pointed to the new server.
See Also
Applies To
