This is the quickest way, but not the safest
way.
I don't mean to split hairs, but this has bit me in the
butt before.
In 4.5, a client did not always create a STREAMS file if
the policy was not marked to Allow multiple data streams. That was the
original reason for the STREAMS file.
Even in 5.1, you can see some that don't create the STREAMS
file. Also, Agent backups (i.e. Oracle and SQL) don't create / update the
STREAMS file.
Don't delete the policies, move them.
I would suggest this policy for everyone. It doesn't
cost you anything and can keep you from going to jail if you have to answer
audit questions. (Being someone's "girlfriend" in the big house is not
something I want to do). Also, how many times have you ever been asked
"remember 3 years ago when we backed up "insert name here"? What was the
frequency and retention?"
Create
a directory named /usr/openv/netbackup/db/Inactive_policies. It will be at
the same level as "class".
Deactivate a policy when it is no longer necessary (and it will also
reduce your load on the scheduler since deactivated policies are not
"computed"). Let it sit for a couple of weeks to ensure that no one needs
"another" final backup to be retained for Infinity + 100
years.
Go
into the command line and move the directory for the policy (directory name =
policy name) from /usr/openv/netbackup/db/class/SOME_POLICY
/usr/openv/netbackup/db/Inactive_policies/SOME_POLICY.
If
anyone ever asks questions about it, you can move it back, refresh your GUI
(very important), and answer any questions.
Bobby Williams
2205 Peterson
Drive Chattanooga, Tennessee 37421 423-296-8200
The totally unsupported method is to look
/usr/openv/netbackup/db/images/<clientname>/STREAMS. You'll see
entries in here with the policy name and path and a time that you'll need to
translate into human-readable method (there are ton of ways of translating this
time).
.../Ed
On Jan 24, 2008 10:21 AM, Shyam Hazari < shazari AT gmail DOT com> wrote:
I
inherited a messy netbackup environment(5.1 MP5). There is a tonne of inactive
policies(more than hundred). Before I nuke them I would like to find out when
was the last time it was executed. Any easy way to find this ? I can look at
the catalog one by one, but it will take forever.
-- Ed Wilts, Mounds View, MN, USA mailto:ewilts AT ewilts DOT org
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|