Standalone backup agents for Linux, Mac, AIX & Solaris workloads on-premises or in the public cloud
Post Reply
PTide
Product Manager
Posts: 6431
Liked: 729 times
Joined: May 19, 2015 1:46 pm
Contact:

TOP ISSUES TRACKER [Version 3.0.0.865]

Post by PTide » 2 people like this post

Top issues that have been fixed (please contact support team directly to obtain the fix)

1. Issues with LVM restores in the recent version of Recovery Media (3.0.0.865). Please use ISO v2.0.1

2. LUKS cryptodevices were not processed

Symptoms:

Code: Select all

Unable to backup object: DEV__dev_dm-0(not found)

3. Issues with Duplicate MBR ID=0x00000000 processing

Symptoms:

Code: Select all

More than one MBR disk with ID 0x00000000 is present in the system

4. HP RAID were not processed (e.g. /dev/cciss!c0d0)

Symptoms:

Code: Select all

Failed to create DeviceInfoEx for device: /dev/cciss!c0d0

5. Selection of LVM snapshots in UI would crash the job

Symptoms: agents service crashes with segfault

Code: Select all

#0  0x00007ffff6663a98 in raise () from /lib64/libc.so.6
#1  0x00007ffff666569a in abort () from /lib64/libc.so.6
#2  0x00007ffff665c227 in __assert_fail_base () from /lib64/libc.so.6
#3  0x00007ffff665c2d2 in __assert_fail () from /lib64/libc.so.6

6. Filesystems that return zero size could not be backed up

Symptoms: du utility returns zero size for files on the filesystem that is a subject to backup. Logs might show the following:

Code: Select all

Failed to write 2595293 bytes into ext2fs file '</path/to/file>' at offset 0. Ext2fs error: 0x0000001ecafa06b8

7. Managed by VBR: file-level backup excludes did not work for kernel versions lower than 3.16

Symptoms: file-level job excludes specified on VBR do not work and are not shown in agent log

Code: Select all

<140712550528768> lpbcore|     Enumerating file backup objects. snapshot required: true
<140712550528768> lpbcore|     Initializing file backup filter.

8. Managed by VBR / backup to VBR: agent service crashed after start with "Another backup job is running."

Symptoms:

Code: Select all

Error: Failed to execute agent management command startBackup. Error: Another backup job is running.
Although no active jobs are running, some veeam processes can be seen:

Code: Select all

[root@hostname /]# ps aux | grep veeam
root      1723  0.0  0.0 112640   976 pts/0    R+   04:21   0:00 grep --color=auto veeam
root     25493  0.0  1.0 842680 19924 ?        Sl   Jan16   0:08 /usr/sbin/veeamservice --daemonize --pidfile=/var/run/veeamservice.pid
root     26012  0.0  0.9 737012 17476 ?        Sl   Jan16   0:00 veeamjobman Service --session {<ID>} --socket /var/tmp/veeam/socket/veeam.sock --log /var/log/veeam/Backup/<directory>  BR-z - <IP>/Session_<ID>/Job.log
Post Reply

Who is online

Users browsing this forum: No registered users and 14 guests