How can I
copy a OnePoint database to a test environment? One of our customers has an
AKM import problem. I got a backup of the db and reinstalled it on our MOM
test environment but when I open the MOM MMC I can only see the root but no
other folders or views?
I’ve tried the information in Microsoft Knowledge Base Article
297771 'How to Move a OnePoint Database to a New Location' but
they didn't help.
The problem is, that I'm installing the OnePoint db on a 'foreign' MOM
installation. In this MOM test environment I just replaced the original
OnePoint DB with the DB from our customer. In this case the SQL server
remains the same.
Is this possible at all what I am trying to do?
Contributed
By: Travis Wright [MSFT]
What you are trying to do isn't officially supported beyond what is
described in the Knowledge Base Article.
The problem arises probably around the configuration group name. The
configuration group name is used in the registry on the DB, DCAMs, and agents
servers. It is also stored in the configuration table in the OnePoint database.
In order to move a database from one configuration group to another you would
have to at least update the configuration group name in the configuration table
to be the new configuration group name before restoring the database in the new
configuration group. There may be other issues though.
Can you setup a NEW MOM installation with the same configuration group name as
the production environment? If so - that would probably be the easiest way if
you just need to troubleshoot a .akm import error. Set it up as a
all-on-one-computer setup so that the DB and DCAM and UI are all on the same
computer.
Be sure to either have a separate network from your production environment or
delete all the computer and computerresponsibility table records before
restoring the DB in the new MOM configuration group. Otherwise, you will end up
with two configuration groups trying to monitor the same computers.
Add the DB/DCAM/UI computer of the new test configuration group to the computer
table and the computerresponsibility table before you restore the DB from the
production configuration group. You could just update the Computer.Domain and
Computer.Name fields of an existing DCAM computer record
in your production configuration group.
|
