Upcoming MongoDB Upgrade Alert - Missing AVX Flag FAQ

We have received some questions regarding the planned MongoDB 6+ upgrade for JetBackup 5 and associated UI banner/alert. 

Will the lack of the AVX flags affect my restores?

No, The AVX flag is an instruction set flag required by our third-party MongoDB dependency (used as JB5's internal database) and doesn't affect backups or restore in any way.

Can AVX/AVX2 flags be added to my server? 

To clarify, the "AVX/AVX2" flags are a CPU instruction set and most modern CPU's should support it, but while the underlying CPU may support it, it's possible those flags aren't being exposed to the Virtual Machine.

There's some information on activating it for the VM here:

https://forum.proxmox.com/threads/cpu-with-avx-support.146138/
https://www.mongodb.com/community/forums/t/setting-up-mongodb-v5-0-on-ubuntu-20-core-dump-status-4-ill/120705/4
https://forum.proxmox.com/threads/avx2-and-avx-flags-on-vm.87808/

Please reach out to your datacenter or server administrator to see if the AVX/AVX2 flags can be enabled for your VM.

Once AVX/AVX2 CPU flags are available and listed in lscpu in the "Flags" field, the server will be "ready" for the future MongoDB upgrade and no further action would be required.

**NOTE: v5.3.11 is the last version to support CentOS 7, so you may be able to disregard this notice on CentOS 7 / CloudLinux 7 servers. The End of Life (EoL) for JetBackup 5 support for COS7/CL7 will proceed as planned on July 1st, 2024, in conjunction with the scheduled official EoL for these operating systems. JetBackup v5.3.11 will be our final scheduled update supporting CentOS7 and CloudLinux7.

I have all my servers under the same Hypervisor, why do some of my servers not have AVX enabled?

This is likely a difference in configuration for those VM's on the host hypervisor. The Host CPU flags aren't being exposed to the VM if you're using a CPU that supports AVX, but doesn't list the AVX flag in the VM's - but this should be configurable on the Hypervisor by referencing their documentation.

What happens if my CPU doesn't support AVX or I can't enable AVX for my VM?

If the AVX/AVX2 flags aren't exposed to the VM or they're unsupported by the CPU, a future JB5 update which includes a MongoDB upgrade won't be installed on the server but you could continue using the installed JetBackup 5 version as long as the license is active.

How do I disable the alert and UI banner?

To disable the alert banner, use the following command: touch /usr/local/jetapps/etc/jetbackup5/disable_avx_alerts.flag

We apologize for any inconvenience caused by the MongoDB third-party dependency changing their minimum system requirements. We greatly appreciate any feedback you have regarding this change - if you have further questions, please feel free to contact us or comment on the feature request

 

 

  • 1 Пользователи нашли это полезным
Помог ли вам данный ответ?

Связанные статьи

Email Notifications Are Not Being Sent

JetBackup 5 uses Notification Integrations to send Notifications based on the configured...

What are the level of Alerts in JetBackup 5?

JetBackup 5 now has only 3 Alert levels compared to JetBackp 4. All 3 levels will appear on the...

Create Destination Error: This destination path is already owned by other destination

On JetBackup 5, you may notice the following error when creating a destination that uses the same...

What does Incremental Backup mean?

Incremental backups will only copy files that have changed or are new since the last full backup....

Common Backup Job Exclude List for DirectAdmin Accounts

Information regarding how to exclude certain files/folders from a backup in JetBackup 5 can be...