Just take a dump of your DB, and copy of your configs, before you upgrade. You should have catalog backups anyway as it’s a vulnerable part of your system. That’s all you really need to roll back manually if needed. I like taking a SQL dump manually even though I have my catalog backups so I can avoid messing with bscan/bextract etc.
It also lets me manually inspect the dump that it worked as planned. (yes always test restore your backups also) Brock Palen 1 (989) 277-6075 [email protected] www.mlds-networks.com Websites, Linux, Hosting, Joomla, Consulting > On Apr 28, 2020, at 8:37 AM, Goncalo Sousa <[email protected]> wrote: > > yum history rollback [id] doesn't do the job? > > terça-feira, 28 de Abril de 2020 às 13:12:40 UTC+1, Oleg Volkov escreveu: > No, I am talking about rollback, reverting back to previous version. > Upgrading of production server suggest that you have any roll back plan. > Anyway it is your choice, not mine. > > -- > 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/34303ce5-505a-4f9c-b531-f9262b169689%40googlegroups.com. -- 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/000B16E2-2EFB-4EF1-9407-04E9363BFB5A%40mlds-networks.com.
