This lab will show you how to set up a Fedora installed system to be used for file backups and introduce you to some tools used in backups.

{{Admon/important|Prerequistites:|Your hard drive Centos machine should have three Fedora 16, 64 bit Live edition 20 virtual machines already installed.<br />You should have at least one VM installed: also Fedora 16, 64 bit Live edition<br />Both your host and guest should have default firewalls enabled.<br />Both host and guest should have all software updated.<br />Ensure the clocks on both all machines are set to the correct date and time.}} *Your virtual system will be used to backup files <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 host machineother rules intact.}}

*Your host machine will be used to backup files from the virtual machines.*Login to vm01 as joker your host using your learnid and open a terminal window. Then "su -" to root run the following two commands: mkdir -p /backup/vm1 rsync -avz 192.168.122x.12:/etc/ /backup/etcvm1*Still on vm01 the host run this command to verify rsync worked correctly: ls /backup/etcvm1*Notice that when running rsync you had to enter the password for root on f16vm1. 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 vm01the host. We'll use an openssh command like this:

*when you enter this command just hit ENTER for all the questions. Here's what I got when I ran it on my vm01host

f5:07:8c:aa:b6:08:e0:45:81:ca:d6:88:8c:aa:1a:7b root@vm01@localdomainhost.pcallagh.org

*Now you'll need to copy vm01the host's public rsa key over to f16vm1. Still on vm01 the host use this command (be sure you have the /root/.ssh/ directory on f16 vm1 - if you don't then make it first): scp /root/.ssh/id_rsa.pub 192.168.122x.12:/root/.ssh/authorized_keys*Now verify that your new authentication method is working. Still on vm01 the host try to ssh to f16 vm1 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 the host if it's not already installed. yum -y install mailx*Now, still as root on vm01the host, use the command 'crontab -e' to edit root's cron table. Insert the following line:(Instead of the IP Address "192.168.X.2", use the IP address of your vm1) 55 * * * * /usr/bin/rsync -avz 192.168.122X.12:/etc/ /backup/etc vm1 *At 55 minutes past the hour rsync should synchronize the /etc/ directory of f16 vm1 to the /backup/vm1/etc/ directory on vm01the host. 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 the host and enter another time for the backup to take place.*You should convince yourself check that /etc/ is being backed up by adding some file (say 'touch /etc/junk' on f16vm1) to /etc and then see if it was indeed copied to vm01the host.*After the cron job runs, root on vm01 the host 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 vm01. Note that that mail may take a minute to show up.*Finally, edit root's cron table on vm01 and add another record to backup the /home directory of f16 vm1 to /backup /vm1/home on vm01 the host once each week at 2am on Saturday.

*Now we will configure your machines to copy their logs to VM 3.  *Go on your VM 3 and edit /etc/rsyslog.conf and uncomment the following: $ModLoad imtcp $InputTCPServerRun 514* Use the firewalld command language to open up tcp port 514 to your internal network only.*Still on VM 3, restart rsyslog.  *On your host machine (f16) vm1 edit /etc/rsyslog.conf and make the following change:

*.* @@192.168.122x.xxx4:514*where xxx x is the IP of vm01 (your logging machine)VM 3.*Now restart your rsyslog service

*Now on vm1 use the logger command to verify logging messages are getting through to your Vm 3. Try this command logger -p user.warn "Hello World"*Use the command "tail /var/log/messages" on the logging VM to view the results of the previous step. *Make the needed changes to have logging of all machines (including your host) take place on your VM 3. Note that your VM3 is already logging to itself and does not need further changes. ==Answer Completing the following questions Lab==Upon completion of this lab you should have your host automatically backing up your VM1's /etc and /home directories, and email them all of your machines should be sending copies of their logs to your teacher in ASCII text format==VM3. You have now gained experience using tools to make, and to automate, remote backups

#What is your full name and 9-digit Seneca student ID?Exploration questions:#Show the RSA public key generated on vm01your host. i.e. the file called id_rsa.pub.

#What was command could you use to view only the output of 'tail /var/log/messages' at the end of the labfrom your host on VM 3?#What is the output of option did you use to limit the iptables-save command on vm01 at rule for port 514 to the end of this lablocal network?