Congratulations on your upgrade!
I do the housekeeping manually, yes, but then I am only there for a
week or so and the database is actively changing while I am messing
with it. In real life people automate this. I would save the output,
though,
and review it later just in case. You would be looking for things like
'Please
delete..', which usually go away by themselves when the map is reopened
but occasionally need help. You are also looking for the unexpected. That
takes a person. But automating it is better than forgetting to do it.
You might need to use the Turbo form if you have devices with lots of
interfaces. Those are not discovered properly until you do. You might
also convert if it is running slowly. I think people usually convert after
they call Support for some wierd problem and are advised to convert.
I seem to be using it everywhere these days, though. Big switches!
And Kevin makes a good point about backing up other things with the
database. In particular, there are certain files that need to match the
database, like location.conf, seedfile, oid_to_type and oid_to_sym.
Once those are stabilized, you might count on your full-system backup
to cover them along with the rest of /usr/OV/conf. But while things are
still evolving, you might want to collect those as well.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
Dean Sullinger <DSullinger@dot.state.az.us>@tkg.com on 05/30/2001 05:35:09
PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "'IBM NetView Discussion'" <nv-l@tkg.com>
cc:
Subject: RE: [NV-L] Netview Maint. Issues and Problems
WOW! What a wealth of information.
1. We did re-install and re-discovered the network. We went with Solaris
8,
Tivoli 3.6.3 and Netview 6.0.2. It's up and running right now and doing
pretty good. We still have a few problems that we are working out with
Paul
Stroud in support.
2. Paul recommended the weekly maintenance, but thank you for the
additional
two bottom lines, I wouldn't have thought of that. I will add it to the
script. I noticed you said to "watch" for messages... do you run this
manually? I was planning a at command once a week to take care of it.
3. We have been backing up our database since we installed the servers,
but
only in a 30 day rotation. After this ordeal, I will start also running a
once a month on the database so we will also have a 12 months a year on
tape.
4. We experienced a strange problem yesterday that lasted all day yesterday
and half of today. Whenever we pinged something, it was taking far to much
time to resolve the name. We shut down Netview to make sure it wasn't
involved, then we thought it might be DNS, but the Netview machine is the
only UNIX box effected. Were still not real sure what happened, but we
will
have to take a look at it again if it ever shows back up.
5. We are not currently using the Turbo database... should we and why?
Thanks for the help.
-----Original Message-----
From: Kevin Smith [mailto:c-kevin.smith1@wcom.com]
Sent: Wednesday, May 30, 2001 10:32 AM
To: 'IBM NetView Discussion'
Subject: RE: [NV-L] Netview Maint. Issues and Problems
You wouldnt want to backup the conf with the backup and restore procedure?
Sincerely,
Kevin Smith
|