We can add to bob944's list
What you are looking for was backed under the virtual name of a cluster
and not the physical name.
2 months ago they moved the data to a new server
So now you backup by name serverB where 3 months ago you backed it up as
serverA.
The server was not in an active policy 3 months ago. They only asked
you to started backing up 2 months ago.
As bob944 said without more detail it could be any of a hundred things.
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of bob944
Sent: Tuesday, January 27, 2009 2:37 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Backup not listed in history in BAR
> While trying to restore backup for a client I could not find
> all the backups taken (the client has a weekly backup
> schedule). There were no failures for any of the backups. But
Do you know that for a fact? How? Many operators/admins/managers
destroy information by deleting failures from at least the activity
monitor as a normal (bad) part of operations. Can you see them in the
activity monitor or bpdbjobs?
> I am unable to see all the backups for the client. For
> example, if I want to restore a backup taken three months
> back, it is not listed in the history of backups in BAR. Do I
> need to import the backup (or catalog) from the media? How do
> I know which media is having a backup of a particular date,
Since you mentioned BAR, I'd suggest the GUI: Reports | Tape Reports |
Tapes Written. That's in newer versions of NetBackup; since you didn't
provide any useful information, I won't try to guess what your customer
is running.
> and then import that backup?
RTFM and learn about importing. Surely you have someone who knows
NetBackup if you have a *customer* for whom you're providing NetBackup
support?
The backup(s) might never have run:
... NetBackup or the master was not running for some reason
... Some NetBackup bug like the daylight-savings one missed the
backup(s)
... The policy isn't set up correctly
or
... The operator disabled the policy/policies, or cleared the window, or
deleted the client, or changed the frequency, or changed the expiration
or advanced the system time, ... perhaps a dozen other human things that
could have kept a client backup from running when you think it should
have
The backup ran and somebody expired it.
The backup failed and somebody deleted the job from activity monitor or
job DB.
You have not correctly configured BAR (server client, backup type, date
range. Forget the GUI: change directory to
images/name-of-client/time-directory-of-interest and list the files for
the period you care about (use bpdbm -ctime to figure out the times or
use the timestamps on the metadata and files files).
If you have logs for the time period, you can theoretically reconstruct
the backup time in detail, from scheduling through expiration. But
that's a big "if" and a lot of work.
Bottom line: for there to be an image to restore, all these things must
be true: it must have run, it must have been successful (0 or 1), it
must not have been expired by the retention parameters or
manually/programatically, and you must be looking for it properly.
This should spawn another discussion about operations checking to see if
what was intended to run, actually did. And documentation. And logs.
And permissions. And tracking. And security. And training. And SLAs.
And quality. And responsibility. And auditing. And support. And
competence. And drive-by webbies on this mailing list. And ...
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
