delete JobId=# should delete the data from the DB.
As to the tape normally you should wait for the other jobs to prune.
If you don't care about the other jobs you can do a purge volume
-Jason
On Thu, 2008-01-10 at 12:49 -0500, Mingus Dew wrote:
> Frank,
> Thanks for t
Frank,
Thanks for the link and tip. A further question though. If the job
failed, were any attributes or job information writtent to the catalog? How
can I purge both the information for this job from the catalog, and any data
that may have been written to the Volume?
Thank you
On Jan 10, 2
Mingus Dew wrote:
> I'm looking at the SQL syntax and can't figure out why it wants to
> insert these values into "batch" table. There was absolutely NO changes
> made to the database. This table has not existed previously. The only
> change that I've made recently was enabling data encryption for
I'm looking at the SQL syntax and can't figure out why it wants to insert
these values into "batch" table. There was absolutely NO changes made to the
database. This table has not existed previously. The only change that I've
made recently was enabling data encryption for these clients. I can't see
My bad... MySQL 4.1.22
On Jan 10, 2008 11:06 AM, Ryan Novosielski <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Mingus Dew wrote:
> > All,
> > I am running Bacula 2.2.5 on Solaris 10_x86. This morning one of my
> > incremental backups failed, thought I'm no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mingus Dew wrote:
> All,
> I am running Bacula 2.2.5 on Solaris 10_x86. This morning one of my
> incremental backups failed, thought I'm not sure why. The previous 24
> hours' jobs were successful however. Here is the error I received in the
> sta
All,
I am running Bacula 2.2.5 on Solaris 10_x86. This morning one of my
incremental backups failed, thought I'm not sure why. The previous 24 hours'
jobs were successful however. Here is the error I received in the status
email.
10-Jan 10:48 mt-back4.director JobId 533: Fatal error: sql_crea
