Search results

I have been backing up to PBS for a few weeks. The backup job contains 3 VMs. THe first one was backed up correctly the next 2 failed with this error: in this code you can see the end of the backup of the first VM followed by the error. INFO: 97% (18.6 GiB of 19.1 GiB) in 4m 57s, read: 85.3...

@fabian thanks for your step-by-step - it seems to be working now and the sync job is running. All that needed changing was this: - give sync@pbs user (+ token) read permission on source datastore (either DatastoreBackup to only sync owned backups, or DatastoreReader to sync everything) I had...

thanks @fabian that sounds good but I am still confused. For one, where does the token on PBS-A get used? I mean if I set up the token on PBS-A that token must somehow be used on PBS-B as PBS-B is the one where the sync job runs. So when adding PBS-A on PBS-B as remote, what credentials do I...

well, let say the command has a bug, I am still having the problem that after adding the remote I am trying to setup a sync job. So I add the job on PBS-B, select the source remote and then when I try to select the source datastore and click the drop-down, instead of it showing me the remote...

Hi there, I have 1 PVE and 2 PBS instances. PBS-A is installed on the same host as PVE while PBS-B is on its own host (remote). I am doing backups to PBS-A and keep them only for a short term. PBS-B is meant to add PBS-A as a remote and then sync backups and keep them long term. What works...

I just wanted to add that apparently you can also use API Tokens instead of user/password.

oh, btw. looking at cat /etc/pve/storage.cfg dir: local-enc path /sixer/backups/ content backup is_mountpoint yes maxfiles 3 shared 0 I had to add the argument: "is_mountpoint" yes so that PVE does not create a directory instead of waiting for the...

systemctl restart proxmox-backup proxmox-backup-proxy did not help systemctl status proxmox-backup proxmox-backup-proxy show all green and working I have now used 127.0.0.1 instead of localhost and its up and working. This is weird though as when I initially connected PVE to PBS I used...

I apologize, I thought you only hinted at "networking misconfiguration". looking at journalctl right after the restart: Dec 03 15:30:39 nas proxmox-backup-proxy[3531]: read disk_usage on "/sixer/backups/pbs" failed - ENOENT: No such file or directory Dec 03 15:30:39 nas...

Reboot didn't help, any hints based upon this error message: pbs-local: error fetching datastores - 500 500 Status read failed: Connection reset by peer (500)

Thanks, I saw that but don't see how networking issues can apply since PVE and PBS are installed on the same host. Nevertheless I will try a reboot and report back.

can I jump onto this thread, today I saw a very similar error. I have installed PVE 6.3-2 AND PBS 1.0-5 on the SAME machine. This is my local homelab. So PBS is addresses as localhost and backups to the PBS are working but when browsing to the PBS via PVE I get the rror: pbs-local: error...

I just wanted to say that the wiki is slightly incorrect regarding the storage location of the encryption key. https://pve.proxmox.com/wiki/Storage:_Proxmox_Backup_Server says: encryption-key A key to encrypt the backup data from the client side. Currently only non-password protected (no key...

thanks, that hint solved it.

test install of pbs here. going straight to add new datastore, give it a name and as path I enter /storage/backups/pbs as a result pbs creates the pbs folder as /storage/backups already exists and seems to make a chown -R backup:backup /storage/backups/pbs and apparently sets 755 as...

I just wanted to add that I had the exact same problem right now with Debian Buster so it seems nothing has changed :-) As I am not aware of having a need for aufs-dkms I have uninstalled it.

not sure if it was purging the different pve components but things seem to work now. Thanks for the help.

ok, after removing most promox-ve leftovers I can't seem to update initramfs-tools apt-get install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After...

found the solution here: https://blog.stevedong.com/post/proxmox-ve-how-to-fixed-upgrade-error/

I am fooling around on a test server and was simply trying out proxmox-ve and installing it with zfs on root. I now would like to remove proxmox-ve and keep doing some tests with zfs so I tried the following: apt-get remove proxmox-ve which asked me to do a touch '/please-remove-proxmox-ve'...