This document covers the creation of a SafeHaven 3.0/3.1 base image. This base image, once complete, should be converted to template in both the Production and Disaster Recovery Data Centers so that the appropriate amount of SRN and CMS appliances can be deployed from the source template. The base-image template is the same for either SRN or CMS appliances, they are configured for their particular roles during the post-deployment run of the ClusterConfigurator.exe within the SafeHaven Executable bundle. Note that these links are valid for the current 3.1 GA release only, and may or may not reflect the most recent codebase.
Build a 2 vCPU/4GB vRAM Ubuntu 14 image within the desired data centers.
Login via SSH. Run
uname -rto determine the kernel version. The desired kernel version for SafeHaven 3.1 is 3.13.0-44 currently.
If the kernel is lower, run:
apt-get install linux-image-3.13.0-44-generic linux-headers-3.13.0-44-generic -y
update-gruband reboot. After reboot,
uname -rshould show the correct kernel.
If the kernel is higher (i.e 3.13.0-83), run:
apt-get remove linux-image-3.13.0-83-generic linux-headers-3.13.0-83-generic -ythe output will show you the other installed kernels, which are likely to be lower. If that is the case, repeat the command
apt-get remove linux-image-3.13-XX-generic linux-headers-3.13-XX-generic -y
You may see that the grub has been updated as there are no more linux entries, in which case you must install the .44 image.
apt-get install linux-image-3.13.0-44-generic linux-headers-3.13.0-44-generic -yand once that is complete, run
update-grub. Reboot the machine and check that
3.13.0-44 as the current kernel. Note that iSCSI servers are tied to the kernel so if you forget to do this step, you will need to rebuild iSCSI after downgrading the kernel.
Download the "base installers" package.
Untar the downloaded file by running:
tar xvfz baseInstaller-SafeHaven3.1.1-u1.tar.gz?dl=0(tar xvz Saf (using tab to autocomplete name should be easier))
Remove the downloaded .gz
rm -rf Safehaven-(tab)(optional).
Change to the baseImages folder
Run the "install" script for Ubuntu, in this instance it would be:
Then run the buildcodes. Both of these scripts should be re-run if you find you have a kernel mismatch down the road, as the builcodes will configure iSCSI services.
Change to your root directory. The fastest way to do this is to issue: the
Download the full kernel from the SafeHaven links. Current 3.1 GA-June26 release can be found below:
Extract the archive, ensuring to use the "-C /" flag so that the necessary code will be written/overwritten in an upgrade:
tar xvfz SafeHaven3.1.1-GA_full_kernel-3.13.0-44-generic...etc.gz -C /
Reboot your server.
Move to the SafeHaven directory:
Verify that you are running the expected version of safehaven:
cat utils_version. The syntropy and utils version should match on all nodes of the cluster. The results of both of these commands should match the expected output (i.e., Syntropy/utils_version =
SafeHaven3.1.1-GA, DataGardens Inc. 2015).