cleverwise/cya

Easy to use snapshot and restore utility for any Linux (Unix) OS and filesystem powered by BASH

CYA .:. Cover Your Ass(ets)

This open source and freely available tool is written to run in the BASH shell and allows for easy snapshots and rollbacks of your Linux (any flavor) or other *nix operating system. It is filesystem agnostic (EXT2/3/4, XFS, UFS, GPFS, reiserFS, JFS, BtrFS, ZFS), easy to remove, and is portable. Plus, obviously, you are free to verify all the code. The core system backups and restores the operating system itself and not your actual user data. However user data backup is now supported!

The underlying backup method is actually rsync - a well known and vetted system. However CYA makes it super simple to create rolling backups. This is because with a single command it will copy all key directories like /bin/ /lib/ /usr/ /var/ and several others. You are even free to add your own unique directories and files into the configuration so CYA will pick those up as well. It is also possible to configure the system to skip subdirectories so if you don't want /var/logs/ backed up with the /var/ directory no problem.

When it comes time to restore CYA will rollback your operating system using the backup profile you specify. This undoes the damage caused by bad updates, configuration changes, intrusions/hacks, etc! These files are stored so you may easily access them even without a complete rollback using your terminal or file manager. This way if you change a configuration file you may manually restore that single file without having to restore the whole system.

However CYA does allow for partial restores, for example just a single directory. You are also able to generate a custom recovery script to automate the mounting of your system partition(s) when you restore off a live CD, USB, or network image.

There are many other features such as the system will keep three separate copies, which is configurable. So that way you have multiple restore points. Then on the fourth snapshot it will overwrite the first, on the fifth it will overwrite the second, etc. As stated the number is configurable. You may also create long term backups that are kept until you delete them. An archiving function is also included in this powerful utility.

CYA even supports mixing all three methods at the same time: rotating, manual, and archiving. However best of all these processes may be automated with crontab, anacron, systemd, etc. It is even super easy to call CYA from other scripts and processes!

Version 2.0 and above is now able to backup user data via the mydata command!

More information: https://www.cyberws.com/bash/cya/

Need help using CYA? Youtube Instruction Videos

---

Updates

• Follow this page
• Follow on Youtube
• Follow on Facebook

Contribute/Contact

If contacting for technical support please see video manuals first. I'll do my best to help troubleshoot but can't make any promises due to limited time.

Contributors please see the "Contributors Readme" for important information.

• Message through Github
• Contact Form on CyberWS

Installing

This is a very easy utility to install. You simply need to put the file cya on your system and turn on executable permissions like chmod 700 or 755. It is suggested you place the file in either /home/YOUR_USER/bin/ or /usr/local/bin/ depending on who you want using this program. Once that step has been done simply run the command from the commandline.

To bring up a list of commands:

shell> cya help

If you are on Linux you should run the following command:

shell> cya script

Now copy the resulting recovery.sh to a USB stick. This will aid you in mounting your drive(s) and setting up a chrooted environment so your system is ready to accept a rollback. Otherwise you can do this manually (see the Recovery section below).

Storing Data

CYA stores all backups and configuration data in /home/cya/ with backups stored in /home/cya/points/BACKUP_NAME. If you wish to alter the system edit the configuration file at /home/cya/cya.conf

Removing

What? You want to remove CYA? Why!? :-(

1. Stop any backup processes then disable and remove systemd units, crontab entries, or anacron entries.
2. Remove the cya file itself; where ever you installed it. If necessary use whereis or find commands to locate the file.
3. Finally delete the directory /home/cya/
4. Done. Now reinstall it right? ;-)

Note: If you performed a restore using cya then in your root file system you'll find CYA_LOG file which contains date and time along with directories restored. Also don't forget the BASH auto complete file if you installed it.

Generating Snapshots/Backups

There are multiple methods that may be issued from the commandline or called from automated sources like systemd, cron, or anacron.

1. For standard rolling backups that keeps three snapshots before overwriting simply use the command:

shell> cya save

2. For custom profile names you three methods/commands:

A) To provide a custom name for a backup that will NOT be overwritten:

shell> cya keep

Script friendly version:

shell> cya keep name BACKUP_NAME

If you use this method the BACKUP_NAME must be unique each time you run the script. So using this method in a script attach a time stamp or random string.

B) To provide a custom name for a backup that WILL overwrite:

shell> cya keep name BACKUP_NAME overwrite

Note the overwrite flag, which tells cya it is okay to overwrite files in the backup profile. This method IS script safe as it will overwrite data.

C) To backup and archive which will tar and gzip then move file to /home/cya/archives directory use the archive tag

shell> cya keep name BACKUP_NAME archive

This method IS script safe as a unix timestamp will be added to make unique filenames. Also note this option will remove the backup profile directory and backup will NOT appear in the back up list.

Backing User Data

Version 2.0 introduced the ability to backup user data along with system files. This is done using the mydata command and uses profiles set in the cya.conf file.

You set MYDATA underscore profile name (case sensitive and unique) then between quotes the source directory (what to backup) space then destination directory (where to backup). Both source and destination directories should end with a trailing slash.

Example:

Let's say we want to backup /home/john/ to /mnt/wd-passport/john/ with a profile name of johnfiles

MYDATA_johnfiles="/home/john/ /mnt/wd-passport/john/"

Now to actually backup /home/john/ you need to enter johnfiles (the profile name, which is case sensitive) with the cya mydata command:

shell> cya mydata johnfiles

This will cause CYA to backup the /home/john/ directory. If you run the command again CYA will update the destination directory. So you simply issue the same command when a backup update is desired.

You may also use the same source directory for multiple backup destinations. This is useful if you want to backup a directory to multiple drives. Also you may backup to any directory (drive) that is mounted so internal drives, external USB (hdd, ssd, flash), NAS, cloud, etc are all acceptable. If desired you may even crontab, anacron, or systemd backup(s) to always connected destinations.

To specify additional backups simply add more entries with one per line. Do remember to use unique profile names!

Examples:

MYDATA_johnwd="/home/john/ /mnt/wd-passport/john/"

MYDATA_johnnas="/home/john/ /nas/john/"

MYDATA_maryfiles="/home/mary/ /mnt/wd-passport/mary/"

You can exclude paths from these MYDATA paths using this format:

EXCLUDE_/home/john/=".config/openstack/ Downloads/"

Recovery

If you find your system in a situation where things aren't right then it is time to restore it. Now should you have a known single file issue it would be faster to restore that single file, however you will need to watch out for ownership and permissions. Thus the cp command may or may not be enough depending on the situation.

Still if you have a more major issue or you aren't sure of the trouble then a full rollback is in order.

You may do this totally manually or if on Linux use the recovery.sh file assuming you created one. You see for best success you really should do the recovery in a live environment booted from a disc, USB, or network image. Why? Because you'll need to overwrite running files that are locked. So ideally these files should NOT be loaded and in use thus the need for a live environment.

Notice: For best results use a live boot environment from same major version as your installed environment! It has been discovered that mixing versions can cause issues. For example your installed system is 16.04 and you use a 17.10 boot image. While it might seem like it shouldn't matter it does at times. So if on 16.04 use a 16.04 boot image.

1. Boot off a live image on disc, USB, or network.
2. Mount your drive(s) so your system's / and /home are mounted to the /mnt/cya directory. This is made really easy and handled automatically by the recovery.sh script for Linux users. If you wish to do this manually see "Setting Up Restore Environment Manually" below.
3. Now run sudo /mnt/cya/home/cya/cya restore and follow the onscreen instructions. This will be done automatically when using the recovery.sh script.
4. Once files have been restored restart your system along with ejecting any images so your system boots off the recovered installed OS.
5. Done. You should now be in your recovered operating system. Now don't forget to run any necessary updates (unless updating was the issue and you need to do some research).

Setting Up Restore Environment Manually

1. Boot off a live image on disc, USB, or network.
2. At the command prompt create the /mnt/cya directory to be used to mount your drive(s). shell> sudo mkdir -p /mnt/cya
3. Now you need to mount your / and /home (if on another partition) into the /mnt/cya point. Below are ONLY examples: shell> sudo mount /dev/sda1 /mnt/cya
   shell> sudo mount /dev/sda3 /mnt/cya/home
4. Now execute the restore command to start the process
   shell> sudo /mnt/cya/home/cya/cya restore

BASH Autocomplete

This project includes a BASH autocomplete script. Once installed this means hitting tab after typing in the cya command will show available options and even completes them.

For example type in the following omitting enter then hit tab a few times:

shell> cya

Now type in the following omitting enter then hit tab:

shell> cya l

This only works when you have installed the bash-completion package (which some distros include) AND the cya-completion file.

Steps:

1. First make sure the bash-completion package is installed on your system. You may run a test by typing in "ls" then hitting tab a few times. If you see a list of available commands you have this package. If not you need to install it.

Installing bash-completion:

A) Debian systems (Ubuntu, Mint, etc):

shell> sudo apt-get install bash-completion

B) Red Hat systems (RHEL, CentOS, Fedora):

shell> sudo yum install bash-completion

or

shell> sudo dnf install bash-completion

2. Now you need to copy the cya_completion file to /etc/bash_completion.d/

You'll need to use sudo. For example let's say you have the file in your Downloads directory:

shell> sudo cp ~/Downloads/cya-master/cya_completion /etc/bash_completion.d/

3. Finally BASH needs to reload the files in order to pick up the modifications. There are multiple ways to accomplish this which include closing the terminal and reopening it or logging out and back in. However you can skip those and simply issue the following command:

shell> source ~/.bashrc

Customizing

Adding Directories

1. Open the following file in your text editor /home/cya/cya.conf
2. Add or edit the following variable

BACKUP_DIRECTORIES=""

Now between the quotes add the directories separated by a space. Note: If a directory contains a space use backslashblackslash or \ before the space.

Example:

BACKUP_DIRECTORIES="/tmp/ /important/ /myfiles/configuration/"

or

BACKUP_DIRECTORIES="/my\ directory\ with\ spaces/"

3. Once completed save and close file. You may verify by running the following command:

shell> cya directories

Exclude Subdirectories And/Or Files

1. Open the following file in your text editor /home/cya/cya.conf
2. Now simply type EXCLUDE (all uppercase) then underscore then parent directory with slashes and between quotes add children directories separated by a space. IMPORTANT: Subdirectories should NOT include the parent directory. NO FORWARD SLASHES FOR CHILDREN DIRECTORIES!

Example:

Let's say we want to exclude /var/tmp/ and /var/logs/ and /var/log/syslog (a file) which are inside /var/, obviously

EXCLUDE_/var/="tmp/ logs/ log/syslog"

You simply repeat for additional directories with EXCLUDE_/dir/ one per line. Note: If a directory contains a space use blashslash or \ before space in EXCLUDE and use backslashblackslash or \ before the space when working between the quotes.

Example:

EXCLUDE_/etc/="logs/ conf/"
EXCLUDE_/var/="tmp/ logs/" EXCLUDE_/var/="my\ directory\ with\ spaces/" EXCLUDE_/custom\ directory\ spaces/="logs/"

3. Once completed save and close file.

Add specific files to include in backup:

You are able to backup specific files instead of whole directories. You should keep in mind this is only necessary for directories not included in the backup. Also files will be stored in a subdirectory called "cya-backup-files" inside the backup profile directory.

1. Open the following file in your text editor /home/cya/cya.conf
2. Add or edit the following variable:

BACKUP_FILES=""

Now between the quotes add the full path to files separated by a space.

Example:

BACKUP_FILES="/custom/my_log /custom/sudir/config /app2/config/settings"

Alter number of rotation backups:

The default number of backups before rotating when using "cya save" is three (3). However you may wish to change this number. This is very easy.

1. Open the following file in your text editor /home/cya/cya.conf
2. Add or edit the following variable while placing the new number between quotes.

Example:

Let's say you want to alter this number to six (6) backups.

MAX_SAVES="6"

Note: If you reduce the number higher profiles will NOT be removed. So if you go from ten (10) to five (5) cya will start rotating at five (5) but backups six to ten will remain unless you remove them.

Removing/Altering Default Top Level Backup Directories

CYA is designed to backup core top level directories like /bin/, /boot/, /var/, etc. You may get a list of these directories by running the directories command.

shell> cya directories

However you may desire to alter the default list. This is easy to do using the OVERRIDE_BACKUP_DIRECTORIES variable in cya.conf located in the /home/cya/ directory. Now when using this variable it should be noted ALL default entries will be cleared. Thus you need to build your own list.

Example:

1. Open the following file in your text editor /home/cya/cya.conf
2. Add or edit the following variable:

OVERRIDE_BACKUP_DIRECTORIES="/boot/ /etc/ /var/"

It should be noted that when you use this variable you may specify custom backup directories here. However using the BACKUP_DIRECTORIES variable still works.

Disable Disclaimer

1. Open the following file in your text editor /home/cya/cya.conf
2. Add the following variable on its own line: DISCLAIMER="off"
3. Once completed save and close file.

Changing Name Of A Backup Profile

If you wish to rename a backup profile simply alter the name of the directory/folder in /home/cya/points/ to the desired name. That's it. However if you have scheduled tasks that call the backup profile then you'll need to edit your command call to the new name.

Scheduling

Wrapper

You'll find a wrapper file in the wrapper directory. This is provided just in case your environment requires such a file. You see some setups will allow you to execute CYA directly from a scheduler. Others however will fail because they start in a SH environment and don't want to switch to BASH.

Therefore if your system doesn't like calling CYA directly then use the wrapper script to call CYA and use your scheduled method: SystemD, cron, anacron, etc to call the wrapper script.

SystemD

In this project is a systemd directory which contains two files to get CYA working with systemd. If necessary use the wrapper file!

1. cya.service = This sets up the service for systemd. You'll need to edit this file to change the path to where you installed the CYA program. Plus if you want to use the manual backup method you'll need to alter the command path.

Look for the following line to modify:

ExecStart=/home/USER/bin/cya save

2. cya.timer = This sets up the time systemd runs CYA. The file included will run a backup once a week. This may or may not be enough for your situation. If a week works for you then no need to change this file.

If you want something other than week modify:

OnCalendar=weekly

3. To setup copy/move both cya.service and cya.timer to /etc/systemd/system/ and chmod 644 both of them

4. Now enable the cya.timer unit by issuing the following two commands at the prompt:

shell> sudo systemctl enable cya.timer
shell> sudo systemctl start cya.timer

That's it! If you want to see the status issue the following command at the prompt:

shell> sudo systemctl status cya

Notes:

• If you want multiple intervals you'll need to create multiple sets of these files and alter the command and timing functions accordingly. For example: cya-weekly.service and cya-weekly.timer, cya-monthly.service and cya-monthly.timer, cya-daily.service and cya-daily.timer
• To remove the systemd units issue the following command:

shell> sudo systemctl disable cya.timer

Now delete cya.service and cya.timer files. That's it.

Crontab

It is recommended you crontab this using root or setup a user that doesn't need to enter a sudo password. If necessary use the wrapper file!

The example entry below will run cya at every Monday at 2:05 am with output dumped into /dev/null.

5 2 * * 1 /home/USER/bin/cya save >/dev/null 2>&1

Why was /home/cya/ choosen?

Please see the "Contributors Readme" for very detailed information on this subject.

cya's Issues

Show MAX_SAVES value

From an admin and configuration view point it would be nice to have the MAX_SAVES value being shown when checking your directories and files being backed-up.

The directories option works very well to double check that things are the way you expect.

A possible idea could be...

$ cya directories 
☀ Cover Your Ass(ets) v2.2 ☀ 

ACTION ⯮ Directories & Files Backing Up

Copies being kept (MAX_SAVES): 3

Directories:
---------------------------------------------
/bin/ ... yes
/boot/ ... yes
[...]

cya directories show excluded dirs and files

The directories option is the closest we have to a "config-check" or a "dry-run".

It would be nice to have cya directories show us the directories and files being excluded to be able to double check that we have the configuration file the way we need to, before we run our back up.

ACTION ⯮ Directories & Files Backing Up

Directories:
---------------------------------------------
/bin/ ... yes
/boot/ ... yes
[...]

Files:
---------------------------------------------
/etc/hosts ... yes
/etc/bash_completion.d/git-prompt ... yes
[...]

==============================================

Excluded Directories & Files

Directories:
---------------------------------------------
/usr/games/ ... excluded
[...]

Files:
---------------------------------------------
/usr/local/bin/search ... excluded
[...]

Using cya mydata <profilename> with EXCLUDE statements

It's not clear from the documentation, but I would like to be able to use cya mydata jon (with the following cya.conf file

MYDATA_jon="/home/jon/ /home/cya/jon"
EXCLUDE_/home/jon/="Dropbox/ Nextcloud/"

Is this currently possible?

Bash Tab Completion

Hi,

I am writing a bash completion script for cya. I am trying to make it somewhat "smart" in the sense of context. For example:

cya keep [TAB] would expand name because is part of keep and wait for the name and then expand overwrite or archive only
but
cya directories would not expand name or anything for that matter.

I am having a hard time to get my head around all possible combinations and I wonder if you have them documented or written down somewhere.

Of course, if you like the end result you can have the script ;) and do anything you like with it.

TIA,
David

rsync unexpected behavior

Hi...

I discovered that rsync is not behaving like I expected. In addition that makes cya show backup results that are surprising.

I ended up typing this on the CLI

sudo rsync -a --delete --exclude=systemd/ --exclude=cron.d/ /etc/ /home/cya/points/2/etc/

From previous runs cya already put systemd and crond directories there (when I had no exclusions). However, since rsync skips them completely, it does not delete them on destination, even if we have --delete option.

The result is that I ended up with a backup that I did not expect to have systemd nor crond directories, but there they were (from a previous run).

As I said, I think that it is an rsync weirdness...

Right now I can only think on deleting (rm -fr) the excluded directory/file before invoking the rsync command. Just and idea... ;)

I hope you can reproduce the results I have seen... ;)
David

Avoid ambiguity in what forward slash we are referring to

In the configfile command, "Exclude subdirectories from backup" section, we can find the following message

NO FORWARD SLASHES FOR CHILDREN DIRECTORIES!

in order to avoid ambiguity, maybe it could be changed to

NO LEADING FORWARD SLASHES FOR CHILDREN DIRECTORIES!

since we do need the trailing slash for children directories.

Just a thought...

What if harddisk dies?

From what I understand, CYA needs to work in /home of the partition with the operating system you want to snapshot. So you are out of luck if your HDD/SDD dies? Is there no way to save the system on another HDD/SDD or an external drive?

SANATIZE_VAR in cya script

Please do a global search and replace on the string SANATIZE_VAR to SANITIZE_VAR in the cya script - thanks :-)

How to specify to exclude a root level directory

In the config file we can exclude 2nd level directories and downwards with the syntax

EXCLUDE_/usr/="games/"

However how can we exclude a 1st level directory... ? Let's say we want to exclude /usr/ entirely

What would be the syntax then ?

I think I tried this in an earlier version and I think it did not work... maybe I am wrong...

EXCLUDE_//="usr/"

TIA

Some "TODO" suggests, notes, recommendations, smells, etc

https://github.com/terminalforlife/cya/blob/master/cya

Hi, shell lover here. I'm "Squidgy Testicle" on YT. Sorry for the weird name... lol I mentioned that I'd have a look at it.

I've forked the project and gone through the majority of cya itself, until my eyes were about to pop from tiredness. lol Plenty of feedback there, just look out for "#TODO - " in the text, using your editor's search feature. Will revisit tomorrow and follow through with some actual code and testing, but bit drained tonight.

Hope I can be or have been of some help!

cya mydata - expand / autocomplete profile names

It would be "really" nice that the command mydata would expand / autocomplete the different profiles defined in the config file.

Following the example, in our config file

MYDATA_johnfiles="/home/john/ /mnt/wd-password/john/"

then

cya mydata [tab]

could result into

cya mydata johnfiles

It would be really nice and useful in order to minimize spelling mistakes.

Last Profile Used

Hi...

Glad to see the new version is out... great!!!

However, I tried to see the last profile used enhancement but I couldn't. It displays the same info as ver 1.6

I ran a new back-up, but still not there...

I ran a diff on versions 1.6 and 1.7

4c4
< Cover Your Ass(ets) v1.6 on 16 November 2017
---
> Cover Your Ass(ets) v1.7 on 23 December 2017
23c23
< VERSION="1.6"
---
> VERSION="1.7"
1357,1358c1357,1359
< 	echo "Feedback:"
< 	echo "- Tom D."
---
> 	echo "Additional collaborators and testers:"
> 	echo "* David Sanroma (BASH auto completion & last save notation)"
> 	echo "* Tom D. (disclaimer modification)"

No code seems to be there to show the "Last Run" profile used.

I just copied cya to ~/bin... is that correct / enough ?

Just FYI...

TIA,
David

Roadmap

Is there a roadmap for where this is going?

Are there advantages to this over say a local repo you can install and re-download packages from for the binary repo-available files that are backed up?

missing exclude files from configfile documentation ?

The following is the outline of the configfile documentation (I generated it with grep)

• Additional directories to include in backup:
• Exclude subdirectories from backup:
• Add specific files to include in backup:
• Alter number of rotation backups:
• Backup user data
• Turn off disclaimer notice:

There is a section I am missing (or not seeing)

Exclude files from backup:

The directories seems to show it can exclude individual files...

+++++++++++++++++++++++++++++++++++++++++++++
Excluded Sources:

Directories:
---------------------------------------------
/usr/bin/ ... skipping
/usr/src/ ... skipping
/var/backups/ ... skipping

Files:
---------------------------------------------

If my assumption is correct, I cannot find the documentation to write the proper config line(s).

Wonderful, but inconsistent "Currently Doesn't Exist:" section

I am really divided on this one. I really like the "Currently Doesn't Exist:" section. However, it is only used for the "Excluded Sources:" side of things.

The "Included Sources:" section deals with missing assets in a different way.

Included Sources:

Directories:
---------------------------------------------
[...]
/lib32/ ... skipping - DOESN'T EXIST!
[...]

Files:
---------------------------------------------
/home/dsanroma/missing_file ... skipping - DOESN'T EXIST!

Where the "Excluded Sources:` section has it own section

Excluded Sources:
[...]

Currently Doesn't Exist:
---------------------------------------------
/directory with spaces/test4/ ... not on system
[...]

Furthermore, the wording and capitalization are also different " - DOESN'T EXIST!" vs "not on system".

I have no idea what I would do about this one... I just wanted to point it out. ;)

Maybe the differences could be smoothed out a little... ;)

Inconsistent syntax dealing with root directory names with spaces

In order to make root directories names with spaces work, I had to do the following

EXCLUDE_/directory\ with\ spaces/="test3/ with\\ spaces/"

As we can see when the root directory itself has spaces, we can only escape the space with a single \. However, when we need to declare a sub-directory, we need to use the \\ in front of the white space.

This obviously inconsistent, but I don't if it has a solution. If it doesn't, maybe it should be documented.

Question: Changing cya HOME_DIR

I just downloaded cya and was looking at the installation instructions and how to configure it.

The cya home or working directory is /home/cya by default.

However my /home partition (actually a btrfs subvolume) contains only "real" user home directories and i'd like to keep it that way. I have a separate backup subvol (/share/backup) so I was considering moving the cya home to there

However, when I Iooked at the cya script to find where HOME_DIR is set, further down the script I noticed the following lines-

if [ ! -d "${HOME_DIR}" ]
then
        RECOVER_DIR="/mnt/cya/home/cya"

i'm really not a shellscript programmer, but this looks to me as if it effectively harcodes the value of HOME_DIR as /home/cya, because if I move HOME_DIR to- (say) /some/other/mount/point, and then later mount that image under /mnt, wouldn't the lines above need to be-

if [ ! -d "${HOME_DIR}" ]
then
        RECOVER_DIR="/mnt/cya/some/other/mount/point/cya"

?

Maybe i'm mis-understanding this, but it looks to me as if the key line should look more like-

RECOVER_DIR="/mnt/cya${HOME_DIR}"

cya does not handle directory names with spaces

The following setting makes cya fail.

BACKUP_DIRECTORIES="/sys/ /home/dsanroma/directory with spaces/"

[...]
/sys/ ... yes
/home/dsanroma/directory ... skipping - DOESN'T EXIST!
with ... skipping - DOESN'T EXIST!
spaces/ ... skipping - DOESN'T EXIST!
[...]

Similar things happen with MYDATA_xxxx settings with spaces in them.

Maybe the string could be broken up with regex instead of just white spaces.

just a though

Last Run indicator

Hello,

Would it be possible to add an asterisk (or something) next to the number to indicate more clearly which one is the last one? Example:

Backup Name                                    Date & Time
--------------------------------------------------------------------------------
1*                                             jue 14 dic 2017 21:55:20 CET
--------------------------------------------------------------------------------
2                                              jue 14 dic 2017 19:58:40 CET
--------------------------------------------------------------------------------
3                                              jue 14 dic 2017 19:58:40 CET
--------------------------------------------------------------------------------

I assume it could be done based on the file LAST_RUN

It could be a nice and helpful touch...

TIA,
David

cya mydata - multiple source directories

The mydata command and profiles are a great addition to cya.

It would be even more flexible if you could define multiple sources for the same profile.

For example:

MYDATA_johnfiles="/home/john/Downloads/ /home/john/Documents/ /mnt/wd-password/john/"

This syntax would be easy to understand since rsync works the same way. All paths (except last one) would be copied to "destination" (last one).

Needless to say that I would keep it with full paths (like in the example), so source paths do not have to share parent folder.

We do have configuration files in multiple directories in our PBX that could benefit from this enhancement.

That would be very flexible and powerful.