No work around
needed. You basically have to wait for the one stream to finish before the
other one starts. It will eventually restore (I’ve seen it take up to 18
hours because that’s how long one stream took to restore then it started the
next stream). We’ve never really worried about it as we usually only
see when we’re doing a database refresh of one of our test/training instances
from our production instance.
I’m not sure you really
can work around any way. You’d have to try to do individual restores
for each stream (backupid) but even then you’d have to make the restores “per
tape” which might not be possible if a file spanned tapes within one of the
streams as is likely the case.
The problem with this
is you don’t “know” it’s the problem until the end of the stream that has the
tape. You can “predict” it is by verifying more than one image
(stream) uses the same tape but then you have to cross your fingers that this is
in fact the issue and not something else. I’ve seen it frequently
enough that once I’ve done the “prediction” I am willing to let it go and check
the next day for completion but then again I have that luxury owing to the
nature of the restores.
Unfortunately I’ve
never found a way to tell separate streams of the same backup to NOT use the
same tape even after asking that question here so its something I’ve learned to
live with on the occasions I’ve run into it.
From: Jackson,
Todd [mailto:c-todd.jackson AT invitrogen DOT com]
Sent: Wednesday, January 09, 2008 2:01
PM
To: Jeff Lightner;
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Restore Job
hung
I think that is exactly
the issue. What is the work around here?
To restore a wider
range of the data so stream 1 will restore?
From: Jeff
Lightner [mailto:jlightner AT water DOT com]
Sent: Wednesday, January 09, 2008 1:47
PM
To: Jackson, Todd;
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Restore Job
hung
I’ve seen this kind of
hang when the tape is:
Reserved by another job
(e.g. duplications)
Is used by more than
one stream of the original backup you are restoring. We’ve seen this where
say the 2nd stream failed and retried so ended up getting a tape on
the retry that was previously used by stream 1. In such a case the
tape is being held to complete the stream 1 restore even if it is the
3rd tape used for that stream’s backup. Stream 2 won’t
start until stream 1 restore has completed because the tape isn’t “available”
until then. You can check the images for the backup if it was
multistream and see if more than one of the images has this tape which would
tell you this is the case.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Jackson, Todd
Sent: Wednesday, January 09, 2008 1:22
PM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Restore Job
hung
There is a sister company having an
issue where they are performing a restore
from tape that was taken on Dec27th
(so not expired) and the job is just hanging.
It is stating that it is mounting
the tape and connected and then nothing.
I have created some necessary logs
to view more info but if anyone has dealt with this
before please let me know some
general things I can check.
----------------------------------
CONFIDENTIALITY
NOTICE: This e-mail may contain privileged or confidential information and is
for the sole use of the intended recipient(s). If you are not the intended
recipient, any disclosure, copying, distribution, or use of the contents of this
information is prohibited and may be unlawful. If you have received this
electronic transmission in error, please reply immediately to the sender that
you have received the message in error, and delete it. Thank
you.
----------------------------------