PVE can't backup to PBS with datastore on SMB share

Tinyblargon

Member
Jun 28, 2018
4
0
21
27
Hi,

I was trying out the 1.0 build of PBS to try and start migrating my PVE backup solution to it.
Currently my PVE Backups to a nas over SMB. I was thinking i could just mount a SMB share and tell PBS to put its datastore on the share and let PVE backup to PBS.
Testing making backups to PBS with a datastore located on a local disk worked just fine, but putting the datastore on a mounted smb share did not.

Thanks

###Detaild information###

PVE version: 6.2-15 (free repos)
PBS version: 1.0-1 (free repos)
The SMB share in question is provided by FreeNas



The PVE Backup Log:
Code:
INFO: starting new backup job: vzdump 17121 --node pve3 --mode snapshot --storage test3 --remove 0
INFO: Starting Backup of VM 17121 (qemu)
INFO: Backup started at 2020-11-12 14:48:28
INFO: status = running
INFO: VM Name: DC1
INFO: include disk 'scsi0' 'local-zfs:vm-17121-disk-0' 16G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/17121/2020-11-12T13:48:28Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 17121 qmp command 'backup' failed - backup register image failed: command error: No such file or directory (os error 2)
INFO: aborting backup job
ERROR: Backup of VM 17121 failed - VM 17121 qmp command 'backup' failed - backup register image failed: command error: No such file or directory (os error 2)
INFO: Failed at 2020-11-12 14:48:29
INFO: Backup job finished with errors
TASK ERROR: job errors



The PBS Syslog:
Code:
Nov 12 14:48:29 pbs proxmox-backup-proxy[491]: starting new backup on datastore 'Proxmox': "vm/17121/2020-11-12T13:48:28Z"
Nov 12 14:48:29 pbs proxmox-backup-proxy[491]: GET /previous: 400 Bad Request: no valid previous backup
Nov 12 14:48:29 pbs proxmox-backup-proxy[491]: created new fixed index 1 ("vm/17121/2020-11-12T13:48:28Z/drive-scsi0.img.fidx")
Nov 12 14:48:29 pbs proxmox-backup-proxy[491]: POST /fixed_chunk: 400 Bad Request: No such file or directory (os error 2)
Nov 12 14:48:29 pbs proxmox-backup-proxy[491]: backup ended and finish failed: backup ended but finished flag is not set.
Nov 12 14:48:29 pbs proxmox-backup-proxy[491]: removing unfinished backup
Nov 12 14:48:29 pbs proxmox-backup-proxy[491]: removing backup snapshot "/mnt/Backup/Proxmox/vm/17121/2020-11-12T13:48:28Z"
Nov 12 14:48:29 pbs proxmox-backup-proxy[491]: TASK ERROR: removing backup snapshot "/mnt/Backup/Proxmox/vm/17121/2020-11-12T13:48:28Z" failed - Directory not empty (os error 39)
Nov 12 14:48:29 pbs proxmox-backup-proxy[491]: Detected stopped task 'UPID:pbs:000001EB:000001CC:00000000:5FAD3D2D:backup:Proxmox\x3avm-17121:root@pam:'

It was able to create this folder structure "vm\17121\2020-11-12T134828Z" and the "owner" file.



The share mount was configured like this.
The default PBS user named "backup" has uid and gid 34
"backup" has by default ownership of "/mnt"

Code:
mkdir -p /mnt/Backup
chattr +i /mnt/Backup #makes it so there are no writes allowed to the directory that wil act as a mountpoint.
mount -t cifs -o vers=3,uid=34,gid=34,username=backup //192.168.17.100/Backup /mnt/Backup



The "/etc/proxmox-backup/datastore.cfg"
Code:
datastore: Proxmox
        comment
        gc-schedule daily
        path /mnt/Backup/Proxmox
        prune-schedule daily

when i changed the datastore path to /mnt it worked just fine, so it's clearly someting with writing to the SMB share.
 
PBS is not designed to use mountpoints. Install PBS natively on a Server.
 
My datastore is located on a Hetzner "storage box" which is accessed through CIFS mount.
It's pretty slow (because of my ISP) but it's working

//server.hostname/backup/PROXMOX /local-mountpoint cifs iocharset=utf8,rw,user=<login>,password=<pass>,file_mode=0777,dir_mode=0777,mapchars,uid=34,noforceuid,gid=34,noforcegid 0 0

When you create the datastore, PBS will create ~66k folders. It can be really slow
 
Last edited:
My datastore is located on a Hetzner "storage box" which is accessed through CIFS mount.
It's pretty slow (because of my ISP) but it's working

//server.hostname/backup/PROXMOX /local-mountpoint cifs iocharset=utf8,rw,user=<login>,password=<pass>,file_mode=0777,dir_mode=0777,mapchars,uid=34,noforceuid,gid=34,noforcegid 0 0

When you create the datastore, PBS will create ~66k folders. It can be really slow
Hetzner SBs are totally fine for remote or desaster backups. But I cannot recommend them for constant mounts (be it CIFS, SSHFS etc.). Hetzner rotates the IP addresses of the storage boxes and CIFS mounts don't like that. This causes problems with stalling mounts. Additionally you share the same hardware node with many other customers and this also means you share a 1G uplink. Wrong timing and you cannot access your data. The same goes for storage performance. If to many people run lots of read/write requests the SBs are really (really!) slow.

I have been using HSBs for years but rather went for a Server Bidding HW node since the performance is better, 1G dedicated uplink is provided and full features of the PBS are available. There a some decend nodes with lots of local storage. Running a local ZFS is simple enough for full integration into PBs features.
 
Last edited:
I am trying pbs 1.0.1

during Backup I get the same error:

Code:
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: starting new backup on datastore 'SynNFS': "vm/101/2021-04-06T10:56:21Z"
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: GET /previous: 400 Bad Request: no valid previous backup
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: created new fixed index 1 ("vm/101/2021-04-06T10:56:21Z/drive-scsi0.img.fidx")
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: POST /fixed_chunk: 400 Bad Request: No such file or directory (os error 2)
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: backup ended and finish failed: backup ended but finished flag is not set.
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: removing unfinished backup
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: removing backup snapshot "/mnt/Backup/vm/101/2021-04-06T10:56:21Z"
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: TASK ERROR: removing backup snapshot "/mnt/Backup/vm/101/2021-04-06T10:56:21Z" failed - Directory not empty (os error 39)

the pbs storage is mounted with nfs
Code:
datastore: SynNFS
        path /mnt/Backup/

The directory vm/101/2021-04-06T10:56:21Z is created, but empty.

Above is mentioned: PBS is not designed to use mountpoints. Install PBS natively on a Server.
Is this the only solution, because I would like to use my HA nfs cluster.
 
I am trying pbs 1.0.1

during Backup I get the same error:

Code:
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: starting new backup on datastore 'SynNFS': "vm/101/2021-04-06T10:56:21Z"
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: GET /previous: 400 Bad Request: no valid previous backup
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: created new fixed index 1 ("vm/101/2021-04-06T10:56:21Z/drive-scsi0.img.fidx")
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: POST /fixed_chunk: 400 Bad Request: No such file or directory (os error 2)
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: backup ended and finish failed: backup ended but finished flag is not set.
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: removing unfinished backup
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: removing backup snapshot "/mnt/Backup/vm/101/2021-04-06T10:56:21Z"
Apr 06 12:56:21 pbs proxmox-backup-proxy[603]: TASK ERROR: removing backup snapshot "/mnt/Backup/vm/101/2021-04-06T10:56:21Z" failed - Directory not empty (os error 39)

the pbs storage is mounted with nfs
Code:
datastore: SynNFS
        path /mnt/Backup/

The directory vm/101/2021-04-06T10:56:21Z is created, but empty.

Above is mentioned: PBS is not designed to use mountpoints. Install PBS natively on a Server.
Is this the only solution, because I would like to use my HA nfs cluster.
NFS works, it's just a bit slow. I use it but had some problems with rights. This is not the right thread though since the OP has cifs problems. Just wanted to let you know it can work. I use a synology NAS and i had to use NFS settings "squash: Map root to admin"
 
Last edited:
please upgrade to the current version - lots of things changed since 1.0.1!
 
I have the same problem.
Proxmox VE hosting Proxmox BS.
Proxmox BS mounted SMB datastore in /mnt/backup/

Bash:
proxmox-backup-manager versions
proxmox-backup-server 1.1.2-1 running version: 1.1.2

Bash:
cat /etc/proxmox-backup/datastore.cfg
datastore: backup
        gc-schedule 04:00
        keep-daily 10
        keep-monthly 12
        keep-weekly 4
        keep-yearly 1
        notify gc=error,sync=error,verify=error
        notify-user SOMEUSER@pbs
        path /mnt/backup
        prune-schedule 04:00

Proxmox VE log output
Bash:
INFO: starting new backup job: vzdump --all 0 --pool backup_daily --quiet 1 --storage pbs --mode snapshot --mailto SOME@EMAIL --mailnotification failure --node pve
INFO: Starting Backup of VM 101 (qemu)
INFO: Backup started at 2021-04-19 16:37:40
INFO: status = running
INFO: VM Name: docker
INFO: include disk 'scsi0' 'local-zfs:vm-101-disk-0' 50G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: snapshots found (not included into backup)
INFO: creating Proxmox Backup Server archive 'vm/101/2021-04-19T14:37:40Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 101 qmp command 'backup' failed - backup register image failed: command error: No such file or directory (os error 2)
INFO: aborting backup job
ERROR: Backup of VM 101 failed - VM 101 qmp command 'backup' failed - backup register image failed: command error: No such file or directory (os error 2)
INFO: Failed at 2021-04-19 16:37:40

INFO: Starting Backup of VM 102 (qemu)
INFO: Backup started at 2021-04-19 16:37:40
INFO: status = running
INFO: VM Name: monitoring
INFO: include disk 'scsi0' 'local-zfs:vm-102-disk-0' 50G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: snapshots found (not included into backup)
INFO: creating Proxmox Backup Server archive 'vm/102/2021-04-19T14:37:40Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 102 qmp command 'backup' failed - backup register image failed: command error: No such file or directory (os error 2)
INFO: aborting backup job
ERROR: Backup of VM 102 failed - VM 102 qmp command 'backup' failed - backup register image failed: command error: No such file or directory (os error 2)
INFO: Failed at 2021-04-19 16:37:41
INFO: Backup job finished with errors
TASK ERROR: job errors

Proxmox BS log output VM 101
Bash:
2021-04-19T16:37:40+02:00: starting new backup on datastore 'backup': "vm/101/2021-04-19T14:37:40Z"
2021-04-19T16:37:40+02:00: GET /previous: 400 Bad Request: no valid previous backup
2021-04-19T16:37:40+02:00: created new fixed index 1 ("vm/101/2021-04-19T14:37:40Z/drive-scsi0.img.fidx")
2021-04-19T16:37:40+02:00: POST /fixed_chunk: 400 Bad Request: No such file or directory (os error 2)
2021-04-19T16:37:40+02:00: backup ended and finish failed: backup ended but finished flag is not set.
2021-04-19T16:37:40+02:00: removing unfinished backup
2021-04-19T16:37:40+02:00: TASK ERROR: removing backup snapshot "/mnt/backup/vm/101/2021-04-19T14:37:40Z" failed - Directory not empty (os error 39)

Proxmox BS log output VM 102
Bash:
2021-04-19T16:37:41+02:00: starting new backup on datastore 'backup': "vm/102/2021-04-19T14:37:40Z"
2021-04-19T16:37:41+02:00: GET /previous: 400 Bad Request: no valid previous backup
2021-04-19T16:37:41+02:00: created new fixed index 1 ("vm/102/2021-04-19T14:37:40Z/drive-scsi0.img.fidx")
2021-04-19T16:37:41+02:00: POST /fixed_chunk: 400 Bad Request: No such file or directory (os error 2)
2021-04-19T16:37:41+02:00: backup ended and finish failed: backup ended but finished flag is not set.
2021-04-19T16:37:41+02:00: removing unfinished backup
2021-04-19T16:37:41+02:00: TASK ERROR: removing backup snapshot "/mnt/backup/vm/102/2021-04-19T14:37:40Z" failed - Directory not empty (os error 39)

Afterwards Proxmox BS shows this
Screenshot_20210419_164619.png

The backups disappear from GUI after I delete the files manually.
The created folders like /mnt/backup/vm/101/2021-04-19T14:37:40Z are empty.
 
how did you mount the samba share? can you give the exact mount options?
 
Hello fabian,

Here's my /etc/fstab mount

Code:
//192.168.10.254/backup_proxmox /mnt/backup cifs credentials=/home/SOMEUSER/.smbcredentials,uid=34,noforceuid,gid=34,noforcegid,defaults,noauto,nofail,x-systemd.automount,x-systemd.requires=network-online.target 0 0

The datastore creation has been done via sudo proxmox-backup-manager datastore create backup /mnt/backup.
 
does the .chunks directory exist in the datastore? do all the prefix subdirs within exist?
 
ls -la on /mnt/backup/ shows the following files:
Bash:
drwxr-xr-x backup backup .chunks
-rwxr-xr-x backup backup .gc-status
-rwxr-xr-x backup backup .lock
drwxr-xr-x backup backup vm

Inside .chunks there are about a quadrillion folders ranging from 0000 to ffff.
 
what does find /mnt/backup/.chunks -type d | wc -l say? it should return "65537"
 
what does find /mnt/backup/.chunks -type d | wc -l say? it should return "65537"
65537
I executed it on the SMB Server, instead of PBS.
The find command took longer than I wanted to wait on PBS, while on the SMB server it was finished nearly instantly.
 
well, backups in general work over CIFS here (for GC you need to enable some flags for locks), so there must be some issue with your datastore and/or samba server. you could try finding out via strace which file it fails to find (but that will be rather noisy).
 
Do you have any hint what might be wrong?
rsync, scp and rdiff-backup work correctly here.
 
like I said, you can attach with 'strace' (e.g., strace -ff -o pbs_ -p $(pidof proxmox-backup-proxy) -e %file and see whether you can find the backup task in the resulting output, there should be a line for the error from the log (some open syscall that returns ENOENT), then you can backtrace from there (or post the corresponding file here) to find the path that it tried to open.
 
Thank you very much, especially for that strace command.
It would've probably taken me another week to understand how to do that :p

I attached the files to this post.
There were 2 more files (pbs_.892 and pbs_.896) but they were empty.

grep ENOENT over all pbs_ files results
Bash:
pbs_.18187:statx(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f7740ba3a10) = -1 ENOENT (No such file or directory)
pbs_.18187:unlink("/mnt/backup/vm/102/2021-04-20T12:55:08Z/drive-scsi0.img.tmp_fidx") = -1 ENOENT (No such file or directory)
pbs_.18187:openat(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
pbs_.18187:statx(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f7740ba3a10) = -1 ENOENT (No such file or directory)
pbs_.18187:statx(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f7740ba3a10) = -1 ENOENT (No such file or directory)
pbs_.18187:statx(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f7740ba3a10) = -1 ENOENT (No such file or directory)
pbs_.31361:openat(AT_FDCWD, "/etc/proxmox-backup/sync.cfg", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
pbs_.31361:openat(AT_FDCWD, "/etc/proxmox-backup/tape-job.cfg", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
pbs_.31361:openat(AT_FDCWD, "/etc/proxmox-backup/tape.cfg", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
pbs_.31361:access("/sys/devices/pci0000:00/0000:00:01.1/ata2/host1/target1:0:0/1:0:0:0/scsi_generic/uevent", F_OK) = -1 ENOENT (No such file or directory)
pbs_.31361:access("/sys/devices/pci0000:00/0000:00:05.0/virtio1/host2/target2:0:0/2:0:0:0/scsi_generic/uevent", F_OK) = -1 ENOENT (No such file or directory)
pbs_.31361:statx(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f772b9f4a10) = -1 ENOENT (No such file or directory)
pbs_.31361:openat(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
pbs_.31361:statx(AT_FDCWD, "/mnt/backup/.chunks/bb9f/bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f772b9f98a0) = -1 ENOENT (No such file or directory)
pbs_.31361:openat(AT_FDCWD, "/mnt/backup/.chunks/bb9f/bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8.tmp", O_WRONLY|O_CREAT|O_TRUNC|O_CLOEXEC, 0666) = -1 ENOENT (No such file or directory)
pbs_.31361:statx(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f772b9f4a10) = -1 ENOENT (No such file or directory)
pbs_.31361:openat(26, "0:54", O_RDONLY|O_NOFOLLOW|O_CLOEXEC|O_PATH) = -1 ENOENT (No such file or directory)
pbs_.31361:statx(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f772b9f4a10) = -1 ENOENT (No such file or directory)
pbs_.31361:statx(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f772b9f4a10) = -1 ENOENT (No such file or directory)
pbs_.31361:openat(26, "0:54", O_RDONLY|O_NOFOLLOW|O_CLOEXEC|O_PATH) = -1 ENOENT (No such file or directory)
pbs_.889:statx(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f77409a2a10) = -1 ENOENT (No such file or directory)
pbs_.889:openat(26, "0:54", O_RDONLY|O_NOFOLLOW|O_CLOEXEC|O_PATH) = -1 ENOENT (No such file or directory)
pbs_.889:unlink("/mnt/backup/vm/101/2021-04-20T12:55:07Z/drive-scsi0.img.tmp_fidx") = -1 ENOENT (No such file or directory)
pbs_.889:openat(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
pbs_.889:statx(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f77409a2a10) = -1 ENOENT (No such file or directory)
pbs_.889:statx(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f77409a2a10) = -1 ENOENT (No such file or directory)
pbs_.891:statx(AT_FDCWD, "/mnt/backup/.chunks/bb9f/bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f7740da98a0) = -1 ENOENT (No such file or directory)
pbs_.891:openat(AT_FDCWD, "/mnt/backup/.chunks/bb9f/bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8.tmp", O_WRONLY|O_CREAT|O_TRUNC|O_CLOEXEC, 0666) = -1 ENOENT (No such file or directory)
pbs_.891:openat(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
pbs_.891:openat(26, "0:54", O_RDONLY|O_NOFOLLOW|O_CLOEXEC|O_PATH) = -1 ENOENT (No such file or directory)
pbs_.891:statx(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f7740da4a10) = -1 ENOENT (No such file or directory)
pbs_.891:statx(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f7740da4a10) = -1 ENOENT (No such file or directory)
pbs_.891:openat(26, "0:54", O_RDONLY|O_NOFOLLOW|O_CLOEXEC|O_PATH) = -1 ENOENT (No such file or directory)
pbs_.891:statx(AT_FDCWD, "/var/log/proxmox-backup/tasks/index", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7f7740da4a10) = -1 ENOENT (No such file or directory)
pbs_.891:openat(26, "0:54", O_RDONLY|O_NOFOLLOW|O_CLOEXEC|O_PATH) = -1 ENOENT (No such file or directory)

I guess these files are not really the problem?
Code:
/var/log/proxmox-backup/tasks/index
/mnt/backup/vm/102/2021-04-20T12:55:08Z/drive-scsi0.img.tmp_fidx
/etc/proxmox-backup/sync.cfg
/etc/proxmox-backup/tape-job.cfg
/etc/proxmox-backup/tape.cfg
/sys/devices/pci0000:00/0000:00:01.1/ata2/host1/target1:0:0/1:0:0:0/scsi_generic/uevent
/sys/devices/pci0000:00/0000:00:05.0/virtio1/host2/target2:0:0/2:0:0:0/scsi_generic/uevent

But these may be?
Code:
/mnt/backup/.chunks/bb9f/bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8
/mnt/backup/.chunks/bb9f/bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8.tmp

The folder /mnt/backup/.chunks/bb9f/ is empty.
 

Attachments

  • pbs_.889.txt
    13.9 KB · Views: 7
  • pbs_.891.txt
    37.2 KB · Views: 1
  • pbs_.18187.txt
    4.9 KB · Views: 1
  • pbs_.31361.txt
    35.1 KB · Views: 1
Last edited:

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!