[BETA2] Download + Known Issues + How to Submit a New Issue

[PTide]

IMPORTANT: There is NO upgrade procedure from BETA1, so if you already have one installed please follow these instructions to be able to install BETA2 properly.

Product Features
• Entire computer, volume-level and file-level backup with support for multiple jobs
• Bare metal recovery, volume-level and file-level restores
• Proprietary snapshot driver (no reliance on LVM snapshots)
• Proprietary changed block tracking driver for incremental backups

What's New in BETA2
• Integration with VBR 9.5
• BitLooker
• Pre/post job scripts
• Rescan of backup/repository
• CentOS/RHEL 7, Fedora 23, Fedora 24 packages were added
• Extra CLI commands
• Resizable UI

Features NOT available in this beta
• Backup encryption
• Restore to a smaller disk
• Encrypted device backup support

Known Issues and Limitations
• BTRFS and ZFS file systems are not supported
• Recovery Media will not boot in a Generation 2 Hyper-V VM
• Only 64-bit Recovery Media is provided with this beta, so you will not be able to perform Bare Metal Recovery on 32-bit hardware
• Backup job to NFS or SMB share may hang in case of network disconnect
• Wrong characters are displayed in putty terminal. To fix the issue, run export NCURSES_NO_UTF8_ACS=1 command
• Backup job may fail if an onboard RAID is used
• Creation time: 1970-01-01 00:00:00 in job info

How to Submit a New Issue
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 from /var/logs/veeam directory from the agent and /usr/share/Veeam/LPB directory from the recovery media (use Dropbox, OneDrive etc. to share the log package with us).

Getting Started
Installation
How to backup
How to restore
Command line

Download
1. Go to http://www.veeam.com/beta/val
2. Logon to web-site with your Veeam credentials
3. Enter password: VALv1beta

[PTide]

BETA2 cannot continue backup chains that have been created by BETA1 and there is no upgrade procedure, so you should first remove BETA1 and then perform clean installation of BETA2.

RHEL/CentOS/Fedora

1. Run:

Code: Select all

rpm –qa | grep veeam

Make sure that the output contains two packages – “veeam” and “veeamsnap”:

Code: Select all

veeamsnap-1.0.0.499-1.noarch
veeam-1.0.0.499-1.el7.x86_64

2. Run:

Code: Select all

rpm –e veeam-1.0.0.499-1.el7.x86_64
rpm –e veeamsnap-1.0.0.499-1.noarch

3. Upload VAL Beta2 rpm packages to the host and place them in a temporary directory. Go to the temporary directory and run the following commands:

Code: Select all

rpm –ivh veeamsnap*
rpm –ivh veeam-*

Debian/Ubuntu

1. Run:

Code: Select all

dpkg –l | grep veeam

Make sure that the output contains two packages – “veeam” and “veeamsnap”:

Code: Select all

ii  veeam                              1.0.0.499                       amd64        Veeam Agent for Linux
ii  veeamsnap                          1.0.0.499                       all          Veeam Agent for Linux kernel module

2. Run:

Code: Select all

dpkg --purge veeam
dpkg --purge veeamsnap

3. Upload VAL Beta2 deb packages to the host and place them in a temporary directory. Go to the temporary directory and run the following commands:

Code: Select all

dpkg –i veeamsnap*
dpkg –i veeam_*

You also might encounter a dependency error similar to this one:

Code: Select all

dpkg: error processing package veeam (--install):
dependency problems - leaving unconfigured
Processing triggers for ureadahead (0.100.0-16) ...
Errors were encountered while processing:
 veeam

In this case run the following:

Code: Select all

apt-get install -f