Difference between revisions of "OPS335 A2 Summer 2015"

From CDOT Wiki
Jump to: navigation, search
(→‎Requirement)
(→‎Phase 3 - Automated Back-ups)
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
DRAFT - Do not use until this line is removed.
 
−
 
 
''' Assignment 2 '''
 
''' Assignment 2 '''
 
This assignment is worth 10% of your final grade and is an individual assignment.
 
This assignment is worth 10% of your final grade and is an individual assignment.
 
= Information =
 
= Information =
−
You should have your VM1 configured as the primary DNS server (lab3) and Vm2 configured as the master NIS server (lab 9) by now. In order to provide redundancy, we want to set up a seconday DNS server and a slave NIS server. We also want to backup the configuration files and database files of those servers to a separate machine at a scheduled time.
+
You should have your VM1 configured as the primary DNS server (lab3) and Vm2 configured as the master NIS server (lab 9). In order to provide redundancy, we want to set up a seconday DNS server and a slave NIS server. We also want to backup the configuration files and database files of those servers to a separate machine at a scheduled time.
  
 
= Requirement =
 
= Requirement =
−
You are to develop a procedure for setting up a secondary DNS server on VM2, a slave NIS server on VM1, and a backup server on VM3 running Fedora 20. The procedure should include test cases to verify that your set up has been completed correctly. Please break down your procedure into the following four phases:
+
The objective is to develop a procedure for setting up a secondary DNS server on VM2, a slave NIS server on VM1, and a backup server on VM3 running Fedora 20. The procedure should include test cases to verify the correctness and completeness of the set up. The complete procedure should be break down into the following three phases:
 
==Phase 1 - Secondary DNS Configuration==
 
==Phase 1 - Secondary DNS Configuration==
−
Due Date: July 31, 2015
+
'''Due Date: August 4, 2015'''
  
−
Describe how to set up (configure) a secondary DNS server. You may have to mentioned the changes that need to be make on the Primary DNS server to support the secondary server.
+
Develop the procedure to setup, configure, and test a secondary DNS server for your domain. You already have your Primary DNS server for your domain up and running on VM1. Your secondary DNS server must comply with the following operation policy:
 +
* It should set answers to queries for resource that have no matching record to be valid for 30 minutes.
 +
* If it fails to retrieve an update from the primary server, it should try again every 10 minutes.
 +
* If it can not contact the primary server for more than 12 hours, it should no longer consider the data it holds to be valid.
 +
* If it is not informed of update by the primary server for more than 3 hours, it should contact the primary to determine if there are updates.
 +
 
 +
You may have to mentioned the changes that need to be make on the Primary DNS server to support the proper operation of the secondary DNS server.
  
 
==Phase 2 - Slave NIS server configuration ==
 
==Phase 2 - Slave NIS server configuration ==
 
'''Due Date: August 7, 2015'''
 
'''Due Date: August 7, 2015'''
  
−
Describe how to set up (configure) a slave NIS server. You may have to mentioned the changes that need to be make to the master NIS server as well.
+
Describe how to setup, configure, and test a slave NIS server for your NIS domain. You may have to mention the changes that need to be made to the master NIS server as well.
  
 
==Phase 3 - Automated Back-ups ==
 
==Phase 3 - Automated Back-ups ==
 
'''Due Date: August 7, 2015'''
 
'''Due Date: August 7, 2015'''
  
−
Describe how to set up a backup server to pull the configuration data from ALL the servers (Primary DNS and master NIS on the host, secondary DNS on VM1, and slave NIS server on VM2). You should consider doing the following steps:
+
Describe how to set up a backup server to <b>pull</b> the configuration data from the Primary DNS server, secondary DNS server, master NIS server, and slave NIS server and save the files in the directories /backup/pri-dns, /backup/sec-dns, /backup/mas-nis, /backup/sla-nis respectively. You should consider doing the following steps:
−
# run a shell script 1 minute after midnight to package all configuration files and database files into a tar ball file. Name the tar ball file as <date>-host-conf-bu.tar on your host, <date>-vm1-conf-bu.tar on VM1, and <date>-vm2-conf-bu.tar on VM2. Create a separate directory for each day's backup file.
+
# run a shell script 1 minute after midnight to package all configuration files and database files into a tar ball file. Name the tar ball file as <date>-primary.tar for all the files for your primary DNS server, <date>-secondary.tar for your secondary DNS server, and <date>-master.tar for your master NIS server, and <date>-slave.tar for your slave NIS server. Pull the tar ball file to the corresponding directory on the backup server.
−
# if the tar ball file is created successfully, create a status file in the same directory.
+
# Create a status file in the corresponding backup directory to indicate when the backup tar ball file was created and when it was successfully backup to the backup server..
−
# run a shell script 1 minute after 1:00am on vm3 transfer each backup file on host, VM1, and VM2 to VM3 if the backup file was created successfully. Create a separate directory for storing each day's backup files using the date so the back ups are sorted.
+
 
 +
=== Sample Directory Structure on the backup server ===
 +
The following listing show the directory structure on the backup server after three successful backups on July 1, July 2, and July 3:
 +
<pre>
 +
/backup
 +
├── mas-nis
 +
│  ├── 20150701-bu-status
 +
│  ├── 20150701-master.tar
 +
│  ├── 20150702-bu-status
 +
│  ├── 20150702-master.tar
 +
│  ├── 20150703-bu-status
 +
│  └── 20150703-master.tar
 +
├── pri-dns
 +
│  ├── 20150701-bu-status
 +
│  ├── 20150701-primary.tar
 +
│  ├── 20150702-bu-status
 +
│  ├── 20150702-primary.tar
 +
│  ├── 20150703-bu-status
 +
│  └── 20150703-primary.tar
 +
├── sec-dns
 +
│  ├── 20150701-bu-status
 +
│  ├── 20150701-secondary.tar
 +
│  ├── 20150702-bu-status
 +
│  ├── 20150702-secondary.tar
 +
│  ├── 20150703-bu-status
 +
│  └── 20150703-secondary.tar
 +
└── sla-nis
 +
    ├── 20150701-bu-status
 +
    ├── 20150701-slavs.tar
 +
    ├── 20150702-bu-status
 +
    ├── 20150702-slavs.tar
 +
    ├── 20150703-bu-status
 +
    └── 20150703-slavs.tar
 +
 
 +
4 directories, 24 files
 +
 
 +
</pre>
  
 
= Important =
 
= Important =
−
Your procedure and test cases should be original, individual work and made so that it can be replicated in Lab S2119 on the PC available.
+
Your procedure and test cases should be original, individual work and made so that it can be replicated on the PC available in the lab.
  
 
= Submission =
 
= Submission =
−
You need to submit a PDF file by both email and hardcopy. The PDF file should contain the entire lab including the answers to lab questions, and the second file is the TXT file containing the questions and answers to the lab ONLY.
+
You need to submit a PDF file by both email and hardcopy. The PDF file should contain the entire procedure and all the test results.
  
 
= Evaluation =
 
= Evaluation =

Latest revision as of 09:17, 7 August 2015

Assignment 2 This assignment is worth 10% of your final grade and is an individual assignment.

Information

You should have your VM1 configured as the primary DNS server (lab3) and Vm2 configured as the master NIS server (lab 9). In order to provide redundancy, we want to set up a seconday DNS server and a slave NIS server. We also want to backup the configuration files and database files of those servers to a separate machine at a scheduled time.

Requirement

The objective is to develop a procedure for setting up a secondary DNS server on VM2, a slave NIS server on VM1, and a backup server on VM3 running Fedora 20. The procedure should include test cases to verify the correctness and completeness of the set up. The complete procedure should be break down into the following three phases:

Phase 1 - Secondary DNS Configuration

Due Date: August 4, 2015

Develop the procedure to setup, configure, and test a secondary DNS server for your domain. You already have your Primary DNS server for your domain up and running on VM1. Your secondary DNS server must comply with the following operation policy:

  • It should set answers to queries for resource that have no matching record to be valid for 30 minutes.
  • If it fails to retrieve an update from the primary server, it should try again every 10 minutes.
  • If it can not contact the primary server for more than 12 hours, it should no longer consider the data it holds to be valid.
  • If it is not informed of update by the primary server for more than 3 hours, it should contact the primary to determine if there are updates.

You may have to mentioned the changes that need to be make on the Primary DNS server to support the proper operation of the secondary DNS server.

Phase 2 - Slave NIS server configuration

Due Date: August 7, 2015

Describe how to setup, configure, and test a slave NIS server for your NIS domain. You may have to mention the changes that need to be made to the master NIS server as well.

Phase 3 - Automated Back-ups

Due Date: August 7, 2015

Describe how to set up a backup server to pull the configuration data from the Primary DNS server, secondary DNS server, master NIS server, and slave NIS server and save the files in the directories /backup/pri-dns, /backup/sec-dns, /backup/mas-nis, /backup/sla-nis respectively. You should consider doing the following steps:

  1. run a shell script 1 minute after midnight to package all configuration files and database files into a tar ball file. Name the tar ball file as <date>-primary.tar for all the files for your primary DNS server, <date>-secondary.tar for your secondary DNS server, and <date>-master.tar for your master NIS server, and <date>-slave.tar for your slave NIS server. Pull the tar ball file to the corresponding directory on the backup server.
  2. Create a status file in the corresponding backup directory to indicate when the backup tar ball file was created and when it was successfully backup to the backup server..

Sample Directory Structure on the backup server

The following listing show the directory structure on the backup server after three successful backups on July 1, July 2, and July 3: 

/backup
├── mas-nis
│   ├── 20150701-bu-status
│   ├── 20150701-master.tar
│   ├── 20150702-bu-status
│   ├── 20150702-master.tar
│   ├── 20150703-bu-status
│   └── 20150703-master.tar
├── pri-dns
│   ├── 20150701-bu-status
│   ├── 20150701-primary.tar
│   ├── 20150702-bu-status
│   ├── 20150702-primary.tar
│   ├── 20150703-bu-status
│   └── 20150703-primary.tar
├── sec-dns
│   ├── 20150701-bu-status
│   ├── 20150701-secondary.tar
│   ├── 20150702-bu-status
│   ├── 20150702-secondary.tar
│   ├── 20150703-bu-status
│   └── 20150703-secondary.tar
└── sla-nis
    ├── 20150701-bu-status
    ├── 20150701-slavs.tar
    ├── 20150702-bu-status
    ├── 20150702-slavs.tar
    ├── 20150703-bu-status
    └── 20150703-slavs.tar

4 directories, 24 files

Important

Your procedure and test cases should be original, individual work and made so that it can be replicated on the PC available in the lab.

Submission

You need to submit a PDF file by both email and hardcopy. The PDF file should contain the entire procedure and all the test results.

Evaluation

Your work will be graded based on understandability, thoroughness and correctness.

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