eRCaGuy_backup

Easily back up your files on any Linux system via an rsync wrapper, dry-runs, include & exclude files, and nice logging.

Status: done and works!

Usage

TODO; start by looking at the comments at the top of back_up_linux_pc.sh.

Build and install the latest version of rsync

...to ensure you have the latest updates & bug fixes.

See the official rsync installation instructions on the official rsync repo by the current primary maintainer on GitHub here: https://github.com/WayneD/rsync/blob/master/INSTALL.md

Tested on Ubuntu 20.04 on 19 Feb. 2023.

# install dependencies
# - Use `aptitude` to fix any which fail to install.
sudo apt update
sudo apt install -y gcc g++ gawk autoconf automake python3-cmarkgfm
sudo apt install -y acl libacl1-dev
sudo apt install -y attr libattr1-dev
sudo apt install -y libxxhash-dev
sudo aptitude install libzstd-dev  # choose the correct options to get it fixed and installed
sudo apt install -y libzstd-dev
sudo aptitude install liblz4-dev # choose N, Y, Y
sudo apt install -y liblz4-dev
sudo apt install -y libssl-dev

# check your current version
rsync --version

# go here and find the latest release: https://download.samba.org/pub/rsync/src/
# OR here, on the official GitHub release page: https://github.com/WayneD/rsync/tags

URL="https://download.samba.org/pub/rsync/src/rsync-3.2.7.tar.gz"
# download it
wget "$URL"
# extract it
tar -xf rsync-3.2.7.tar.gz

# build and install it
cd rsync-3.2.7
time ./configure  # Ensure it says "rsync 3.2.7 configuration successful" at the end
time make
sudo make install
. ~/.profile  # re-source bash config files

# check new version
rsync --version

`rsync` notes

tee doesn't seem to be able to log to a remote ssh host, so log locally instead, then manually rsync the log over when done.
If rsyncing over ssh, ensure that both computers have the same exact version of rsync, or else you may get weird errors. Ex: If you have the following error, try forcing the sender rsync version to match the receiver rsync version. My receiver (Ubuntu 18.04 at the time) rsync --version was "rsync version 3.1.2 protocol version 31", whereas my sender (an older version of Ubuntu) rsync --version was "rsync version 3.1.0 protocol version 31".

Here's the error from the sender's side:
```
path/to/some/file
         10.20G  20%  600.01MB/s    0:05:22  
rsync: [sender] write error: Broken pipe (32)
rsync error: error in rsync protocol data stream (code 12) at io.c(837) [sender=3.1.0]
```
Google search for "ubuntu 14.04 install rsync 3.1.2"

Upgrading to rsync 3.1.2 on the sender seemed to have fixed the problem. I followed these instructions: http://www.beginninglinux.com/home/backup/compile-rsync-from-source-on-ubuntu. In short (paraphrased or copied from their instructions):
1. Download the source code from rsync official website: https://download.samba.org/pub/rsync/src/
2. Unzip the source file and change to that directory, make sure not to use -z option:
```
tar -xf rsync-3.1.1.tar.gz 
cd rsync-3.1.1
```
3. Build
```
./configure
make
sudo checkinstall
```
4. Check new version
```
rsync --version
```
Note: When compiling, you may use ./configure --help | less to show options. For example, the installation location may be chosen. In this case I did not choose to enter any options, so I used the regular ./configure.

With command sudo checkinstall, the default options were chosen by pressing Enter. At the first run of checkinstall you may be asked to enter EOF. Press Ctrl + D. sudo checkinstall will create a .deb file and makes removal of the installed package easy. At the end of the process, it will even give you the command to uninstall the package, and it will tell you the location of the .deb file. So, I recommend using sudo checkinstall instead of the more-common sudo make install.
More research notes:

rsync 3.1.0 and 3.0.9 incompatibility

rsync error: error in rsync protocol data stream (code 12) at io.c(441) [sender=3.0.9]

Solutions:
1. Don't use compression (-z, --compress)
2. Use ssh compression as shown below instead of rsync's compression! Source: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1300367:
  
  Simply move compression from rsync to ssh: -a -e "ssh -C"
[NEED TO STUDY & READ] How to interpret the symbols and meaning in rsync logs: What does f+++++++++ mean in rsync logs?

TODO

See TODO.md.

Example `rsync` runs and cmds

You can extract the main rsync run cmds using set -x in your script, just before the place where you want your cmd to be printed. It will be printed with a + symbol just before it.

Here are some example commands I extracted, modified, and manually ran during testing:

works

sudo rsync --dry-run --dry-run -rah -v --stats --relative --delete --delete-excluded --partial-dir=.rsync-partial --files-from /home/gabriel/.back_up_linux_pc.files_to_include.txt --exclude-from /home/gabriel/.back_up_linux_pc.files_to_exclude.txt / /media/gabriel/Linux_bak/Backups/rsync/Main_Dell_laptop
works great with logging!

sudo rsync --dry-run --dry-run -rah -v --stats --relative --delete --delete-excluded --partial-dir=.rsync-partial --files-from /home/gabriel/.back_up_linux_pc.files_to_include.txt --exclude-from /home/gabriel/.back_up_linux_pc.files_to_exclude.txt --log-file ~/rsync_logs/rsync.log / /media/gabriel/Linux_bak/Backups/rsync/Main_Dell_laptop
works perfectly as well, with logging to a log-file and with total progress via --info=progress2. Note that progress data (repetitive, % complete statements) is not logged, which is nice so that it does not clog up the logs!

See my modifications to this answer here: https://superuser.com/a/1002097/425838:
Use the --log-file option. See man rsync for details. Example usage:
```
rsync -av /source/ /dest/ --log-file=mylog.log
```
Note that successive runs will append to the log file, rather than overwriting it. Also, rsync logs both stderr and stdout type information to the specified log file.
sudo rsync --dry-run --dry-run -rah -v --stats --relative --delete --delete-excluded --partial-dir=.rsync-partial --files-from /home/gabriel/.back_up_linux_pc.files_to_include.txt --exclude-from /home/gabriel/.back_up_linux_pc.files_to_exclude.txt --log-file ~/rsync_logs/rsync2.log --info=progress2 / /media/gabriel/Linux_bak/Backups/rsync/Main_Dell_laptop
[Best so far] Works! Log stderr to its own file as well, to quickly see if any errors occurred during the sync.

Meaning of 3>&1 1>&2 2>&3: it swaps stderr and stdout: https://unix.stackexchange.com/a/42776/114401

sudo rsync --dry-run --dry-run -rah -v --stats --relative --delete --delete-excluded --partial-dir=.rsync-partial --files-from /home/gabriel/.back_up_linux_pc.files_to_include.txt --exclude-from /home/gabriel/.back_up_linux_pc.files_to_exclude.txt --log-file ~/rsync_logs/rsync2.log --info=progress2 / /media/gabriel/Linux_bak/Backups/rsync/Main_Dell_laptop 3>&1 1>&2 2>&3 | tee -a ~/rsync_logs/stderr.log

ElectricRCAircraftGuy/eRCaGuy_backup