help with disaster recovery process

[Markus Dubois]

Hi,

i´m trying to build a structural process for a disaster recovery.

We have a copy job to a remote location. If the main bareos db gets rebuild, the remote copied volumes need to be reimported into the db

For this there is bscan available.

For this approach i have a few questions.
1.) for bscan to work, the volume names need to be preexisting in the bareos-db is this true, or are they created with the bscan?
2.) bscan is single volume oriented. Whats the best approach to get a huge amount (full backup) of volumes processed with bscan?

3.) is 1+2 the correct way or are there other/better approaches?

[Philipp Storz]

Hello Markus.

Am 11.05.25 um 12:01 schrieb Markus Dubois:

> Hi,
>
> i´m trying to build a structural process for a disaster recovery.
>

> We have a copy job to a remote location. If the main bareos db gets rUsing bscan is not recommended, aebuild, the remote copied

> volumes need to be reimported into the db
> For this there is bscan available.

No. If you find yourself using bscan, something is wrong with your recovery process.

The correct recovery process is as follows:

1.: You make sure, that both the medium containing your catalog backup and the corresponding
bootstrap file are available in an disaster event. (That is why the bootstrap file of the catalog
backup is sent via email in the default configuration).

2.: In the disaster case, you install Bareos on your new machine and use bextract together with the
bootstrap file to extract the most recent catalog backup and the configuration.

3.: You put the configuration files that have just been extracted into /etc/bareos and restore the
database with the just restored dump file.

4.: You can start the Bareos daemons and everything is working again.

Best regards,

Philipp

>
> For this approach i have a few questions.
> 1.) for bscan to work, the volume names need to be preexisting in the bareos-db is this true, or are
> they created with the bscan?
> 2.) bscan is single volume oriented. Whats the best approach to get a huge amount (full backup) of
> volumes processed with bscan?
> 3.) is 1+2 the correct way or are there other/better approaches?
>

> --
> 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 bareos-
> users+un...@googlegroups.com <mailto:bareos-users...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/bareos-users/13dd2c6a-5e85-4158-
> a0bd-18c59a096e7an%40googlegroups.com <https://groups.google.com/d/msgid/bareos-
> users/13dd2c6a-5e85-4158-a0bd-18c59a096e7an%40googlegroups.com?utm_medium=email&utm_source=footer>.


--
Mit freundlichen Grüßen

Philipp Storz philip...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221 63 06 93-92
http://www.bareos.com

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz

Die "dass IT GmbH" wurde mit der "Bareos GmbH & Co. KG" verschmolzen,
siehe https://www.bareos.com/de/dassit-verschmelzung/

[Markus Dubois]

okay, so you´re saying i need the bareos database where the backup files are already included?

then of course no import is needed, so the approach is to shift the database backup (sql dump) also to the remote location.

Sure this is very possible.

But just out of curiosity, when "everything" goes wrong and there is no database with the backup included available?

Isn´t then the import in a newly created database needed and bscan the tool to do it?

[Bruno Friedmann (bruno-at-bareos)]

Hi Markus,

Nope in case everything goes wrong, we used the bsr file to extract the sql dump from the volume where the last BackupCatalog job is stored.

Then we import the sql dump to a new db but with pg_restore or psql not with bscan

Hope this clarify a bit the whole process.