I have a backup problem on Proxmox 6.3, on a hundred VMs backed up daily, I have no errors, for 2 of them, it goes into error in suspend mode, if I do the backup in stop mode manually , no problem.
Bakckup are send to NFS, generate on local tmp folder.
For both, I have this log on backup...
Some of my schedule backup failed with the error:
gzip --rsyncable failed - wrong exit status 1
Although backup progress in the log finished at 100%, the backup still failed with gzip (or zstd) wrong exit status.
This happen with both CT and VM backup, and with gzip and zstd...
Wanted to change from CIFS to NFS, but now backups fail:
INFO: starting new backup job: vzdump 100 --storage LXC_Backups --compress zstd --mode snapshot --remove 0 --node 0v3rw4tch
INFO: Starting Backup of VM 100 (lxc)
INFO: Backup started at 2021-02-17 18:23:42
INFO: status = running...
I'm having trouble on our Proxmox nodes with backing up. I noticed that LZO compressed backups were failing to create, so I have tried backing up using no compression at all but get the following error text.
INFO: 98% (117.9 GiB of 120.0 GiB) in 14m 54s, read: 1.3 GiB/s, write: 0 B/s...
I just set up a PBS and wanted to try it with my PVE Lab consisting of 3 nodes and CEPH storage at the latest version (6.2-11)
I added my PBS Storage and started a Backup to my storeage with ZSTD compression, Snapshot mode. (All done via GUI)
The task immediatly errors out with:
ich möchte auf meinem Proxmox ein Backup einrichten. Das Backup soll zu meiner NAS übertragen werden.
Ich habe auf meiner NAS NFS aktiviert und den Proxmox Host über eine IP-Adresse zugelassen.
Der User hat auch Admin Rechte.
Auf dem Proxmox habe ich ein neues Storage über...
When we try to Backup a container we get the following output:
INFO: trying to get global lock - waiting...
INFO: got global lock
INFO: starting new backup job: vzdump 107 --node node2 --remove 0 --compress zstd --storage fileserver_daily --mode snapshot
INFO: filesystem type on dumpdir is...
I just recently dicided to try using ceph for my home servers. I backed up all VMs and LXCs and then restored them to ceph on the new cluster. Everything was working fine except for the Nextcloud LXCs. I have two nextcloud LXCs running and I am having same problem with both. I have...
Got a subscribed proxmox 5.4-6 with all packages updated.
Since 19 of april we're unable to do backups or cloning.
Tried changing compression and making all kind of backups (stop/suspend/snapshot) but the system reboots and lock the machine with the error:
Backup of VM 100 failed - command...
Dear members of the Proxmox forum
Since yesterday I'm experiencing a problem with the vzdump back-up tool.
When the backup of my vm's starts, everything goes well, except after a minutes or 5-10 I receive the following error message: unable to find configuration file for VM 100 - no such...
I have a cluster consisting of three nodes. As it's a fairly small cluster I run ceph directly on the pve nodes. Currently I'm running 13 VMs on that cluster. I'm using HA and I run automatic backups of most VMs once per night.
A couple of days ago a VM (id 107) couldn't complete the backup job...
I've configured VZDump to run daily and to backup all VMs (which include KVM and LXC).
LXC containers backup without issues every time; KVM, however, does not.
My current KVM guests are Windows 10 Pro and Windows Server 2016. Both have enabled "Shutdown: Allow system to be shutdown without...
I've getting an error with the backup of an LXC container to my NFS shared storage for a while now. I was hoping someone could make some sense of the error message and point me in the right direction to get it backing up again. I have other CT's and VM's backing up to this shared storage...
I have been trying to find a solution to this annoying problem for over six months. Have updated both servers (one is a community edition subscription and one is without subscription). This happens with both of them.
Whenever I try to have an automated or manual backup of my VM (I don't...