I’m assuming you are using disk based volumes, and not using Always Incremental.
Assuming you just copy off the old volumes that have the old jobs and never recycle them or expire them the SD will never try to access them. That does give you the option to move them back and forth as needed. If the SD does try to read them you will get an error, can then copy them back etc.
That said I would not do it that way. I”m sure there are better ways to make storage removable, I know there are several people that use USB devices etc kinda like tape.
I would look at examples using the Removeable Media option online
https://docs.bareos.org/Configuration/StorageDaemon.html
I would then create a new Pool and storage devices just for these ‘long term jobs’.
I would then use a Migrate Job
https://docs.bareos.org/TasksAndConcepts/MigrationAndCopy.html
To move the jobs in question form your online storage to your external drive, and then remove the drive when complete.
This keeps track of having these archived jobs on a different volume and storage device etc, but are still there is you want to get them back.
This person doesn’t even even bother with Removeable Media = yes just manaully copies over the jobs, this much like copying them off above as long as you know bareos isn’t going to try and read/write from those volumes when your drive isn’t connected at the path it expects to find those volumes generally is ok.
http://www.chriscouture.com/archive-full-bacula-backups-removable-hard-drive/
Brock Palen
bro...@mlds-networks.com
www.mlds-networks.com
Websites, Linux, Hosting, Joomla, Consulting
> --
> 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...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/f5ebc3ac-7b4b-40b6-92d9-f78f660440b1n%40googlegroups.com.