Centos7 agent error

[yanndre]

Hi,

I have a problem on a backup agent job on centos7.
At the first backup all work good and job finish with success, but for a second start of job the result is a fail ( https://www.dropbox.com/s/3oae1kyg2jvy0 ... d.PNG?dl=0 ).
But i have understand why, it's because at the end of the first job some mount point don't have been umount.

mout | grep btrfs :

Code: Select all

/dev/veeamimage2 on /tmp/{d16184c2-727a-4eed-8542-b07907af32d1} type btrfs ([b]ro[/b],noexec,noatime,nodiratime,space_cache,subvolid=5,subvol=/)
/dev/veeamimage2 on /tmp/{d337dd46-eccb-43a2-845a-0bdb0b91a5c8} type btrfs ([b]ro[/b],noexec,noatime,nodiratime,space_cache,subvolid=5,subvol=/)
/dev/veeamimage2 on /tmp/{6575f5cd-c462-427f-a88c-f8d801f89ba0} type btrfs ([b]ro[/b],noexec,noatime,nodiratime,space_cache,subvolid=5,subvol=/)

And if i umount all 3 moint point and retry the job all work well, but at the end of this retry new mount point /dev/veeamimage2 still remain.

veeammout.log :

Code: Select all

cat veeammount.log (10:17 : failed see screenshot // 10:34 Success after i umount manualy /dev/veeamimage2)
[26.01.2018 10:17:34] <140081338468288> cli    | Initializing new log filter.
[26.01.2018 10:17:34] <140081338468288> vmnt   | //////////////////////////////////////////////////////////////////////////
[26.01.2018 10:17:34] <140081338468288> vmnt   | name /usr/sbin/veeammount
[26.01.2018 10:17:34] <140081338468288> vmnt   | Mount
[26.01.2018 10:17:34] <140081338468288> vmnt   |   deviceName=/dev/veeamimage0
[26.01.2018 10:17:34] <140081338468288> vmnt   |   mountPointName=/tmp/{845d2a3d-9cef-4df0-a6ae-cf66d1783137}/
[26.01.2018 10:17:34] <140081338468288> vmnt   | Mount Failed.
[26.01.2018 10:17:34] <140081338468288> vmnt   | ERR |Failed to open [/dev/veeamimage0].
[26.01.2018 10:17:34] <140081338468288> vmnt   | >>  |Failed to get filesystem of device [/dev/veeamimage0].
[26.01.2018 10:17:34] <140081338468288> vmnt   | >>  |--tr:Mounting device [/dev/veeamimage0] on mount point [/tmp/{845d2a3d-9cef-4df0-a6ae-cf66d1783137}/] failed.
[26.01.2018 10:17:34] <140081338468288> vmnt   | >>  |An exception was thrown from thread [140081338468288].

[26.01.2018 10:34:02] <140295275800512> cli    | Initializing new log filter.
[26.01.2018 10:34:02] <140295275800512> vmnt   | //////////////////////////////////////////////////////////////////////////
[26.01.2018 10:34:02] <140295275800512> vmnt   | name /usr/sbin/veeammount
[26.01.2018 10:34:02] <140295275800512> vmnt   | Mount
[26.01.2018 10:34:02] <140295275800512> vmnt   |   deviceName=/dev/veeamimage0
[26.01.2018 10:34:02] <140295275800512> vmnt   |   mountPointName=/tmp/{318f0a0e-d2fa-4750-bd9d-9b86d31b6074}/
[26.01.2018 10:34:02] <140295275800512> lodev  |   Mount via syscall
[26.01.2018 10:34:02] <140295275800512> lodev  |     Mounting [/dev/veeamimage0] on [/tmp/{318f0a0e-d2fa-4750-bd9d-9b86d31b6074}/], fstype=[btrfs], flags=0x00000000c0ed0c08, data=[].
[26.01.2018 10:34:02] <140295275800512> vmnt   | Mount ok.
[26.01.2018 10:34:03] <139906424330176> cli    | Initializing new log filter.
[26.01.2018 10:34:03] <139906424330176> vmnt   | //////////////////////////////////////////////////////////////////////////
[26.01.2018 10:34:03] <139906424330176> vmnt   | name /usr/sbin/veeammount
[26.01.2018 10:34:03] <139906424330176> vmnt   | Umount
[26.01.2018 10:34:03] <139906424330176> vmnt   |   deviceName=/dev/veeamimage0
[26.01.2018 10:34:03] <139906424330176> vmnt   | Umount ok.
[26.01.2018 10:34:05] <139763102693312> cli    | Initializing new log filter.
[26.01.2018 10:34:05] <139763102693312> vmnt   | //////////////////////////////////////////////////////////////////////////
[26.01.2018 10:34:05] <139763102693312> vmnt   | name /usr/sbin/veeammount
[26.01.2018 10:34:05] <139763102693312> vmnt   | Mount
[26.01.2018 10:34:05] <139763102693312> vmnt   |   deviceName=/dev/veeamimage1
[26.01.2018 10:34:05] <139763102693312> vmnt   |   mountPointName=/tmp/{821fef43-32d4-4bf3-8e92-47fd0b194f94}/
[26.01.2018 10:34:05] <139763102693312> lodev  |   Mount via syscall
[26.01.2018 10:34:05] <139763102693312> lodev  |     Mounting [/dev/veeamimage1] on [/tmp/{821fef43-32d4-4bf3-8e92-47fd0b194f94}/], fstype=[btrfs], flags=0x00000000c0ed0c08, data=[].
[26.01.2018 10:34:05] <139763102693312> vmnt   | Mount ok.
[26.01.2018 10:34:05] <139974656403392> cli    | Initializing new log filter.
[26.01.2018 10:34:05] <139974656403392> vmnt   | //////////////////////////////////////////////////////////////////////////
[26.01.2018 10:34:05] <139974656403392> vmnt   | name /usr/sbin/veeammount
[26.01.2018 10:34:05] <139974656403392> vmnt   | Umount
[26.01.2018 10:34:05] <139974656403392> vmnt   |   deviceName=/dev/veeamimage1
[26.01.2018 10:34:05] <139974656403392> vmnt   | Umount ok.
[26.01.2018 10:34:06] <140641770620864> cli    | Initializing new log filter.
[26.01.2018 10:34:06] <140641770620864> vmnt   | //////////////////////////////////////////////////////////////////////////
[26.01.2018 10:34:06] <140641770620864> vmnt   | name /usr/sbin/veeammount
[26.01.2018 10:34:06] <140641770620864> vmnt   | Mount
[26.01.2018 10:34:06] <140641770620864> vmnt   |   deviceName=/dev/veeamimage2
[26.01.2018 10:34:06] <140641770620864> vmnt   |   mountPointName=/tmp/{1c427d32-a1ec-4e65-8ddf-10a2d9e96883}/
[26.01.2018 10:34:06] <140641770620864> lodev  |   Mount via syscall
[26.01.2018 10:34:06] <140641770620864> lodev  |     Mounting [/dev/veeamimage2] on [/tmp/{1c427d32-a1ec-4e65-8ddf-10a2d9e96883}/], fstype=[btrfs], flags=0x00000000c0ed0c08, data=[].
[26.01.2018 10:34:06] <140641770620864> vmnt   | Mount ok.
[26.01.2018 10:34:06] <140262159144896> cli    | Initializing new log filter.
[26.01.2018 10:34:06] <140262159144896> vmnt   | //////////////////////////////////////////////////////////////////////////
[26.01.2018 10:34:06] <140262159144896> vmnt   | name /usr/sbin/veeammount
[26.01.2018 10:34:06] <140262159144896> vmnt   | Umount
[26.01.2018 10:34:06] <140262159144896> vmnt   |   deviceName=/dev/veeamimage2
[26.01.2018 10:34:06] <140262159144896> vmnt   | Umount ok.
[26.01.2018 10:34:07] <140349226538944> cli    | Initializing new log filter.
[26.01.2018 10:34:07] <140349226538944> vmnt   | //////////////////////////////////////////////////////////////////////////
[26.01.2018 10:34:07] <140349226538944> vmnt   | name /usr/sbin/veeammount
[26.01.2018 10:34:07] <140349226538944> vmnt   | Mount
[26.01.2018 10:34:07] <140349226538944> vmnt   |   deviceName=/dev/veeamimage3
[26.01.2018 10:34:07] <140349226538944> vmnt   |   mountPointName=/tmp/{ace046a4-2945-437f-b571-ab86286a7ab0}/
[26.01.2018 10:34:07] <140349226538944> lodev  |   Mount via syscall
[26.01.2018 10:34:07] <140349226538944> lodev  |     Mounting XFS with [nouuid] option.

And to try to escape this i want to call a post script who executes the umount but don't work, can someone tell me what the code have to look like ?

So two questions : - This bug about no umount point can be solved or i need to wait an update of the agent ?
- How to make a post script or script for Linux ?

I'm french, sorry for my english
Thank you

[PTide]

Hi,

I have a couple of questions:

- What's the agent version that you use?
- Those btrfs devices - what are they? Are you trying to backup them?

Thanks

[yanndre]

Hi,

I have a couple of questions:

- What's the agent version that you use?
- Those btrfs devices - what are they? Are you trying to backup them?

Thanks

Hi,

Thank for this quick reply.

For the version of agent :

Code: Select all

[root@centos7 ~]# yum list installed | grep veeam
kmod-veeamsnap.x86_64                 2.0.0.400-1.el7            installed      
veeam.x86_64                          2.0.0.400-1.el7            installed      
veeam-release-el7.x86_64              1.0-1                      installed

In case my Veeam B&R version : 9.5.0.1536

And for those btrfs devices i think it's the agent who mount them, not me.

It's look like a bad umount process with the agent, no ?

Thanks

[PTide]

Right, it's agent who mounts them, but I'm afraid you understood me wrong Did you specify the BTRFS devices for backup? What are the settings of the job?

Thanks

[yanndre]

Right, it's agent who mounts them, but I'm afraid you understood me wrong Did you specify the BTRFS devices for backup? What are the settings of the job?

Thanks

No i don't specify this particular devices, but my job settings include them because i have choose to backup the 'Entire computer'.

Thank

[PTide]

Ok, that's the reason - VAL does not support BTRFS yet. You can create a separate volume-level job that does not include BTRFS volumes for that machine. However this seems to be a bug, because the system should have skipped BTRFS devices automatically. Please contact our support team directly so they can confirm the described behaviour. Please post your case ID once you do.

Thanks

[yanndre]

Ok, that's the reason - VAL does not support BTRFS yet. You can create a separate volume-level job that does not include BTRFS volumes for that machine. However this seems to be a bug, because the system should have skipped BTRFS devices automatically. Please contact our support team directly so they can confirm the described behaviour. Please post your case ID once you do.

Thanks

Ok, i will open a ticket on the support, but i have some problem to load my.veeam.com website, i think the problem is in my side i will try later.

And about create a script ? What a script for linux agent have to look like ?

Thanks,

[nielsengelen]

Veeam Agent for Linux supports scripts in the SH file format.

[yanndre]

Hi,

My case 02591105

Sorry for the long time without reply


Tahank's,

[ravi33]

Is the solution found for this issue , I have a similar failure in centos7

[PTide]

Hi Ravi,

Not sure which error you are referring to, and which version of VAL you are using, please elaborate.

Overall, although VAL v3.0 supports BTRFS, it requires the system to run kernel version 3.16 or later. CentOS 7 has kernel 3.10, thus BTRFS configs cannot be supported in this case.

Thank you!

[ravi33]

Hi Tide ,

Agent version : - 3.0.1.1046

Error message : Backing up files /boot, /home, /var, /, /sahome, /var/crash, /opt, /opt/controlm 00:02
Failed to perform managed backup
Failed to open [/dev/veeamimage1].
Failed to get filesystem of device [/dev/veeamimage1].

[PTide]

Do any of those locations reside on BTRFS? Do you have BTRFS in your system at all?

Thanks!

[ravi33]

No , We dont have that

[PTide]

Then kindly open a case with support team and post your case ID. There is something wrong with the block device (/dev/veeamimage1) that is created when veeam takes a snapshot, hence it is required to troubleshoot the kernel module (veeamsnap).

Thanks!