-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greetings,
Again, thanks everyone for your support thus far.
Regarding Volume Retention, Job Retention et all. I am not clear on
the matter, its a little confusing. I thought if I supply *no*
expiration dates on *anything* - but - Volume Retention to each
pools, the volumes will get "deleted" (from the database, not the
hdd). And Bacula is "smart enough" to prune/delet all jobs
associated with that volume. As I have Max Jobs per Volume = 1,
thus, one file per job, I expect this behavior:
1. Day: Backup Full
2.-6th. Day: Incremental.
7th Day: Backup Full
8[..]
61th day: file volume-001, with retention period of 60 days is
now marked for deletion/ recycling. Marking volume volume-001 as
empty, append. Oh! There was a job associated with volume-001,
I will now delete Backup Job #1 and all corresponding files from
the database.
Optional: Mh. I also notice that jobs #2 to #6 are incrementals
to Job #1, wont need those anymore, too. Deleting job and file
records #2 to #6.
62th day: Doing a full/incremental (doesnt matter) of client.
Using next free volume, thus, volume-001 instead of volume-062.
I got this opinion from the manual, the paragraph reads:
"Volume Retention = <time-period-specification>
The Volume Retention directive defines the length of time that
Bacula will keep Job records associated with the Volume in the Catalog
database. When this time period expires, and if AutoPrune is set to yes
Bacula will prune (remove) Job records that are older than the specified
Volume Retention period. All File records associated with pruned Jobs
are also pruned. The time may be specified as seconds, minutes, hours,
days, weeks, months, quarters, or years. The Volume Retention applied
independently to the Job Retention and the File Retention periods
defined in the Client resource. This means that the shorter period is
the one that applies. Note, that when the Volume Retention period has
been reached, it will prune both the Job and the File records."
To my understanding it means: If you retire a volume, all jobs and
file will also go bye-bye. Thus, a good method of "cleanly" cycle
the backup files.
I just hope if volume-001 (full backup) has a size of ~30gb, and
is marked for recycling, that the next job using this volume does
set the file size back to zero, and not append to it. I dont care
if volumes are actually deleted from the harddisk once they reach
their retention periods, but I do care that the required space
does not grow towards INF.
With weeky full backups and daily incrementals and a retention period
of 60 days.. that leaves me with max 8 full backups per client, thus,
I dont really care if the oldest backups are pruned. As long as there
is one running set.. :)
Its nearly 17:00.. the bat will come soon.
- -Christian.
- --
,----------------------------------------------------------------------
| Christian Reiss
|
| [EMAIL PROTECTED] /"\ ASCII Ribbon
| PGP-Key ID: 02FF71B2 \ / Campaign
| Public Key: http://demonlord.de/pgp.txt X against HTML
| Jabber: [EMAIL PROTECTED] / \ in eMails
|
| "Don't give up. Lose interest."
`----------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDT8N1GLayMgL/cbIRAg3mAJ9ZQKQ121lEZXSoAG2cvV4a49QiDgCg1PX2
8vM0DvHpXZb3zW40ozFotVQ=
=Wow3
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
