Ask the Community
Groups
UEB Installable Software Configuration Tips - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Describe additional UEB Installable Software configuration information that may be useful.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h3 data-id="ueb-installable-software-configuration-tipspurpose"> <b>UEB Installable Software Configuration Tips</b><br><br>Purpose </h3> Describe additional UEB Installable Software configuration information that may be useful. <br>The primary source of UEB Installable Software information should be the Deployment Guide at <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fwww.unitrends.com%2Fdocuments%2Fadministrators-guide%2F">http://www.unitrends.com/documents/administrators-guide/</a> , and the UEBInstallableSoftwareGuide.pdf documentation included with your software.<br><br><b>Storage Configuration Tips</b><br><b>Requirements</b> <ul><li>The system should be regarded as a single-purpose system, so that the Unitrends software can run without interference from other production tasks.</li> <li>The following are minimum hardware requirements:</li> <li>64‐bit little endian CPU with at least 4 cores.</li> <li>4 GB of memory.</li> <li>Enterprise SATA or SAS disks with a minimum of 140 GB. The disks must have enough space to accommodate your backups.</li> <li>During installation of the operating system, you must create a <i>/backups </i>partition with at least 140 GB, but it should be large enough to accommodate your backups. 95% of the partition will be used for backups, and 5% for system information. If you create a <i>/usr </i>partition, it must be at least 80 GB, and if the <i>/root </i>partition will include <i>/var</i>, it must be at least 50 GB.</li> <li>Check the UEBInstallableSoftwareGuide.pdf documentation included in your software download or media for supported adapters and other information.</li> </ul> The install script for Installable UEB will detect and handle any dependencies required by the Unitrends software.<br><br><b>Best Practices</b> <ul><li>We usually install the ‘Minimum’ or ‘Server’ bundles from CentOS6</li> <li>Generally don’t install a GUI (gnome desktop, etc.), because it won’t be used, and can conflict with our console app.</li> <li>Do not install a custom non-CentOS NIC driver, if that is your only NIC. Some of those use different NIC naming if they are derived from a later kernel, and UEB requires the first NIC to be ‘eth0’. </li> </ul> For example, this pre-release driver (derived from kernel 3.1.0) for an Intel I217-LM Ethernet NIC on a Dell server, taken from a non-CentOS/RHEL repo uses NIC naming like ‘em1’: kmod-e1000e-3.1.0.2-1.el6.elrepo.x86_64.rpm.Newer NIC drivers will be included in the CentOS/RHEL repos fairly quickly.<br> <br><b>Filesystem for large storage partitions</b><br>Unitrends recommends using xfs for large storage partitions, like <i>/backups</i>. The xfs filesystem can handle the largest filesystems.<br> <br><b>Automatically Mounting External Storage for /backups (needed if release 8.1.0)</b><br>If we are configuring external storage on the system for the /backups partition, we must be sure that the external storage is mounted correctly before the /etc/init.d/bp_rcscript starts the database. The steps can be more complex for iSCSI storage, where there are several steps involved.<br> <br>With Unitrends release 8.2.0 and later, the <i>/usr/bp/bin/stateless_init </i>and <i>/usr/bp/bin/stateless_stop</i> scripts are automatically created in order to handle this. These are called by /etc/init.d/bp_rcscript at the appropriate time.<br> <br>For Unitrends releases prior to 8.2.0, see below. Later releases handle this automatically.<br>This mounting can be done manually if desired, inserting the mount/unmount steps into the init script at <i>/usr/bp/bin/stateless_init</i> and the unmounts steps into <i>/usr/bp/bin/stateless_stop</i>, which are called during init at the appropriate time and are empty except when the software is deployed as a virtual ‘stateless’ UEB image with NAS or iSCSI storage for /backups. <br> <br>--- Examples for iSCSI:<br>Sample stateless_init steps which would mount myiscsi on /backups:<br>cmciscsi=/usr/bp/bin/cmc_iscsi<br>STORNAME=backups<br>NODE=192.168.215.100<br>IPORT=3260<br>ITARGET=iqn.1987-05.com.cisco:nss326:iscsi.myiscsi.f0c046<br>ILUN=0<br>$cmciscsi discover $NODE $IPORT <br>$cmciscsi connect $STORNAME stateless $NODE $IPORT $ITARGET $ILUN 0 <br> <br>Sample stateless_stop script steps with iSCSI:<br>cmciscsi=/usr/bp/bin/cmc_iscsi<br>$cmciscsi disconnect backups<br>umount /backups <br>$cmciscsi logoutall<br> <br>Sample stateless_init steps for iSCSI raw commands (for myiscsi target, with /dev/sdf1 as its partition):<br>iscsiadm -m node<br>iscsiadm -m node --targetname "iqn.1987-05.com.cisco:nss326:iscsi.myiscsi.f0c046" --portal 192.168.215.100:3260 --login<br>sdev=`lsscsi |tail -n1 |cut -c54-80 | awk '{ print $1 }'`<br>mount ${sdev}1 /backups<br> <br> <br>--- Examples for NFS:<br>Sample stateless_init steps for NFS (node=mynode|myIP, share=myshare):<br>mount -t nfs -overs=3 mynode:/myshare /backups<br> <br>Sample stateless_stop steps for NFS:<br>umount /backups </article> </main>