Thank you for the replies.
The physical disk has about 2% free space (446GB) so it shouldn't be
locked preventing any maintenance from occurring due to insufficient
storage.
I issued the "update pool" command, which output
+--------+------+---------+---------+---------+------------+-----------------+--------------+----------------+----------------+------------+-------------+----------------+--------------+-----------+---------+---------------+----------+-----------+-------------+---------+---------------+---------------+------------+--------------------+-------------------+---------------+
| PoolId | Name | NumVols | MaxVols | UseOnce | UseCatalog |
AcceptAnyVolume | VolRetention | CacheRetention | VolUseDuration |
MaxVolJobs | MaxVolFiles | MaxVolBytes | MaxPoolBytes | AutoPrune |
Recycle | ActionOnPurge | PoolType | LabelType | LabelFormat | Enabled |
ScratchPoolId | RecyclePoolId | NextPoolId | MigrationHighBytes |
MigrationLowBytes | MigrationTime |
+--------+------+---------+---------+---------+------------+-----------------+--------------+----------------+----------------+------------+-------------+----------------+--------------+-----------+---------+---------------+----------+-----------+-------------+---------+---------------+---------------+------------+--------------------+-------------------+---------------+
| 2 | File | 310 | 310 | 0 | 1
| 0 | 31,536,000 | 0 | 50,400
| 0 | 0 | 53,687,091,200 | 0 | 1
| 1 | 1 | Backup | 0 | Vol- | 1
| 0 | 0 | 0 | 0
| 0 | 0 |
+--------+------+---------+---------+---------+------------+-----------------+--------------+----------------+----------------+------------+-------------+----------------+--------------+-----------+---------+---------------+----------+-----------+-------------+---------+---------------+---------------+------------+--------------------+-------------------+---------------+
then
* update volume fromallpools
All Volume defaults updated from "Default" Pool record.
All Volume defaults updated from "File" Pool record.
All Volume defaults updated from "Scratch" Pool record.
then
* prune expired volume yes
all Volumes reported "Found no Job associated with the Volume to prune"
then
* purge volume action=truncate allpools storage=File1
No Volumes found to perform the command.
I then attempted to run an incremental backup, and again received "The
job needs media. Please create a new volume for storage"
Apparently I've done something wrongly, but I'm not sure what. Your
instructions were quite easy to understand.
On 11/23/22 12:50, Bill Arlofski via Bacula-users wrote:
On 11/23/22 10:19, Nick Bright wrote:
>
Speculating this has to do with retention, I turned my retention for
both Jobs and Files down to 7 days, but still 'nothing to truncate' is
the output.
Yes...
After reloading the Director's config and doing "update pool=xxxx" for
the pool(s) you have updated (per Pedro's comment),
you will need to update all the volumes that exist in these pools with
the new retention periods.
If you do:
* ll volume=xxxx
For some existing volumes you will see that the retention is still the
old, longer one.
Then, do:
* update volume fromallpools
And then re-check those volumes and you will see they have the new
retention periods set.
Then you can try another prune and should see some new, better results.
Hope this helps,
Bill
--
Bill Arlofski
w...@protonmail.com
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
---------------------------------
- Nick Bright -
- KwiKom Communications -
- Office 800-379-7292 -
- Direct 620-228-5653 -
- Web https://www.kwikom.com/ -
---------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
