Este conteúdo não está disponível no idioma selecionado.
Chapter 2. Preparing the backup node
Before you back up the undercloud or control plane nodes, prepare the backup node to accept the backup images.
2.1. Preparing the NFS server
ReaR can use multiple transport methods. Red Hat supports back up and restore with ReaR using NFS.
- Install the NFS server on the backup node. - dnf install -y nfs-utils - [root@backup ~]# dnf install -y nfs-utils- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
- Add the NFS service to the firewall to ensure ports - 111and- 2049are open. For example:- firewall-cmd --add-service=nfs firewall-cmd --add-service=nfs --permanent - [root@backup ~]# firewall-cmd --add-service=nfs [root@backup ~]# firewall-cmd --add-service=nfs --permanent- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
- Enable the NFS server and start it. - systemctl enable nfs-server systemctl restart nfs-server - [root@backup ~]# systemctl enable nfs-server [root@backup ~]# systemctl restart nfs-server- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
2.2. Creating and exporting the backup directory
To copy backup ISO images from the undercloud or control plane nodes to the backup node, you must create a backup directory.
Prerequisites
- You installed and enabled the NFS server. For more information, see Preparing the NFS server.
Procedure
- Create the backup directory: - mkdir /ctl_plane_backups - [root@backup ~]# mkdir /ctl_plane_backups- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
- Export the directory. Replace - <ip-addr>/24with the IP address and subnet mask of the network:- [root@backup ~]# cat >> /etc/exports << EOF /ctl_plane_backups <ip-addr>/24(rw,sync,no_root_squash,no_subtree_check) EOF - [root@backup ~]# cat >> /etc/exports << EOF /ctl_plane_backups <ip-addr>/24(rw,sync,no_root_squash,no_subtree_check) EOF- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow - The entries in the - /etc/exportsfile are in a space-delimited list. If the undercloud and the overcloud control plane nodes use different networks or subnets, repeat this step for each network or subnet, as shown in this example:- cat >> /etc/exports << EOF /ctl_plane_backups 192.168.24.0/24(rw,sync,no_root_squash,no_subtree_check) /ctl_plane_backups 10.0.0.0/24(rw,sync,no_root_squash,no_subtree_check) /ctl_plane_backups 172.16.0.0/24(rw,sync,no_root_squash,no_subtree_check) EOF - cat >> /etc/exports << EOF /ctl_plane_backups 192.168.24.0/24(rw,sync,no_root_squash,no_subtree_check) /ctl_plane_backups 10.0.0.0/24(rw,sync,no_root_squash,no_subtree_check) /ctl_plane_backups 172.16.0.0/24(rw,sync,no_root_squash,no_subtree_check) EOF- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
- Restart the NFS server: - systemctl restart nfs-server - [root@backup ~]# systemctl restart nfs-server- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
- Verify that the entries are correctly configured in the NFS server: - showmount -e `hostname` - [root@backup ~]# showmount -e `hostname`- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow