Hi, Chad
> I've noticed that bareos will reuse volume files which aren't in the
>database.
afaik, bareos cannot re-use volumes which not in catalog database because
it simply doesn't know about their existence.
To use volume, bareos looks in the catalog database for the volumes for
writing (f.e. in "Append" status) or which can be re-used ("Recycle").
If bareos cannot find in the catalog db volumes for writing, it will
generate a new volume name based on Label Format definition in the pool.
Do you mean that the new volume name from pool definition produces the same
name as old (but not bscanned yet) volume named?
You may easily avoid this behavior with ${JobId} or start time in Label
Format.
Or was re-used currently bscanning volume?
> This is a big problem in the following situation: You lose the
>catalog. (Say your building burns down, but you have fortunately saved
>the volume files offsite.) So you begin bscanning volume information
>back into the catalog. At the same time you begin making backups as
>computers come back online. While backing up these computers, bareos
>might choose a volume name which matches one fo the existing file names.
> If it does, it adds the volume name to the catalog, then reuses the
>volume file, overwriting the volumes' information which has not yet been
>bscanned into the catalog. Oops, that data is no longer recoverable!
we should avoid incremental backups until bscan completed, otherwise, the
incremental backup can be based on improper Full or contain already backed
up (but not scanned yet) files.
Also, keep in mind, that bscanned to the catalog db volumes have 'Archive'
status which prevents them from re-using (we have to change the status for
correct volume rotation)
> The obvious thing would be to not allow bareos to reuse volumes which
>are not already in the catalog.
On Fri, Dec 6, 2019 at 3:50 AM 'Chad W Seys' via bareos-users <
[email protected]> wrote:
> Hello all,
> I've noticed that bareos will reuse volume files which aren't in the
> database.
> This is a big problem in the following situation: You lose the
> catalog. (Say your building burns down, but you have fortunately saved
> the volume files offsite.) So you begin bscanning volume information
> back into the catalog. At the same time you begin making backups as
> computers come back online. While backing up these computers, bareos
> might choose a volume name which matches one fo the existing file names.
> If it does, it adds the volume name to the catalog, then reuses the
> volume file, overwriting the volumes' information which has not yet been
> bscanned into the catalog. Oops, that data is no longer recoverable!
> The obvious thing would be to not allow bareos to reuse volumes which
> are not already in the catalog.
>
> Thanks!
> Chad.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/bareos-users/83e5ac9e-3aa7-4fce-38e7-7339ddfa5c58%40physics.wisc.edu
> .
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/CANfMhsvVL%2B4eNbCps1RnrxP96Fohi%3D354O5oGeUvjtE%2BGiUUeQ%40mail.gmail.com.
