[SOLVED] Backup fails with PBS

T

Taylan

Active Member
Oct 19, 2020
92
33
38
54
After reinstalling my pve I tried to run my backup job, which should backup everything on my pbs.
I can't run the job however, I get following error:

Code: 
Some errors have been encountered:
Proxmox: Parameter verification failed. (400)

next-run: property is not defined in schema and the schema does not allow additional properties

Here are the backup details:
Bash: 
# cat /etc/pve/jobs.cfg
vzdump: backup-bc19d4fc-dca9
    schedule 00:00
    compress zstd
    enabled 1
    mailnotification always
    mailto no-reply@proxmox.com
    mode snapshot
    prune-backups keep-last=3
    storage local
    vmid 110,101,102,103,104,105,106,107,108

vzdump: backup-1dd24a1b-d33f
    schedule 00:00
    all 1
    enabled 1
    mailnotification always
    mailto no-reply@proxmox.com
    mode snapshot
    node Proxmox
    prune-backups keep-all=1
    storage pbs


Edit: I just tried to take a backup to local, same error:


Edit2: If I try to backup individual container/VMs, it works...

Edit3: The scheduled jobs ran fine.

Final Edit: The issue gets resolve after updating to pve-manager/stable 7.1-10.
 
Last edited:
Mh, same issue here.
Some Jobs are working some are not working.

Is there still a Work-Arround?
 
I had to reinstall the os, so there is for me no way to revert the affected packages. Other workaround is to manually individually backup one by one.
 
  • Like
Reactions: ikarlo
Hey,

this is not a Solution to install all my servers. pretty sure its something with the update and there will be a fix very soon.
 
Last edited:
  • Like
Reactions: jemerson.jsilva
I have an update. When i start it manuely it doese not work.
When it runs via Cronjob it seems to be working. Tested on 2 nodes and both are working when the backup is initiated via Cronjob/pmx itself
 
Taylan said:
After reinstalling my pve I tried to run my backup job, which should backup everything on my pbs.
I can't run the job however, I get following error:
Click to expand...
Which version (roughly) were they running prior to the reinstallation?
Did you install the latest updates after the reinstallation?
Did you do a clean reinstall or is there a cluster, and you reinstalled one node at a time?
baldy said:
I have an update. When i start it manuely it doese not work.
When it runs via Cronjob it seems to be working.
Click to expand...
If it only fails when starting the job manually via the GUI (?), try to do a full reload of the GUI (for example Shift+F5) as it is possible that the browser cache is interfereing.
 
aaron said:
Which version (roughly) were they running prior to the reinstallation?
Did you install the latest updates after the reinstallation?
Did you do a clean reinstall or is there a cluster, and you reinstalled one node at a time?

If it only fails when starting the job manually via the GUI (?), try to do a full reload of the GUI (for example Shift+F5) as it is possible that the browser cache is interfereing.
Click to expand...
Hey aaron,

I can't say. I'm using my pve not in a cluster, it's just one server and I had to reinstall the proxmox (SSDs exchanged). After reinstalling with the newest ISO, I've run one dist-upgrade. I'll take a look at the logs (or to the ones in the backup), which version was updated (after work).

I don't think, it has anything to do with the browser though.
 
AFAIU you run into the issue when you start the job via the GUI by clicking "Run Now"?

Which version of pve-manager do you have installed? Looks like there was some issue that has been fixed in the very recent version 7.1-10 which was released today in the no-subscription repository. https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=076af227ef47707e41ab1d8b2a85c77536abc3df

After installing the updates and refreshing the browser, starting jobs manually worked fine. Before updating the browser, I ran into the same error message.
 
  • Like
Reactions: ielbury
aaron said:
AFAIU you run into the issue when you start the job via the GUI by clicking "Run Now"?

Which version of pve-manager do you have installed? Looks like there was some issue that has been fixed in the very recent version 7.1-10 which was released today in the no-subscription repository. https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=076af227ef47707e41ab1d8b2a85c77536abc3df

After installing the updates and refreshing the browser, starting jobs manually worked fine. Before updating the browser, I ran into the same error message.
Click to expand...
Yes, the error comes only by clicking "Run Now" on the Web-UI.

I'm extracting the necessary package logs from backup, it takes a while.

In the mean time I tested with a fresh installed browser. Same issue.
 
You can get the currently used by running pveversion -v or in the node summary (top left)
 
I just updated to PVE Manager Version 7.1-10, rebooted the node and then tried to run Datacenter Backup job and I am still getting the errror.

Backup Job:
Code: 
vzdump: backup-9d98d52e-d293
        schedule 21:00
        all 1
        compress zstd
        enabled 1
        mailnotification always
        mailto andjones132@gmail.com
        mode stop
        node node2
        prune-backups keep-daily=7,keep-last=7,keep-monthly=3,keep-weekly=4
        storage synology-nfs

Error:
Code: 
Some errors have been encountered:
node2: Parameter verification failed. (400)

next-run: property is not defined in schema and the schema does not allow additional properties

pveversion -v info:

Code: 
proxmox-ve: 7.1-1 (running kernel: 5.13.19-3-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-8
pve-kernel-5.13: 7.1-6
pve-kernel-5.11: 7.0-10
pve-kernel-5.13.19-3-pve: 5.13.19-6
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.3-1
proxmox-backup-file-restore: 2.1.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-4
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1
 
aj132 said:
I just updated to PVE Manager Version 7.1-10, rebooted the node and then tried to run Datacenter Backup job and I am still getting the errror.

Backup Job:
Code: 
vzdump: backup-9d98d52e-d293
        schedule 21:00
        all 1
        compress zstd
        enabled 1
        mailnotification always
        mailto andjones132@gmail.com
        mode stop
        node node2
        prune-backups keep-daily=7,keep-last=7,keep-monthly=3,keep-weekly=4
        storage synology-nfs

Error:
Code: 
Some errors have been encountered:
node2: Parameter verification failed. (400)

next-run: property is not defined in schema and the schema does not allow additional properties

pveversion -v info:

Code: 
proxmox-ve: 7.1-1 (running kernel: 5.13.19-3-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-8
pve-kernel-5.13: 7.1-6
pve-kernel-5.11: 7.0-10
pve-kernel-5.13.19-3-pve: 5.13.19-6
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.3-1
proxmox-backup-file-restore: 2.1.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-4
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1
Click to expand...
For me there was no reboot needed, I just had to clear my browser history and cache.
 
  • Like
Reactions: ielbury
@Taylan Thank you . That was it. After clearing Chrome browser cache and logging into Proxmox again, now the Backup job is running. Very strange. Thanks for your help.
 
  • Like
Reactions: Taylan
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom