>>>>> On Fri, 3 Jul 2020 16:00:10 -0600, Greg Woods said:
>
> I am getting this error when running copy jobs. I have an "ARCHIVE-ALL" job
> that searches for any client backup jobs that terminated normally and have
> not yet been copied from online to archive backups, and runs copy jobs for
> each. I have been using this system for 7 years now, and it has worked well
> until today.
>
> Here's the Pool definitions (File is the online pool, and Archive is a
> vchanger with 6 removable disks as magazines):
>
> Pool {
> Name = File
> Pool Type = Backup
> Recycle = yes # Bacula can automatically recycle
> Volumes
> AutoPrune = yes # Prune expired volumes
> Volume Retention = 365 days # 1 year
> Maximum Volume Bytes = 50G # Limit Volume size to something
> reasonable
> Maximum Volumes = 245 # Limit number of Volumes in Pool
> Storage = BKUP
> Next Pool = Archive # Where to copy/migrate to
> }
> Pool {
> Name = Archive
> Pool Type = Backup
> Recycle = yes # Bacula can automatically recycle
> Volumes
> AutoPrune = yes # Prune expired volumes
> Volume Retention = 365 days # one year
> Maximum Volume Bytes = 50G # Limit Volume size to something
> reasonable
> Maximum Volumes = 136 # Limit number of Volumes in Pool
> Storage = ARCH
> }
>
> As you can see, the volume retention in the Archive pool is set to 365
> days., and Recycle is set to yes, which means (if I understand this
> correctly) that any volume that hasn't been written to in more than a year
> should be available to recycle. So why is it suddenly telling me that there
> are no appendable volumes after 7 years of running this configuration?
>
> All of my client definitions look like this:
>
> Client {
> Name = "myhost"
> Address = myhost.my.domain
> Catalog = "My Catalog" # there is only one
> Password = "big secret"
> File Retention = 365 days
> Job Retention = 365 days
> }
>
> Did I miss something? There are definitely some volumes in the Archive
> pool that have not been written to in more than a year; shouldn't those be
> available for recycling?
The output of "list volumes pool=Archive" might show something. In
particular, what is the volstatus of these volumes? It must be Used or Full
to allow recycling.
> Lastly, what command would I use to let Bacula know that a given volume can
> be made available? Eventually I have to solve my configuration issue, but
> for now I'd like to just mark some old volumes as available manually so
> that my copy jobs can continue.
You could try the purge volume command.
__Martin
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users