Hello.
I do not have a complete understanding of how bareos works, but I try to
understand.
I'm trying to use bareos on Linux, testing different situations.
In my test configuration, I have a 1 pool with 1 storage - hard drive.
Bareos scheduled backups, until the disk was full. After that, if the
backup job is started, a message is written to the log about the
impossibility of creating a Volume; the storage connection with the
client hangs for days, the backup job remains in Runninig state,
Job/File retention and Volume Recycling does not start. It seems that in
such a situation bareos cannot get out without manual intervention.
Can bareos be configured to detect such problems and solve them
automatically? For example, it would terminate a backup job, mark a
backup job as completed with an error, start jobs/files pruning, etc.
Maybe there is another question: under what circumstances does job/file
pruning run? In my journal, Prune marks stopped after the disk was full.
Part of Director's config:
Pool {
Name = pool_1;
Storage = stor_1;
Label Format = "volume_";
Maximum Volume Bytes = 262144000; #250MiB
Auto Prune = yes;
Catalog Files = yes;
Recycle = yes;
Volume Retention = 345600; #4 days
}
Client {
..skip..
Auto Prune = yes;
Job Retention = 172800; #2 days
}
Thank you.
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/85556068-ec88-2918-260d-5fcda7a9063c%40tiny-vps.com.
For more options, visit https://groups.google.com/d/optout.
