Open main menu

CDOT Wiki β

Changes

OPS335 Archiving Lab

192 bytes added, 17:29, 20 December 2012
m
Switched direction of automatic backup to make more sense.
This lab will show you how to set up a Fedora installed system to be used for file backups.
{{Admon/important|Prerequistites:|Your hard drive should have Fedora 17, 64 bit Live edition already installed and updated.<br />Ensure the clocks on both machines are set to the correct date and time.<br />If you have not already done so, remove the iptables rules preventing your host from pinging or SSH'ing your VMs, but leave the other rules intact.}}
*Your virtual system host machines will be used to backup files from the host machinevirtual machines.
===Using rsync and cron to automate system backup===
*Login to vm01 f17 using your learnid and open a terminal window. Then "su -" to root run the following two commands: mkdir /backup/vm01 rsync -avz 192.168.x.12:/etc/ /backup/vm01/etc*Still on vm01 f17 run this command to verify rsync worked correctly: ls /backup/vm01/etc*Notice that when running rsync you had to enter the password for root on f17vm01. To automate this process so that it will run without requiring a password we'll use an RSA public/private key pair for passwordless authentication. To do this we'll have to generate an RSA public/private key pair on vm01f17. We'll use an openssh command like this:
ssh-keygen -t rsa
*when you enter this command just hit ENTER for all the questions. Here's what I got when I ran it on my vm01f17
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
f5:07:8c:aa:b6:08:e0:45:81:ca:d6:88:8c:aa:1a:7b root@vm01f17@localdomainpcallagh.org
The key's randomart image is:
+--[ RSA 2048]----+
| . . |
+-----------------+
*Now you'll need to copy vm01f17's public rsa key over to f17vm01. Still on vm01 f17 use this command (be sure you have the /root/.ssh/ directory on f17 vm01 - if you don't then make it first): scp /root/.ssh/id_rsa.pub 192.168.x.12:/root/.ssh/authorized_keys*Now verify that your new authentication method is working. Still on vm01 f17 try to ssh to f17 vm01 as root. You should be able to login without entering a password. If you were successful then move on to the next step, otherwise repeat steps 3 and 4.*Install mailx on vm01 f17 if it's not already installed. yum -y install mailx*Now, still as root on vm01f17, use the command 'crontab -e' to edit root's cron table. Insert the following line:(Instead of the IP Address "192.168.122.12", use the IP address of your host machinevm01) 55 * * * * /usr/bin/rsync -avz 192.168.122.12:/etc/ /backup/etc *At 55 minutes past the hour rsync should synchronize the /etc/ directory of f17 vm01 to the /backup/vm01/etc/ directory on vm01f17. If this time has passed and you don't want to wait an hour for the next time rsync runs, just edit root's cron table on vm01 f17 and enter another time for the backup to take place.*You should convince yourself that /etc/ is being backed up by adding some file (say 'touch /etc/junk' on f17vm01) to /etc and then see if it was indeed copied to vm01f17.*After the cron job runs, root on vm01 f17 should have received an email containing the output of the cron job. Verify this by using the mail command to check root's mail on vm01f17.*Finally, edit root's cron table on vm01 f17 and add another record to backup the /home directory of f17 vm01 to /backup /vm01/home on vm01 f17 once each week at 2am on Saturday.
===Using syslog to route log files to a remote host===
932
edits