I found what the problem was. I should have filled in the read limit in the restore window. However it suggests (greyed out) that not filling in a value means that the default will be used. I tried 0 as suggested the value to be unlimited, did not work either. I used value 1 and than the restore...
When restoring a LXC container I got the this error:
Parameter verification failed. (400)
bwlimit: type check ('number') failed - got ''
The same on my second Proxmox (not clustered).
What can be wrong?
first server version:
proxmox-ve: 6.1-2 (running kernel: 5.3.13-1-pve)
pve-manager: 6.1-4...
This is a serious problem for me. And I would like to know whether it has the attention of the Proxmox Team.
So, dear Dietmar, give us one of your famous one word answers on my question: is the Proxmox Team working on this problem?
Peter
Yesterday 15/1/2016 I updated the node and rebooted it. Backup to NFS was perfect. Today the scheduled backup failed: the vm's were O K.
The first CT hung on suspend vm. Still the same pattern: one backup is perfect, and then the next backups have this issue. After reboot one goog backup. Etc...
Well Dietmar, look here: https://forum.proxmox.com/threads/lxc-backup-randomly-hangs-at-suspend.25345/
This seems to be a real bug. Reported 28-12-2015 on this very list. No reaction of the Proxmox team. Very unusual I must agree. But still.
For the rest I'm quite happy to use the Turnkey LXC...
Still the same problem here. Did a complete reinstall of proxmox 4.1, with all the latest updates. Vm and lxc vt's backup fine two times. Then the vm's are still well backupped but the lyxcct's start to fail at suspend vm. At first the second one then the first one.
After a restart of the...
Same problem here.
KVM's are backuped without any problem.
LXC containers are backup once on a clean nfs share, next backups fail, at first on the last lxc container and then on the backup of the first.
vzdump.conf changed:
# vzdump default settings
tmpdir: /tmp
#dumpdir: DIR
#storage...
Hi,
Searching on google I found that the problem could be the mbr. The bios not immediatly recognizing the boot data in the MBR written on the disk for zfs.
Since I plan to invest in two new Proxmox servers without having to pay for expensive raid cards. it is very important for me to know...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.