Yeah, thats exactly what I did, the other volume I could save (I purged it),
but since I'm running short on Tapes here, I just wondered if there was a
way to save that space on the first volume...
The logic about concurrent Jobs is absolutely right, but since I KNOW that
there was only one Job on that space, i thought it would be possible to
recover it... and that "until some day you recycle the hole volume" is going
to be in 4 months... :)
Well, thanks for the answer!
2011/1/18 Timo Neuvonen <timo-n...@tee-en.net>
> "Rodrigo Renie Braga" <rodrigore...@gmail.com> kirjoitti viestissä
> news:AANLkTi=vLBszk=7e9f7aoeeqssny6b2vhacvrfqci...@mail.gmail.com...
> > Sorry, actually the Volume is marked as "Full", not "Used" as I posted
> > before...
> >
> > thanks...
> >
> >
> > 2011/1/18 Rodrigo Renie Braga <rodrigore...@gmail.com>
> > >
> > > Hello everyone..
> > >
> > > I'm currently using, in my Tape Storage, LTO-4 Tapes (800Gb each). I
> had
> > > a Volume on a specific Pool with already 100G of space used by previous
> > > Full backups. After that, I started a Full Backup job on the same Pool,
> > > which ended up using the same Volume (no problem there). Since the
> > > Client of that Job was using over 1Tb of data, the Job filled up that
> > > first Volume and started to use another volume (no problem there
> > > either).
> > >
> > >The problem is, the partition of my PostgreSQL database was very small
> > >and before that Job had a chance to end, that partition got 100% full
> and
> > >Bacula couldn't insert any more queries. Hence, the Job was cancelled by
> > >Bacula.
> > >
> > > My question is, all that space used by only one Job on the first tape
> > > (little over 700G), will no longer be usable? That Volume is currently
> > > marked as "Used", since Bacula started to use a second volume for that
> > > Job.
>
> Correct. That space won't be available until you some day recycle the whole
> volume.
>
> This may sound strange, or even stupid. However, your case is very
> simplified: in general case there could have been several concurrent jobs
> running (on of which then failed) and thus data from several jobs had been
> interleaved. In that case it wouldn't any more look that simple to
> "backspace" in the volume.
>
> But you can freely purge the second (newly started) volume immediatedly, if
> you didn't append other jobs (to be kept) after the failed one.
>
> Regards,
> Timo
>
>
>
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
