Carbonite Server Backup
Linux Agent (64-bit) 
Version 9.20.1004
Release Notes, August 26, 2022
1 Overview
1.1  Release History
1.2  Compatibility
1.3  Supported Platforms
2 NEW FEATURES
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

© Carbonite Inc. 2022. All Rights Reserved.
The release notes are governed by the Terms of Service found at https://www.carbonite.com/terms-of-use/carbonite-general-enterprise-terms-of-service. Carbonite, at its sole discretion, reserves the right to modify or revoke these Release Notes at any time, 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.
Important: Beginning in version 9.20, only a 64-bit version of the Linux Agent is available. Starting on June 1, 2022, Carbonite only offers best effort support for 32-bit Linux Agent versions. On June 1, 2023, the 32-bit Linux Agent will reach its end of life.
1.1  Release History
Version 9.20.1004, August 26, 2022
1.2  Compatibility
Portal	To manage this Linux Agent version, we recommend using Portal version 9.00 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.20, 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.62, 8.61 and 8.56.	
1.3  Supported Platforms
The Agent is supported on the following 64-bit Linux platforms: 
•	CentOS 7 (up to Update 9) 1
•	Debian 11 (up to Update 3)
•	Debian 10 (up to Update 12)
•	openSUSE Linux 15 (up to Service Pack 4) 2
•	Oracle Linux 9
•	Oracle Linux 8 (up to Update 6)
•	Oracle Linux 7 (up to Update 9)
•	Red Hat Enterprise Linux Server 9
•	Red Hat Enterprise Linux Server 8 (up to Update 6)
•	Red Hat Enterprise Linux Server 7 (up to Update 9) 
•	SUSE Linux Enterprise Server 15 (up to Service Pack 4) 2
•	SUSE Linux Enterprise Server 12 (up to Service Pack 5) 2 3
•	Ubuntu Server 22.04
•	Ubuntu Server 20.04
•	Ubuntu Server 18.04
•	Ubuntu Server 16.04
1 The Linux Agent will be supported on CentOS 7 until its end of support on June 30, 2024. Because CentOS Stream is a pre-release branch of RHEL and has no long-term, stable versions, the Linux Agent will not be supported on CentOS Stream.
2 This platform is not supported when the BTRFS file system is used.
3 The Agent is supported on this platform, but BMR backups are only supported for BIOS-based systems (not UEFI-based systems).	
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
Updated supported platforms
The Agent is now supported on Oracle Linux 9, Red Hat Enterprise Linux Server 9 and Ubuntu Server 22.04.
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 version 2.6 must be installed on the Linux system before you install Agent version 9.20. For more information, see the Linux Agent and Oracle Plug-in User Guide . 
Note: Relax-and-Recover version 2.5 was required for BMR backups with Linux Agent 8.83. 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.6 before upgrading the Agent to version 9.20.
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.20.1004.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 	e6fd4959845fa3071d4dfd8656753253	
bmragent	d56d2af95f632e4d8364f8288701142b	
buagent 	bf05e3958e90c7fb01c007b6e451423c	
libcrypto.so.1.0.0 	dfe23879fe262cfc342ec3d410a767d5	
libevccl.so	d17b3e86f9d97480698edf0c0d661054	
libevclient.so	b53f2d74a8c85942dc44f7dbc44be6a5	
libevplugins.so	24ea9219bea61e5ad381113687e1177d	
libevtrace.so	de61be5c3944675d2bc3cf2cd482b5e3	
liblz4.so.1.3.0	7bc3a9a830d28e8973429dc9a0be7a5f	
libprotobuf.so.15.0.1	d8c195898a06e209074d5ea761653ddf 	
libssl.so.1.0.0 	d7cc34eb4c22dc7faccf909031b16782	
libstdsoap2.so.2.8	0da0a5f9c3e0aa9a56191156b33639b5	
VV	c90f800920a4eab2aa8b21c4705873d5	
VVAgent	d03106c5c90638466121acbe36547fb6	
xlogcat	258f7f7f074642fb8a529691ef11fa2c	
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 Linux Agent version 8.x to version 9.20.
To upgrade a previous Linux Agent version to version 9.20, 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.6 before upgrading the Agent to version 9.20.
4 FIXES and KNOWN ISSUES
4.1  Fixes
There are no fixes in this version. 
4.2  Known Issues
•	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. (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. (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. (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. (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. (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 Agent for Linux (64-bit):
•	Server Backup online help (https://onlinehelp.evault.com) and knowledge base (http://support.carbonite.com/evault)
•	Release notes (this document)
•	User Guide