In theory, I agree...in practice, I haven't found it worked that well..
:o(

The reason I'm having issues is due to only having a 90 Gig DSSU. To
backup 5 machines, each with around 15-20 gigs of data......(total of
all 5 is about 80 gigs.)

However, we're using the DSSU (comprised of left over un allocated space
on a couple disks) to back these machines up over a 10M excrypted link,
which only passes about 300KB/s, and we can't afford to have these 5
machines consume a tape drive for 20+ hours for full backups.

We do have a Enterprise storage solution going online in Q3, so
hopefully I'll get a SAN attached Terabyte DSSU then!
;o)

Paul

> -----Original Message-----
> From: Rob Worman (home) [mailto:rob AT worman DOT org] 
> Sent: February 2, 2005 10:14 PM
> To: Paul Keating
> Cc: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] Disk Staging & Storage Unit Groups
> 
> 
> Paul: "It is a good idea to have fulls and incrementals go to 
> different 
> DSU's"
> If a backup to a DSSU encounters a diskfull error, the 
> following results:
>     (1) pause the backup
>     (2) expire up to two [this number was recently upped to 
> ten] of the 
> oldest images that have been duped to tape
>     (2a) if there are no images to expire in (2), fail the 
> backup with 
> an 84
>     (3) resume the backup;  if another diskfull condition occurs, see 
> step (1)
>