Hello, wt., 7 lis 2023 o 21:57 Rob Gerber <r...@craeon.net> 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
