Search results

Afaik not, as this is by design in qemu :/

Thats right, but the question was "This upgrade is needed to later upgrade to 4.x proxmox version, is'nt it ?" - and this is not the case.

qm unlock <ID>

That is no problem, just an information.

Wie kommst du denn darauf? Ceph ist sicher Vieles, experimentell aber ganz sicher nicht :)

Yeah :D

As this is the case also for some other actions imho it would be nice to have a "disable HA" button or command, which completely disables HA. This would be very useful to avoid fencing, reboots and various VM migrations before/during updates!

Das bietet sich auf jeden Fall an.

Hallo, interner Traffic wir i.d.R. nicht berechnet. Genau kann dir das aber nur dein RZ sagen :)

Sounds great, but pigz can burn all CPU cores, which can cause problems in in VM enviroment ;-) You could test lzop, which PVE also uses for VMA format. Its very fast with medium compression, which is enough in most cases. Mounting it as RAW ist very nice, indeed, and makes it really...

Thanks for clarifying! Raw sounds good, but the backups are fullsized filesystems then, right? What about compression?

You can simply use: ip link set dev eth0 mtu 9000 i.e. The change in /etc/network/interfaces should also be made for persistence.

I dont't know :( Must have something to do with the chunk size and its allocation when importing.

We're using HP DL160 gen9 with Dual Xeon E5 and 2 x Samsung SM863 SSD, so imho this does exist on actual machines, too :/ Problem occured with the first import on that empty and new machine (20+ loadavg and 50k IOPS while importing). Our problem ist not slowness, but heavy load when importing...

For daily backups we also use rsync and Bareos, but to have a VMA image by the hand is good to know in case of hardware emergency :-)

The hanging NFS ist one problem, but that should imho not bringing the running VM from which the backup is made in an unuseable state :/

Sure, but same problems when NFS uplink is "full". We always use LZO compression.

Oh stimmt, sorry - hatte das nur von den HDDs gelesen. RaiserCard könnte es dennoch sein.

Ganz spontan würde ich hier auf einen defekten RAID Controller und/oder Mainboard und/oder RaiserCard tippen. Wir haben recht viele LSI MegaRAID SAS 9271-4i mit PVE laufen, ohne Probleme. Allerdings ohne CacheVault.

Wenn du wüsstest wie populär das bei den Kunden noch ist :-( Wir forcieren schon sehr lange SCP/SFTP, aber FTP bekommst du einfach nicht weg. Immerhin nutzen viele inzwischen FTPS, seit Filezilla per default STARTTLS sendet ;)