[Bacula-users] My backup files aren't being reused and my backups are stuck. Help ?
Hello,
I'm having some problems with backup file configuration.
I want the backup file area to consume 100GB and no more.
I decided on file sizes of 1GB
Pool {
...
Volume Retention = 365 days # one year
Maximum Volume Bytes = 1G # Limit Volume size to something reasonable
Maximum Volumes = 100 # Limit number of Volumes in Pool
Recycle = yes # Bacula can automatically recycle Volumes
AutoPrune = yes # Prune expired volumes
...
}
I enabled the following schedule:
#
# When to do the backups, full backup on first sunday of the month,
# differential (i.e. incremental since full) every other sunday,
# and incremental backups other days
Schedule {
Name = "WeeklyCycle"
Run = Full 1st sun at 23:05
Run = Differential 2nd-5th sun at 23:05
Run = Incremental mon-sat at 23:05
}
... and what I saw is 100 files written and filled, and then all backups
stopping in their tracks and no further backups produced.
Every new job errors out.
None of the older backup files were reused.
Backups only resumed when I manually deleted the oldest volumes from bconsole,
and stopped again when the maximum number of files had been reached
I want automatic space management so that when the maximum number of volumes
are created, the oldest ones are reused.
I don't know how to set the "Volume Retention" accurately (as my backup sizes
are not predictable, as I install new software or accumulate business data
their size will likely increase),
I want the backups to always fit within my prescribed amount of storage space
and recycle that space when needed, without manual intervention.
How can I achieve this ?
Thanks.___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula purges old jobs and I don't want it to do that
Hello, wt., 7 lis 2023 o 21:57 Rob Gerber napisał(a): > To update this thread, I ultimately was able to avoid a bscan of all my > backed up media by restoring a backup of my catalog database. I have set > file, job, and volume retention to 1000 years. > Volume retention for 1000Y means you will never recycle your backups, so it will occupy all your available storage in the long term and you will be forced to manually delete oldest unused backups. IMVHO, doing manual backup recycle on will, is the last clever idea anyone can get. It is always better to set a real and usable volume retention and let the Bacula (enterprise class backup software) do this job for you. > Does a virtual full job strategy eliminate information about changed > files? ie, if the full backup captured fileA in one state, and if a later > incremental backup captured fileA in a different state, would the virtual > full consolidation process eliminate reference to the first backup of fileA? > Bacula Community does not maintain backups as data references, but always does a data copy on virtual full. You have to use Bacula Enterprise GED feature to get data references on virtual full. So, in your question virtual full consolidation process will use fileA state from incremental backup level and will copy it to the new virtual full backup job. > Lets assume that once a tape is full it, nor its associated files or jobs > will never be recycled, at least not for a 7 year period or so. > It doesn't matter. Virtual full will be a fully independent backup copy from all its ingredients. It will occupy a new backup space. > Incrementals forever could scale very badly in a larger enterprise, > Did you check BackupsToKeep functionality in Bacula? I have a different opinion on this matter. > but my objective is to protect a single set of files on a single system. > My largest concern is tapes going missing in an incremental chain, and for > that reason I'm probably going to need to do differential backups > periodically. > If you want to maintain a few hundred thousand incrementals chain because you've made a single full a 1000Y ago and did incrementals only, then this policy won't work by design. Incrementals forever means your backup client won't need to execute full backup (despite a first one) any more. It doesn't mean your backup chain only grows. It means backup software consolidates automatically full+incrementals chain for oldest backups or creates a full level from data already saved. Bacula uses a virtual full backup level for this. In this case you can set up a time base consolidation, i.e. once a week or number based consolidation, i.e. number of remaining incrementals. or I totally misunderstood your concerns here. R. -- Radosław Korzeniewski rados...@korzeniewski.net ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Q: what will bacula do if I reduce pool MaximumVolumes lower than number of existing vols in pool?
Hello, pon., 20 lis 2023 o 00:27 Justin Case napisał(a): > Hi there, > > I realise that my short term pool will have more volumes than actually > necessary, as I started the backups earlier than on the day per month when > fulls are taken. So this pool will have at least two fulls in the first > month. In subsequent months there will only be the need for 1 full per > month. > > Now I had this thought: may I reduce the MaximumVolumes of that pool after > 2 months when the superfluous first full has been purged? Explicitly this > does mean I would set MaximumVolumes of the pool to a number that is lower > than the number of volumes currently help in this pool. How would Bacula > react? would it throw the oldest purged volumes into the Scratch pool? Or > what else? > MaximumVolumes parameter will prevent automatic volume labeling or moving existing volume from Scratch pool only. No other procedures will be performed when the number of volumes exceeds this limit. So, unless configured by different parameters it won't move volumes out of the pool automatically. If you set up a recycle pool in your pool configuration then Bacula will always put recycled volumes in this pool, regardless of MaximumVolumes set. It is an independent parameter. Setting both on your pool will allow you to automatically lower the number of volumes in the pool and maintain a maximum number of them. best regards -- Radosław Korzeniewski rados...@korzeniewski.net ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] newbie: errors in baculum
Am 26.01.24 um 21:01 schrieb Marcin Haba: Hello Stefan, Yes, for PostgreSQL 15 you need this patch. It should still be valid. At the moment Bacula GitLab stopped working so I am sending the patch in attachment. It is a one line patch. After applying it, the TDbCommand error should not occur anymore. correct, thanks! Yours is a different patch than the one I had found. GUI works now, I can proceed learning and configuring ... ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
