Hello all, while I have running backup jobs the storage is running out of space (disk file changer volumes). As the pool (pool2) that is currently written has already been truncated (manually some weeks ago), recycling of volumes does not create free space.
I thus wanted to truncate volumes from a different pool (pool1) while the backup is writing to pool2: truncate pool=pool1-incr storage=storage1 I get the following error (for each purged volume in pool1)(showing just 1 here): Error truncating Volume “pool1-incr-vol-1109" 3908 Error reserving volume: vol_mgr.c:418 Cannot free Volume “pool2-full-vol-0703", because it is reserved by someone else. What is the reason that I cannot truncate on storage1 while a backup job is running on storage1? There is only 1 backup job running at a time. The MaximumConcurrentJobs directives are configured as follows: SD config file: -Storage1 allows 20 concurrent jobs in the SD config file. -The device allows for 5 concurrent jobs. Director config file: -The director allows 20 concurrent jobs. -Storage1 only allows 1 concurrent job in the director config file. Would this have to be configured to the same number as in the SD config file? -Is the limit of 1 here prohibiting me to truncate while the backup job is running? -The clients allow only 1 concurrent job. FD config file: -The FD allows 20 concurrent jobs. In general I want jobs to run sequentially, but truncating should be able to happen simultaneously. Is it possible to realize that? Wich MaximumConcurrentJobs directives would I need to change and how? Thanks for taking the time to consider my question, J/C _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
