-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
But you did not expect that to work properly, because the previous job
failed, right?
Does everything work properly if the previous job did not fail? I
actually have never had this happen with my setup -- if the previous job
fails, I know about it and
On Mon, 2006-05-08 at 14:51 -0400, Ryan Novosielski wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> But you did not expect that to work properly, because the previous job
> failed, right?
>
> Does everything work properly if the previous job did not fail? I
> actually have never had
On Fri, 2006-05-05 at 21:17 -0400, Peter Sjoberg wrote:
> On Fri, 2006-05-05 at 16:06 -0400, Ryan Novosielski wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > It absolutely does work, at least with single drives. I do this
> > currently (writing larger fulls to a DAT72 drive an
On Fri, 2006-05-05 at 16:06 -0400, Ryan Novosielski wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> It absolutely does work, at least with single drives. I do this
> currently (writing larger fulls to a DAT72 drive and smaller
> incrementals to a DDS4).
>
> Here's an example:
>
> Sc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It absolutely does work, at least with single drives. I do this
currently (writing larger fulls to a DAT72 drive and smaller
incrementals to a DDS4).
Here's an example:
Schedule {
Name = "UMD-F13T-Inc"
Run = Level=Full Storage=helios_DAT72 1st,3r
On Wednesday 03 May 2006 05:32, Peter Sjoberg wrote:
> I'm asking for suggestions on how I can best utilize two tape libraries.
> One tape library is a 10 x DLT7000
> The other is 15 x DLT8000
>
> At first I was thinking of putting the FULL backup to the bigger library
> and run diff and inc to the
I'm asking for suggestions on how I can best utilize two tape libraries.
One tape library is a 10 x DLT7000
The other is 15 x DLT8000
At first I was thinking of putting the FULL backup to the bigger library
and run diff and inc to the smaller one but I don't know the best way to
do that.
I kind o
