Great news! You're welcome Nick!
Nice to hear everything is working fine now :-)
Best,
Ana
On Thu, Dec 1, 2022 at 4:49 PM Nick Bright wrote:
> Previously I had tried truncating and the output was essentially 'nothing
> to truncate', but today it's truncating volumes - it may have just needed
>
Previously I had tried truncating and the output was essentially
'nothing to truncate', but today it's truncating volumes - it may have
just needed some time to pass before running successfully.
Thank you very much for your help on this!
- Nick Bright
On 12/1/22 05:53, Ana Emília M. Arruda
Hello Nick,
It seems to me that everything is working fine now.
The job log you have sent here is from November 23th, and I see the
Vol-0001 has been used on November 25th:
| 1 | Vol-0001 | Full | 1 | 53,687,078,657 | 12 |
604,800 | 1 |0 | 0 |
Hello Nick,
If you have volumes in Purged status, the truncate command should be able
to truncate volumes. Unless there is a misconfiguration related to media
types and storages.
Can you please share with us the following?
- list media output
- "File1"configuration in both the bacula-dir.conf
On 11/25/22 09:20, Ana Emília M. Arruda wrote:
Can you share your pool resource configuration here? Bacula has many
directives to different ways to recycle volumes, it would be nice to
see how you have the pool configured.
Sure, here is my pool configuration:
Pool {
Name = File
Pool Type
On 2022-11-25 16:00, Nick Bright wrote:
[...]
inelegant. The system should automatically be pruning or at least
allowing me to overwrite the old data - it ought to be cyclical - use
the available disk space (17T) to back up systems, letting old backups
fall off automatically so that new backups
Hello Nick,
On Fri, Nov 25, 2022 at 4:00 PM Nick Bright wrote:
> On 11/25/22 04:45, Ana Emília M. Arruda wrote:
>
> The easiest way is to allow Bacula to automatically prune Jobs and Files
> from the Catalog. It means to have "AutoPrune = Yes" in both the Client
> resource and in the Pool
On 11/25/22 04:45, Ana Emília M. Arruda wrote:
The easiest way is to allow Bacula to automatically prune Jobs and
Files from the Catalog. It means to have "AutoPrune = Yes" in both the
Client resource and in the Pool resource.
I already had AutoPrune = yes in both the client and pool; I had
Hello Nick,
Bill, I'm here :-) Sorry for not jumping in earlier.
Nick, I will try to summarize a bit about retention values and
pruning/truncation in Bacula. Pruning is about "the deletion of jobs and
files from Catalog". Automatic or manual prune will not touch the data in
the volumes, but only
I changed the Volume retention to 7 days, repeated all of the commands,
and ran a BackupCatalog job; still reports "The job needs media"
On 11/23/22 13:39, Bill Arlofski via Bacula-users wrote:
On 11/23/22 12:27, Nick Bright wrote:
In the Pool definition there is a Volume Retention of 365
If your volumes were allowed to fill the disk to 100%, that might be part
of your problem. Your (max volumes * volume size) should leave some buffer
space on the disk allocated to Bacula. If your working directory is on the
same disk, you need to be even more generous with that buffer (I often use
On 2022-11-23 20:02, Nick Bright wrote:
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.
Hi Nick
If your file system is configured to reserve some percentage of blocks
On 11/23/22 12:27, Nick Bright wrote:
In the Pool definition there is a Volume Retention of 365 days; however
each client has it's own File Retention and Job Retention (7 days each)
Shouldn't this result in the data contained within the volumes being
expired, and thus the volume could be
In the Pool definition there is a Volume Retention of 365 days; however
each client has it's own File Retention and Job Retention (7 days each)
Shouldn't this result in the data contained within the volumes being
expired, and thus the volume could be recycled/purged/truncated once
its'
Hello Nick,
For the pool you showed us, the VolRetention is `31,536,000` seconds.
This is not 7 days, but 1 year.
You may need to restart your Director, then perform the steps in my previous
email again to see the results you are looking for.
For VolRetention, you should see `604800` which
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
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=" for the
pool(s) you have
Hi Nick
Please execute update pool from resource command in bconsole so Bacula can
reflect the retention perio change in the existing volumes. Only after you
can execute the truncate command.
Best
Pedro
Nick Bright escreveu em qua., 23/11/2022 às 17:49 :
> Greetings,
>
> I'm new to Bacula,
18 matches
Mail list logo
