How do I add PBS to PVE?

A

aaronstuder

Member
Jul 11, 2020
12
0
6
38
Using the docs here: https://pbs.proxmox.com/docs/administration-guide.html#proxmox-ve-integration

pvesm add pbs backups --server <IP_ADDRESS> --datastore backups
create storage failed: error during cfs-locked 'file-storage_cfg' operation: proxmox-backup-client failed: Error: error trying to connect: the handshake failed: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1915:: self signed certificate

pvesm set backups --fingerprint <FINGERPRINT>
update storage failed: error during cfs-locked 'file-storage_cfg' operation: storage 'backups' does not exist

So how do I get this setup?
 
Did you create a user with permissions on the datastore backups? I don't see any in the pvesm command.
 
You can also use the GUI (Add storage) on Proxmox VE.

But make sure, you have very latest proxmox-backup-client (at least 0.8.6-1) and pve-manager 6.2.9 installed on your Proxmox VE
 
Hi Tom,

... I wasn't able to add it using the GUI (pve is up2date...) but managed to add it using command line...

Still, when I try to create a backup, this is what happens (backup fails):
2020-07-11T11:36:20+02:00: starting new backup on datastore 'pbs01': "vm/802/2020-07-11T09:36:20Z"
2020-07-11T11:36:20+02:00: GET /fixed_index: 404 Not Found: Path not found.
2020-07-11T11:36:20+02:00: backup ended and finish failed: backup ended but finished flag is not set.
2020-07-11T11:36:20+02:00: removing unfinished backup
2020-07-11T11:36:20+02:00: TASK ERROR: backup ended but finished flag is not set.

I have the datastore on NFS, just FYI.

EDIT: Logs on PVE are:
INFO: starting new backup job: vzdump 802 --mode snapshot --compress zstd --remove 0 --node blahnjukur --storage pbs01
INFO: Starting Backup of VM 802 (qemu)
INFO: Backup started at 2020-07-11 11:36:20
INFO: status = running
INFO: VM Name: opencart-compination
INFO: include disk 'virtio0' 'esns-b:802/vm-802-disk-0.qcow2' 32G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating pbs archive on storage 'pbs01'
ERROR: VM 802 qmp command 'backup' failed - backup register image failed: command error: HTTP Error 404 Not Found: Path not found.
ERROR: Backup of VM 802 failed - VM 802 qmp command 'backup' failed - backup register image failed: command error: HTTP Error 404 Not Found: Path not found.
INFO: Failed at 2020-07-11 11:36:20
INFO: Backup job finished with errors
TASK ERROR: job errors


Tobias
 
iprigger said:
Hi Tom,

... I wasn't able to add it using the GUI (pve is up2date...) but managed to add it using command line...

Still, when I try to create a backup, this is what happens (backup fails):
2020-07-11T11:36:20+02:00: starting new backup on datastore 'pbs01': "vm/802/2020-07-11T09:36:20Z"
2020-07-11T11:36:20+02:00: GET /fixed_index: 404 Not Found: Path not found.
2020-07-11T11:36:20+02:00: backup ended and finish failed: backup ended but finished flag is not set.
2020-07-11T11:36:20+02:00: removing unfinished backup
2020-07-11T11:36:20+02:00: TASK ERROR: backup ended but finished flag is not set.

I have the datastore on NFS, just FYI.

EDIT: Logs on PVE are:
INFO: starting new backup job: vzdump 802 --mode snapshot --compress zstd --remove 0 --node blahnjukur --storage pbs01
INFO: Starting Backup of VM 802 (qemu)
INFO: Backup started at 2020-07-11 11:36:20
INFO: status = running
INFO: VM Name: opencart-compination
INFO: include disk 'virtio0' 'esns-b:802/vm-802-disk-0.qcow2' 32G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating pbs archive on storage 'pbs01'
ERROR: VM 802 qmp command 'backup' failed - backup register image failed: command error: HTTP Error 404 Not Found: Path not found.
ERROR: Backup of VM 802 failed - VM 802 qmp command 'backup' failed - backup register image failed: command error: HTTP Error 404 Not Found: Path not found.
INFO: Failed at 2020-07-11 11:36:20
INFO: Backup job finished with errors
TASK ERROR: job errors


Tobias
Click to expand...
Btw... just as a follow-up: Just did the same using a ZFS Datastore on the backup server - same exact result (unfortunately).

Tobias
 
Hi,
tom said:
Why not, any error message?
Click to expand...

I run pve-626 (I run on the subscription-version and not on the free version).

That's probably why.... nevertheless it seems like the backup isn't finding something when trying to create...

It looks like the storage is valid and the integration at first worked... at least I get:

Name Type Status Total Used Available %
pbs01 pbs active 3104308864 24960 3104283904 0.00%

on all pve cluster members.

tobias
 
iprigger said:
run pve-626 (I run on the subscription-version and not on the free version).

That's probably why.... nevertheless it seems like the backup isn't finding something when trying to create...
Click to expand...

Yes, an update for this is still pending for enterprise. You should then be able to add it directly over the Webinterface like other storages.

For now you can use the CLI as workaround:
Bash: 
pvesm add pbs <id> --datastore <pbs-datastore-name> --server <ip-or-host> --fingerprint 00:AB:CD:...  --username root@pam --password

(Using "--password" without a value will ask for the password over the tty)
Most important things to check is:
* set the fingerprint if you use self-signed certs for the Proxmox Backup Server (default) - it can be copied from the PBS GUI dashboard
* if you do not use the PBS root@pam you add some permissions first, new users have none on the server.
https://pbs.proxmox.com/docs/administration-guide.html#access-control
 
Hi,

t.lamprecht said:
Yes, an update for this is still pending for enterprise. You should then be able to add it directly over the Webinterface like other storages.

For now you can use the CLI as workaround:
Bash: 
pvesm add pbs <id> --datastore <pbs-datastore-name> --server <ip-or-host> --fingerprint 00:AB:CD:...  --username root@pam --password

(Using "--password" without a value will ask for the password over the tty)
Most important things to check is:
* set the fingerprint if you use self-signed certs for the Proxmox Backup Server (default) - it can be copied from the PBS GUI dashboard
* if you do not use the PBS root@pam you add some permissions first, new users have none on the server.
https://pbs.proxmox.com/docs/administration-guide.html#access-control
Click to expand...

Still no luck...

pvesm add pbs pbs01 --server <IPY--username proxmoxbackup@pbs --password <PASS> --datastore pbs01 --fingerprint 10:[..]:5d

# pvesm status --storage pbs01
Name Type Status Total Used Available %
pbs01 pbs active 3104308864 24960 3104283904 0.00%



INFO: starting new backup job: vzdump 640 --node burfell --remove 0 --compress zstd --storage pbs01 --mode snapshot
INFO: Starting Backup of VM 640 (qemu)
INFO: Backup started at 2020-07-11 13:27:05
INFO: status = running
INFO: VM Name: smb4dc01
INFO: include disk 'virtio0' 'esns-b:640/vm-640-disk-1.raw' 32G
INFO: exclude disk 'virtio1' 'zz_PVE_TMS:640/vm-640-disk-0.raw' (backup=no)
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating pbs archive on storage 'pbs01'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 640 qmp command 'backup' failed - backup register image failed: command error: HTTP Error 404 Not Found: Path not found.
ERROR: Backup of VM 640 failed - VM 640 qmp command 'backup' failed - backup register image failed: command error: HTTP Error 404 Not Found: Path not found.
INFO: Failed at 2020-07-11 13:27:06
INFO: Backup job finished with errors
TASK ERROR: job errors


... somehow doesn't work.

Same result no matter if I use the nfs-storage on pbs or the zfs drive... Could this be because of the proxmox version?

Tobias
 
iprigger said:
ERROR: VM 640 qmp command 'backup' failed - backup register image failed: command error: HTTP Error 404 Not Found: Path not found.
Click to expand...

This means that an API request was made on an API path which does not exist.

Can you post the following information from Proxmox VE side please :
Bash: 
pveversion -v

proxmox-backup-client version --repository user@pbs@serveraddress:pbs01
 
Hi,

t.lamprecht said:
This means that an API request was made on an API path which does not exist.

Can you post the following information from Proxmox VE side please :
Bash: 
pveversion -v

proxmox-backup-client version --repository user@pbs@serveraddress:pbs01
Click to expand...

here you go:
Code: 
proxmox-ve: 6.2-1 (running kernel: 5.4.41-1-pve)
pve-manager: 6.2-6 (running version: 6.2-6/ee1d7754)
pve-kernel-5.4: 6.2-4
pve-kernel-helper: 6.2-4
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.4.44-1-pve: 5.4.44-1
pve-kernel-5.4.41-1-pve: 5.4.41-1
pve-kernel-4.15: 5.4-8
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-4.15.18-20-pve: 4.15.18-46
pve-kernel-4.15.18-12-pve: 4.15.18-36
ceph-fuse: 12.2.13-pve1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve2
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-3
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-8
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-8
pve-cluster: 6.1-8
pve-container: 3.1-8
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-3
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1

and
Code: 
client version: 0.8.6
server version: 0.8.6
 
iprigger said:
pve-manager: 6.2-6
pve-qemu-kvm: 5.0.0-4
qemu-server: 6.2-3
Click to expand...

Yes those are too old, note that the enterprise repository is still missing a few updates (not moved yet due to stability policy) which it will get soon, if nothing comes up.

You'd need at least the following set:
Code: 
pve-manager: 6.2-9
pve-qemu-kvm: 5.0.0-9
qemu-server: 6.2-8

Or newer.
 
  • Like
Reactions: iprigger
Hi,

t.lamprecht said:
Yes those are too old, note that the enterprise repository is still missing a few updates (not moved yet due to stability policy) which it will get soon, if nothing comes up.

You'd need at least the following set:
Code: 
pve-manager: 6.2-9
pve-qemu-kvm: 5.0.0-9
qemu-server: 6.2-8

Or newer.
Click to expand...

Well, pity. Then I'm looking forward to the next update of PVE (the cluster I run is on the enterprise...) :)

Tobias
 
t.lamprecht said:
Yes those are too old, note that the enterprise repository is still missing a few updates (not moved yet due to stability policy) which it will get soon, if nothing comes up.

You'd need at least the following set:
Code: 
pve-manager: 6.2-9
pve-qemu-kvm: 5.0.0-9
qemu-server: 6.2-8

Or newer.
Click to expand...

It looks like I'm running modern actual versions but still here is the error:

pvesm add pbs prox-backup --server localhost --datastore backup --fingerprint 58:...:fe --username root@pam --password

Code: 
create storage failed: error during cfs-locked 'file-storage_cfg' operation: proxmox-backup-client failed: Error: error trying to connect: the handshake failed: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1915:: self signed certificate

Code: 
proxmox-ve: 6.2-1 (running kernel: 5.4.44-2-pve)
pve-manager: 6.2-11 (running version: 6.2-11/22fb4983)
pve-kernel-5.4: 6.2-5
pve-kernel-helper: 6.2-5
pve-kernel-5.4.55-1-pve: 5.4.55-1
pve-kernel-5.4.44-2-pve: 5.4.44-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-5
libpve-guest-common-perl: 3.1-2
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-6
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-11
pve-cluster: 6.1-8
pve-container: 3.1-12
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-2
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-12
pve-xtermjs: 4.7.0-1
pve-zsync: 2.0-3
qemu-server: 6.2-11
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve1


Also the same error via PVE GUI interface.

In most cases, I will be happy to install the correct SSL certificate from PVE if this could help but there are no references in docs how to do that.

Any suggestions?
 
Last edited:
Honestly, I could just imagine that the fingerprint you entered is wrong.
As you installed the Proxmox Backup Server directly on the same Proxmox VE you can just check proxmox-backup-manager cert info
 
t.lamprecht said:
Honestly, I could just imagine that the fingerprint you entered is wrong.
As you installed the Proxmox Backup Server directly on the same Proxmox VE you can just check proxmox-backup-manager cert info
Click to expand...

Actually fingerprint has been taken exactly from proxmox-backup-manager cert info output and tried in both CLI and UI.
Any other suggestions?
 
So answering myself from the future to share knowledge - it is impossible to setup storage with root@pam user but only with user@pbs
 
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
Back