Re: [Bacula-users] Job Retention strangeness
On Tue, 03 Jul 2007 18:39:36 +0200, Andreas Koch said: Martin Simmons wrote: Maybe the Volume Retention is set in the volumes, so they were pruned? This prunes the jobs too. __Martin No, the Volume Retention is set much longer, too: +-+--+---+--+--+--+-+--+---+---+-+ | MediaId | VolumeName | VolStatus | VolBytes | VolFiles | VolRetention | Recycle | Slot | InChanger | MediaType | LastWritten | +-+--+---+--+--+--+-+--+---+---+-+ | 1 | Monthly-0001 | Recycle | 1| 0| 15768 | 1 | 0| 1 | LTO-2 | 2005-09-04 20:36:36 | | 2 | Monthly-0002 | Purged| 55995302042 | 57 | 15768 | 1 | 0| 1 | LTO-2 | 2005-10-02 06:10:29 | | 3 | Monthly-0003 | Purged| 61234491048 | 63 | 15768 | 1 | 0| 1 | LTO-2 | 2005-11-06 07:11:20 | ... That's the reason why I'm so stumped, I thought I had figured all of these details out by now :-) Right, looks OK. Bacula would write something to the Messages log file if it purged the volume. Maybe you still have those log entries? __Martin - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Job Retention strangeness
Hi Andreas,
You could try to update volume parameters on the volumes used for full
backup - perhaps the volumes were created before you defined the File
retention of 60 days - and it's one of the parameters that are stored on
the volume itself (my bacula server is currently unavailable - so I
can't verify if that parameter actually is on the volume).
on 07/03/07 11:55 Andreas Koch wrote:
Hi all,
we've been relying on Bacula for quite a while now and are very
satisfied users. However, I just noticed a strangeness with regard to
Job Retention on 1.38.9:
It appears to be obeyed only for our differential backup jobs, _not_ for
the full backups. Specifically, we set common retention periods for the
the client (there's only one in this setup) as:
# Client (File Services) to backup
Client {
Name = erebor-fd
Address = localhost
FDPort = 9102
Catalog = MyCatalog
Password = secret
File Retention = 60 days
Job Retention = 5 years
AutoPrune = yes # Prune expired Jobs/Files
}
and then have two backup jobs for that client (each consisting of either
a full or differential backupd, followed by a full backup of the catalog:
Schedule {
Name = WeeklyCycle
Run = Level=Full Pool=MonthlyTapePool 1st sun at 4:05
Run = Level=Differential Pool=SundayTapePool 2nd-5th sun at 4:05
Run = Level=Differential Pool=ThursdayTapePool thu at 4:05
}
# This schedule does the catalog. It starts after the WeeklyCycle
Schedule {
Name = WeeklyCycleAfterBackup
Run = Level=Full Pool=MonthlyTapePool 1st sun at 4:10
Run = Level=Full Pool=SundayTapePool 2nd-5th sun at 4:10
Run = Level=Full Pool=ThursdayTapePool thu at 4:10
}
However, when I look at the list of jobs using `list jobs`, only older
Differential jobs (from the Sunday and Thursday pools) are listed, e.g., as
| 7 | DefaultBackup | 2005-09-08 04:05:02 | B| D |
109705 | 4215201717 | T |
| 8 | BackupCatalog | 2005-09-08 04:16:54 | B| F | 1
| 309270413 | T |
starting in September 2005. The earliest full backup (Monthly) backup is
| 279 | DefaultBackup | 2006-12-03 04:05:04 | B| F |
2950669 | 88924511321 | T |
| 280 | BackupCatalog | 2006-12-03 10:49:32 | B| F | 1
| 1667026066 | T |
thus, December 2006. What happened to all of the other Full backups in
the meantime (which were definitely written to the tapes)?
At a glance, it appears that the Job Retention time appeared to ``take''
only for the Differentials, and that the Full backups use the default of
180 days.
Any ideas on what I might be doing wrong here?
Many thanks,
Andreas Koch
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
Regards,
Klavs Klavsen, GSEC - [EMAIL PROTECTED] - http://www.vsen.dk
PGP: 7E063C62/2873 188C 968E 600D D8F8 B8DA 3D3A 0B79 7E06 3C62
Those who do not understand Unix are condemned to reinvent it, poorly.
--Henry Spencer
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Job Retention strangeness
On Tue, 03 Jul 2007 11:55:11 +0200, Andreas Koch said:
Hi all,
we've been relying on Bacula for quite a while now and are very
satisfied users. However, I just noticed a strangeness with regard to
Job Retention on 1.38.9:
It appears to be obeyed only for our differential backup jobs, _not_ for
the full backups. Specifically, we set common retention periods for the
the client (there's only one in this setup) as:
# Client (File Services) to backup
Client {
Name = erebor-fd
Address = localhost
FDPort = 9102
Catalog = MyCatalog
Password = secret
File Retention = 60 days
Job Retention = 5 years
AutoPrune = yes # Prune expired Jobs/Files
}
and then have two backup jobs for that client (each consisting of either
a full or differential backupd, followed by a full backup of the catalog:
Schedule {
Name = WeeklyCycle
Run = Level=Full Pool=MonthlyTapePool 1st sun at 4:05
Run = Level=Differential Pool=SundayTapePool 2nd-5th sun at 4:05
Run = Level=Differential Pool=ThursdayTapePool thu at 4:05
}
# This schedule does the catalog. It starts after the WeeklyCycle
Schedule {
Name = WeeklyCycleAfterBackup
Run = Level=Full Pool=MonthlyTapePool 1st sun at 4:10
Run = Level=Full Pool=SundayTapePool 2nd-5th sun at 4:10
Run = Level=Full Pool=ThursdayTapePool thu at 4:10
}
However, when I look at the list of jobs using `list jobs`, only older
Differential jobs (from the Sunday and Thursday pools) are listed, e.g., as
| 7 | DefaultBackup | 2005-09-08 04:05:02 | B| D | 109705
| 4215201717 | T |
| 8 | BackupCatalog | 2005-09-08 04:16:54 | B| F | 1
| 309270413 | T |
starting in September 2005. The earliest full backup (Monthly) backup is
| 279 | DefaultBackup | 2006-12-03 04:05:04 | B| F | 2950669
| 88924511321 | T |
| 280 | BackupCatalog | 2006-12-03 10:49:32 | B| F | 1
| 1667026066 | T |
thus, December 2006. What happened to all of the other Full backups in
the meantime (which were definitely written to the tapes)?
At a glance, it appears that the Job Retention time appeared to ``take''
only for the Differentials, and that the Full backups use the default of
180 days.
Any ideas on what I might be doing wrong here?
Maybe the Volume Retention is set in the volumes, so they were pruned? This
prunes the jobs too.
__Martin
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Job Retention strangeness
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Klavs Klavsen wrote:
Hi Andreas,
You could try to update volume parameters on the volumes used for full
backup - perhaps the volumes were created before you defined the File
retention of 60 days - and it's one of the parameters that are stored on
the volume itself (my bacula server is currently unavailable - so I
can't verify if that parameter actually is on the volume).
I think that only Volume Retention is on the volumes. Job and File
Retention are in the Client:
*llist clients
ClientId: 1
Name: erebor-fd
Uname: x86_64-pc-linux-gnu,redhat,Enterprise release
AutoPrune: 1
FileRetention: 5184000
JobRetention: 15768
So, that can't be it. Actually, it was my first thought, too, that I
needed to do an update. But there seems to something else wrong here.
Andreas
on 07/03/07 11:55 Andreas Koch wrote:
Hi all,
we've been relying on Bacula for quite a while now and are very
satisfied users. However, I just noticed a strangeness with regard to
Job Retention on 1.38.9:
It appears to be obeyed only for our differential backup jobs, _not_ for
the full backups. Specifically, we set common retention periods for the
the client (there's only one in this setup) as:
# Client (File Services) to backup
Client {
Name = erebor-fd
Address = localhost
FDPort = 9102
Catalog = MyCatalog
Password = secret
File Retention = 60 days
Job Retention = 5 years
AutoPrune = yes # Prune expired Jobs/Files
}
and then have two backup jobs for that client (each consisting of either
a full or differential backupd, followed by a full backup of the catalog:
Schedule {
Name = WeeklyCycle
Run = Level=Full Pool=MonthlyTapePool 1st sun at 4:05
Run = Level=Differential Pool=SundayTapePool 2nd-5th sun at 4:05
Run = Level=Differential Pool=ThursdayTapePool thu at 4:05
}
# This schedule does the catalog. It starts after the WeeklyCycle
Schedule {
Name = WeeklyCycleAfterBackup
Run = Level=Full Pool=MonthlyTapePool 1st sun at 4:10
Run = Level=Full Pool=SundayTapePool 2nd-5th sun at 4:10
Run = Level=Full Pool=ThursdayTapePool thu at 4:10
}
However, when I look at the list of jobs using `list jobs`, only older
Differential jobs (from the Sunday and Thursday pools) are listed, e.g., as
| 7 | DefaultBackup | 2005-09-08 04:05:02 | B| D |
109705 | 4215201717 | T |
| 8 | BackupCatalog | 2005-09-08 04:16:54 | B| F | 1
| 309270413 | T |
starting in September 2005. The earliest full backup (Monthly) backup is
| 279 | DefaultBackup | 2006-12-03 04:05:04 | B| F |
2950669 | 88924511321 | T |
| 280 | BackupCatalog | 2006-12-03 10:49:32 | B| F | 1
| 1667026066 | T |
thus, December 2006. What happened to all of the other Full backups in
the meantime (which were definitely written to the tapes)?
At a glance, it appears that the Job Retention time appeared to ``take''
only for the Differentials, and that the Full backups use the default of
180 days.
Any ideas on what I might be doing wrong here?
Many thanks,
Andreas Koch
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
- --
Prof. Dr. Andreas Koch[EMAIL PROTECTED]
Technische Universität Darmstadt, FB20Phone : x49-6151-16-4378
Embedded Systems and Applications Group (ESA) FAX: x49-6151-16-5472
Hochschulstr. 10, D-64289 Darmstadt, Germany * PGP key available *
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGingNk5ta2EV7DowRAhpxAJ98mq9wfBqE4epEcgitmKv+RWFKqwCfUcHS
gonnqn83dB9mXopoEQuo+TY=
=mpJO
-END PGP SIGNATURE-
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Job Retention strangeness
On Tue, 03 Jul 2007 12:47:51 +0200, Klavs Klavsen said:
Hi Andreas,
You could try to update volume parameters on the volumes used for full
backup - perhaps the volumes were created before you defined the File
retention of 60 days - and it's one of the parameters that are stored on
the volume itself (my bacula server is currently unavailable - so I
can't verify if that parameter actually is on the volume).
None of the retention times are stored on the volume itself, but the volume
retention time is stored in the catalog record for each volume (copied from
the pool). Since a volume can contain many jobs for many clients, the file
and job retentions can't be stored on the volume.
__Martin
on 07/03/07 11:55 Andreas Koch wrote:
Hi all,
we've been relying on Bacula for quite a while now and are very
satisfied users. However, I just noticed a strangeness with regard to
Job Retention on 1.38.9:
It appears to be obeyed only for our differential backup jobs, _not_ for
the full backups. Specifically, we set common retention periods for the
the client (there's only one in this setup) as:
# Client (File Services) to backup
Client {
Name = erebor-fd
Address = localhost
FDPort = 9102
Catalog = MyCatalog
Password = secret
File Retention = 60 days
Job Retention = 5 years
AutoPrune = yes # Prune expired Jobs/Files
}
and then have two backup jobs for that client (each consisting of either
a full or differential backupd, followed by a full backup of the catalog:
Schedule {
Name = WeeklyCycle
Run = Level=Full Pool=MonthlyTapePool 1st sun at 4:05
Run = Level=Differential Pool=SundayTapePool 2nd-5th sun at 4:05
Run = Level=Differential Pool=ThursdayTapePool thu at 4:05
}
# This schedule does the catalog. It starts after the WeeklyCycle
Schedule {
Name = WeeklyCycleAfterBackup
Run = Level=Full Pool=MonthlyTapePool 1st sun at 4:10
Run = Level=Full Pool=SundayTapePool 2nd-5th sun at 4:10
Run = Level=Full Pool=ThursdayTapePool thu at 4:10
}
However, when I look at the list of jobs using `list jobs`, only older
Differential jobs (from the Sunday and Thursday pools) are listed, e.g., as
| 7 | DefaultBackup | 2005-09-08 04:05:02 | B| D |
109705 | 4215201717 | T |
| 8 | BackupCatalog | 2005-09-08 04:16:54 | B| F | 1
| 309270413 | T |
starting in September 2005. The earliest full backup (Monthly) backup is
| 279 | DefaultBackup | 2006-12-03 04:05:04 | B| F |
2950669 | 88924511321 | T |
| 280 | BackupCatalog | 2006-12-03 10:49:32 | B| F | 1
| 1667026066 | T |
thus, December 2006. What happened to all of the other Full backups in
the meantime (which were definitely written to the tapes)?
At a glance, it appears that the Job Retention time appeared to ``take''
only for the Differentials, and that the Full backups use the default of
180 days.
Any ideas on what I might be doing wrong here?
Many thanks,
Andreas Koch
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
Regards,
Klavs Klavsen, GSEC - [EMAIL PROTECTED] - http://www.vsen.dk
PGP: 7E063C62/2873 188C 968E 600D D8F8 B8DA 3D3A 0B79 7E06 3C62
Those who do not understand Unix are condemned to reinvent it, poorly.
--Henry Spencer
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Job Retention strangeness
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin Simmons wrote: Maybe the Volume Retention is set in the volumes, so they were pruned? This prunes the jobs too. __Martin No, the Volume Retention is set much longer, too: +-+--+---+--+--+--+-+--+---+---+-+ | MediaId | VolumeName | VolStatus | VolBytes | VolFiles | VolRetention | Recycle | Slot | InChanger | MediaType | LastWritten | +-+--+---+--+--+--+-+--+---+---+-+ | 1 | Monthly-0001 | Recycle | 1| 0| 15768| 1 | 0| 1 | LTO-2 | 2005-09-04 20:36:36 | | 2 | Monthly-0002 | Purged| 55995302042 | 57 | 15768| 1 | 0| 1 | LTO-2 | 2005-10-02 06:10:29 | | 3 | Monthly-0003 | Purged| 61234491048 | 63 | 15768| 1 | 0| 1 | LTO-2 | 2005-11-06 07:11:20 | ... That's the reason why I'm so stumped, I thought I had figured all of these details out by now :-) Andreas - -- Prof. Dr. Andreas Koch[EMAIL PROTECTED] Technische Universität Darmstadt, FB20Phone : x49-6151-16-4378 Embedded Systems and Applications Group (ESA) FAX: x49-6151-16-5472 Hochschulstr. 10, D-64289 Darmstadt, Germany * PGP key available * -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGinvIk5ta2EV7DowRAlPtAJwNBUeI52o8gzCK+nM9Gnizcnq3YgCfRgBV vbSz1SKBF+jgerhsMT+woeE= =/ZVd -END PGP SIGNATURE- - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
