JAMES SHANKS wrote:
Ken -
I don't know what may fail, but your procedure assumes that nothing new was
added and that nothing old was changed when we went from NetView V4 to NetView
V5. That's not an assumption I would like to have to live with. Much is the
same, that is true, but the reason there is a migration procedure rather than a
simple note specifying your method is for precisely those two cases.
But I am not expert enough to assess the risk. I just worry about all the
changes being lost ...
What exactly did you tar/untar? All of /usr/OV ? Not only would you lose the
default files in /usr/OV/conf for example, but you would also lose the samples
of the new stuff in /usr/OV/newconfig, so you couldn't even check there to see
if anything was missing or copy in a new copy if something had changed. And
what about binaries and scripts? Or was /usr/OV/bin excluded? When you do
"xnmtrap" can you still add / alter TEC/classes and slot map values?
I'm glad it seems to have worked for you, but I don't see how I could recommend
it.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Of course, James is always CORRECT. The proper way to do things is to
"migrate". However, sometimes you just get tired of dealing with glitches, bugs
and whatnots and try something on your own.
In my case I wanted to save two things, all customizations in trapd.conf and the
current databases and maps. I did not touch anything in /usr/OV/bin. I tarred
everything in /usr/OV/databases from NetView 4.1 and untarred them in the
NetView 5.1.1 host. In fact I have done this several times and it works
perfectly each time. Keep in mind that this is a very restricted but
nevertheless important "fast migration".
Regards,
ken
kgarst@giantofmaryland.com
|