932
edits
Changes
m
Switched references to f16 to f17.
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 1617, 64 bit Live edition already installed and updated.<br />Ensure the clocks on both machines are set to the correct date and time.}}
*Your virtual system will be used to backup files from the host machine.
*Still on vm01 run this command to verify rsync worked correctly:
ls /backup/etc
*Notice that when running rsync you had to enter the password for root on f16f17. 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 vm01. 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 vm01
| . . |
+-----------------+
*Now you'll need to copy vm01's public rsa key over to f16f17. Still on vm01 use this command (be sure you have the /root/.ssh/ directory on f16 f17 - if you don't then make it first):
scp /root/.ssh/id_rsa.pub 192.168.x.1:/root/.ssh/authorized_keys
*Now verify that your new authentication method is working. Still on vm01 try to ssh to f16 f17 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 if it's not already installed.
*Now, still as root on vm01, use the command 'crontab -e' to edit root's cron table. Insert the following line:(Instead of the IP Address "192.168.122.1", use the IP address of your host machine)
55 * * * * /usr/bin/rsync -avz 192.168.122.1:/etc/ /backup/etc
*At 55 minutes past the hour rsync should synchronize the /etc/ directory of f16 f17 to the /backup/etc/ directory on vm01. 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 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 f16f17) to /etc and then see if it was indeed copied to vm01.
*After the cron job runs, root on vm01 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.
*Finally, edit root's cron table on vm01 and add another record to backup the /home directory of f16 f17 to /backup on vm01 once each week at 2am on Saturday.
===Using syslog to route log files to a remote host===
*to
*.* @@192.168.x.x:514
*where xxx is the IP of f16 f17 host (your logging machine)
*Now restart your rsyslog service
systemctl restart rsyslog.service
*Go on your f16 f17 host and edit /etc/rsyslog.conf and uncomment the following:
$ModLoad imtcp
$InputTCPServerRun 514
*Still on f16f17, restart syslog. NOTE: At this point you should use iptables to open up tcp port 514*Now on vm01 and use the logger command to verify logging messages are getting through to your f16 f17 host. Try this command
logger -p user.warn "Hello World"
*Use the command "tail /var/log/messages" on the f16 f17 host to view the results of the previous step.
*Make the needed changes to have logging of all vm's take place on your host.
