> > There are two approaches: > > 1) The bareos way - purge jobs associated with given client and let the > bareos do its job. And that's the approach I'd recommend. Purge jobs > from given client, make sure you have "purge volume action=truncate" set > and the prune all volumes. If volumes are no longer associated with any > jobs (because you purged jobs from a particular client) they get purged. > When they get purged, they are truncated. And voila > I have an always incremental setup, would it prune/truncate the volumes anyways? Retention time for the last possible backup is set to 1 year, would i have to wait for that long?
> 2) The manuall fiddling way - you get list of volumes containing only > jobs from a given client by clever sql query (like inner join on > jobmedia and job with a where on particular client and group by media id > and count to select only volumes containing this single client jobs), > then you manually delete volumes and manually delete files from storage. > It can be done but it's not something that I'd recommend since the > previous approach is IMO much safer. > You are right, it would be safer to do bareos it's thing. But i don't really want to wait for 1 year. I am not really fluent in postgre, i mostly work with mysql. > You didn't tell us whether you're using one job per volume setup or any > other settings because that could make your task a little bit easier. > It's a pretty standard always incremental Setup from the documentation with 4 pools 1.Full 2.AI-Incemental 3.AI-Consolidated and 4. AI-LongTerm. The jobs can get mixed in the Volumes. > The database issue is another story. Depending on database type (MySQL? > Postgres? I don't suppose you're running this installation on sqlite) > and even database configuration (MySQL table engine and - for example - > file per table settings in case of innodb) you might need to do > different things. Of course dump/restore will give you a "shrinked > database" but that's a very radical approach. You might get away with > vacujming postgres database but keep in mind that for the vacuuming > process you need additional storage temporarily (my database shrunk from > 3.3GB to 2.6G after vacuuming but needed over 5G during vacuuming) and > the process itself is time-consuming. > I use postgresql, right now i have 64TB on the Storage and 12TB on the Director where The Database lives remaining. Can i vaccum while Bareos services are running or should i stop them? Best regards > > MK > Thank you very much. -- 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 bareos-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/ec6977ba-7644-4af5-81dc-5fd07d0caa6f%40googlegroups.com.
