__ __ __ __ _____ _ _ _____ _ _ _ | \/ | \ \ / / | __ \ (_) | | / ____| | | | | | \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | | | |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | | | | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | | |_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1 if you need WebShell for Seo everyday contact me on Telegram Telegram Address : @jackleetFor_More_Tools:
# Begin example setup for SLE12-SP1 with default btrfs subvolumes.
# On SLE12-SP1 what is mounted at '/' is a btrfs snapshot subvolume
# see https://github.com/rear/rear/issues/556
# You must adapt "your.NFS.server.IP/path/to/your/rear/backup" at BACKUP_URL.
# You must decide whether or not you want to have /home/* in the backup.
# It depends on the size of your harddisk whether or not /home is by default
# a btrfs subvolume or a separated xfs filesystem on a separated partition.
# You may activate SSH_ROOT_PASSWORD and adapt the 'password_on_the_rear_recovery_system'.
# For basic information see the SLE12-SP1 manuals.
# Also see the support database article "SDB:Disaster Recovery"
# at http://en.opensuse.org/SDB:Disaster_Recovery
# In particular note:
# There is no such thing as a disaster recovery solution that "just works".
# Regarding btrfs snapshots:
# Recovery of btrfs snapshot subvolumes is not possible.
# Only recovery of "normal" btrfs subvolumes is possible.
# On SLE12-SP1 the only exception is the btrfs snapshot subvolume
# that is mounted at '/' but that one is not recreated but instead
# it is created anew from scratch during the recovery installation with the
# default first btrfs snapper snapshot subvolume path "@/.snapshots/1/snapshot"
# by the SUSE tool "installation-helper --step 1" (cf. below).
# Other snapshots like "@/.snapshots/234/snapshot" are not recreated.
# Create the ReaR recovery system as ISO image:
OUTPUT=ISO
# Store the backup file via NFS on a NFS server:
BACKUP=NETFS
# BACKUP_OPTIONS variable contains the NFS mount options and
# with 'mount -o nolock' no rpc.statd (plus rpcbind) are needed:
BACKUP_OPTIONS="nfsvers=3,nolock"
# If the NFS server is not an IP address but a hostname,
# DNS must work in the ReaR recovery system when the backup is restored.
BACKUP_URL=nfs://your.NFS.server.IP/path/to/your/rear/backup
# Keep an older copy of the backup in a HOSTNAME.old directory
# provided there is no '.lockfile' in the HOSTNAME directory:
NETFS_KEEP_OLD_BACKUP_COPY=yes
# Have all modules of the original system in the recovery system with the
# same module loading ordering as in the original system by using the output of
# lsmod | tail -n +2 | cut -d ' ' -f 1 | tac | tr -s '[:space:]' ' '
# as value for MODULES_LOAD (cf. https://github.com/rear/rear/issues/626):
#MODULES_LOAD=( )
# On SLE12-SP1 with default btrfs subvolumes what is mounted at '/' is a btrfs snapshot subvolume
# that is controlled by snapper so that snapper is needed in the recovery system.
# In SLE12-SP1 some btrfs subvolume directories (/var/lib/pgsql /var/lib/libvirt/images /var/lib/mariadb)
# have the "no copy on write (C)" file attribute set so that chattr is required in the recovery system
# and accordingly also lsattr is useful to have in the recovery system (but not strictly required):
REQUIRED_PROGS+=( snapper chattr )
PROGS+=( lsattr )
# Snapper setup by the recovery system uses /usr/lib/snapper/installation-helper
# that is linked to all libraries where snapper is linked to
# (except libdbus that is only needed by snapper).
# "installation-helper --step 1" creates a snapper config based on /etc/snapper/config-templates/default
COPY_AS_IS+=( /usr/lib/snapper/installation-helper /etc/snapper/config-templates/default )
# Files in btrfs subvolumes are excluded by 'tar --one-file-system'
# so that such files must be explicitly included to be in the backup.
# Files in the following SLE12-SP1 default btrfs subvolumes are
# in the below example not included to be in the backup
# /.snapshots /var/crash
# but files in /home are included to be in the backup.
# You may use a command like
# findmnt -n -r -o TARGET -t btrfs | grep -v '^/$' | grep -Ev 'snapshots|crash'
# to generate the values:
BACKUP_PROG_INCLUDE=( /var/tmp /srv /var/lib/pgsql /var/spool /var/lib/libvirt/images /var/opt/ /tmp /var/lib/named /var/log /boot/grub2/i386 /var/lib/mariadb /home /var/lib/mailman /opt /usr/local /boot/grub2/x86_64 )
# Set a root password for the ReaR recovery system in a confidential way
# to allow SSH connection without a public/private key pair.
# Never use your original root password here:
#{ SSH_ROOT_PASSWORD='password_on_the_rear_recovery_system' ; } 2>>/dev/$SECRET_OUTPUT_DEV
# Let the ReaR recovery system run dhclient to get an IP address
# instead of using the same IP address as the original system:
#USE_DHCLIENT="yes"
# End example setup for SLE12-SP1 with default btrfs subvolumes.
| Name | Type | Size | Permission | Actions |
|---|---|---|---|---|
| PXE-booting-example-with-URL-style.conf | File | 1020 B | 0644 |
|
| RHEL6-NETFS-of-NBU-master-example.conf | File | 838 B | 0644 |
|
| RHEL7-ISO-Oracle-example.conf | File | 2.77 KB | 0644 |
|
| RHEL7-PPC64LE-Multipath-PXE-GRUB.conf | File | 2.07 KB | 0644 |
|
| SLE11-SLE12-SAP-HANA-UEFI-example.conf | File | 3.02 KB | 0644 |
|
| SLE11-ext3-example.conf | File | 1.56 KB | 0644 |
|
| SLE12-SP1-btrfs-example.conf | File | 4.36 KB | 0644 |
|
| SLE12-SP2-btrfs-example.conf | File | 5.02 KB | 0644 |
|
| SLE12-btrfs-example.conf | File | 2.81 KB | 0644 |
|
| USB-and-Samba-example.conf | File | 755 B | 0644 |
|
| borg-example.conf | File | 912 B | 0644 |
|
| rescue-and-backup-on-same-ISO-image-example.conf | File | 481 B | 0644 |
|