Error 191:
>bperror -S 191 -r
no images were successfully processed
A verify, duplicate, or import was attempted and failed for all selected
images.
Try the following:
* Check the NetBackup Problems report for the cause of the error. To obtain
detailed troubleshooting information, create an admin debug log directory
and retry the operation. Check the resulting debug log.
* If the error was encountered during duplication of backups, check the
duplication progress log to help determine the root cause of the problem.
* If the error was encountered by a Vault job which is doing duplication,
check the duplicate.log files in your sidxxx directories to help determine
the root cause of the problem:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Dean
Sent: Wednesday, November 30, 2005 1:58 AM
To: WEAVER, Simon
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Netbackup Broke - Possible Way Out and Require
Opinions
I can't recall what 191 means right now.
But, one thing I discovered recently - I was trying to import an old DLT
tape and it kept failing due to a media error somewhere on the tape. I only
needed to recover a single file so there was a good chance that bit of the
tape was still OK.
I had a standby master with the old catalog on it. This server didn't even
have any tape drives - it was purely hosting the NBU catalog. In the event
someone needed to restore data from this "legacy" catalog, bpimagelist was
run on the standby server so that the required tapes could be identified,
and then imported into the "real" master.
Obviously I couldn't get the import to work on this dodgey tape, so I
located the appropriate catalog files for the backupid I needed (from
netbackup/db/images/ on the standby master), and copied those files over to
the active Master Server. I was then able to restore the file I needed.
So obviously I like the idea of keeping a standby master server in these
situations - even if it is just to host the catalog :) And if you don't need
tape drives, technology like VMware can make it a very simple and
cost-effective option! I guess it depends how often you are expecting to
need to restore from this old catalog.
Cheers,
Dean
On 11/30/05, WEAVER, Simon <simon.weaver AT astrium.eads DOT net> wrote:
Dean
They are failing due to (what veritas say) is bad media
NBU Activity Monitor shows status 191 !
Simon Weaver
Technical Support
Windows Domain Administrator
EADS Astrium
Tel: 02392-708598
Email: Simon.Weaver AT Astrium.eads DOT net
-----Original Message-----
From: Dean [mailto:dean.deano AT gmail DOT com]
Sent: 30 November 2005 08:21
To: WEAVER, Simon
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Netbackup Broke - Possible Way Out and Require
Opinions
I would not mess with the production "working" master server. Wiping out
your active catalog on purpose and relying on bprecover to get it back
sounds ... risky. Not that I've ever seen bprecover fail, but I believe in
NOT tempting fate.
Is it possible to have a 'spare' server sitting around, with the same OS and
hostname as the production master, but not registered in your DNS, or not
normally connected to the LAN at all? bprecover your pre-problems catalog to
it and just let it sit there until it's needed. It wouldn't need to be too
powerful. Then if a restore is required, update /etc/hosts on the client (or
the Windows equivelant) to point to your "standby" master server, do the
restore, then undo the /etc/hosts change. I've seen this done with an old
Ultra 5, and even on a VMware guest machine.
Of course, you'd also need a tape drive connected to this "standby" master
if/when you need it for a restore.
But apart from that, why are the imports failing? Bad tapes? If that's the
case, having a good catalog is not necesarily going to help.
Remember, with import you have to complete phase 1 import of all tapes in a
connected set before beginning pase 2.
Good luck,
Dean
On 11/30/05, WEAVER, Simon <simon.weaver AT astrium.eads DOT net> wrote:
Hi everyone
A week and a bit, I mentioned that all my tapes had expired through no fault
of my own.
Veritas has not been able to re-produce this and under their guidance,
carried on running as I am, but having to import tapes BACK into Netbackup!
This is not going well! The majority of imports are failing, and I am
becoming increasingly concerned about the entire system, and much more
importantly, the previous backups!
So, thinking about the situation, I wanted to know if this theory is
possible.
I still have a Catalogue Backup on a tape going back to 16th November 2005 -
prior to the problems.
Rather than importing the tapes like I am doing, if I need to do a restore
from a Tape say that was run in September 05, could I revert the system BACK
to how it was prior to the problems I experienced. This Catalogue tape is
currently suspended, and I have told NBU not to use this tape as a Catalogue
Backup (presently using 1 tape and 1 drive).
Once the restore is done, I could use BPRECOVER to revert the system BACK to
how it is now (ie: todays date).
I am sure there is going to be a con here (for example, recovering back to
the 16th will mean the Netbackup Database will now wonder why there are new
tapes in the Robot and probably send them to scratch!!
I really am looking for some alternatives options here and open to some real
help! Veritas have told me its the media thats the problem!
This is not looking good :(
Simon Weaver
Technical Support
Windows Domain Administrator
EADS Astrium
Tel: 02392-708598
Email: Simon.Weaver AT Astrium.eads DOT net
This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate
or otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS
Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or
obligation.
EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS,
England
This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate
or otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS
Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or
obligation.
EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS,
England
|
