Search results

I have noticed this problem with HP-SSDs as well as other server-SSDs. the same problem when used with LVM (normal). support says: is a problem with backup-battery, but this wasn't. I have on all HP-Servers battery backup online. As I said, with formating the disk e.g. with xfs and mount it in a...

I have the same problem since 7.x: on 3 different HPE Prolinet with SSD - lvm-thin. No stuck when using an SSD-directory directly, without lvm-thin. I have noted this many times.

The described server, where I want to make a backup, has everything in the gui greyed out, cpu/server load and io is nothing displayed. I have 2 similar server (HP DL 380) but other configurations. One with RADI5 and 3xSSD, one with Mirror SAS, etc. I have upgraded one from 6.1 to one of the...

In the gui is mostly everything greyed out. kern.og shows nothing about disks. The Backup-Directoy shows no log nor zst file fpr this job. dmesg does not show any disk-device problems. dmesg ... [14051133.396868] vmbr0: port 5(fwpr401p0) entered disabled state [14092732.624156] fwbr402i0...

Here you are. No further output, no entries in logs, no errors. The VMS are still running, backup from VMS which are NOT in the lvm-thin are working. root@taurus:/var/log# ps auxwf | grep vzdump root 3693050 0.1 0.0 317116 116752 pts/0 S 11:12 0:01 | \_ /usr/bin/perl -T...

>Perfect Idea! But there is no error message. It only stucks - making nothing. I nfuture I want to use ProxmoxBackupServer. But for this, I have to make a backup to a local disk: root@taurus:/BACKUP/dump# vzdump 405 INFO: starting new backup job: vzdump 405 INFO: Starting Backup of VM 405...

I will fix this - but before, I want to make a Backup. But due to a software problem from qmrestore there is a lock to the lvm-thin - and no backup is possible. Do you have an idea to solve the situation? (is there a fscp for lvm-thin which solves locks and repairs the partition inside)? tx

Maybe you are right. But this does not explain, why the first 20 GBYtes are OK in speed, and then exponentially the restore needs more time. It does also not explain, why this has been worked correctly with VME before 6.4. (e.g. 5.4 it works like a sharm). It does not explain, why a break locks...

No Kernel entries. In the log-files of vzdump is only the notice of starting backup, then nothing more. I can reproduce this behaviour: New installed server, actual PVE. Use 3 disks (e.g. SAS) and one boot disk with spare for backup. copy a 80 GB VM-Backup from a running VME to this server and...

Hi, No, there is no BBU, but write Cache is disabled. Anyhow, the drives are working really fast. But only in directy access mode. Not in LVM or LVM-thin mode. Yes, I have updated to the actual software. I have tested with 3 differnt HP 380 servers (gen8, Gen9, differnt configs). With Proxmox...

Additional information: I have reinstalled 2 more new servers and had the same problem: qmrestore to a single HDD or single SSD had no problems. But using the RAID for the server to e.g. RAID 5 for 3 x SAS or 3xSSD (lvm-thin), increases the speed for the restore process. For 30 GB VM, it will be...

I have here 2 HP Servers which have the same problems (3 more servers of dL380 with older PV which are working): * SATA and SSD HD are well working * SAS RAID is extremly slow. Backup recover with wmrestore from 30 GB HDD needs 5 hours. Gen8: Smart Array P420i on Gen9: Smart Array P840 ...