Change storage definition in pools and jobs seamlessly?

[Jens Köhler]

Hey guys,

I'm about to switch our backup system to a new server + tape drive and I want to know if there is any (catalog) trouble to be expected if I replace the current Storage definition in pool and job configuration files with a new one.

Further explanation:

- the old backup server (Windows 2008) has mounted a virtual drive from our SAN where all volumes are stored

- the Bareos Storage Daemon FileStorage device points to this drive and uses it for backup and restore jobs

- the new backup server (Windows 2019) will have this exact drive mounted the exact same way

- so the only things that will actually change are:

-- Storage IP address

-- Storage name (e.g. "backup2008" -> "backup2019")

-- transport encryption TLS might be enabled for the new Storage Daemon

Do I have to update the catalog in any way so that Bareos knows where to find all pre-existent volumes after the switch?

Do I risk anything like triggering a full backup for all pools/jobs because of the change?

Thanks in advance

Regards

Jens

[Jens Köhler]

So I basically did the following:

- change Storage in all Job and Pool configuration files

- update all Pools with bconsole update pool

- change Storage of all volumes in Bareos database (Catalog) with a one liner for-loop using "bconsole list volumes" and "bconsole update volume=$volume Storage=$newbackupserver"

Everything works as aspected.

Jens Köhler <koe...@rzhartmann.de> hat am 03.11.2021 15:28 geschrieben:

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/1949026004.295949.1635949737770%40mail.rzhartmann.de.