Can VAL run inside an LXC?

[ovidiu]

I was giving it a try and when installing saw this:

Code: Select all

root@bailey:/tmp/x64/deb# apt-get install dkms -u
Reading package lists... Done
Building dependency tree
Reading state information... Done
Recommended packages:
  menu sudo linux-headers-686-pae linux-headers-amd64 linux-headers-generic linux-headers
  linux-image
The following NEW packages will be installed:
  dkms
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 70.9 kB of archives.
After this operation, 347 kB of additional disk space will be used.
Get:1 http://debian.mirrors.ovh.net/debian/ jessie/main dkms all 2.2.0.3-2 [70.9 kB]
Fetched 70.9 kB in 0s (1,666 kB/s)
Selecting previously unselected package dkms.
(Reading database ... 28643 files and directories currently installed.)
Preparing to unpack .../dkms_2.2.0.3-2_all.deb ...
Unpacking dkms (2.2.0.3-2) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up dkms (2.2.0.3-2) ...
Setting up veeamsnap (1.0.0.499) ...
Loading new veeamsnap-1.0.0.499 DKMS files...
First Installation: checking all kernels...
dpkg: warning: version '*-*' has bad syntax: version number does not start with digit
It is likely that 4.4.10-1-pve belongs to a chroot's host

[PTide]

Hi,

LXC container shares the kernel with the host and is not allowed to load kernel modules. Please install all required packages on the host's OS and try installing VAL inside the container again. Also please note that the product has not been fully tested for containers thus no guarantee it will work stable.

Thanks

[ovidiu]

I certainly can give it a try so I would install dkms on the host first followed by veam or veamsnap? Which one of those 2 goes into the host and which into the guest?

[dellock6]

veeamsnap is the component that compiles and loads the kernel module, so this one has to go for sure in the host. You can then try to run veeam in the guest.

[PTide]

Luca is right - first install veeamsnap on the host, it should pull all packages it depends on automatically, including dkms. Afterwards you should be able to install veeam-1.0.0.499 package inside a container. Make sure that the kernel-headers and kernel versions match each other.

Thanks

[ovidiu]

installed veamsnap in the host and veeam in the guest.
tried backing up:

Code: Select all

Backup session on bailey [0] %                                 Status: Failed




     Summary                                Data

     Duration:           00:00:00           Processed:          ---
     Processing rate:    ---                Read:               ---
     Bottleneck:         ---                Transferred:        ---


     Time                Action                                        Duration

     2016-07-10 18:41:40 Job started at 2016-07-10 18:41:40
     2016-07-10 18:41:40 Starting backup
     2016-07-10 18:41:40 [error] No objects to backup.
     2016-07-10 18:41:40 [error] Failed to perform backup

I can supply all the logs if anyone is keen to look into this?
veeam backup runs fine on the host as I just ran a test backup.

[nielsengelen]

Which type of backup did u configure ? Entire computer, volume or file?

[ovidiu]

entire server

[PTide]

I suspect that veeam found no block devices inside the guest thus backup session has failed. Could you please post an output of lsblk -af. Have you tried running a file level backup inside the guest?

Thanks

[ovidiu]

This is from the guest as requested:

Code: Select all

root@bailey:~#  lsblk -af
lsblk: dm-0: failed to get device path
lsblk: dm-0: failed to get device path
NAME   FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1
├─sda2
├─sda3
└─sda4
loop0
loop1                    /
loop2
loop3
loop4
loop5
loop6
loop7
root@bailey:~#

A file level backup also failed:

Code: Select all

Backup session on bailey [0] %                                    Status: Failed


                                                                                               
       Summary                                  Data

       Duration:           00:00:03             Processed:          ---
       Processing rate:    ---                  Read:               ---                               Bottleneck:         ---                  Transferred:        ---                        

       Time                Action                                           Duration

       2016-07-11 14:28:57 Job started at 2016-07-11 14:28:57
       2016-07-11 14:28:57 Starting backup
       2016-07-11 14:28:57 [error] Failed to create volume snapshot         00:00:02
       2016-07-11 14:28:59 [error] Bad file descriptor
       2016-07-11 14:28:59 [error] Failed to perform backup

Let me know if you would like to see logs.

[PTide]

I have to conclude that the current version of VAL cannot backup containers, indeed. It was developed not for container-based virtualization but rather for a fully-virtualized and physical hosts. Thank you for raising the topic, it will be interesting to see how many people are going to request a support for conatiners. If many are interested then we certainly will find the way to fulfill the request.

Thank you for your time and interest!

[ovidiu]

Thanks for the feedback. (I got your PM about logs but haven't gotten around to send you a link yet).
I'm very interested in LXC as I switched from openvz. I only have very few (fully-virtualized) KVMs left running.

[futureweb]

Hello,

will Veeam Linux Agent be compatible with Virtuozzo Container Virtualization? (https://virtuozzo.com/)
Containers reside on EXT4 formatted ploop device which is presented to Containers. Snapshot functionality is already given at ploop Level.

Hope on some insight into this.

thx
Andreas Schnederle-Wagner

[nielsengelen]

Currently you can backup the host without any problems however the containers can't be backed up. This is due the fact that they share devices with their host and we can't access these inside the containers. Also have a look at this thread.

[futureweb]

Hello vmniels,
thank you for your fast reply!
As far as I know - with Virtuozzo 6+ there are no more hard-links/links to templates outside of the Container (this was the "old" behaviour before Virtuozzo 6 with VZFS - also openVZ still does is that way if I remember correctly)

[nielsengelen]

From my initial test I ran into some issues with the current beta, however I haven't done extended testing as I used a standard openvz install. We would love to hear feedback from you if it works or not

[futureweb]

Do you have some technical insights into how Veeam Agent for Linux hooks into dev/FS?
Then I will ask Virtuozzo Support if it is possible to use it in conjunction with their ploop EXT 4 thing ...
Thx

[futureweb]

ps) I just asked within Virtuozzo Boards about VZ+Veeam Agent ... http://forum.odin.com/threads/veeam-age ... ty.337948/ ... don't know - but maybe you could contribute some technical insights there?
Hope we end up with a working Veeam+Virtuozzo configuration ...

Andreas

[PTide]

<...>don't know - but maybe you could contribute some technical insights there?

I don't think it's something that can be briefly described Besides, VAL is currently in a Beta phase so the snapshot driver is likely to be modified in future releases because beta testers report performance issues with certain configurations in other threads on this forum.

As it's been already said - VAL is not intended to backup containers, however we are well aware that our users are interested in such technology and we expect that later we will work out the way to meet the demand.

Thanks!

[futureweb]

VAL is not intended to backup containers, however we are well aware that our users are interested in such technology and we expect that later we will work out the way to meet the demand.

alright - according to Pavel's (Odin Team) non-official statement Virtuozzo 7 (and maybe 6) CTs most likely could be backed up if KVM/libvirt support is added to VAL ... so I hope you will add this in future Release ... would add big value to VAL!!!
http://forum.odin.com/threads/veeam-age ... ost-794810

[burman1]

does veeam support LXC containers?

using an LXC as the backup workstation.

have a centos7 LXC container with a mount point to the host so we can get access to the files that need to be backed up.

but in this config veeam continues to say:
Network filesystems (NFS, SMB) cannot be backed up. Please exclude: /mnt/test

regardless of any directory selected even its a local directory. the directory is NOT an NFS or SMB share

Thanks,

[PTide]

Hi,

Containers are not supported now, noted as a feature request.

Thank you

[toddehb]

Hi,

on a remote server I have setup the linux agent. When I start a backup job I get this

[18.10.2018 16:28:31] <3073833792> lpbcore| >> |Backup job has failed.
[18.10.2018 16:28:31] <3073833792> lpbcore| >> |An exception was thrown from thread [3073833792].
[18.10.2018 16:28:31] <3073836864> | Closing socket device.
[18.10.2018 16:28:31] <3073836864> lpbcore| LpbManSession: Processing commands. ok.
[18.10.2018 16:28:31] <3073836864> | Closing socket device.
[18.10.2018 16:28:31] <3073833792> lpbcore| JOB STATUS: FAILED.
[18.10.2018 16:28:31] <3073833792> | Thread finished. Role: 'Volume backup job execution'.
[18.10.2018 16:28:31] <3073836864> | Closing socket device.
[18.10.2018 16:28:31] <3073836864> | Closing socket device.
[18.10.2018 16:28:31] <3073836864> lpbman | Application session has been finished.

The linux system is connected via VPN to hat site hosting B&R 9.5. It ist just a 30day trial if this would be important to know for you.

During configuring that backup job, the repository is shown in the wizard, so connection to the backup host should not be the problem.

Any ideas?

Regards, todde

[toddehb]

Just tried to do just a file level backup instead of volume level. No matter whic files I select, this is the outcome of veeam

"Network filesystems (NFS, SMB) cannot be backed up. Please exclude: /"

I just selected /etc and /var

This server runs virtualized in OpenVZ.

[PTide]

That is expected if you run VAL inside a container, which is not a supported scenario for now.

Thanks

[mkevenaar]

Hi,

I have been working with support ([ID# 03560165]) regarding Virtuozzo support. Currently it seems that only file-based backup is supported.

We would love to have Virtuozzo support available.

Is there anyone using Virtuozzo and Veeam? How did you implement it?

Thanks,

Maurice

[DGrinev]

Hi Maurice and welcome to the Veeam community!

Thank you for the feature request!
Please review this existing discussion about the similar request.

[mkevenaar]

Hi DGrinev,

This topic is started to backup a specific container, not the whole host with all it's containers. I believe these things are two different issues/requests.

[nielsengelen]

Maurice, there are currently no plans for Virtuozzo support so as suggested by supported, file-based backup is the method to use.

[prewest]

Is it possible to run Veeam on the host server to backup the containers that are on there?