IBM QRadar

 View Only

 Qradar Update on Azure Hosts

Paulo Silva's profile image
Paulo Silva posted Wed March 19, 2025 11:09 AM

Hello, soon I will have to perform an update of QRadar from version 7.5 UP7 to version UP9. However, the environment is hosted on Azure, and a series of questions have arisen during the planning process.

We took these questions to support, but it was recommended that we contact the Expert Labs team before proceeding. Before doing so, I would like to know if you have already encountered any doubts/issues that I will list in this post:

  1. Regarding the Secure Boot option, it appears that this option is natively enabled on virtual machines, and we cannot disable it as it is a prerequisite for Azure service compliance. What impact could this option have during the upgrade?

  2. We have some external disks mounted to store environment backups. After the upgrade, will QRadar automatically reconnect to these disks, or will we need to intervene manually?

  3. In our environment, the data disk and the operating system disk are separate. After the upgrade, is the script capable of remounting these disks automatically?

Karl Jaeger's profile image
Karl Jaeger IBM Champion posted Thu April 10, 2025 10:07 AM

Paulo,

trying to get this answered. Sorry for the late reply.

  1. This is a no brainer. Just go ahead as it is greyed out anyway. Never got into a problem with this security type option so far.
  2. I just answered a question regarding extra disks mounted. MS azure will not behave differently regarding addon mounts. Pls have a look at https://community.ibm.com/community/user/discussion/disk-storage-not-accessible-error
  3. in general the upgrade will not touch your environment while upgrading. The 100$ question is how you have mounted your disks in the 1st place. If you defined your fstab during initial setup youll be fine. If you manipulated your disk environment afterwards using CLI Qradar wont know about and use standard mount points during upgrade. In this case you have to manually adjust after upgrade again. Note: during standard setup there is an option for customizing ptn setup. This should be used rather than CLI in order to make your config permanent. All user scripts in your RHEL environment will be ignored if not defined in your database and admin config settings.

Related Content