|
All
>>>>You
will have to perform some form of installation/migration on the new box. I doubt
you can simply copy the /usr/OV directory and restore that on a different box
which has never had a formal installation >>>>performed (and expect
it all to work) as there are files placed elsewhere (/etc, /var ??) and other
system files updated, like /etc/services. There are probably other gotchas that
I haven't mentioned
Of course....there
are RC scripts in etc/init.d ...rc3.d ...and more.
>>>>Stephen probably has the best approach
for moving NetView to a new box. Just remember that NetView migration does not
necessarily include user directories and files. It does not simply copy the
>>>>entire /usr/OV directory structure and restore it. For example,
the migration does not need to copy the contents of the /usr/OV/bin directory as
new binaries are being layed down (hence an upgrade), so you
>>>>might find that either your "OV.back..." directory doesn't
contain the scripts you say you stored in /usr/OV/bin, or if they were included
then they will be ignored during a migration - you would have to copy them
>>>>manually.
Actually, it does. One of the things that nvp.v7r1
does is this: GREPs original /usr/OV/bin/"program" from
/usr/OV/install/filesets compares them with current
/usr/OV/bin/"programs" and moves the difference to /usr/OV.back.v7r1/bin, and
you get your exec files in you backup/bin directory.
Based on Stephens suggestion, I should put
OV.back.xxxx to /usr/ and then install NV " ./nvinstall -K server ..... Will the
install process automatically figure out the OV.back.xxxx , install
NV and restore OV.back.xxxx to the new /usr/OV? If this is true, then yes,
that would be fine and the best solution.
Thanks
Dejan Mijailovic
You should
check the contents of the "OV.back...." directory to see if all of your
customizations were saved as not all of the directories within /usr/OV are
included in a "OV.back...." style backup.
Stephen probably has the best approach for moving NetView to a new box.
Just remember that NetView migration does not necessarily include user
directories and files. It does not simply copy the entire /usr/OV directory
structure and restore it. For example, the migration does not need to copy the
contents of the /usr/OV/bin directory as new binaries are being layed down
(hence an upgrade), so you might find that either your "OV.back..." directory
doesn't contain the scripts you say you stored in /usr/OV/bin, or if they were
included then they will be ignored during a migration - you would have to copy
them manually.
You will have to
perform some form of installation/migration on the new box. I doubt you can
simply copy the /usr/OV directory and restore that on a different box which
has never had a formal installation performed (and expect it all to work) as
there are files placed elsewhere (/etc, /var ??) and other system files
updated, like /etc/services. There are probably other gotchas that I haven't
mentioned
I don't know what would
be considered best practise - hopefully somebody else can share their
experiences.
Gareth
Holl
Staff Software Engineer
gholl@us.ibm.com
IBM Software Group
- Tivoli Brand
Research Triangle Park, North Carolina.
|
| "Dejan Mijailovic"
<dejan.mijailovic@inquent.com>
09/27/2002 09:40 AM
|
To:
Gareth Holl/Raleigh/IBM@IBMUS
cc:
<nv-l@lists.tivoli.com>
Subject:
RE: [nv-l] a question about backup
|
Hi Gareth.
What I need is to replace my Sun
server. And I have a lot's of custom config stuff, custom scripts in
/usr/OV/bin, oid_to_whatever,..a lot's of ARF add-ons. LRFs
mibExpr.conf....and a lot more.
I think if I make OV.back.v7r1 and then use cp -r, that will do it. Is
this what NetView does during migration, or something else?
Also, I was thinking to TAR C the whole thing and
making up one big OV.tar.
Basically what I need is the best way of backing up the whole Netview
and restoring it on different box. of course with the same IP, SNMP
Community...
What is the best
way to do this, and what are the best practices?
Regards
Dejan Mijailovic
-----Original Message-----
From: Gareth Holl
[mailto:gholl@us.ibm.com]
Sent: Thursday, September 26, 2002 7:52
PM
To: Dejan Mijailovic
Cc:
nv-l@lists.tivoli.com
Subject: Re: [nv-l] a question about
backup
This kind of backup is
mainly used when performing a migration. The update/migration process looks
for the existance of this directory and migrated the databases and conf files
and other contents. You could manually go through it and copy parts back in
but this would probably be tedious and potentially lead to
mistakes.
If your goal was to backup the NetView databases,
simply tar up the /usr/OV/databases/openview directory and restore using pax
(don't restore using tar). Or use the "Hot Backup" feature introduced into
v7.1 - refer to the 7.1 Release Notes for description and steps to
restore.
Gareth Holl
Staff Software
Engineer
gholl@us.ibm.com
IBM Software Group - Tivoli
Brand
Research Triangle Park, North Carolina.
|
| "Dejan Mijailovic"
<dejan.mijailovic@inquent.com>
09/26/2002 04:07 PM
|
To:
<nv-l@lists.tivoli.com>
cc:
Subject:
[nv-l] a question about backup
|
re: Tivoli Neview 7.1, Solaris 7
Does someone know, after
generating backup files/directories "OV.back.v7r1",
how to restore the
files back to /usr/OV?
Do I just use "cp -r" after stopping the NetNiew
programs or there is a
Netview script to do it?
Thanks
Dejan
Mijailovic
Inquent
Technologies.
---------------------------------------------------------------------
To
unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional
commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an
Offical Tivoli Support forum. If you need immediate
assistance from Tivoli
please call the IBM Tivoli Software Group
help line at
1-800-TIVOLI8(848-6548)
|