Hello Dan

First of all, thank you very much for all the information you sent me.
Thank you for taking your time to write me in detail the operation of bareos.
This information is very important because I have not seen it in bareos 
reference manual.

Thank you also for your tips for optimizing backups (not to make full backup 
every days)
But unfortunately the backup policy of my company requires to make full backup 
2 ​​times per week. This is one of my constraints ^ _ ^.

Otherwise, to facilitate the understanding of my problem I will provide some 
additional details.

As I said in one of my messages the configuration of bareos is the following
- 1 backup = 1 server = 1 job = 1 volume = 1 file on the disk
but no volume is recycled. So a status volume is either full, used or purged

For any new backup of the same server, a new file will be created.
This is to avoid any interleaving of data in the same volume.
I configured my pool with parameter  "Action On Purge = Truncate" so that 
bareos deletes all volumes from a job with obsolete retention.

But as you said in your message bareos 16.2.4 (my current version), do not 
delete any volume or job even if the volume is in the "purged" state.

So I then created a script that searches all the volumes with the "purged" 
status in the catalog and deletes the files on the disks corresponding to the 
"purged" volumes.
This script is launched every morning at 02:00 am.

And my backup of 2To is launched twice a week at 5:00 am.

My problem that I noticed is that the expiration status of the volume is 
updated when there are backups which running.

So when I backup twice a week (with a 6-day retention) a server with 2TB of 
data for example, Bareos makes 3 backups (6 TB of used disk space) before 
updating volumes status.
And so, my script delete the oldest backup only next day.

I expected that everyday at midnight, bareos updated the status (purge, use and 
so on ..) of all its  volumes.

If my observation is correct, I repeate my question (sorry ç_ç), is it possible 
to run jobs without making backup (for example do a job test without making a 
backup)? This running would just update the status of the volume and job 
without making any backup on my disks.

Thank you in advance for your help

Regards Knoax

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to