|
Yes,
that's exactly what I'm getting. We're actually just on 6.5, not even
6.5.1, and we've been wanting to move up to 6.5.2A anyway.
I've
got a ticket in with Symantec about it now, and the tech did mention he thought
this was a known problem. He's trying to see if it was fixed in a
later release, so hopefully I'll have it fixed soon enough.
P.S -
I just found this in the 6.5.2A release notes, which seems to confirm that it is
a known bug and is fixed in the latest release:
--------------------------------------------------------------------------------
Etrack
Incident = ET1255224
Associated Primary Etrack = ET1167945
Titan cases:
220-204-657 230-518-698 240-719-166 240-766-752 281-242-138
290-916-950
290-935-090 290-943-738 290-985-114 290-986-582 290-994-641
311-821-582
320-105-655
Description:
DSSU duplication jobs would fail with a
status 50 that appeared in the
Activity Monitor if more than one copy was
made concurrently.
For Duplications with two copies being created
at the same time, BPJOBD
appeared to cancel the duplication after 20
minutes
The problem would occur if duplicating more than one
copy concurrently.
If you're getting
return codes 82 or 50, this is a known error and requires an engineering
binary (bpduplicate replacement). We had the same problem when we
upgraded to 6.5.1.
Ken
Zufall
Technical Analyst
D660C
The Goodyear Tire & Rubber
Company
GTN 446.0592 or 330.796.0592
<Brian.Beaird AT cat DOT com>
Sent by:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
10/20/2008 02:52 PM
|
|
To
| <veritas-bu AT mailman.eng.auburn DOT edu>
|
|
cc
|
|
|
Subject
| [Veritas-bu] Duplicating Large
Images to Multiple Copies Fails After
20 Minutes |
|
This one has me stuck. We recently upgraded to NBU 6.5 and did
not experience this problem with 5.1. I have several images on tape I
need to duplicate to two copies on other tapes so that I can send them
off-site. However, whenever I try to run the duplication job (just
manually kicked off), it fails after 20 minutes every time (almost to the
second). These images are fairly large (about 100GB). Here is what
I've figured out so far:
-Running the duplication job with any smaller image
that takes less than 20 minutes succeeds just fine
-Running the large duplication job with
just a single copy works fine.
-Running the large duplication job with any combination of storage
units or tape drives makes no difference.
Looking at the logs while this happens, I noticed
that right as the job begins to fail, I get a lot of lines like
this:
13:41:25.826 [9151] <2> drivename_open:
Called with Create 1, file PP-L700-SDLT01
13:41:25.826 [9151] <2> drivename_lock: lock
failed
13:41:25.826
[9151] <2> drivename_close: Called for file PP-L700-SDLT01
13:41:25.878 [9152] <2>
drivename_open: Called with Create 1, file PP-L700-SDLT08
13:41:25.878 [9152] <2>
drivename_lock: lock failed
13:41:25.878 [9152] <2> drivename_close: Called for file
PP-L700-SDLT08
13:41:30.827 [9151] <2> drivename_open: Called with Create 1,
file PP-L700-SDLT01
13:41:30.827 [9151] <2> drivename_lock: lock
failed
It's always at that mysterious 20 minute mark and
if I'm trying to make more than 1 copy. It's like there's some limit
somewhere that was implemented on 6.5. Has anyone else experienced
this?
Thanks,
Brian Beaird _______________________________________________
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
| 