Carbonite Server Backup
Agent for Linux (64-bit)
Version 8.62.7474
Release Notes, July 17, 2019
__________________________________________________________________________
Contents
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	Licensing
3.3	Install
3.4	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. 2019.  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
This document contains release notes for the 64-bit Linux Agent 8.62.
The Linux Agent is installed on each 64-bit Linux computer that you want to protect. Using Portal or Windows CentralControl, 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 8.62.7474, May 8, 2019
Version 8.61.7472, January 16, 2019
Version 8.60.7469, March 23, 2018
1.2	Compatibility
Portal	Linux Agent 8.62 is supported with Portal version 8.50 and later.
Important: You can only register a newly-installed Linux Agent 8.62 to Portal version 8.30 or later. However, if a Linux Agent is already registered to a previous Portal version, you can upgrade the Agent to version 8.62 and it remains registered to Portal. To determine your Portal version, sign in to Portal and go to Need Help > About.	
Windows CentralControl	You can manage Linux Agent 8.62 with Windows CentralControl version 8.60 or later.
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. 
Because important security fixes and new features are available in Portal, we recommend using Portal to manage the Linux Agent instead of the legacy Windows CentralControl. 	
Linux	Linux Agent 8.62 is supported with Director version 8.00 and later. 	
1.3	Supported Platforms
This Agent is supported on the following 64-bit Linux platforms: 
·	SUSE Linux Enterprise Server 15
·	SUSE Linux Enterprise Server 12 (SP4)
·	SUSE Linux Enterprise Server 11 (SP4)
·	SUSE Linux Enterprise Desktop 11 (SP4)
·	openSUSE Leap 15.0
·	openSUSE Leap 42.3
·	openSUSE Leap 42.2
·	openSUSE Linux Enterprise Server 13.2
·	openSUSE Linux Enterprise Server 13.1
·	Red Hat Enterprise Linux Server 8.0
·	Red Hat Enterprise Linux Server 7 (Update 6)
·	Red Hat Enterprise Linux Workstation 7 (Update 4)
·	Red Hat Enterprise Linux Server 6 (Update 10)
·	Red Hat Enterprise Linux Workstation 6 (Update 9)
·	CentOS 7 (Update 6)
·	CentOS 6 (Update 10)
·	Oracle Linux Server 7 (Update 6)
·	Oracle Linux Server 6 (Update 10)	
·	Ubuntu Server 18.10
·	Ubuntu Server 18.04
·	Ubuntu Server 16.04
·	Ubuntu Server 14.10
·	Ubuntu Desktop 14.10
·	Ubuntu Server 14.04
·	Ubuntu Desktop 14.04
·	Ubuntu Server 12.04 LTS
·	Debian 9 (Update 8)
·	Debian 8.10
·	Debian 8.8
·	Debian 7.8
·	Debian 6.0.10
The Agent is supported with the following Linux file systems: ext2, ext3, ext4, XFS, GFS, ReiserFS, and JFS.
2	NEW FEATURES
You can now specify whether scheduled backups should automatically retry after failed backup attempts. You can specify the number of times that a backup should retry, and the number of minutes to wait before the next backup attempt.
Note: This option only applies to scheduled backup attempts. A job will not automatically retry after a failed ad-hoc backup.
Note: Backup job retry settings are available in Portal version 8.50 and later, but are not available in Windows CentralControl.
3	INSTALLATION NOTES
3.1	Installation Requirements
·	CPU: 64-bit processor (No support for Itanium processors.)
Note: Meet or exceed the hardware requirements of your operating system. 
·	RAM: Minimum of 2 GB
·	Disk space: The Agent requires at least 100 MB of free space for a new (fresh) installation. An upgrade may require more free space. If there is not enough disk space, the system will issue a message.
·	SELinux must be disabled on the system.
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	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.3	Install
The file name of the 64-bit Agent installation kit is: Agent-Linux-x64-8.62.7474.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 	ea0e06365c694969dd3cfb58ac9a5b98	
buagent 	43dbbd047b6d3aa5d1e48f06766739ed	
libcrypto.so.1.0.0 	3da01a423a02686067380a6b932bba3f	
libssl.so.1.0.0 	09f1d0375c8478df90f2c9cbcc882ea7	
VV	48c2f65c1b4dcc944e743dbcd827d591	
VVAgent	35d10d61e84035f38c116e7569853d43	
xlogcat	63c29a03576a35c985a5677fb9b9a9e5	

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.4	Upgrade
You can upgrade the following Linux Agent versions to version 8.62:
•	Version 8.6x
•	Version 8.50
•	Version 8.1x
•	Version 8.00
•	Version 7.50
•	Version 7.2x
To upgrade a previous Linux Agent version to version 8.62, first upgrade the Agent to version 7.2x.
4	FIXES and KNOWN ISSUES
4.1	Fixes
4.1.1	Fix in Version 8.61
Restores no longer fail with an Unexpected SIDF data error. The agent completes large restores successfully. (EV-30781, EV-30742, EV-30519, EV-25074)
4.1.2	Fixes in Version 8.60
The Agent has an updated SSL certificate. (EV-19835)
An error message no longer appears in the backup log when the Agent searches for a file that has been deleted from the system. (EV-8574/31359)
When the Agent tries to reconnect to a vault after a network interruption, failures are logged correctly as information instead of errors unless all reconnection attempts fail. (EV-17547)
4.2	Known Issues
Scheduled custom commands are not supported with this agent version. (EV-31488)
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 Director (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
·	Help menu in Windows CentralControl
5.2	Product Updates
Product updates are available from your service provider. 
5.3	Documentation
The following documentation is available for the Agent:
·	Agent for Linux and Oracle Plug-in Guide
·	Portal online help
·	Windows CentralControl Operations Guide
·	Windows CentralControl online help
·	Agent 64-bit for Linux release notes (this document)
All documentation is available from your service provider.