IntroductionThis document will explain the steps required to use scp in cron. This is generally useful to do automated backups on Linux and other nix variations.
InstructionsThese instructions will walk you through what it takes.
1. Generate a private/public key pair
Simple command to do this:
ssh-keygen -t rsaLeave the passphrase empty so that cron can use it passwordless. Just be sure nobody gets your private key.
2. Copy the public key to the remote server
scp ~/.ssh/id_rsa.pub remote_host:
3. Add local key to remote servers trusted keyLog on to the remote server and if there has never been a key created for this user on the remote machine, run the ssh-keygen-t rsa just to get the key directory and stuff set up.
Then concatenate the new key to your authorized_keys file:
cat ~/id_rsa.pub >> ~/.ssh/authorized_keysNow for some reason, you may have to do this to the keys file:
chmod 644 ~/.ssh/authorized_keys4. Now try logging into the remote machine again from local
ssh REMOTE_USERNAME@remote_hostThis should log you in without asking for a password. If it doesn't, then something must be wrong at this point and you should go through the steps above again. This should also mean that scp will work the same way and you might want to test that scp works by copying a file from local to remote usingscp. If no password, then we're all good.
5. Now lets test the cron scriptMy cron script for this example is simply going to copy a directoryof files using scp to the remote server.
scp -r /PATH_TO_FILES/ REMOTE_USER@remote_host:BACKUPS/And that's about all she wrote. Save that in a file called backup.sh (or whatever you want to call it), chmod 755 i it and then try running it. ./backup.sh to run it. If it works, then next stop is to cron it.
6. Add script to cron jobsEasiest way is to simply copy the backup.sh file into /etc/cron.daily/ . This will make it run every day. Choose another cron.SOMETIME to make it run more or less often. If you want more control on when it's run, read up on adding it to the crontab.