[Veritas-bu] Disk Storage Unit, migration to tape using multiple bpduplicates each with own bidfile
2005-03-21 23:35:19
Subject: |
[Veritas-bu] Disk Storage Unit, migration to tape using multiple bpduplicates each with own bidfile |
From: |
rob AT worman DOT org (Rob Worman (home)) |
Date: |
Mon, 21 Mar 2005 22:35:19 -0600 |
Doug-
I would claim the opposite. i.e.
NetBackup duplication has historically ignored the media_unmount_delay
parameter, until very recently. Looking at the docs, I see that this
change was introduced in 4.5 MP8 (and FP7, and 5.1 GA and 5.0 MP1)
e.g., look for _DELAY in the MP8 readme:
http://seer.support.veritas.com/docs/271500.htm
HTH
rob
On Mar 21, 2005, at 8:55 PM, Douglas Ritschel wrote:
> Has anyone seen the following problem with NB 4.5,
> Disk Storage Unit, migration to tape using multiple
> bpduplicates each with own bidfile.
>
> The problem is, if I have 4 bpduplicates running, each
> with it's own bidfile (each bidfile containing unique
> image ids to migrate from disk to tape). Instead of a
> bpduplicate keeping a tape mounted, the entire time it
> processes the bid file, it releases the tape, and
> another bpduplicate grabs the tape, and starts using
> it.
>
> I've heard that this use to work, but was broken in
> MP6. That bpdupliate is ignoring the UNMOUNT_TIMEOUT
> option in bp.conf. And that this problem is fixed in MP7.
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Sports - Sign up for Fantasy Baseball.
> http://baseball.fantasysports.yahoo.com/
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
|
|
|