When the Secure Boot option is enabled in Linux systems the AOFO-L (snapshot) driver does not get loaded and the AOFO-L snapshot backups do not work.
Article ID: 100047953
Updated On:
Description
Error Message
The following messages can be seen on /var/log/messages file when driver load failure occurs on SecureBoot enabled systems.
Jun 23 21:41:30 rhel8 SYMBDSNAP_SDK[14035]: Driver is not loaded. Loading symbdsnap.
Jun 23 21:41:30 rhel8 SYMBDSNAP_SDK[14035]: Missing symbdsnap driver.
Jun 23 21:41:30 rhel8 SYMBDSNAP_SDK[14035]: Failed to open device: /dev/symbdsnapctl, errno: 2.
Jun 23 21:41:30 rhel8 SYMBDSNAP_SDK[14035]: Driver is not loaded. Loading symbdsnap.
Jun 23 21:41:30 rhel8 kernel: Lockdown: modprobe: Loading of untrusted modules is restricted; see man kernel_lockdown.7
Cause
On Redhat and SUSE Linux setups where SecureBoot is enabled and Linux snapshot backup driver is supported and installed. But the driver does not load because Backup Exec AOFO-L driver is proprietary licensed and not GPL license, also it is not signed for specific reasons. As the AOFO-L driver cannot load all backups on such systems work without snapshot technology and use traditional file backup methods.
Resolution
Workaround:
Disable SecureBoot on such systems for performing snapshot backups with the RALUS agent. If SecureBoot cannot be disabled then all Linux system backups would work with non-snapshot method.
All the backup jobs would complete successfully and no backup failures would occur on such systems even without snapshots method.
Veritas Technologies LLC has acknowledged that the above-mentioned issue is present in the current version(s) listed under the Product(s) Section of this article. Veritas Technologies LLC is committed to product quality and satisfied customers. This issue is currently under investigation by Veritas Technologies LLC. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns. For information on how to contact Veritas Sales, please see http://www.veritas.com.
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here
Issue/Introduction
Additional Information
