OpenText Server Backup
Linux Agent (64-bit) 
Version 9.41.1020
Release Notes, July 21, 2026
1 Overview
1.1  Release History
1.2  Compatibility
1.3  Supported Platforms
2 NEW FEATURES
2.1  New Features in Version 9.41
2.2  New Features in Version 9.40
3 INSTALLATION NOTES
3.1  Installation Requirements
3.2   Bare Metal Restore Requirements
3.3  Licensing
3.4  Install
3.5  Upgrade
4 FIXES and KNOWN ISSUES
4.1  Fixes
4.2  Known Issues
5 PRODUCT SUPPORT
5.1  Technical Support
5.2  Product Updates
5.3  Documentation

© 2026 Open Text
The release notes are governed by the Terms of Service found here. The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
1 Overview
The Linux Agent is installed on each 64-bit Linux computer that you want to protect. Using Portal, you can manage the agent, back up data to a vault, and restore data from the vault. A plug-in for protecting Oracle databases on Linux is also available.
1.1  Release History
Version 9.41.1020, February 3, 2026
Version 9.40.1011, December 5, 2024
1.2  Compatibility

Portal

To manage this Linux Agent version, we recommend using Portal version 9.50 or later.
Important: This agent version checks the public key of the Portal certificate when it tries to connect to Portal. If users are hosting their own Portal, we recommend updating the Portal certificate before new agents are registered to Portal or existing agents are upgraded from a version earlier than 8.63.

Windows CentralControl

We do not recommend managing agents using Windows CentralControl. To take advantage of new features and important security enhancements, we highly recommend using Portal to manage the Linux Agent. 
By default, the Linux Agent cannot connect to Windows CentralControl. If you must manage the Linux Agent using Windows CentralControl 9.41, please contact Support for assistance. 
Note: You cannot create Linux Bare Metal Restore jobs using Windows CentralControl. 
Important: Changing job configurations using Portal and Windows CentralControl alternately is not supported. Do not manage the same agent using both Portal and Windows CentralControl.

Director | This Linux Agent version is supported with Director version 8.73, 8.72, and 8.70.
1.3  Supported Platforms
The Agent is supported on the following 64-bit Linux platforms: 
•	Debian 13 (up to Update 2)
•	Debian 12 (up to Update 12)
•	Debian 11 (up to Update 11)
•	Debian 10 (up to Update 13)
•	openSUSE Linux 16 (up to Service Pack 0) ^1 ^2
•	openSUSE Linux 15 (up to Service Pack 6) ^1 ^2
•	Oracle Linux 10 (up to Update 1)
•	Oracle Linux 9 (up to Update 7)
•	Oracle Linux 8 (up to Update 10)
•	Oracle Linux 7 (up to Update 9)
•	Red Hat Enterprise Linux Server 10 (up to Update 1)
•	Red Hat Enterprise Linux Server 9 (up to Update 7)
•	Red Hat Enterprise Linux Server 8 (up to Update 10)
•	Red Hat Enterprise Linux Server 7 (up to Update 9)
•	Rocky Linux 10 (up to Update 1)
•	Rocky Linux 9 (up to Update 7)
•	Rocky Linux 8 (up to Update 10)
•	SUSE Linux Enterprise Server 16 (up to Service Pack 0) ^1
•	SUSE Linux Enterprise Server 15 (up to Service Pack 7) ^1
•	SUSE Linux Enterprise Server 12 (up to Service Pack 5) ^1
•	Ubuntu Server 26.04
•	Ubuntu Server 24.04
•	Ubuntu Server 22.04
•	Ubuntu Server 20.04
•	Ubuntu Server 18.04

Important: To enable BMR backups on a Linux system, Relax-and-Recover must be installed on the system before you install Agent version 9.41. The required Relax-and-Recover version depends on the Linux platform and version. See Bare Metal Restore requirements.
^1 This platform is not supported when the BTRFS file system is used.
^2 The Agent is supported on this platform, but BMR backups are not supported for an openSUSE 16.0 UEFI or openSUSE 15.6 UEFI system with a FAT16 EFI boot partition.
Because CentOS Stream is a pre-release branch of RHEL and has no long-term, stable versions, the Linux Agent is not supported on CentOS Stream.

The Agent is supported with the following Linux file systems: ext2, ext3, ext4, XFS, GFS, ReiserFS, and JFS. 
The BTRFS file system is not supported.
2 NEW FEATURES
2.1  New Features in Version 9.41
Security enhancements
Security enhancements have been added in this Linux Agent version.
2.2  New Features in Version 9.40
Agent managed using systemd
To ensure that the agent starts automatically when a Linux system starts, Linux agent services are now managed by systemd: the default init system in most modern Linux distributions.
In previous versions, agent services were managed using SysV-style init scripts. However, the initscripts package has largely been deprecated in favor of systemd's service management framework.
By using systemd, the agent benefits from improved dependency handling, faster boot times, and more consistent service management across distributions.
Security enhancements
Security enhancements have been added in this Linux Agent version.
3 INSTALLATION NOTES
3.1  Installation Requirements
•	CPU: 64-bit processor (No support for Itanium processors or IBM Power processors)
Note:   Meet or exceed the hardware requirements of your operating system. 
•	RAM: Minimum of 2 GB.
•	Disk space: We recommend at least 1 GB of disk space reserved on the installed path file system (/opt, by default). For an upgrade, we recommend 700 MB of disk space in addition to the current installed path size.
•	SELinux must be disabled on the system.
•	glibc runtime libraries version 2.16 or later. An agent installation will terminate if the required glibc version is not available on the server.
Note: You may see core dumps related to semaphore limits on the system. You can change the semaphore limits through the following kernel configuration parameters: 
Parameter /  Recommended Minimum Limit
semmni    /  128
Defines the number of semaphore identifiers in the kernel. 
This is the maximum number of unique semaphore sets that can be active at any one time. 
semmns    /  32000
Defines the maximum number of semaphores in the system. User processes include jobbed processes, plus all other semaphores required by other software. 
semmsl    /  250
Defines the maximum number of semaphores per identifier list. 
semopm    /  100
Controls the number of semaphore operations that can be performed per semop system call. 
3.2   Bare Metal Restore Requirements
To enable BMR backups, Relax-and-Recover must be installed on the Linux system before you install Agent version 9.41. The required Relax-and-Recover version depends on the Linux version on the system.
Relax-and-Recover version 2.9 is required for BMR backups on the following Linux versions:
•	Debian 13  ^3 
•	Debian 12 (Update 12)  ^3
•	OpenSUSE Linux 16  ^3 ^6 ^7
•	OpenSUSE Linux 15 (Service Pack 6)  ^3 ^5 ^6 ^7
•	Oracle Linux 10  ^3  ^4
•	Rocky Linux 10  ^3  ^4
•	Red Hat Enterprise Linux Server 10  ^3  ^4
•	SUSE Linux Enterprise Server 16  ^3 ^4 ^6 ^7
•	SUSE Linux Enterprise Server 15 (ServicePack 6 and later)  ^3 ^5 ^6 ^7
•	Ubuntu Server 26.04
Relax-and-Recover version 2.7 or 2.6 is required for BMR backups on other platforms where the Linux Agent is supported.

^3 Relax-and-Recover does not announce official support for this Linux platform. To enable BMR backups on this platform, you might need to apply workarounds, including the workaround for known issue 5105363.
^4 Before installing Linux Agent 9.41 on this platform, make sure that the libcrypt-compat package is installed on the system. See known issue 5104176.
^5 To prevent backup and restore issues on this platform, apply the workaround for known issue 5130544.
^6 To enable BMR restores of an upgraded SUSE or OpenSUSE system, the EFI boot partition must be FAT32. See known issue 5119813.
^7 To ensure successful BMR restores of SUSE and OpenSUSE systems, apply the workaround for known issue 5130544.

For more information about Relax-and-Recover, see the Linux Agent and Oracle Plug-in User Guide.
When you first run a BMR backup job, we recommend reserving a minimum of 1 GB of space in the root file system for the resulting .iso file.
When restoring a Linux server from a BMR backup, the destination machine must have:
•	At least 4 GB of RAM.
•	The same boot type (BIOS or UEFI) as the source system, and compatible hardware.
•	Hard drives should be the same size or larger than drives on the source system.
•	A connection to the network, so that it can communicate with the vault.
3.3  Licensing
Agent and Plug-in licenses are distributed automatically when the Agent connects to a vault (based on your license quota). To back up and restore data to or from a vault, you need a valid account, username and password. Contact your service provider to obtain the required information.
3.4  Install
The file name of the 64-bit Agent installation kit is: Agent-Linux-x64-9.41.1020.tar.gz
Note:   You can only install the 64-bit Linux Agent on a 64-bit system. You cannot install the 64-bit Linux Agent on a 32-bit system.
The Agent kit installs the following binary files:
Binary File | md5sum Value
AgtUpgd | f0f5124cb1cd7237c39a8f3eccd7b811
bmragent | d4ae44e75f66a6c03216abadc2ffd5b8
buagent | 78e638e9e828a7aee3d4998ab3089731
libcrypto.so.3 | 46b9d8120e9d093fdbe48cc01bb1f7e9
libevccl.so | e62bd2f7d2a525572105eed337481d38
libevclient.so | dabb6e336dab44c301d785fed943d78b
libevplugins.so | 9325f3be435c9216a5a667b37173713b
libevtrace.so | b66fce18d1e15befce8fbf6bf14f20e1
liblz4.so.1.9.4 | b9ca0f1bbd6c45699284a832c2f0f342
libprotobuf.so.32.0.5 | 73b74e2e5b665c454e427100fc9f0a68
libssl.so.3 | 044515c39f2a31b6ae7e3870b4cd35a4
libstdsoap2.so.2.8 | 5524a1032a9a8b0508417dfcc0fb47c8
VV | 0d960f108cc15d6c43526724899f5dd7
VVAgent | 1202a316957f35e903f433e9b678d59f
xlogcat | 64de73fecfec9a7fc9e7c35d2de0e5cf
set_language | 5e70eb593e5c8c9aedaf875e80d047a3
register | 25137079cb91786bf4f1134483a33817
bmrregister | 84d6da2b0cee3c2502c1e925c3bab294
accesscontrol | 3004f9335f66efd6cf05b93c51000fe9
xlogmore | dad783c2caa1fadad38c9389e8fa6c8f
To obtain md5sum values, issue the following commands. These commands are examples based on an Agent that has been installed in the default location (i.e., /opt/BUAgent).
 cd /opt/BUAgent
 md5sum *
3.5  Upgrade
You can upgrade to Linux Agent version 9.41 from version 9.40, 9.2x, 9.00 or 8.x.
To upgrade a previous Linux Agent version to version 9.41, first upgrade the Agent to version 8.x.
Note:   If Relax-and-Recover 2.5 was installed for use with Linux Agent 8.83, we recommend uninstalling Relax-and-Recover version 2.5 and performing a fresh install of Relax-and-Recover version 2.7 or 2.6 before upgrading the Agent to version 9.41.
4 FIXES and KNOWN ISSUES
4.1  Fixes
There are no fixes in Linux Agent 9.41 or 9.40. 
4.2  Known Issues
•	On recent Linux distributions such as Oracle Linux 10, Rocky Linux 10, and RedHat Enterprise Linux 10, the Linux Agent installation fails with the following error: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
WORKAROUND: Install the libxcrypt-compat package before installing the Linux Agent.
(5104176)
•	When you try to start a Linux system restored from a BMR backup, the system does not start and the following error appears: Failed to execute /usr/bin/systemd-tty-ask-password-agent: No such file or directory
WORKAROUND: Add the following line to the /etc/rear/local.conf file on the Linux system:
PROGS=( "${PROGS[@]}" systemd-tty-ask-password-agent )
(5105363)
•	When you try to uninstall Linux Agent 9.40 from a system with SUSE 16 or OpenSUSE 16, an insufficient privileges error occurs, even when you have sufficient privileges to uninstall the agent.
WORKAROUND: After installing the Linux Agent on a system with SUSE 16 or OpenSUSE 16, run the following command:
if grep -q 'ID_LIKE="suse' /etc/os-release && grep -q 'VERSION_ID="16' /etc/os-release; then
sed -i 's@^[[:space:]]*\[ -w ${init_dir} ] || ok=1@#&@' /opt/BUAgent/uninstall.sh;
chmod +x /opt/BUAgent/uninstall.sh;
fi
(5107256)
•	BMR backup and restore issues sometimes occur for SUSE or OpenSUSE systems with Relax-and-Recover 2.9.
WORKAROUND: Before running BMR backups on a SUSE or OpenSUSE system with Relax-and-Recover 2.9, run the following command:
rear dump | grep -E "^[[:space:]]*(OS.*|ARCH)=" | sed 's/^ //; s/"//g; s/RedHatEnterpriseServer/RedHat/g' > /etc/rear/os.conf
(5130544)
•	On an Ubuntu 22.04 BIOS-based system running Relax-and-Recover version 2.9, the Agent cannot create a BMR ISO file. 
WORKAROUND: 
1. Get the DNS server IP address by running the following command:
resolvect1 status | grep "DNS Servers"
2. Append the following two lines to the /etc/rear/local.conf file:
NAMESERVER=( "<the DNS IPs from step 1>" )
USE_RESOLV_CONF=( "no" )
(5133656)
•	An OpenSUSE or SUSE UEFI system that was upgraded from a previous operating system version or update might not start after a BMR Restore.
WORKAROUND: The EFI boot partition must be FAT32 for SUSE UEFI and OpenSUSE UEFI new distributions and updates. If you upgrade from a previous SUSE/OpenSUSE release or update with a FAT16 boot partition, convert the boot partition to FAT32. 
(5119813)
•	The Linux agent does not start on a system where SELinux is enabled. 
WORKAROUND: Disable Selinux on the Linux system. (4223240)
•	When you restore a Linux system from a BMR backup, file systems that are mounted in subdirectories of /media, /run, /mnt and /tmp are not recreated. This is due to an exclusion in Relax-and-Recover (rear). 
WORKAROUND: If a file system is mounted in a subdirectory of /media, /run, /mnt or /tmp, you must manually recreate and remount the file system during or after the system recovery. We do not recommend mounting local file systems subdirectories of /media, /run, /mnt or /tmp. (2453797/EV-97864)
•	When you try to recover a Debian, Ubuntu, SUSE or OpenSUSE Linux system with UEFI firmware from a Bare Metal Restore (BMR) backup to a different server or virtual machine, the recovery fails with kernel-related error messages. This issue is due to a problem in Relax-and-Recover (rear) version 2.6.
WORKAROUND: On each Debian, Ubuntu, SUSE and OpenSUSE Linux system with UEFI firmware, upgrade Relax-and-Recover to version 2.7. Run the BMR backup job for each system to create a new ISO file for recovering the system. (2456098/EV-92806)
•	When you try to recover a Red Hat 9 or Oracle Linux 9 system from a Bare Metal Restore (BMR) backup to a different server, an error might state that you need to recreate the physical volume at the disk layout recreation stage. This is a known issue for Red Hat 9 when the new "use_devicesfile" lvm2 feature is enabled. For more information, see information from Red Hat for Bug 1965941. 
WORKAROUND: Turn off the "use_devicesfile" feature by modifying the /etc/lvm/lvm.conf file, set the "use_devicesfile=0" flag (remove the '#' in front), and run the BMR backup job again to create a new iso file for restoring the system. If you do not want to disable this feature, you can manually recreate the lvm PV if the physical volume recreation error occurs. For more information, please contact Support. (2456425/EV-86190)
•	This Linux Agent version cannot connect to Windows CentralControl without a configuration change. If you must manage the Linux Agent using the legacy Windows CentralControl, please contact Support.
Note: To take advantage of new features and important security fixes, we highly encourage using Portal to manage the Linux Agent.
•	If you uninstall the Agent and reinstall it with a different Relax-and-Recover path, the old Relax-and-Recover path is restored if you re-register the Agent to the same vault and synchronize jobs. A BMR job could fail to create an .iso file in this case. 
WORKAROUND: Run the bmrregister script after re-registering to the vault. (2461921/EV-44185)
•	When restoring an Oracle Linux 7 UEFI-based system from a BMR backup, the system might shut down during the recovery if you select the default "no secure boot" option in Relax-and-Recovery.
WORKAROUND: When restoring an Oracle Linux 7 UEFI-based system from a BMR backup, select the "Relax-and-Recover (Secure Boot)" option. (2413346/EV-55410)
•	If a job is seeded to a vault using Agent version 7.34 or earlier and reseeded using Agent version 7.50 or later, the vault storage size for the job data cannot be reduced. (2470271/EV-25740)
•	When you re-register an Agent with a vault, backup jobs that never ran may not be brought to the Agent. The jobs still exist on the vault, so you cannot create jobs with the same names.
WORKAROUND: After an Agent re-registration, delete jobs with no safesets from the vault before creating jobs with the same names. (2477186/EV-13227)
•	When only permissions have changed in a file in the ReiserFS file system, permissions are backed up successfully but the deltized size may appear as 0 bytes in the Backup Summary report. (2475368/EV-13683)
•	When a backup is run from the Linux Bash shell, it may end with the following message: User defined signal 2 
WORKAROUND: Trap the signal, which is used to terminate running threads, by beginning the backup script with the following line: trap " USR2 
•	If your backup selection contains hardlinks outside of your selection, you may receive a backup log warning indicating that some hard links related to these file(s) were not selected and have not been backed up. This may occur even if you exclude these hardlink files. To avoid this warning, include all the hardlink files sharing the same inode. (19795)
•	When you perform a complete system restore (DR), make sure that there is sufficient disk space for the creation of large recovery logs from the Agent (and other possible logging or auditing from the operating system). File-level logging on a setup containing a large file system may generate a large log, which may fill up the available or allocated disk space. If the logs are on the same partition as the root file system, this may prevent the OS from booting. (19353)
•	An NFS backup job for a mounted file system may fail if the NFS mount is disconnected at run time. The error messages for this failure may not explain that the problem is related to NFS. (19215)
•	When you restore a very large number of files to an alternate location, you may run out of inodes for the file system. This may stop the restore process from responding. If you kill the VV process, defunct processes may remain and truncated restore logs may result. The logs may indicate that there is no space left on the device, but this may not be true. Because each file consumes an inode, you may not be able to restore additional files (regardless of how much space is available). 
Recommendation: Allocate more inodes for the destination file system. (18967)
•	The command-line log viewer, xlogcat, uses the default language that you select during installation unless the LANG environment variable indicates a different supported language. For example, if German (de-DE) is your selected language, but your LANG value specifies U.S. English (LANG=en_US.utf8), xlogcat may display the log in English. You can override this using the "-l" (lowercase L) command-line parameter, or by adjusting the LANG variable. (18941)
•	For a backup or restore task on an NFS system to succeed, you need permissions to read, write and create files and directories on the mounted Network File System. This includes the remote system allowing operations for an anonymous user. A good test is to try it from the command line first. If you cannot read/write/create files or directories on NFS manually, the Agent backup and restore may not work. This issue applies to all Linux platforms.
•	Linux systems may be configured with strong firewall settings (IP tables) that may block communication between the Agent and Portal or Windows CentralControl.
The following ports are used by default for the Agent:
  * 808, 8031 (inbound) - VVAgent control by Windows CentralControl
  * 8086, 8087 (outbound) - buagent registration and control by Portal
  * 25 (outbound) - email notification
  * 2546 (outbound) - VV backup, restore, and synchronization with the Vault
To allow management of the Agent by Windows CentralControl, you may open the firewall with a rule similar to this:
  iptables --append <chain-name> -p tcp -m tcp --dport 808 --syn -j ACCEPT
This rule may be made permanent in the normal way for your distribution.
•	Certain file systems and directories may be excluded from backups, including the /dev (device) directory (including the devpts file system at /dev/pts), /boot directory, /var/run directory, and the proc file system (usually at /proc). In Linux kernel version 2.6, the sysfs file system may represent the system hardware devices and drivers (usually at /sys). This may also be excluded from backups. 
Note:   On a complete system backup, /dev and /proc directories are not backed up. 
The Linux Agent only protects these locations under their default names. These files must be restored to an alternative location and replaced manually if necessary, as automatic replacement may leave the operating system in an unusable state.
•	When restoring Linux system files, the boot loader should be reconfigured to find the restored operating system files and kernel in their current positions on the hard drive. When using GNU GRUB (http://www.gnu.org/software/grub/), follow the instructions from the GRUB user manual for installing GRUB natively: http://www.gnu.org/software/grub/manual/grub.html#Installation
For other boot loaders, refer to the manual provided by your vendor.
By default, chkconfig may not include VVAgent in the list of services that it manages. If you add VVAgent to chkconfig, the default run levels become 3 and 5. 
Recommendation: Use 3 and 5 as default run levels for starting the VVAgent script. (8321)
5 PRODUCT SUPPORT
5.1  Technical Support
Contact information for your provider is available through the Need Help button in Portal.
5.2  Product Updates
Product updates are available through your provider.
5.3  Documentation
The following documentation is available for this product: 
•	Server Backup online help and knowledge base
•	Release notes (this document)
•	User Guide