Difference between revisions of "OPS335 Archiving Lab"

From CDOT Wiki
Jump to: navigation, search
(Created page with 'FOCUS: SAMBA PART A: Connecting to a Linux SMB Server (Matrix) from a Windows Client (Windows 7) Power up a Windows 7 system in the lab and login using your LEARN username and …')
 
Line 1: Line 1:
−
FOCUS: SAMBA
+
===Automating System Backup===
 +
This lab will show you how to set up a Fedora installed system to be used for file backups.
  
−
PART A: Connecting to a Linux SMB Server (Matrix) from a Windows Client (Windows 7)
+
{{Admon/important|Prerequistites:|Your hard drive should have Fedora 13, 64 bit Live edition already installed.<br />You should have at least one VM installed: also Fedora 13, 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 machines are set to the correct date and time.}}
−
Power up a Windows 7 system in the lab and login using your LEARN username and password.
 
−
You should see an icon of Tux, the Linux penguin, on your desktop. Double-click it to login to your Matrix account. A window of your Matrix home directory should open.
 
−
Use the mouse to drag and drop files to and from your Matrix account and your Windows 7 lab machine.
 
−
Once you are satisfied that you can easily move files to/from your Matrix account power off the PC.
 
−
Set the HD selector switch to boot from your Fedora 13 Linux drive and power on the PC.
 
−
PART B:  Connecting to a Linux SMB Server (Matrix) from a Linux Client (Fedora 13)
 
  
−
There are 4 ways that a Linux client can connect to an SMB server. Start by logging into your Fedora 13 system as joker and opening a terminal window.
+
*Your virtual system will be used to backup files from the host machine. Your setup should look like the following diagram:
−
The first way is to use the "Places" menu from a Gnome desktop:
 
−
Switch to root and ensure you are using the default Fedora 13 firewall.
 
−
As root, ensure Samba is installed. Use these two commands: "yum install samba" and "yum install samba-client"
 
−
NOTE: Fedora encrypts passwords when authenticating SMB connections. Unfortunately Windows clients (here at Seneca) insist on passwords being sent in plain text. For this reason Matrix SMB is set to use plain text passwords. To change Fedora to use plain text passwords switch to root and edit the /etc/samba/smb.conf file and immediately after the [global] section header insert these two lines:
 
−
client plaintext auth = yes
 
−
client lanman auth = yes
 
−
Create a new account on Fedora with the same name as your LEARN acount. Set the password to 'seneca99'.
 
−
Logout of joker and login to Fedora using your LEARN name.
 
−
Now try the following:
 
−
From the "Places" menu at the top of your screen, select "Network"
 
−
and wait until the network scan completes. Then click on the
 
−
"Windows Network" and then click the "File" menu and select
 
−
"Connect to Server" and input matrix.senecac.on.ca for the server,
 
−
your username for the ShareName and UserName fields. Then click the
 
−
Connect button. You should now be able to browse your Matrix files.
 
−
The second way is to use a web browser with support for the SMB protocol such as Konqueror.
 
−
If Konqueror is not installed then install it with the command: 'yum install kdebase'.
 
−
Start Konqueror, the web/file browser, and in the Location edit box enter the following:
 
−
smb://matrix/xxxxxx
 
−
where
 
−
xxxxxx is your Matrix username
 
−
Login to your Matrix account. Konqueror should open a window of your Matrix home directory. Use the mouse to drag and drop files to and from your Matrix account and your Fedora Linux machine.
 
−
Close Konqueror.
 
−
The third way is to use the "smbclient" command in a terminal window.
 
−
At the command prompt enter the following:
 
−
smbclient '\\matrix\xxxxxx' -U xxxxxx
 
−
where
 
−
xxxxxx is your Matrix username
 
−
You should get a prompt similar to
 
−
smb: \>
 
−
Enter the ls command to see a list of your Matrix files.
 
−
Enter ? to see a list of smbclient commands.
 
−
Use the get and put commands (similar to ftp) to move files to and from your Matrix account and your Fedora 13 Linux system.
 
−
When done enter the quit command.
 
−
The fourth way is to use the mount command. THIS PART IS IN RED BECAUSE IT PROBABLY WILL NOT WORK !
 
−
Use the mount command to mount your matrix home directory. NOTE: This mount command will only work if your kernel was configured to allow mounting CIFS with unencrypted passwords.
 
−
mount -t cifs //matrix/xxxxxx /mnt -o username=xxxxxx
 
−
where
 
−
xxxxxx is your your Matrix username.
 
−
If the previous step worked, browse your /mnt directory using cd and ls commands and when done use the umount command to unmount your Matrix home directory.
 
−
PART C: Configuring an SMB Server on Linux
 
−
Login to Fedora as joker and open a terminal window.
 
−
Use "su -" to become root.
 
−
Ensure SAMBA is installed:
 
−
yum install samba
 
−
Edit the file /etc/samba/smb.conf, delete all original lines and include the following:
 
−
        [global]
 
−
        workgroup = OPS335
 
−
        server string = "put your real name here without the quotes"
 
−
        encrypt passwords = yes
 
−
        smb passwd file = /etc/samba/smbpasswd
 
−
        hosts allow = 142.204.141.
 
−
        ; note: the above line will allow access from the Seneca domain in lab T2107
 
  
−
        [home]
+
PART B: Using rsync and cron to automate system backup:
−
        comment = "put your real name here without the quotes"
+
Login to vm01 as joker and open a terminal window. Then "su -" to root run the following two commands:
−
        path = /home/xxxxxxx
+
mkdir /backup
−
        valid users = xxxxxxx
+
rsync -avz 192.168.122.1:/etc/ /backup/etc
−
        ; remember xxxxxxx is your LEARN/MATRIX account name
+
Still on vm01 run this command to verify rsync worked correctly:
−
        public = no
+
ls /backup/etc
−
        writable = yes
+
Notice that when running rsync you had to enter the password for root on f13. 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:  
−
        printable = no
+
ssh-keygen -t rsa
−
        create mask = 0765
+
−
You can comment out all other lines in the file.
+
when you enter this command just hit ENTER for all the questions.
−
Create a SAMBA password for user xxxxxxx with the command
+
Here's what I got when I ran it on my vm01
−
        smbpasswd -a xxxxxxx
 
−
Test your configuration with the command
 
−
        testparm
 
−
You can now start your SAMBA server
 
−
        /etc/init.d/smb start
 
−
or
 
−
service smb start
 
−
Test if you have a connection with the command
 
−
        smbclient -L 142.204.141.yyy -Uxxxxxxx%ppppppp
 
−
where 142.204.141.yyy is your Fedora Linux IP address
 
−
and xxxxxxx is your Matrix account name
 
−
and ppppppp is your SAMBA password
 
−
If the previous command worked, use another PC (Fedora then Windows) to establish a connection with the SMB server on your Fedora Linux machine. This step is important to ensure your SMB server on Linux is working. NOTE: If your set up looks correct but you can't connect to your SMB server from the outside then you may need to adjust your firewall to allow SMB connections.
 
−
From another Linux PC, use the mount command to mount your home directory onto /mnt. Step 4 in PART B should help you with this. Record this command as you'll need it for PART D.
 
−
PART D: Answer the following questions
 
  
−
What is your full name and 9 digit Seneca student ID?
+
Generating public/private rsa key pair.
−
In PART C step 9, explain how you connected to your SMB server on Linux from a Windows PC. List exactly what you had to do on the Windows PC to test your Linux server.
+
Enter file in which to save the key (/root/.ssh/id_rsa):
−
What is the purpose of the testparm command?
+
Enter passphrase (empty for no passphrase):
−
What is the purpose of the smbclient command?
+
Enter same passphrase again:
−
What does SMB stand for? CIFS?
+
Your identification has been saved in /root/.ssh/id_rsa.
−
What does the text inside square brackets in the smb.conf file mean? (e.g., "[homes]").
+
Your public key has been saved in /root/.ssh/id_rsa.pub.
−
Explain the meaning of the line "create mask = 0765" in the smb.conf file?
+
The key fingerprint is:
−
What does the smbpasswd command do?
+
f5:07:8c:aa:b6:08:e0:45:81:ca:d6:88:8c:aa:1a:7b root@vm01@localdomain
−
What exact mount command did you use in PART C step 10?
+
The key's randomart image is:
 +
+--[ RSA 2048]----+
 +
|      o+++      |
 +
|    E .ooo..    |
 +
|    ...o.      |
 +
|      ...o    .|
 +
|      .S+ +  o.|
 +
|        . = . o .|
 +
|          o +  |
 +
|          o +    |
 +
|          . .  |
 +
+-----------------+
 +
Now you'll need to copy vm01's public rsa key over to f13. Still on vm01 use this command (be sure you have the /root/.ssh/ directory on f13 - if you don't then make it first):
 +
scp /root/.ssh/id_rsa.pub 192.168.122.1:/root/.ssh/authorized_keys2
 +
Now verify that your new authentication method is working. Still on vm01 try to ssh to f13 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:
 +
15 * * * * /usr/bin/rsync -avz 192.168.122.1:/etc/ /backup/etc
 +
At 15 minutes past the hour rsync should synchronize the /etc/ directory of f13 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 f13) 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 f13 to /backup on vm01 once each week at 2am on Saturday.
 +
PART C: Using syslog to route log files to a remote host:
 +
On your host machine (f13) edit /etc/rsyslog.conf and make the following change:
 +
change
 +
#*.* @@remote-host:514
 +
to
 +
*.* @@192.168.122.xxx:514
 +
where xxx is the IP of vm01 (your logging machine)
 +
 
 +
Now restart your rsyslog service (service rsyslog restart).
 +
Go back on to vm01 and edit /etc/rsyslog.conf and make the following change:
 +
change these two lines
 +
#$ModLoad imtcp.so
 +
#$InputTCPServerRun 514
 +
to
 +
$ModLoad imtcp.so
 +
$InputTCPServerRun 514
 +
Still on vm01, restart syslog. NOTE: At this point you should use iptables to open up tcp port 514 on vm01.
 +
Now go back onto f13 and use the logger command to verify logging messages are getting through to vm01. Try this command
 +
logger -p user.warn "Hello World"
 +
Use the command "tail /var/log/messages" on vm01 to view the results of the previous step.
 +
PART D: Answer the following questions and and email them to your teacher in ASCII text format.
 +
 
 +
What is your full name and 9-digit Seneca student ID?
 +
Show the RSA public key generated on vm01. i.e. the file called id_rsa.pub.
 +
Explain the meaning of the -avz options on the rsync command.
 +
What did root's cron table on vm01 look like after step 11 of PART B?
 +
What were the last two lines of the email sent to root upon completion of the cron job in PART B step 10?
 +
What was shown in PART C step 6?
 +
What is the output of the iptables-save command on vm01 at the end of this lab?

Revision as of 20:24, 6 September 2011

Automating System Backup

This lab will show you how to set up a Fedora installed system to be used for file backups.

Important.png
Prerequistites:
Your hard drive should have Fedora 13, 64 bit Live edition already installed.
You should have at least one VM installed: also Fedora 13, 64 bit Live edition
Both your host and guest should have default firewalls enabled.
Both host and guest should have all software updated.
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. Your setup should look like the following diagram:

PART B: Using rsync and cron to automate system backup: Login to vm01 as joker and open a terminal window. Then "su -" to root run the following two commands: mkdir /backup rsync -avz 192.168.122.1:/etc/ /backup/etc 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 f13. 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

Generating public/private rsa key pair. Enter file in which to save the key (/root/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /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@vm01@localdomain The key's randomart image is: +--[ RSA 2048]----+ | o+++ | | E .ooo.. | | ...o. | | ...o .| | .S+ + o.| | . = . o .| | o + | | o + | | . . | +-----------------+ Now you'll need to copy vm01's public rsa key over to f13. Still on vm01 use this command (be sure you have the /root/.ssh/ directory on f13 - if you don't then make it first): scp /root/.ssh/id_rsa.pub 192.168.122.1:/root/.ssh/authorized_keys2 Now verify that your new authentication method is working. Still on vm01 try to ssh to f13 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: 15 * * * * /usr/bin/rsync -avz 192.168.122.1:/etc/ /backup/etc At 15 minutes past the hour rsync should synchronize the /etc/ directory of f13 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 f13) 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 f13 to /backup on vm01 once each week at 2am on Saturday. PART C: Using syslog to route log files to a remote host: On your host machine (f13) edit /etc/rsyslog.conf and make the following change: change #*.* @@remote-host:514 to *.* @@192.168.122.xxx:514 where xxx is the IP of vm01 (your logging machine)

Now restart your rsyslog service (service rsyslog restart). Go back on to vm01 and edit /etc/rsyslog.conf and make the following change: change these two lines #$ModLoad imtcp.so #$InputTCPServerRun 514 to $ModLoad imtcp.so $InputTCPServerRun 514 Still on vm01, restart syslog. NOTE: At this point you should use iptables to open up tcp port 514 on vm01. Now go back onto f13 and use the logger command to verify logging messages are getting through to vm01. Try this command logger -p user.warn "Hello World" Use the command "tail /var/log/messages" on vm01 to view the results of the previous step. PART D: Answer the following questions and and email them to your teacher in ASCII text format.

What is your full name and 9-digit Seneca student ID? Show the RSA public key generated on vm01. i.e. the file called id_rsa.pub. Explain the meaning of the -avz options on the rsync command. What did root's cron table on vm01 look like after step 11 of PART B? What were the last two lines of the email sent to root upon completion of the cron job in PART B step 10? What was shown in PART C step 6? What is the output of the iptables-save command on vm01 at the end of this lab?

Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=OPS335_Archiving_Lab&oldid=68649"