I had a similar project once few years ago. I cannot post the detailed solution due to legal restrictions but I can describe the general idea. The situation was that a piece of software running on a server would create archive files in a given directory. Those files were to be archived in sufficiently many copies and then removed. So I did a full backup job with a fileset created dynamicaly using a script which would do a directory scan in the directory, then run a query against bareos catalog and only backup those files which: 1) Weren't backed up sufficiently many times and 2) Weren't backed up on this media yet. Apart from that I'd run a cron job completely asynchronously which would scan the directory and remove the files which had been already backed up enough times. This way I made sure that each archive file would get backed up on several different media and only after that it would get removed from the source server. In my case it was an all-in-one installation of bareos so I had easy access to both director database and FD directory contents. If you have those components separated you might need to do some access rights juggling of course. Of course you need to set the retention values to some ridiculously high periods in order to not get the files pruned from the database.
Hope this helps On Thursday, July 8, 2021 at 5:50:47 PM UTC+2 Olivier Ardouin wrote: > Hi Frank, > > Thank you for this article, but it's not applicable in my case. > > I have only one client (for this Archive task) and my datas are, when > archived, frozen, just some new data to append from time to time. The total > volume of data (more than 34 tb now and still growing) is not compatible > with consolidation tasks (and only one drive in the autoloader). > In fact it could be done whithout bareos by a simple tar command and add > all the new folder to the tape manually. I may end with this solutions and > keep a track of which folders were in wich tape. Restore will be more > manual cause I will not be able to rely on the bareos catalog. I guess the > fonction should be in bareos in the pool type = Archive which is not yet > implemented in Bareos. > > A workaround may be to specified a file set for the "new" data do regular > full backup of this file set with 30 years retention time and a specific > "archive" pool, and move them automatically after the job in an "archived" > folder exclude from the file set. > > Did someone know if the Archive pool type will be implemented soon ? > > Thank's > > Le lundi 5 juillet 2021 à 13:50:24 UTC+2, frank....bareos.com a écrit : > >> Bonjour Olivier, >> >> if I understand correctly this article (page 3) should help >> >> https://translate.google.com/translate?sl=auto&tl=fr&u=https://www.admin-magazin.de/Das-Heft/2020/02/Always-Incremental-mit-Bareos/%28offset%29/6 >> >> >> >> best, >> Frank >> >> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/92dd375a-4cc5-4431-b736-7734a6b24d17n%40googlegroups.com.
