Difference between revisions of "hidden:Backup with Relax-and-Recover"

From Lsdf
Line 1: Line 1:
 
IBM,Jonathan had installed Relax-and-Recover an all HPSS machines but it has been configured only on HPSS Test Core and HPSS Test Mover
 
IBM,Jonathan had installed Relax-and-Recover an all HPSS machines but it has been configured only on HPSS Test Core and HPSS Test Mover
  +
[root@hpsstmvr etc]# /usr/sbin/rear -V
  +
Relax-and-Recover 1.17.1 / Git
  +
This version is not in the git repository any longer
  +
Installed by IBM, Jonathan
  +
I let this version because it is the version we already made a recovery from.
  +
'''Should we replace it?'''
  +
 
Dorin deployed it on all HPSS machines and installed and configured it on all front end machines on 11.07.2016
 
Dorin deployed it on all HPSS machines and installed and configured it on all front end machines on 11.07.2016
Dorin changed the mount point for raer backups
+
Dorin changed the mount point for ReaR backups
 
from
 
from
 
nfs://lsmb02.lsdf.kit.edu/gpfs/nfsshares/scc/hpss/rear/
 
nfs://lsmb02.lsdf.kit.edu/gpfs/nfsshares/scc/hpss/rear/
Line 7: Line 14:
 
nfs://hpa.lsdf.kit.edu/export/hpa/ReaR_Backups/
 
nfs://hpa.lsdf.kit.edu/export/hpa/ReaR_Backups/
 
Reasons:
 
Reasons:
since the hpss mover 4 has no 141. IP it is not able to mount the gpfs file system
+
since the hpss mover 4 has no IP network 141 it is not able to mount the gpfs file system
rear makes every day an bare metal backup and keeps only one version on the mounted nfs file system
+
ReaR makes every day an bare metal backup and keeps only one version on the mounted nfs file system
a TSM backup will be configured for hpa and the "rear backups" will be archived in tsm so that more versions will be keeped
+
a TSM backup will be configured for hpa and the "rear backups" will be archived in tsm so that more versions will be kept
  +
  +
'''On all machines'''
  +
ReaR mounts the nfs file system at the running time on /mnt/ba_os_image/
  +
ReaR configuration file /etc/rear/local.conf
  +
Rear log: /var/log/rear/rear-HOSTNAME.log
  +
ReaR default configuration file: /usr/share/rear/conf/default.conf
  +
'''IMPORTANT'''
  +
According to relax-and-recover documentation (see /usr/share/rear/conf/default.conf)
  +
# Exclude LVM2 volume groups. This will automatically exclude also the creation of the corresponding
  +
# physical and logical volumes that belong to the excluded volume group.
  +
#
  +
# NOTE: YOU MUST ALSO EXCLUDE THE CORRESPONDING MOUNTPOINTS IN EXCLUDE_MOUNTPOINTS (see above)
  +
# OTHERWISE THE RECOVERY ***WILL*** TRY TO RECREATE THE FILESYSTEMS ONTO NON-EXISTING LVs
  +
#
  +
# Y O U H A V E B E E N W A R N E D ! !
  +
EXCLUDE_VG=()
 
 
   

Revision as of 15:25, 11 July 2016

IBM,Jonathan had installed Relax-and-Recover an all HPSS machines but it has been configured only on HPSS Test Core and HPSS Test Mover
[root@hpsstmvr etc]# /usr/sbin/rear -V
Relax-and-Recover 1.17.1 / Git
This version is not in the git repository any longer
Installed by IBM, Jonathan 
I let this version because it is the version we already made a recovery from.
Should we replace it?
Dorin deployed it on all HPSS machines and installed and configured it on all front end machines on 11.07.2016
Dorin changed the mount point for ReaR backups 
from 
nfs://lsmb02.lsdf.kit.edu/gpfs/nfsshares/scc/hpss/rear/ 
to
nfs://hpa.lsdf.kit.edu/export/hpa/ReaR_Backups/
Reasons:
since the hpss mover 4 has no IP network 141 it is not able to mount the gpfs file system
ReaR makes every day an bare metal backup and keeps only one version on the mounted nfs file system
a TSM backup will be configured for hpa and the "rear backups" will be archived in tsm so that more versions will be kept 
On all machines
ReaR mounts the nfs file system at the running time on /mnt/ba_os_image/
ReaR configuration file /etc/rear/local.conf
Rear log: /var/log/rear/rear-HOSTNAME.log
ReaR default configuration file: /usr/share/rear/conf/default.conf
IMPORTANT
According to relax-and-recover documentation (see /usr/share/rear/conf/default.conf)
# Exclude LVM2 volume groups. This will automatically exclude also the creation of the corresponding
# physical and logical volumes that belong to the excluded volume group.
#
# NOTE: YOU MUST ALSO EXCLUDE THE CORRESPONDING MOUNTPOINTS IN EXCLUDE_MOUNTPOINTS (see above)
#       OTHERWISE THE RECOVERY ***WILL*** TRY TO RECREATE THE FILESYSTEMS ONTO NON-EXISTING LVs
#
#       Y O U   H A V E   B E E N   W A R N E D  ! ! 
EXCLUDE_VG=()

1. Backup with Relax-and-recover a HPSS Mover