Differences

This shows you the differences between two versions of the page.

--- public:ahsayubs [2019/08/22 15:39]
ronnie.chan
+++ public:ahsayubs [2022/11/28 10:57] (current)
kirk.lim
@@ Line 1: / Line 1: @@
 ====== AhsayUBS ======
+Last modified: 2019/08/22 (Note: Content written for AhsayUBS v7+v8, and still generally apply to latest product release)
 AhsayUBS (Ahsay Universal Backup System) is a low price yet powerful operating system for a backup appliance to operate with. It has been optimized for [[public:ahsaycbs|AhsayCBS]] to run smoothly on it. With AhsayUBS, you can get AhsayCBS deployed onto a bare server hardware within a few minutes.
@@ Line 114: / Line 116: @@
 ===== Setup Overview =====
 The process to setup AhsayUBS firmware onto a machine is done in four stages:
-  - Installer Image Deployment, installation to physical server. \\ \\ Deploys Ahsay Universal Backup System Installer image (ubs-installer.img) on a removable USB storage device. \\ \\
-  - Firmware Installation/Upgrade. \\ \\ Install/upgrade Ahsay Universal Backup System Firmware onto the machine. \\ \\
+. Installer Image Deployment, installation to physical server.
-  - Ahsay Universal Backup System Configuration. \\ \\ Configure the Ahsay Universal Backup System Firmware (FreeBSD).  \\ \\
+Deploys Ahsay Universal Backup System Installer image (ubs-installer.img) on a removable USB storage device.
-  - Backup Server Configuration. \\ \\ Configure the Backup Server, Redirectors, or Replication Server (AhsayCBS)
+. Firmware Installation/Upgrade.
+Install/upgrade Ahsay Universal Backup System Firmware onto the machine.
+. Ahsay Universal Backup System Configuration.
+Configure the Ahsay Universal Backup System Firmware (FreeBSD).
+. Backup Server Configuration.
+Configure the Backup Server, Redirectors, or Replication Server ([[public:ahsaycbs|AhsayCBS]])
 There are different software/hardware requirements for each stage. Please ensure that all the requirements are met before deploying the AhsayUBS to the machine.
+==== AhsayUBS Firmware ====
+AhsayUBS Firmware is based on a customized version of FreeNAS firmware with AhsayCBS bundled and is specifically optimized to run AhsayCBS. Apart from AhsayCBS, it also contains some basic features that system administrator require, e.g. SSH and system monitoring tools.
+==== AhsayUBS Storage Concepts ====
+The AhsayUBS installer will automatically detect all available local hard disk(s) during the installation progress. The selected hard disk(s) will be partitioned to form “System Storage”. Several RAID devices will be created on the “System Storage”:
+. GPT Boot (GPBT)
+. Operating System Framework (OSFW)
+. Firmware Module Framework (FMFW)
+. Logical Storage Framework (LSFW)
+The GPBT, OSFW and FMFW volume are configured as RAID1 mirror in UFS file system to form the core system.
+The LSFW software RAID device:
+  * Supports JBOD, RAID0, RAID1 and RAID5 in UFS format for old version of AhsayUBS.
+  * Supports RAID0, RAID1 and RAIDZ in ZFS format for the new version of AhsayUBS (The raid type depends on the number of hard disks installed and selected during AhsayUBS installation, for RAID0 the minimum number of disks is required is 1 [data loss for any one failed drive], for RAID1 and RAIDZ the minimum number of disks required is 2 [data loss if more than one failed drive]).
+These volumes are named “System Storage”. The OSFW, FMFW devices will be created on the Unix File System (UFS). The firmware configuration files will be stored on OSFW and the AhsayCBS configuration files and backup data will be stored on LSFW.
+<WRAP tip>
+**HARDWARE RAID?** For systems employing hardware RAID, you are limited to one hardware RAID presentable to the server at time of AhsyUBS installation (you may add additional hardware RAID volumes, after AhsayUBS new installation is completed.). If you have more than one hardware RAID volumes, then you will be prevented from installation. For such systems, you will not be presented with choice of RAID settings at time of AhsayUBS installation (you only present one volume).
+</WRAP>
+If the LSFW file system runs out of disk space, extra storage can be added to the system by either:
+. Adding a new block device to the system hardware.
+. Creating an iSCSI connection to a remote storage server.
+The added block devices will be partitioned and formatted to form "Modular Storage (ZFS + ZIL)".
+The previously supported additional storages: 'Modular Storage (ZFS)', 'Expandable Storage (ZFS)' and 'Optional Storage (UFS);' will also be listed in the summary page. However, only removal of those additional storage is allowed.
+Expandable Storage volumes (ZFS) can no longer be created.
+There are three types of Additional Storage:
+. Modular Storage (ZFS / ZFS+ZIL)
+can be created by one or more local block device to form a volume either in RAID0, RAID1 or RAIDZ (is dependent on the number of hard disks used to form the volume). Since this AhsayUBS version, the underlying ZPOOL will be added with a ZIL layer (ZIL = ZFS Intent Log).
+.	Expandable Storage (ZFS) [legacy]
+created in the former AhsayUBS versions with a hardware RAID volume or an iSCSI initiator session connected to this AhsayUBS machine. A RAID0 ZFS filesystem will be formed for each of the Expandable Storage. It is for supporting the old migrated AhsayUBS only and cannot be created in this version of AhsayUBS.
+.	Optional Storage (UFS) [legacy]
+called “Optional Labelled Device” on earlier AhsayUBS versions. It is for supporting the older migrated AhsayUBS installations only and cannot be created in this version of AhsayUBS.
+By configuring the AhsayCBS, the “Additional Storage” can be used as additional storage for storing server configuration files and backup data.
+Note:
+Minimum size 500GB is required for the AhsayUBS Backup System block devices (i.e. System Storage and Additional Storage). Otherwise, the added block device will not be allowed for fail disk replacement and additional storage.
+The AhsayUBS WebAdmin page, under [Storage] > [Summary] will show the overview of the volumes created on AhsayUBS. \\ {{public:ahsay_wiki_software_ubs_10.png?640}}
+----
+===== Important Notice =====
+AhsayUBS provides console access to the “System Management Console” by connecting a keyboard and a VGA monitor to the physical machine.
+To prevent unauthorized access to the AhsayUBS System Management Console, it is advised to change the default AhsayUBS administrator password.
+----
+===== System Requirements =====
+This section describes the system requirements for the Installer Image Deployment, Backup System firmware Installation/ Upgrade, Backup System and Backup Server Configuration.
+==== Backup System Requirements ====
+The selected machine must meet the following requirements:
+  * CPU: At least 1 CPU that is FreeBSD i386 / amd64 compatible.
+  * Memory Size: 4 GB minimum. If the AhsayUBS installer detects the machine is installed with less then 2GB RAM the installation or upgrade process will be aborted.
+  * Disk Storage Space: 1000GB per disk minimum. (If your users will store backup data onto the AhsayUBS server, you should plan for the largest drives allowable by your system, as future drive upgrade will be difficult.)
+  * Network interface card (NIC): At least 1 NIC that is FreeBSD 11.2 i386/amd64 compatible.
+  * Motherboard: If the motherboard supports Unified Extensible Firmware Interface (UEFI) standard. The boot mode **must be set to BIOS boot manager** and the AhsayUBS installed hard disk specified as the first the boot device.
+For production AhsayUBS servers configured with ZFS volume(s). It is strongly recommended to:
+. Install AhsayUBS on a 64bit machine.
+. Install at least 8 GB RAM, as ZFS volumes require relatively large amount of memory to run. The amount of memory required is dependent on the size of the ZFS volume and the amount of I/O activity.
+<WRAP indent>
+=== Firewall Settings ===
+Please ensure you have updated your network firewall settings to allow network traffic through the following ports to your AhsayUBS server:
+^ Port ^ Description ^
+| 80 | HTTP port for incoming backup and restore traffic, browsing the AhsayCBS web interface. [Port number can be customized] |
+| 443 | HTTPS port for incoming backup and restore traffic, browsing the AhsayCBS web interface. [Port number can be customized] |
+| 25 | Outgoing SMTP port to the SMTP server. |
+| 8080 | AhsayUBS web administration console. [Port number can be customized] |
+| 111 | Port Mapper |
+| 1058 | Mount Port ** Required for Run Direct on AhsayCBS |
+| 2049 | Port for NFS Service |
+| Any incoming TCP port(s) | Any incoming TCP port(s) used by previous version of replication receiver(s), e.g. 9444, 9445… |
+=== AhsayUBS Processor Configuration ===
+AhsayUBS supports up to a maximum of 32 virtual processors for both i386/amd64 compatible CPU’s.
+In order to comply with the maximum supported virtual processors limit on FreeBSD, the system administrator should verify the number of virtual processors enabled on the AhsayUBS machine and apply the correct processor setup on the machines BIOS before proceeding with AhsayUBS installation or upgrade.
+The maximum number of virtual processors is calculated as:
+<WRAP prewrap><code>
+ (No. of sockets) * (No. of cores per processor) * (Hyper Threading).
+</code></WRAP>
+The following are examples of processor configurations.
+<WRAP indent>
+== Supported Processor Configurations ==
+. One Socket, Dual-Core Intel CPU, Hyper Threading Enabled
+<WRAP prewrap><code>
+(1) * (2) * (2) = 4 virtual processors
+</code></WRAP>
+. Two Sockets, 6-Core Intel CPU, Hyper Threading Enabled
+<WRAP prewrap><code>
+(2) * (6) * (2) = 24 virtual processors
+</code></WRAP>
+. Two Sockets, 8-Core Intel CPU, Hyper Threading Enabled
+<WRAP prewrap><code>
+(2) * (8) * (2) = 32 virtual processors
+</code></WRAP>
+. Four Sockets, 4-Core Intel CPU, Hyper Threading Enabled
+<WRAP prewrap><code>
+(4) * (4) * (2) = 32 virtual processors
+</code></WRAP>
+== Non-supported Processor Configurations and workarounds ==
+. Two Sockets, 12-Core AMD CPU, Hyper Threading Enabled
+<WRAP prewrap><code>
+(2) * (12) * (2) = 48 virtual processors
+</code></WRAP>
+It is recommended the number of cores per CPU be set at 8 on the machine BIOS:
+<WRAP prewrap><code>
+(2) * (8) * (2) = 32 virtual processors
+</code></WRAP>
+. Four Sockets, 8-Core Intel CPU, Hyper Threading Enabled
+<WRAP prewrap><code>
+(4) * (8) * (2) = 64 virtual processors
+</code></WRAP>
+It is recommended that Hyper Threading is disabled on both CPU’s on the machine BIOS:
+<WRAP prewrap><code>
+(4) * (8) * (1) = 32 virtual processors
+</code></WRAP>
+. Four Sockets, 10-Core Intel CPU, Hyper Threading Enabled
+<WRAP prewrap><code>
+(4) * (10) * (2) = 80 virtual processors
+</code></WRAP>
+It is recommended that Hyper Threading is disabled on both CPU’s and the number of cores per CPU be set at 8 on the machine BIOS:
+<WRAP prewrap><code>
+(4) * (8) * (1) = 32 virtual processors
+</code></WRAP>
+</WRAP>
+</WRAP>
+<WRAP important>
+If AhsayUBS is installed on a machine where the number of virtual processors configured exceeds the maximum supported value of 32. This will cause FreeBSD to become unstable and crash, which could result in data corruption on AhsayCBS.
+</WRAP>
+==== Installer Media Requirements ====
+AhsayUBS installer is available in img and ISO formats.
+  - The img format is used for deployment on a USB flash drive (minimum 2GB), for installation to a physical server. \\ \\
+  - The ISO format is used for VMware installation/upgrades only; and is not for use on deployment to CD/DVD media.
+==== Installer Deployment ====
+For physical server deployment, please ensure the following requirements are met before deploying Ahsay™ Universal Backup System image to a USB flash drive.
+For physical server deployment, please ensure the following requirements are met before deploying Ahsay™ Universal Backup System image to a USB flash drive.
+  - The USB flash drive should meet the minimum 2GB storage size requirements. \\ \\
+  - Previous data stored on the USB flash drive should be backed up properly. Once the deployment process begins, all data on the USB flash drive will be OVERWRITTEN. \\ \\
+  - To avoid selecting the incorrect drive for deployment, it is advised to remove all other USB storage devices such as USB portable hard disk and other USB flash drive.
+==== AhsayUBS Firmware Installation / Upgrade ====
+Please ensure the following requirements are met before installing / upgrading AhsayUBS Firmware:
+  * Connect a VGA Monitor and a keyboard to the target machine. \\ \\
+  * Make sure that there are local block devices (e.g. “ide”, “scsi” disk volumes) installed in the machine. \\ \\
+  * The new installation process will destroy all the data in the local block devices installed in the machine. To protect the data in some of the local block devices, it is recommended to remove them before the installation of AhsayUBS Firmware. \\ \\
+  * The upgrade process requires the existing hardware/software RAID storage configuration to be healthy.
+<WRAP important>
+The upgrade process will not be able to continue on system configuration with one or more DEGRADED RAID devices.
+</WRAP>
 ----
@@ Line 130: / Line 320: @@
   * [[public:5237_faq:how_to_install_the_latest_patch_set_for_ahsayubs_version_7|How to install the latest patch set for AhsayUBS v7?]]
+  * [[public:8026_faq:how_to_install_the_latest_patch_set_for_ahsayubs|How to install the latest patch set for AhsayUBS v8?]]
 ===== Issues =====
   * [[public:5064_issue:cannot_download_ahsayobm_install_file_for_linux_unix_platforms_via_the_ahsaycbs_console_ahsaycbs_installation_on_ahsayubs|Cannot download AhsayOBM install file for Linux / Unix platforms via the AhsayCBS console (AhsayCBS installation on AhsayUBS)]]

User Tools

Site Tools

Differences

Page Tools