Feature request: Support Cloudlinux and OpenVZ kernels

[BobTSS]

We're trying to move our backup infrastructure over to Veeam but a significant portion of our production environment consists of Cloudlinux based physical servers and VMs. We also have a number of OpenVZ VPS nodes for which there are no prebuilt modules.

Our Veeam support engineer and one of your cloud solution architects involved suggested I post a feature request, so here it is!

Thanks!
Bob

[PTide]

Hi,

Your request has been noted. I would like to ask a couple of questions regarding your needs, if you don't mind.

Do you intend to backup those machines as a whole, on a volume-level, or just a particular set of files and directories?

Thanks

[BobTSS]

Entire server. So a bare metal restore is possible if needed. We'll need to be able to do file level restores as well but that seems to be doable from what I've seen of entire server backups in veeam so far..

[rmaliszewski]

+1

[wahabkhan]

Any update regarding this?

We still dont have any support for CloudLinux kernels?

[nielsengelen]

Since VAL v3, you can back up an entire server in file level backup mode without a snapshot so this will allow you to back up those instances without issues.

[PTide]

Just keep in mind that the described approach does not provide consistency, i.e. you should not change files being backed up until the backup job finishes

Thanks!

[wahabkhan]

What does this mean Ptide?

No one can control the users changing files. What happens when someone changes file while its being backed up ?

[PTide]

Snapshot-less mode operates just like almost any legacy backup solution out there:

No snapshot --> no freeze of a filesystem --> no consistency --> if a file is changed while being copies, then the copy of the file might be inconsistent (i.e. different part of file represent different moments in time).
There are several ways to avoid that, such as mounting the disk ro before copying from it, or using snapshots of any kind (veeam, lvm, btrfs), or schedule a backup window when noone is allowed to modify anything from the backup scope.

Thanks!