13,420
edits
Changes
→Performing Full Backups
There are a number of other problems that could prevent your network connection from functioning but the above are the most common problems.
==== "Run Script to Break My Network" script Connection for Troubleshooting ====
You will now download, set execute permissions and run a Bash shell script to try to "break" the network connection for your vm1. This will provide troubleshooting practice to check your network configuration file, look and correct errors and restart your network interface connection.
'''Record steps, commands, and your observations in INVESTIGATION 1 in your OPS335 lab log-book'''
== INVESTIGATION 2: Configuring SSH ==
#Make certain that you have performed a full backup for '''vm1''', '''vm2''', and '''vm3'''.
It is recommended to create a Bash shell script to automate the backing up of ALL your VMs in sequence. You can do this by running a for loop using a list for vm1, vm2, and vm3image file pathnames.
<ol><li value="5">Create the sub-directory '''/root/bin'''</li>
<li>You should know how to create full backups of your VMs in your OPS235 course. Create a Bash shell script called '''/root/bin/fullbackup.bash''' that will backup all of your other vms (i.e. vm1, vm2, and vm3) one at a time using the '''gzip''' command to your host machine into the respective directory path-namesname: '''/backup/full/vm1''', '''/backup/full/vm2''', and '''/backup/full/vm'''</li>
<li>Set execute permissions, and run the shell script to verify that you shell script works.</li>
<li>It is also recommended to backup to your USB key as well (qcow2 images and xml config files).</li></ol>
