[SOLVED] Backupproblem with Snapshot, VM crashes sporadically after starting backup process

fireon

Distinguished Member
Oct 25, 2010
4,511
479
153
Austria/Graz
deepdoc.at
Hello,

at customer after update from 3.1 to proxmox 3.2 we have a problem to backup one VM with snapshot (VM is an Gentoo, up to date). On my homeserver the same problem, but the VM is an Ubuntu 12.04 LTS. At my homeserver the backuprocess does not work sporadically. Sometimes it work.
But on customers server, every backup from the vm let the vm crash. It is a little Cluster with two nodes. On Customer we have the Basic Subscription. So updates should be ok. Here are the logs from the backups:

Code:
[COLOR=#000000][FONT=tahoma]NFO: starting new backup job: vzdump 102 --quiet 1 --mailto technik@local --mode snapshot --compress gzip --storage sicherung[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: Starting Backup of VM 102 (qemu)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status = running[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: update VM 102: -lock backup[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: backup mode: snapshot[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: ionice priority: 7[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: creating archive '/mnt/pve/sicherung/dump/vzdump-qemu-102-2014_03_22-00_15_02.vma.gz'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: started backup task 'ce8af6cf-cf06-4f8f-9726-4f9037dc0291'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 0% (87425024/16106127360), sparse 0% (20480), duration 3, 29/29 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 1% (178651136/16106127360), sparse 0% (3944448), duration 8, 18/17 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 2% (349700096/16106127360), sparse 0% (3973120), duration 15, 24/24 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 3% (495845376/16106127360), sparse 0% (8286208), duration 20, 29/28 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 4% (661389312/16106127360), sparse 0% (8327168), duration 26, 27/27 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 5% (813432832/16106127360), sparse 0% (12673024), duration 32, 25/24 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]ERROR: VM 102 not running[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: aborting backup job[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]ERROR: VM 102 not running[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]ERROR: Backup of VM 102 failed - VM 102 not running[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: Backup job finished with errors[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK ERROR: job errors

Anohter backup, The VM crashes later:

[/FONT][/COLOR]
Code:
[COLOR=#000000][FONT=tahoma]INFO: starting new backup job: vzdump 102 --quiet 1 --mailto technik@local --mode snapshot --compress gzip --storage sicherung[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: Starting Backup of VM 102 (qemu)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status = running[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: update VM 102: -lock backup[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: backup mode: snapshot[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: ionice priority: 7[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: creating archive '/mnt/pve/sicherung/dump/vzdump-qemu-102-2014_03_22-00_00_02.vma.gz'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: started backup task 'f870193c-f679-4c06-a2d4-74e6802d873b'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 0% (87425024/16106127360), sparse 0% (57344), duration 3, 29/29 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 1% (176422912/16106127360), sparse 0% (3985408), duration 8, 17/17 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 2% (333185024/16106127360), sparse 0% (4005888), duration 15, 22/22 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 3% (486539264/16106127360), sparse 0% (8318976), duration 20, 30/29 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 4% (646184960/16106127360), sparse 0% (8327168), duration 26, 26/26 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 5% (826474496/16106127360), sparse 0% (12255232), duration 33, 25/25 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 6% (969277440/16106127360), sparse 0% (12296192), duration 38, 28/28 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 7% (1131282432/16106127360), sparse 0% (16240640), duration 46, 20/19 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 8% (1295515648/16106127360), sparse 0% (20537344), duration 54, 20/19 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 9% (1455816704/16106127360), sparse 0% (20537344), duration 62, 20/20 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 10% (1623064576/16106127360), sparse 0% (20762624), duration 70, 20/20 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 11% (1778909184/16106127360), sparse 0% (20905984), duration 78, 19/19 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 12% (1944453120/16106127360), sparse 0% (21254144), duration 86, 20/20 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 13% (2117206016/16106127360), sparse 0% (21577728), duration 93, 24/24 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 14% (2261647360/16106127360), sparse 0% (21581824), duration 99, 24/24 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 15% (2425094144/16106127360), sparse 0% (21581824), duration 106, 23/23 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 16% (2603548672/16106127360), sparse 0% (21590016), duration 113, 25/25 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 17% (2751987712/16106127360), sparse 0% (21598208), duration 121, 18/18 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 18% (2900230144/16106127360), sparse 0% (21823488), duration 129, 18/18 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 19% (3076915200/16106127360), sparse 0% (22646784), duration 136, 25/25 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 20% (3243114496/16106127360), sparse 0% (22654976), duration 141, 33/33 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 21% (3395289088/16106127360), sparse 0% (22659072), duration 145, 38/38 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 22% (3557818368/16106127360), sparse 0% (26644480), duration 151, 27/26 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 23% (3706060800/16106127360), sparse 0% (26644480), duration 156, 29/29 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 24% (3880910848/16106127360), sparse 0% (30576640), duration 164, 21/21 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 25% (4036755456/16106127360), sparse 0% (30646272), duration 171, 22/22 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 26% (4196401152/16106127360), sparse 0% (30646272), duration 179, 19/19 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 27% (4354146304/16106127360), sparse 0% (30646272), duration 192, 12/12 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 28% (4511891456/16106127360), sparse 0% (30707712), duration 204, 13/13 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]ERROR: VM 102 not running[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: aborting backup job[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]ERROR: VM 102 not running[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]ERROR: Backup of VM 102 failed - VM 102 not running[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: Backup job finished with errors[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK ERROR: job errors[/FONT][/COLOR]

Since the Upgrade, no Backup of the VM was successfully. So copied the VM to my homeserver. And the backup works correctly. I'am confusing.
What can i do, what could be causing the problem?

Best Regards
Fireon
 
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

What kind of backup storage do you use (nfs, cifs, ...)?
 
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

Nfs at Customer, at my Homeserver i use SSHFS.
 
Last edited:
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

Hi Dietmar

Thinking about of the error of Mr. Fireon: "ERROR: VM 102 not running", that is the same error messages of many people that have a Backup snapshot in progress, should not "KVM" keep running your virtual machine despite an alleged error in the NFS shared?

Best regards and the best of success to you that are doing a great job
Cesar
 
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

I copied the VM from Customer to my homeserver and do an backup every 30 minutes, after 9 Backups the backup failed (BackupStorage with SSHFS). So i think the storagemodel is not really the problem. Maybe it is depend on the VM, i have also an CentOS 6.5 another Gentoo and anohter Ubuntu 12.04 that backups every day, no problems. Confusing...

106: Mar 24 14:00:03 INFO: Starting Backup of VM 106 (qemu)
106: Mar 24 14:00:03 INFO: status = running
106: Mar 24 14:00:04 INFO: update VM 106: -lock backup
106: Mar 24 14:00:05 INFO: backup mode: snapshot
106: Mar 24 14:00:05 INFO: ionice priority: 7
106: Mar 24 14:00:05 INFO: creating archive '/mnt/pve/ISO-images/dump/vzdump-qemu-106-2014_03_24-14_00_03.vma.gz'
106: Mar 24 14:00:05 INFO: started backup task '529f6ca3-b913-4260-b983-a2d19cdb9141'
106: Mar 24 14:00:08 INFO: status: 0% (79822848/16106127360), sparse 0% (20480), duration 3, 26/26 MB/s
106: Mar 24 14:00:14 INFO: status: 1% (162004992/16106127360), sparse 0% (3977216), duration 9, 13/13 MB/s
106: Mar 24 14:00:24 INFO: status: 2% (341049344/16106127360), sparse 0% (3977216), duration 19, 17/17 MB/s
106: Mar 24 14:00:30 INFO: status: 3% (490340352/16106127360), sparse 0% (8290304), duration 25, 24/24 MB/s
106: Mar 24 14:00:37 INFO: status: 4% (649920512/16106127360), sparse 0% (8339456), duration 32, 22/22 MB/s
106: Mar 24 14:00:45 INFO: status: 5% (824836096/16106127360), sparse 0% (12267520), duration 40, 21/21 MB/s
106: Mar 24 14:00:51 INFO: status: 6% (975765504/16106127360), sparse 0% (12324864), duration 46, 25/25 MB/s
106: Mar 24 14:00:59 ERROR: VM 106 not running
106: Mar 24 14:00:59 INFO: aborting backup job
106: Mar 24 14:00:59 ERROR: VM 106 not running
106: Mar 24 14:00:59 ERROR: Backup of VM 106 failed - VM 106 not running
I'm afraid to update our Proxmox 3.1 Clusters to 3.2.
The last years since Version 1.0 we never had problems with backups :)

Update: I've seen the customers machine have done an reboot at 3:11 AM. I read the logs, but there was nothing interesst. It was an hardreset. All problem since the update to 3.2.

Regards
Fireon
 
Last edited:
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

In the other thread I posted some steps on how to start kvm manually. When KVM crashes you should see an error.
Confirming that your problem is indeed a Seg fault would be helpful.
A method that allows dietmar to reproduce the error would be very helpful.

http://forum.proxmox.com/threads/18...2-VM-crashing-during-backup?p=92368#post92368
 
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

What kind of backup storage do you use (nfs, cifs, ...)?

Hello Dietmar,

the crash of the VM has nothing to to with the kind of storage (nfs, cifs or local).
The error is reproducible.

Every night one of my VM's crash during a snapshot backup to a cifs store.
Now I have tested the snapshot backup with my local storage.
result: 2 of 3 trials failed.

Trial 1: Fail
Mar 25 07:20:45 INFO: Starting Backup of VM 110 (qemu)
Mar 25 07:20:45 INFO: status = running
Mar 25 07:20:45 INFO: update VM 110: -lock backup
Mar 25 07:20:45 INFO: backup mode: snapshot
Mar 25 07:20:45 INFO: ionice priority: 7
Mar 25 07:20:45 INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-110-2014_03_25-07_20_45.vma.gz'
Mar 25 07:20:45 INFO: started backup task 'aeb8fdc1-9e46-41e6-a23e-24d81832ae8c'
Mar 25 07:20:48 ERROR: VM 110 not running
Mar 25 07:20:48 INFO: aborting backup job
Mar 25 07:20:48 ERROR: VM 110 not running
Mar 25 07:20:48 ERROR: Backup of VM 110 failed - VM 110 not running

Trial 2: Success
Mar 25 07:22:17 INFO: Starting Backup of VM 110 (qemu)
Mar 25 07:22:17 INFO: status = running
Mar 25 07:22:17 INFO: update VM 110: -lock backup
Mar 25 07:22:17 INFO: backup mode: snapshot
Mar 25 07:22:17 INFO: ionice priority: 7
Mar 25 07:22:17 INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-110-2014_03_25-07_22_17.vma.gz'
Mar 25 07:22:17 INFO: started backup task '206cb474-52ee-4e6b-8567-fa5e80286952'
Mar 25 07:22:20 INFO: status: 0% (136839168/53687091200), sparse 0% (27357184), duration 3, 45/36 MB/s
...
Mar 25 07:37:05 INFO: status: 100% (53687091200/53687091200), sparse 69% (37097263104), duration 888, 3701/0 MB/s
Mar 25 07:37:05 INFO: transferred 53687 MB in 888 seconds (60 MB/s)
Mar 25 07:37:05 INFO: archive file size: 5.21GB
Mar 25 07:37:05 INFO: Finished Backup of VM 110 (00:14:48)

Trial 3: Fail
Mar 25 07:45:31 INFO: Starting Backup of VM 110 (qemu)
Mar 25 07:45:31 INFO: status = running
Mar 25 07:45:31 INFO: update VM 110: -lock backup
Mar 25 07:45:31 INFO: backup mode: snapshot
Mar 25 07:45:31 INFO: ionice priority: 7
Mar 25 07:45:31 INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-110-2014_03_25-07_45_31.vma.gz'
Mar 25 07:45:31 INFO: started backup task '29c91d79-8960-4358-92a5-ffb7cf16c35a'
Mar 25 07:45:34 INFO: status: 0% (140640256/53687091200), sparse 0% (30453760), duration 3, 46/36 MB/s
Mar 25 07:45:37 INFO: status: 1% (779223040/53687091200), sparse 1% (591482880), duration 6, 212/25 MB/s
Mar 25 07:45:41 INFO: status: 2% (1094713344/53687091200), sparse 1% (682594304), duration 10, 78/56 MB/s
Mar 25 07:45:55 ERROR: VM 110 not running
Mar 25 07:45:55 INFO: aborting backup job
Mar 25 07:45:55 ERROR: VM 110 not running
Mar 25 07:45:55 ERROR: Backup of VM 110 failed - VM 110 not running

After the upgrade from Proxmox 3.1 to 3.2, I also change the graphiccard in the VM's from Standard to Spice (qxl).
I change back to Standard graphiccard, but that doesn't solve the backup and vm crash problem.
So that's not the reason.

Best regards Stephan
 
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

Ok, i search for reproduce this fault. On all two servers i've done an Upgrade from Debian 6 to 7. And then after a month i updatet to Proxmox 3.2. Maybe this is the Problem, the Upgrade von Debian 6 to 7 in junction with the Update to 3.2?


 
Last edited:
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

I copied the VM from Customer to my homeserver and do an backup every 30 minutes, after 9 Backups the backup failed (BackupStorage with SSHFS). So i think the storagemodel is not really the problem. Maybe it is depend on the VM, i have also an CentOS 6.5 another Gentoo and anohter Ubuntu 12.04 that backups every day, no problems. Confusing...

106: Mar 24 14:00:03 INFO: Starting Backup of VM 106 (qemu)
106: Mar 24 14:00:03 INFO: status = running
106: Mar 24 14:00:04 INFO: update VM 106: -lock backup
106: Mar 24 14:00:05 INFO: backup mode: snapshot
106: Mar 24 14:00:05 INFO: ionice priority: 7
106: Mar 24 14:00:05 INFO: creating archive '/mnt/pve/ISO-images/dump/vzdump-qemu-106-2014_03_24-14_00_03.vma.gz'
106: Mar 24 14:00:05 INFO: started backup task '529f6ca3-b913-4260-b983-a2d19cdb9141'
106: Mar 24 14:00:08 INFO: status: 0% (79822848/16106127360), sparse 0% (20480), duration 3, 26/26 MB/s
106: Mar 24 14:00:14 INFO: status: 1% (162004992/16106127360), sparse 0% (3977216), duration 9, 13/13 MB/s
106: Mar 24 14:00:24 INFO: status: 2% (341049344/16106127360), sparse 0% (3977216), duration 19, 17/17 MB/s
106: Mar 24 14:00:30 INFO: status: 3% (490340352/16106127360), sparse 0% (8290304), duration 25, 24/24 MB/s
106: Mar 24 14:00:37 INFO: status: 4% (649920512/16106127360), sparse 0% (8339456), duration 32, 22/22 MB/s
106: Mar 24 14:00:45 INFO: status: 5% (824836096/16106127360), sparse 0% (12267520), duration 40, 21/21 MB/s
106: Mar 24 14:00:51 INFO: status: 6% (975765504/16106127360), sparse 0% (12324864), duration 46, 25/25 MB/s
106: Mar 24 14:00:59 ERROR: VM 106 not running
106: Mar 24 14:00:59 INFO: aborting backup job
106: Mar 24 14:00:59 ERROR: VM 106 not running
106: Mar 24 14:00:59 ERROR: Backup of VM 106 failed - VM 106 not running
I'm afraid to update our Proxmox 3.1 Clusters to 3.2.
The last years since Version 1.0 we never had problems with backups :)

Update: I've seen the customers machine have done an reboot at 3:11 AM. I read the logs, but there was nothing interesst. It was an hardreset. All problem since the update to 3.2.

Regards
Fireon

Hi Fireon, when you have done backup test on the copied vm, does it crash without any write/read activity in the vm ?
 
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

When i've done a Backup, and the backup goes ready without stop, the backuped VM works. This was the way that i've test the VM from Customer at my Homeserver.
 
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

Hello Dietmar,

the crash of the VM has nothing to to with the kind of storage (nfs, cifs or local).
The error is reproducible.

Best regards Stephan

Is your proxmox installation a baremetal one, or did you installed debian and after that the proxmox kernel with pve packages?
 
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

Is your proxmox installation a baremetal one, or did you installed debian and after that the proxmox kernel with pve packages?


Hello Dietmar,

No baremetal installation with Proxmox ISO, but Debian-70-wheezy-64-minimal installation from Hetzner and then proxmox kernel with pve packages.

Best regards Stephan
 
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

On my Servers all baremetal installations.
 
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

Ok, i think there is definitely a problem with the neu kvmversion/kernel and these two guests. Always the same VMs crashes at the backup, and definitely after Upgrade to 3.2. 3.2 comes with new kernel/kvm version. For about 1 year ago i had something similar problem with an gentoo guest. After an upgrade from proxmox i had to recompile the guestkernel, because gentoo vm's won't start anymore. So, maybe the same problem with some older VMs. This one gentoo is very old, and the ubuntu 12.04 too. But such a thing should not even be.
 
Last edited:
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

Thank you Dietmar, i test it to run Backup every hour.

Edit: Only for information: http://forum.proxmox.com/threads/18069-After-update-to-3-2-VM-crashing-during-backup

Hi Fireon

Since 4 days ago i am waiting the results of your test of backup snapshot every hour (for this moment you must have done ninety six tests if did not stop him before.).

Can you tell us the results of your tests and how many tests did you do?

Re-Edit: And if the results are good, only was applied the patch of Dietmar ( ftp://download.proxmox.com/debian/dists/wheezy/pvetest/binary-amd64/pve-qemu-kvm_1.7-6_amd64.deb )?.

Best regards
Cesar
 
Last edited:
Re: Backupproblem with Snapshot, VM crashes sporadically after starting backup proces

Hello :)

since the patch, i'am running up to now an hourly backup of this server. And the backup never crashes the VM. So it looks like the patch is working fine! Thank you Dietmar, good work!
@Dietmar: How long does some tests need to go in the Enterprise Repository?

Regards
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!