Search results

Encryption is client side, you're right. I was thinking of the fingerprint that is linked to the PBS (proxy.pem and proxy.key). Copying the whole /etc/proxmox-backup folder and keeping IP/name seems the way to go.

Once posted, I also thought about the PBS key (encryption). Is there a CLI tool/script to export everything needed to move/rebuild PBS to another VM/server? Or maybe the easiest way would be to backup/clone PBS (with clonezilla or why not VeeamAgent or another solution) and restore it to the...

Hello all. My PBS is currently a VM (running on my Ceph Proxmox cluster) and backups happen on a FreeNAS NFS share. It's not fast (at all) and the more backup I have, the more garbage collector takes time (soon 20 hours). My FreeNAS boots on a pair of RAID1 SSD, I'm contemplating the idea of...

Thank you!

I actually name the file .ova on download but I could have used any other extension 8-) But any name/extension I decide to use, I'll end up with a tar archive. Shouldn't the wiki be upddated to reflect that (and that you have to untar it before use)?

Hello. I tried a V2V import based on the wiki steps. https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#CLI I installed vmware's ovftool on a node and downloaded a VM from a vSphere Infrastructure (it works, you can connect to the vCenter and download through it, no need to...

It might be related to the slowness of my repo (FreeNAS NFS mount) and might not happen with a dedicated server + local ZFS.

Hi. The error did not happen this night. root@pbs:~# proxmox-backup-manager versions --verbose proxmox-backup 1.0-4 running kernel: 5.4.78-2-pve proxmox-backup-server 1.0.6-1 running version: 1.0.6 pve-kernel-5.4 6.3-3 pve-kernel-helper 6.3-3...

Most of it is is post #3. Longer version below: Jan 26 01:03:41 pbs proxmox-backup-proxy[6187]: starting new backup on datastore 'BKP_PBS_NCP': "vm/131/2021-01-26T00:03:41Z" Jan 26 01:03:41 pbs proxmox-backup-proxy[6187]: download 'index.json.blob' from previous backup. Jan 26 01:03:41 pbs...

There is this error for several VM. Jan 26 00:30:11 pbs proxmox-backup-proxy[6187]: error during snapshot file listing: 'unable to load blob '"/mnt/BKP/vm/168/2021-01-25T23:30:03Z/index.json.blob"' - No such file or directory (os error 2)' Jan 26 00:30:13 pbs proxmox-backup-proxy[6187]: error...

There's a 400 error (bad request) in PBS'syslog: Jan 26 01:04:18 pbs proxmox-backup-proxy[6187]: Upload statistics for 'drive-scsi0.img.fidx' Jan 26 01:04:18 pbs proxmox-backup-proxy[6187]: UUID: 517ba5ee62f74948b3f5f12cde84d5b5 Jan 26 01:04:18 pbs proxmox-backup-proxy[6187]: Checksum...

Hi. I got this in my mailbox this morning, last night backup; if the mail is right, one of the VM did not backup correctly. 137: 2021-01-26 01:03:23 INFO: Starting Backup of VM 137 (qemu) 137: 2021-01-26 01:03:23 INFO: status = running 137: 2021-01-26 01:03:23 INFO: VM Name: lm-old 137...

Great. Can you modify the thread and add "Solved" to the subject?

It seems you have declared the backup datastore at the root of your PBS server. You should delare it in an empty subfolder of the server. See here: https://forum.proxmox.com/threads/permission-issue-error-on-garbage-collection.79014/

You were right. I found my error: I used this repo to create a VM (the day the GC failed) instead of the correct storage. I'm removing the "Disk image" property of the storage right now!

Hi Fabian, this should not have changed (no server reboot, no new user, no known change). Also, backup happens correctly, pruning too. root@pbs:/mnt# ls -la total 36 drwxr-xr-x 4 root root 4096 Oct 19 15:33 . drwxr-xr-x 18 root root 4096 Jan 18 16:00 .. drwxrwxrwx 14 backup backup...

.gs-status file still exist in the root of the mountpoint (my repo is NFS). File date is the end of the last GC that worked correctly...

Hi. Since two days (january 15), garbage collect start at midnight. Before that, it started during the day, at very different time (see screenshot). Since this schedule change, it fails with this error: Garbage collection failed: cannot continue garbage-collection safely, permission denied...

I had the "Directory not empty (os error 39)" error on my NFS datastore. The error was shown on backup pruning (trying to delete backups older than the retention). Upgrading to 1.0.6-1 seems to have fixed it. I upgraded yesterday then forced a "Datastore prune" and it went OK. No more error in...

root@pve01:~# ceph osd pool autoscale-status POOL SIZE TARGET SIZE RATE RAW CAPACITY RATIO TARGET RATIO EFFECTIVE RATIO BIAS PG_NUM NEW PG_NUM AUTOSCALE SSD 6005G 3.0 71535G 0.2519 1.0...