I would be interested in giving the rpm you mentioned a try.
What I am doing is not at a critical point at this time.
I'm trying to upgrade and hoping to not have to re download all the data from my clients servers. Trying to make this as seamless as possible. I'm playing with about 1 tb of data.
Thanks for the info.
will do something by the end of the month, quite busy until the 27th.
then need to send the zipped backups to google drive
I might suggest
https://wiki.contribs.org/Rclone for that part
for the other question it depends on your needs:
- multiple backups versions in case of disaster and or user doing wrong (backuppc, rsync) ,
- unique backup (rsync or unisson),
- not really a backup but rather a unique synced copy (rsync or unisson),
- need to have an identical machine ready to replace the other in case of failure (Affa)
most tools would be able to be adapted for all the needs, but are more intended for a specific use, and the one I put in front of the situation, are most likely more adapted. For instance, backuppc will be able to keep a single version of the Centos7 box, but this would be overkill for that prupose, plus it would be stored in a way it is not directly accessible with cli, and thus might not be best option for sync after to a cloud .
Affa is more intended for SME <->SME or Centos<->Centos works, but it still could do, but again might be overkill for the need.
Rsync (not necessary the rsync contrib, but mostly a simple one liner script ) / unisson might be the more suitable from what I understand, but again you must clarify your needs in term of number of version, purpose of the copy (ies), and how you want to access it.
On top of that you might also need an ecryption procedure, at least for the cloud backup, rclone might be able to do the trick for you too