Replies: 1 comment
-
See #3076 and #3075 for the implementation and further conversation |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
We like to request a Veeam Linux Client disaster recovery integration option with relax and recover.
Our approach is to create a small PXE configuration for each single client, upload it to an NFS/PXE server and restore those
systems with PXE and the Veeam Backup agent for Linux.
Here is our procedure to run a successful backup and recovery with relax and recover:
Client-side configuration
File /etc/rear/local.conf:
OUTPUT=PXE
OUTPUT_PREFIX_PXE=$HOSTNAME
BACKUP=NETFS
BACKUP_URL=nfs://192.168.0.1/var/lib/tftpboot
PXE_TFTP_URL=nfs://192.168.0.1/var/lib/tftpboot/
PXE_CONFIG_URL=nfs://192.168.0.1/var/lib/tftpboot/pxelinux.cfg
PXE_RECOVER_MODE="unattended"
PXE_CONFIG_GRUB_STYLE=y
PXE_TFTP_IP=192.168.0.1
SSH_ROOT_PASSWORD=changeme
USING_UEFI_BOOTLOADER=1
COPY_AS_IS+=( /usr/share/rear/* /etc/veeam/* /usr/bin/veeam* /usr/lib/veeam/* /usr/sbin/veeam* /usr/share/veeam/* /usr/share/doc/veeam/* )
Backup procedure
rear -v mkbackup
After the backup task is completed, it should have created a PXE configuration file with initrd, vmlinuz kernel files on the NFS/PXE server.
Example:
[root@rhel8-veeam-rear tftp]# cat 01-02-a7-18-00-00-13
default hd
prompt 1
timeout 300
label hd
localboot -1
say ENTER - boot local hard disk
say --------------------------------------------------------------------------------
display /rhel8-veeam-rear.message
say ----------------------------------------------------------
say rear = disaster recover this system with Relax-and-Recover
label rear
kernel /rhel8-veeam-rear.kernel
append initrd=/rhel8-veeam-rear.initrd.cgz root=/dev/ram0 vga=normal rw selinux=0 console=ttyS0,9600 console=tty0
[root@rhel8-veeam-rear tftp]#
Restore Procedure
Commands to use
rear recover
systemctl start veeamservice
'veeamconfig vbrServer add --name --address --domain --login Administrator (IP und Hostname von Veeam Server) --password '
veeamconfig backup list --all (Always use the last backup ID
Example:
veeamconfig backup mount --id {Use same the mount-id which was provided from the previous command)}
: Info:
This could raise an error, because the software want´s to mount the device in read/write mode, which is not allowed.
:The device was only mounted as veeamloop device and needs to be remounted agains as read-only device for recovery
Final recovery procedure
Recover the files from /mnt/backup to /mnt/local
shopt -s dotglob
cp -rpva /mnt/backup/* /mnt/local/ # Copyjob time can depend of the amount of data :)
Chroot and rewrite the GRUB Bootloader
chroot /mnt/local
sudo dnf reinstall shim-* grub2-*
exit (von rear console)
Did you restore the backup to /mnt/local ? Are you ready to continue recovery ? yes
After this "umount -a" and "reboot"
SELinux will be relabeled if necessarry
Last Post Task:
Add the client/server back to an Veeam Protection Group with an XML file:
-- veeamconfig mode setVbrSettings --cfg
Please let us know, how we can proceed on this or if we can get some help from the community.
Any answer is kindly appreciated.
Thanks and best regards,
Andreas
Beta Was this translation helpful? Give feedback.
All reactions