[ALL VERSIONS] Veeam Agent for Linux

Backup agent for Linux servers and workstations on-premises or in the public cloud

[ALL VERSIONS] Veeam Agent for Linux

Veeam Logoby PTide » Tue Dec 13, 2016 2:46 pm 1 person likes this post

Veeam Agent for Linux

GA build: 1.0.0.944 (December 13, 2016)
Latest build: 1.0.1.364 > Update 1 (May 22, 2017)

Available in Veeam Repository > link
Latest repository installation packages > Download page

GPG keys > http://repository.veeam.com/keys/

Previous versions (NOT SUPPORTED):

• BETA2 (build 1.0.0.678) on August 30 > BETA2 thread
• BETA1 (build 1.0.0.499) on June 14 > BETA1 thread

System Requirements, Known Issues, Installation and Upgrade > Release Notes
All user guides, manuals and other documentation in multiple formats > Veeam Help Center

How To Submit A New Issue
PTide
Veeam Software
 
Posts: 3237
Liked: 269 times
Joined: Tue May 19, 2015 1:46 pm

System Requirements

Veeam Logoby PTide » Tue Dec 13, 2016 2:48 pm 1 person likes this post

Hardware
CPU: x86 processor (i386 or later)
Memory: 1 GB RAM
Disk Space: 100 MB free disk space for product installation.
Network: 10 Mbps or faster network connection to a backup target.
System firmware: BIOS or UEFI.

OS

Linux kernel 2.6.32 or later is required.

Both 64-bit and 32-bit versions of the following distributions are supported:
• Debian 6 - 8
• Ubuntu 10.04 - 16.10
• CentOS / Oracle Linux / RHEL 6 - 7
• Fedora 23 - 25
• openSUSE 11.3 - 13.2
• openSUSE Leap 42
• SLES 11 SP2 – 12 SP2

File systems

All file systems available in the supporter distributions are supported except BTRFS, ZFS, and NSS

Software

Protected computer must have the following components installed:
• dkms*
• gcc
• make
• perl
• kernel-headers*
• kernel-devel*
• libudev
• libacl
• libattr
• lvm2
• libfuse
• efibootmgr (for UEFI-based systems)

* These packages may require special handling, check Known Issues section below for more details.

Backup Target

Backup can be performed to the following disk-based storage:
• Local (internal) storage of the protected computer (not recommended).
• Direct attached storage (DAS), such as USB, eSATA or Firewire external drives.
• Network Attached Storage (NAS) able to represent itself as SMB (CIFS) or NFS share. Requires cifs-utils or nfs-utils packages to be installed, depending on what type of a network storage is used.
• Veeam Backup & Replication 9.5 Update 2 or later backup repository (except DataDomain DDboost, HP StoreOnce, Cloud, and scale-out backup repositories).
PTide
Veeam Software
 
Posts: 3237
Liked: 269 times
Joined: Tue May 19, 2015 1:46 pm

Known Issues

Veeam Logoby PTide » Tue Dec 13, 2016 2:50 pm 1 person likes this post

General
• User interface may appear unreadable in some terminal programs due to using incorrect symbols for pseudographics. To fix the issue, do the following:

Putty: execute
Code: Select all
echo export "NCURSES_NO_UTF8_ACS=1" >> ~/.bashrc

Kitty: select Allow ACS line drawing in UTF checkbox.

Backup
• Backup to CIFS is not supported for x86+PAE systems.
• Network shares (both CIFS and NFS) cannot be selected in with backup mode, including file-level backup. Only block devices are supported.
• LVM physical volumes cannot be backed up, as well as RAID members. Only LVM/RAID logical volumes containing filesystems can be backed up.
• Disks partitioned with cfdisk version older than 2.25 are not supported.
• File level backup masks do not apply to directories.
• Backup job type cannot be switched between file and volume levels.
• Very high data change rate during backup may cause snapshot overflow. Should this happen, the job will attempt to retry processing up to 3 times with a larger snapshot.

Restore
• File-level restore cannot be performed on kernels versions 4.0.x-4.1.33 due to the bug in FUSE kernel module. To work around the issue, either upgrade the kernel, or perform file-level restore from the Recovery Media.
• Concurrent file level restore sessions from different restore points are not supported because only one restore point can be mounted at a time. To perform a file level restore from another restore point, unmount currently mounted one first.
• Restore of encrypted devices is not supported.
• Restores to software raid configurations are not supported.

Veeam Backup & Replication Integration
• Encrypted backups cannot be imported to Veeam Agent for Linux directly.
• Fast clone is not supported for ReFS repositories.

Installation
• dkms package is not present in default repositories for some Linux distributions. You should obtain it from third-party repositories:
CentOS / RHEL / Oracle Linux / Fedora : EPEL repository
OpenSUSE / SLES : Packman repository

For openSUSE/SLES: dkms from the Packman repository contains wrong dependencies so if you see
Code: Select all
Problem: nothing provides kernel-devel needed by dkms-2.2.0.3-14.1.noarch
Solution 1: do not install dkms-2.2.0.3-14.1.noarch
Solution 2: break dkms-2.2.0.3-14.1.noarch by ignoring some of its dependencies

then make sure that you have an appropriate kernel-devel package installed and its version matches your kernel version:
Code: Select all
root@localhost:~> rpm -qa | grep kernel-default
kernel-default-devel-3.0.101-91.1
kernel-default-3.0.101-91.1

and tell zypper to ignore dependencies:
Code: Select all
zypper -n install --force dkms


• kernel-devel version must match your current kernel version.
Extended kernels such as kernel-pae, kernel-uek, and others, require appropriate kernel-devel packages to be installed, for example:

kernel-uek > kernel-uek-devel, kernel-default > kernel-default-devel, kernel-pae > kernel-pae-devel.
To check your current kernel version, execute
Code: Select all
uname -r

• RHEL and derivatives: if yum package manager installs packages that do not match your current kernel version, either update your system or fetch older versions of the required packages from CentOS Vault repository.

• SLES/OES: Veeam Agent for Linux was successfully installed but you see the error

Code: Select all
|--tr:Failed to execute [modprobe].
[05.01.2017 08:04:48] <140669894625024> lpbcore| >>  |Failed to load module [veeamsnap] with parameters [zerosnapdata=1


To fix the issue edit /etc/modprobe.d/unsupported-modules.conf and change the value of the variable to 1
PTide
Veeam Software
 
Posts: 3237
Liked: 269 times
Joined: Tue May 19, 2015 1:46 pm

New Issues

Veeam Logoby PTide » Tue Dec 13, 2016 3:13 pm

If you use Veeam Agent for Linux with a paid license installed, you can submit a support case to the Veeam Support Team at www.veeam.com/support.html. If you use Veeam Agent for Linux FREE, please submit issues by creating a separate topic for each issue. Please do not post log snippets, instead include the link to full logs package.

To export logs:

1. Launch the Veeam Agent for Linux control panel with the veeam or veeamconfig ui command.

2. In the Veeam Agent for Linux control panel, press the 'm' key to open the Miscellaneous menu.

3. In the menu, select the Export Logs option and press Enter.

4. In the Choose logs directory window, browse to a directory to which you want to export logs and press Ok to start logs export process.

Veeam Agent for Linux will collect product logs, export them to an archive file with the name veeam_logs.tar.gz, and save the archive file to the specified directory.
PTide
Veeam Software
 
Posts: 3237
Liked: 269 times
Joined: Tue May 19, 2015 1:46 pm


Return to Veeam Agent for Linux



Who is online

Users browsing this forum: No registered users and 1 guest