Hi,
I see this as well. I believe that's normal behaviour as the check for the
high water mark is done before it starts writing the image.
/Steve
--
On Fri, 24 Oct 2008, Justin Piszcz wrote:
> Say you have 4 clients, each have 10TiB of data on them.
> For disk staging you only have 1TiB on each client.
>
> When it gets to 98% of the total capacity of the staging area (default)--
> shouldn't it pause, bleed to tape, delete the files on disk and then
> continue?
>
> Instead, it keeps backing up the files to disk until the disk runs out of
> capacity, has anyone encountered this?
>
> /dev/cciss/c0d0p2 55G 51G 627M 99% /local
> /dev/cciss/c0d0p2 55G 51G 503M 100% /local
> /dev/cciss/c0d0p2 55G 51G 311M 100% /local
> /dev/cciss/c0d0p2 55G 52G 154M 100% /local
> /dev/cciss/c0d0p2 55G 52G 7.1M 100% /local
> /dev/cciss/c0d0p2 55G 52G 0 100% /local
>
> And then..
>
> 10/24/2008 04:15:26 - Critical bpdm (pid=32317) bp_sts_write_image failed:
> error 31
> 10/24/2008 04:15:26 - Warning bpdm (pid=32317) storage unit my_stage01 is
> full: processing disk full condition
> 10/24/2008 04:15:41 - Critical bpdm (pid=32317) bp_sts_write_image failed:
> error 31
> 10/24/2008 04:15:41 - Error bpdm (pid=32317) cannot write image to disk,
> attempted write of 262144 bytes, system wrote 0
> 10/24/2008 04:15:42 - Error bpbrm (pid=32310) from client client-name: ERR -
> Cannot write to STDOUT. Errno = 104: Connection reset by peer
>
> About 10-15 seconds later..
>
> /dev/cciss/c0d0p2 55G 55G 0 100% /local
> /dev/cciss/c0d0p2 55G 55G 0 100% /local
> /dev/cciss/c0d0p2 55G 51G 593M 99% /local
> /dev/cciss/c0d0p2 55G 29G 24G 55% /local
> /dev/cciss/c0d0p2 55G 23G 29G 45% /local
> /dev/cciss/c0d0p2 55G 19G 33G 37% /local
> /dev/cciss/c0d0p2 55G 18G 35G 34% /local
> /dev/cciss/c0d0p2 55G 18G 35G 34% /local
> /dev/cciss/c0d0p2 55G 18G 35G 34% /local
> /dev/cciss/c0d0p2 55G 18G 35G 34% /local
>
> It starts deleting the files even though it has not yet written anything
> to tape?
>
> With other backup SW-- it sticks to the settings you have it set
> to, e.g., 70% and then backup to tape, pause backup until it pushes
> all of the data off disk. With NetBackup that is not the case, any
> ideas?
>
> Justin.
>
> _______________________________________________
> 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
|
