Just as a suggestion, get your backup running manually first before running from cron. That reduces the time for troubleshooting. Understand what your rsync is doing. Validate that your backup on the destination is good. If you are going to use ssh keys, get that tested. Then put everything in cron. It's a lot easier to figure out what is going wrong that way.
For example, in your original post, you don't need to rsync from / if all you want are your home directory and other specific files/directories backed up. You need to ask yourself if you need a backup of system files. It just depends on the purpose of the backup. -- Cathy L. Smith IT Engineer Pacific Northwest National Laboratory Operated by Battelle for the U.S. Department of Energy Phone: 509.375.2687 Fax: 509.375.4399 Email: cathy.sm...@pnnl.gov -----Original Message----- From: plug-boun...@pdxlinux.org <plug-boun...@pdxlinux.org> On Behalf Of Rich Shepard Sent: Thursday, November 15, 2018 10:07 AM To: Portland Linux/Unix Group <plug@pdxlinux.org> Subject: Re: [PLUG] rsync in a cron job On Thu, 15 Nov 2018, Larry Brigman wrote: > Note that none of your shell variables from your login will be set > when you run from cron. Larry, Would this affect synchronizing files in ~/ on both hosts? Thanks, Rich _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
