This article explains how to install JetBackup 5 on RHEL 8, AlmaLinux 8, and CloudLinux 8 servers that do not support the AVX/AVX2 CPU flags. If the AlmaLinux 8 server does have AVX CPU flags, we also include instructions on upgrading to the MongoDB 8.0.X branch for the latest security and performance improvements.
New JetBackup 5 installations of 5.3.19.3, 5.4.0.4, and 5.4.1.1 may attempt to install the latest jetmongod package, which is based on MongoDB 8.0.26. MongoDB 8 requires AVX CPU support. If the server CPU does not support AVX, the local MongoDB installation may fail during a new installation of JetBackup 5.
I have JetBackup 5 installed on AlmaLinux 8 already. Do I need to do anything?
Existing installations will keep running as-is and will not fetch the jetmongod-8.0.26 package automatically, and will continue receiving JetBackup 5 product/software updates until the AlmaLinux 8 End-of-Life date. If you re-install JetBackup 5 on the same server or wish to use a newer MongoDB version, you may need to use this guide. Skip to the relevant "Recommended Actions" sections for instructions that apply to an existing AlmaLinux 8 and JetBackup 5 installation.
Symptoms
During a new JetBackup 5 installation, the installation may fail with an error similar to the following:
# cat /usr/local/jetapps/var/log/jetapps/20260611.203035_31546.log
<snipped>
****************************************************************************************
** Your CPU is missing the AVX instruction set flag required for the local jetmongod RPM installation. **
** Please enable AVX support on the CPU, then try again. **
****************************************************************************************
Recommendation:The JetApps installation log can be found under:
/usr/local/jetapps/var/log/jetapps/Cause
This occurs because the server CPU does not support the AVX instruction set required by the newer local jetmongod package.
On AlmaLinux 8-based systems, JetBackup 5 can still be installed with the jetmongod-4.4.X package. The MongoDB 4.4 branch does not require AVX/AVX2 CPU support, allowing JetBackup 5 to run locally on supported RHEL 8-based systems without AVX.
Resolution - For New Installations
If you are installing JetBackup 5 on RHEL 8, AlmaLinux 8, or CloudLinux 8 and encounter the AVX-related error above, install JetBackup 5 using the MongoDB 4.4 package.
Step 1: Install the JetApps Repository
bash <(curl -LSs https://repo.jetlicense.com/static/install)Step 2: Install JetBackup 5 with MongoDB 4.4
dnf install jetbackup5-base jetbackup5-{PANEL} jetmongod-4.4.* --enablerepo=jetapps,jetapps-{TIER}Replace {PANEL} with the correct JetBackup 5 package for your control panel. Additionally, replace jetapps-{TIER} with the proper release tier: release, rc, edge, or alpha.
jetbackup5-cpanelfor cPanel/WHMjetbackup5-directadminfor DirectAdminjetbackup5-pleskfor Pleskjetbackup5-linuxfor Linux
For example, to install on a cPanel & WHM server from the release tier:
dnf install jetbackup5-base jetbackup5-cpanel jetmongod-4.4.* --enablerepo=jetapps,jetapps-releaseRecommended Actions for Existing Installations:
1) Servers without AVX: Upgrade jetmongod 4.4.30 to 4.4.31
If you have an existing installation already using MongoDB 4.4.30, we recommend updating jetmongod to the latest available 4.4 package, as the ability to use either MongoDB 4.4 or 8.0 requires that the RPM dependency requirement is unchanged for JB5 packages.
Note: If you followed the instructions above, you can skip this section because you've already installed the latest MongoDB 4.4 version.
On RHEL 8, AlmaLinux 8, or CloudLinux 8 servers that are using MongoDB <4.4.31 and do not have AVX/AVX2 CPU support, use the following commands:
- Check your mongodb version:
rpm -qa | grep jetmongod - If you see jetmongod-4.4.30 or older, use this command to update and stay within the MongoDB 4.4 branch:
dnf update jetmongod-4.4.* --enablerepo=jetappsThis keeps the server on the MongoDB 4.4 branch while applying the latest available MongoDB package and security updates for that branch.
2) Servers with AVX: Upgrade from MongoDB 4.4 to MongoDB 8.0.X
If your AlmaLinux 8 server does support the AVX CPU flag, you may manually upgrade from the MongoDB 4.4 branch to the MongoDB 8.0 branch to use the latest MongoDB version available for JetBackup 5, including the associated MongoDB performance and security improvements that come with the 8.0.X branch.
You can use the following bash short-circuit command to check for the AVX flag in /proc/cpuinfo. If AVX is detected, the command will proceed with the jetmongod-8.0 update. If AVX is not detected, the update command will not run.
grep -m1 -qw avx /proc/cpuinfo && dnf update jetmongod-8.0.* --enablerepo=jetappsAfter the update completes, confirm that JetBackup and MongoDB services are running normally:
systemctl status jetbackup5d
systemctl status jetmongodIf the server does not have the AVX CPU flag, do not attempt to remove the grep portion to force an upgrade to jetmongod-8.0.
3) Keeping MongoDB Updated
After applying the update to 4.4.31+ or 8.0.26+, you can also place a cron job on the server to ensure jetmongod is updated automatically on AlmaLinux/CloudLinux 8. This is not necessary for AlmaLinux 9,10, Ubuntu 22,24 LTS, Debian 12,13 etc as normal JetBackup 5 package updates will include the requirement for a newer mongodb, when available.
The following command will create a `/etc/cron.d/jetmongod-branch-updates` file which will run every Sunday at 3:30AM Server Time.
cat > /etc/cron.d/jetmongod-branch-updates <<'EOF' SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin # If AVX is available, update MongoDB 8.0 branch. Otherwise, update MongoDB 4.4 branch. 30 3 * * 0 root if grep -m1 -qw avx /proc/cpuinfo; then dnf -y update 'jetmongod-8.0.*' --enablerepo=jetapps; else dnf -y update 'jetmongod-4.4.*' --enablerepo=jetapps; fi >> /var/log/jetmongod-branch-updates.log 2>&1 EOF chmod 644 /etc/cron.d/jetmongod-branch-updates
Alternative Option: Self-Hosted Remote MongoDB
If your server is running AlmaLinux 9 or newer or any other supported OS and your CPU does not support AVX/AVX2, the MongoDB 4.4 package cannot be used. Instead, configure JetBackup 5 to use a self-hosted remote MongoDB instance.
You may also use the remote MongoDB option if you prefer to host MongoDB separately from the JetBackup 5 server, even if you have AVX flags available for your CPU.
Please refer to the guide below for more information:
Installing and Configuring a Self-Hosted Remote MongoDB
Summary
- MongoDB 8.0.26 and newer require AVX CPU support. We made MongoDB 8.0 optional on AlmaLinux 8 due to some servers not having AVX flags.
- Servers without AVX/AVX2 may fail to install the local
jetmongod-8.0.26package during a fresh installation of JetBackup 5 on AlmaLinux 8. - On RHEL 8, AlmaLinux 8, and CloudLinux 8, install JetBackup 5 with
jetmongod-4.4.*to bypass the AVX flag requirement and use the Legacy 4.4 branch.
- Servers without AVX/AVX2 may fail to install the local
- After installing with MongoDB 4.4, keep up to date with the latest 4.4 package using
dnf update jetmongod-4.4.* --enablerepo=jetapps - If the server has AVX support, you could also manually upgrade an existing installation to
jetmongod-8.0.*to use the latest MongoDB 8.0 package. - On AlmaLinux 9 or newer without AVX/AVX2, use the Self-Hosted Remote MongoDB option instead or enable AVX/AVX2 flags on the CPU.
If you encounter any issues following this guide, please reach out to our Support Technicians via [email protected] and we'd be happy to assist.
