Re: bacula rescue cdrom source code
Josip Deanovic via Bacula-users <[email protected]>
| Newsgroups | gmane.comp.bacula.user |
|---|---|
| Message-ID | <[email protected]> |
On 2024-08-24 01:32, Jose Alberto wrote: > rear with bacula????? work??? Test > > https://packages.debian.org/bookworm/rear Hello, Yes, it works. I am using it for several years now, with Centos 6, Centos 7, Centos 8, Debian 10, Debian 11 and Debian 12. In my case, bootable rear image is between 180 and 550 MB, depending on the OS. I didn't have to use it for real but all the tests I have performed were successful. It can restore the correct partition table with file systems and will boot with the same IP address as the server that was used to create the image. I managed to configure it the way that it can add bacula client and all the needed libraries to the image. The ReaR configuration to achieve that is quite complicated and there were some limitations that I had to work around (without modifying the source). I got the impression that it is not an easy task for ReaR developers to maintain the code. Looks like bugs are easily introduced and hard to trace. I have a bacula job that builds fresh rear image every month for all the servers and a job called baremetal-restore which is meant to be used in conjunction with a rear iso image. The procedure for restoration using rear image in my setup goes like this: 1. get the newest bootable rear iso image from bacula 2. write the image to a bootable medium or use it as-is in case of virtual machine 3. boot the system using bootable rear iso image 4. use bacula director to initiate a bare metal restore 5. reboot the system The idea was to make the bare metal restore procedure quick and easy, with the hardware which is the same or similar to the original server. Regards -- Josip Deanovic