Changes

From Amahi Wiki
Jump to: navigation, search

Rsnapshot (view source)

Revision as of 03:23, 23 June 2020

9,057 bytes added ,  03:23, 23 June 2020
→‎Preparing an External USB Drive
{{NeedsUpdate}}[http://rsnapshot.org/ '''''rnapshotrsnapshot'''''] is an excellent backup application and has been around for a long time and is extremely stable.
Why are backups important? Well, hardware failures, accidental file deletion(s), files become corrupted, etc.. Backups can help recover data where applications are being updated/upgraded. Enough reasons?
__TOC__
=Quick rsnapshot Recipe== Preparing an External USB Drive ===
Here Off-the-shelf external USB drives normally are setup to work with computers that utilize CIFS type filesystems. rsnapshot uses a "hard links" feature that is unique to Linux/Unix filesystems (ext3). "Hard Links" are not supported on filesystems such as: '''"smbfs"''', '''"Samba (SMB)"''', '''"FAT"''', '''"FAT32"''', '''"NTFS"''', '''"CIFS"''', '''"vfat"'''. Please note that "Amahi Greyhole" mounts Amahi shares that will look like "local disk drives" '''''but''''' these are Samba (SMB) mounted shares. An external disk drive will have to be prepared for a quick recipe Linux/Unix filesystem, in particular ext3. Why? ext3 has been around for sometime, is stable, and "Windows" computers have Open Source drivers available that can be installed to gain access to configure rsnapshotan ext3 drive.
These are the critical settings in /etc/rsnapshot.confPrepare an external drive for ext3 as follows:
snapshot_root /mnt/1tb-* The external/snapshots/USB drive used in this example is a 1 Terabyte (1 TB) Seagate drive. interval daily 14* Plug the drive in to a USB connector and power it up. interval weekly 4* Using a "terminal" session, login in using the "root" user ID. interval monthly 4* The "device name" of the drive needs to be determined.
This will create a series of directories called daily.0 through daily.13
weekly.0 to weekly.3 ... etc.
=Another example of rsnapshot configuration on amahi 5.1=Enter the following command: dmesg
In this example automated backups are made to an external The following information is displayed:<pre>[11122.304178] usb drive2-4: new high-speed USB device number 5 using ehci_hcd[11122.422152] usb 2-4: New USB device found, idVendor=0bc2, idProduct=3320Plug in the [11122.422165] usb 2-4: New USB drivedevice strings: Mfr=2, Product=3, it will probably mount automatically under SerialNumber=1[11122.422173] usb 2-4: Product: Expansion Desk[11122.422180] usb 2-4: Manufacturer: Seagate . . . . .[11123.516813] sdb: sdb1</media/yourdisklabelpre>* The "device name" is "sdb1".* The USB drive needs to be "unmounted".
First login as root in a terminal (putty or ssh root@hda)and type umount /dev/sdb1
:mount* Format drive for ext3 filesystem and set drive label name as "usbdisk".
in the output, find which device is your usbdrive, possibly mkfs -t ext3 -v -L usbdisk /dev/sdb1
=Format usb disk=
You need to format (ext3, ext4) an external USB disk drive for rsnapshot to work. rsnapshot uses a "hard links" feature that is unique to Linux/Unix filesystems. "Hard Links" are not supported on filesystems such as: '''"smbfs"''', '''"Samba (SMB)"''', '''"FAT"''', '''"FAT32"''', '''"NTFS"''', '''"CIFS"''', '''"vfat"'''. "Amahi Greyhole" mounts Amahi shares that look like "local disk drives" '''''but''''' these are Samba (SMB) mounted shares.
:umount '''Please Note: THIS WILL ERASE ALL DATA ON /mediadev/yourdisklabel sdb1, MAKE SURE THIS IS THE CORRECT USB DRIVE AND NOT ANOTHER DRIVE.'''
The following information is displayed:mkfs <pre>mke2fs 1.42.5 (29-t Jul-2012)fs_types for mke2fs.conf resolution: 'ext3 -v -L 'Filesystem label=usbdisk OS type: Linux . . . . .Writing superblocks and filesystem accounting information: done</dev/sdb1pre>* Whenever a drive is formatted in Linux, about 5% is reserved of the total space on the drive for the operating system to continue using the hard drive to operate, even if it gets full. This is totally unnecessary for a USB external hard drive if it stores only data and not to run an operating system.
THIS WILL ERASE ALL DATA ON /dev/sdb1, MAKE SURE THIS IS YOUR USB DRIVE AND NOT ANOTHER DRIVE
=Install rsnapshot=Enter the following to remove the reserved space::yum install rsnapshot tune2fs -m 0 /dev/sdb1
The following information is displayed:mkdir -p /media/usbdisk/ tune2fs 1.private/42.snapshots5 (29-Jul-2012) Setting reserved blocks percentage to 0% (0 blocks)
:chmod 0700 /media/usbdisk/* The external drive is now ready for use.private/
:chmod 0755 /media/usbdisk/.private/.snapshots/ === Mounting an External USB Drive ===
=Mount your usbdisk permanently=To Mount your usbdisk permanently (so There are two methods of mounting an external USB drive. The first, mounts the backup will work after a reboot) do drive automatically each time the following:server "boots" or "reboots". The second, is mounted manually by the "root" user via the "command-line".
Before proceeding a couple of information items need to be gathered:cp /etc/fstab /etc/fstab_bak
:nano /etc/fstab* In the previous section the device name found found via the "dmesg" command. The device name found was "sdb1".* We set the set the external drive's "label". It was set to "usbdisk".
Add to this file
To find the label at anytime via the "root" user ID enter:LABEL=usbdisk e2label /mediadev/usbdisk ext3 defaults 0 0sdb1
Save the file.The following information is displayed: usbdisk
=Modify rsnapshot Both methods of mounting will be controlled by the server's "fstab" configuration=:nano /etc/rsnapshotfile. The fstab (a.k.a. file systems table) file is a system configuration file containing lists of available disks and disk partitions, and indicates how they are to be initialized or otherwise integrated into a system's file system. When the "mount" command is used, the fstab file is read to determine which options should be used when mounting a specified device.conf
make the following modifications to the file rsnapshot.conffor blank spaces use TABS!==== Auto-Mounting ====
:snapshot_root /media/usbdisk/Auto-mount of an external USB drive will occur when a server "boots" or "reboots".private/Provided the fstab configuration file is properly configured. A powered up USB drive that is plugged in after a server has completed the boot process is not auto-mounted. However, using a "terminal" session with the "root" user ID, and issuing a "mount -a" command will mount an external USB drive.snapshots/
Configure fstab to auto-mount an external USB drive do the following:no_create_root 1
:interval hourly 6* Start a "terminal" session login to the "root" user ID.
:interval daily 7* Navigate to the "etc" directory with the "cd" command and make a backup of the current fstab file. cd /etc cp /fstab /fstab_bak
:interval weekly * Using a preferred file editor (i.e. vi, nano), open the fstab file. 4fstab
* Near the bottom of the and after the other fstab entries, add the following:interval monthly 12
:verbose 3 LABEL=usbdisk /media/usbdisk ext3 defaults 0 0
:backup * Now save the fstab file and exit the editor.* Navigate to the /var/hda/files/docs/ localhostmedia directory and create a "usbdisk" directory. This is where the external drive will be mounted, this is called a "mount point". cd /media mkdir usbdisk
:backup * Make sure the external drive USB cable is connected to the server and is powered up.* Reboot the server.* Remember the disk label set earlier when formatting the drive? During the boot process when the "LABEL" is read, this instructs the system to find a hard disk with the label "usbdrive", and then mounts it to the mount point, "/var/hda/files/pictures/ localhostmedia/usbdisk".
:backup /var/hda/files/movies/ localhost/==== Manual Mounting ====Mount of an external USB drive will not occur when a server "boots" or "reboots" when the fstab configuration file is configured for manual mounting. A powered up USB drive that is plugged in after a server has completed the boot process is also not mounted.
Configure fstab for a manual mounting of an external USB drive with the following:backup /var/hda/files/music/ localhost/
:backup /var/hda/files/othersharesyoumade localhost/* Start a "terminal" session login as the "root" user ID.
Save * Navigate to the "etc" directory with the "cd" command and make a backup of the current fstab file. cd /etc cp /fstab /fstab_bak
:rsnapshot configtest* Using a preferred file editor (i.e. vi, nano), open the fstab file. nano fstab
this should return* Near the bottom of the and after the other fstab entries, add the following: syntax OK LABEL=usbdisk /media/usbdrive ext3 rw,noauto,users,exec,noatime 0 0
=Email reporting=* Now save the fstab file and exit the editor.* Navigate to the /media directory and create a "usbdisk" directory. This is where the external drive will be mounted, this is called a "mount point". cd /media mkdir usbdrive* Make sure the external drive USB cable is connected to the server and is powered up.* Reboot the server.* Start a "terminal" session login as the "root" user ID.* To manually mount the external drive issue the following command: mount -L usbdisk* The system reads the fstab, when it finds a line entry with the label "usbdrive", it mounts the drive the mount point, "/media/usbdisk".
for email reporting on your backups:==== Unmounting ====
With both mounting methods the external drive can be unmounted by the following:cp /usr/share/doc/rsnapshot*/utils/rsnapreport.pl /root
* Start a "terminal" session login as the "root" user ID.* Issue the following command to unmount the external drive:chmod 744 rsnapreport umount /media/usbdrive* Should an error occur indicating that the drive is busy and cannot be unmounted enter the command below. Then try the unmount command again.pl fuser -km /media
=Automate backup with cronjob==Installing rsnapshot===rsnapshot is available as a package in both the Fedora and Ubuntu Linux distributions. The installation shown here is based on Fedora.
* Open a "terminal" session and login using the "root" user ID:crontab -l > cronjobs
:nano cronjobs yum install rsnapshot
add to this file * Now create the directory structures for running rsnapshot and a weekly email report on rsnapshotstoring the backups:
:0 * mkdir -p /4 * * * media/usrusbdisk/bin.private/rsnapshot hourly 2>&1 | .snapshots chmod 0700 /rootmedia/usbdisk/rsnapreport.pl > private/root chmod 0755 /media/usbdisk/.private/.snapshots/rsnapreport
:30 23 * * * /usr/bin/=== Configuring rsnapshot daily===This section shows how to configure the rsnapshot.conf configuration file.
:00 23 * * 1 /usr/bin/rsnapshot weeklyOpen a "terminal" session and login to the "root" user ID.
:30 22 1 * * /usr/binMove to the "/rsnapshot monthlyetc" directory.
:00 22 * * 6 cd /usr/bin/rsnapshot du >> /root/rsnapreport | nail –r "somereturnadress@provider.com" -s"HDA backup report" -S smtp=smtp.yourprovider.com youremail@provider.com < /root/rsnapreportetc
Save * Make a backup copy of the rsnapshot configuration file. Why? So that there is a reference just in case.
:crontab cronjobs cp rsnapshot.conf rsnapshot.conf.bkup
Rsnapshot should now be operational* Now using a favourite editor, open the "rnapshot.conf" file.<br/>'''Please Note:''' Items in the configuration file are separated by "tab" characters and NOT multiple spaces. nano rsnapshot.conf
* Find the "SNAPSHOT ROOT DIRECTORY" section and change "snapshot_root" to path where the backups will be stored.   snapshot_root /media/usbdisk/.private/.snapshots/}} * Find the "no_create_root" section and remove the "#". This will allow rsnapshot to create the "snapshot root" directory.  no_create_root 1 * Find the "BACKUP INTERVALS" section and change the line items. What does this all mean? The "#" character at the beginning of each line means the configuration line item will not be enabled. Remove the "#" character as required. For example, when enabled the "interval daily" line will be active and 7 days of backups will be kept.  interval hourly 6 interval daily 7 interval weekly 4 interval monthly 12 * Find the "GLOBAL OPTIONS" section. This section defines how much information will be saved in the rsnapshot "log" file. The options are: Verbose level, 1 through 5. 1 Quiet Print fatal errors only 2 Default Print errors and warnings only 3 Verbose Show equivalent shell commands being executed 4 Extra Verbose Show extra verbose information 5 Debug mode EverythingChange the following options as required: verbose 3 loglevel 3 * Find the "logfile" line and change the line item. After rsnapshot has completed backups this is where the resulting "log" file is stored. Change this line as required.  logfile /var/log/rsnapshot}} * Find the "BACKUP POINTS / SCRIPTS" section. Add changes as seen below. This is the section that defines the "key directories" that will be backed up. Please note the "localhost/", this represents the server that it being backed up. "localhost/" is a default name given to the current server. Change this name as required, say "amahiBox/"?  backup /var/hda/files/docs/ localhost/ backup /var/hda/files/pictures/ localhost/ backup /var/hda/files/movies/ localhost/ backup /var/hda/files/music/ localhost/ backup /var/hda/files/other_shares_you_made localhost/ * Save the "rsnapshot.conf" file. === Test the Configuration Changes ===* Now the changes to the rsnapshot configuration file have to be tested. rsnapshot has a feature to test changes to make sure things have been setup correctly. * Enter the following on the command-line to initiate the test.  rsnapshot configtest}} * When the test completes the following should be displayed:  Syntax OK * If an error occurs the rsnapshot configuration file will need to be checked. ===Automate Backups ===Backups can be automated by creating a "cron job" that can be executed by the system at predetermined intervals. * Using a "terminal" session and "root" user ID a "cron job" configuration can be created to perform automated backups.Create a "cronjobs" text file as follows: crontab -l > cronjobs * Using a favourite text editor open the cronjobs file.  nano cronjobs * Add to the cronjobs file for rsnapshot:   0 */4 * * * /usr/bin/rsnapshot hourly 30 23 * * * /usr/bin/rsnapshot daily 00 23 * * 1 /usr/bin/rsnapshot weekly 30 22 1 * * /usr/bin/rsnapshot monthly * Save the cronjobs file.* Now update the "root" user IDs "crontab" with the following:  crontab cronjobs}} * Reboot the server and rsnapshot will be operational. ===Email reporting===* To email a report of backups:  cp /usr/share/doc/rsnapshot*/utils/rsnapreport.pl /root chmod 744 rsnapreport.pl'''*''' above indicates an rsnapshot version number  * Add the following to crontab for a weekly email report on rsnapshot: <pre style="white-space: pre-wrap; word-break: keep-all;">0 */4 * * * /usr/bin/rsnapshot hourly 2>&1 | /root/rsnapreport.pl > /root/rsnapreport00 22 * * 6 /usr/bin/rsnapshot du >> /root/rsnapreport | nail –r "somereturnadress@provider.com" -s"HDA backup report" -S smtp=smtp.yourprovider.com youremail@provider.com < /root/rsnapreport</pre> '''Please Note:''' The above information maybe out of date due to technology changes. Please feel to update as required. ===Make your backups available on clients (READ ONLY)===
If you want to make the backups accesible from your clients:
Create a //hda/backup share in the HDA webinterface
: chkconfig nfs --level 2345 on
add a read only NFS export:
: nano /etc/exports
add
: /media/usbdisk/.private/.snapshots/ 127.0.0.1(ro,no_root_squash)
Save file
Unfortunately mounting an NFS share in fstab did not work on my machine after a reboot, so I chose an alternative configuration that mounts the share later in the booting process:
: nano /etc/rc.local
Add
: mount -r -t nfs localhost:/media/usbdisk/.private/.snapshots/ /var/hda/files/backup/
save file
[[Category: Apps]]
Bigfoot65
Trusted, Bureaucrats, Administrators
12,424

edits

Retrieved from "https://wiki.amahi.org/index.php/Special:MobileDiff/68924...114831"