Search results

Hello. Out of curiosity. When we do a backup of our VMs with Proxmox Backup Server, we use the snapshot method. It works perfectly. But when we create a snapshot over the web interface for a certain VM, the VM get's stuck for about 20 minutes and the snapshot creation fails with an timeout. And...

We are still on pve 6.3. Can we just update directly to 7.0?

Problem is bandwidth to our backup server, it has only 2x1 Gbit bonded in alb mode. So 6 (wrongly wrote 4 hosts before) hosts at once pushing each on 1 gbit to PBS I think could be problematic.

Where can I write about a feature request? 'Backup only one VM at once over the entire cluster'

Ok, thanks. So we will make a backup job for every node on different day. Regards, Thomas

Hello, do not know if the answer to my question is obvious..... If I make on our 4 hosts cluster a backup job of all VMs, are the VMs backed up sequentially? Or for example is a backup started on every host, so there wil be 4 backups running in parallel? Latter would not be a good thing in our...

Great. Thanks.

Hello, I have a doubt. Do I need to reboot the PVE hosts on every update, or only when there is a new kernel? For example now I have the following Updates waiting: libproxmox-backup-qemu0/stable 1.0.3-1 amd64 [upgradable from: 1.0.2-1] libpve-storage-perl/stable 6.3-8 all [upgradable from...

Hello, we are evaluating to install a Proxmox Server and while reading the documentation, some question have arisen: 1. is the datastore encrypted or do I have to use client-side encryption? We do not need client-side-encryption, but would be nice if the datastore itself is encrypted...

Hi, here is the config of the VM: root@pve4:~# qm config 175 agent: 1 bootdisk: scsi0 cores: 2 cpu: Broadwell description: CentOS Template no Software%0ARepos MariaDB/PHP/CodeIT aktiviert.%0A%0ALetztes Update%3A 27.05.2020 17%3A30 ide2: NFS2:iso/CentOS-7-x86_64-Minimal-1908.iso,media=cdrom...

Hi, we have added a new server to our cluster. When we try to migrate a VM from the old (Intel Xeon 5120) to the new server (Xeon 6240) we get the following error: 020-11-16 10:08:32 starting migration of VM 175 to node 'pve8' (10.10.2.94) 2020-11-16 10:08:33 starting VM 175 on remote node...

Stupid me ..... we are not using QCow2 on this particular server. It's using lvm-thin on local disks. So a 10 TB logical volume should not be a problem I asume.

Same problem here......never found a solution, other than migrating VMs regularly back and forth to another host. Forum Post

Hello, what is the maximum size of a single QCow2 Image for a KVM VM? Have a client who wants a VM with 10 TB diskspace. Can/should I assign a single QCow2 file with 10 TB or assemble with LVM p.e. 5 x 2 TB Images? Thanks and greetings, Thomas

Warranty of the entire server is up to 3 years, depends how much we are willing to pay. In the techspecs there is a line "Drive writes per day" for 5 years with 1 dwpd. Should be an indication that it should last longer than the normal warranty of the rest of the server, shouldn't it?

The SATA-DOM Specs are in the attached screenshot. Do not know the brand of the DOMs. We buy from a known german company, do not know if I can post the name here. But they have the option to buy 'Proxmox' compatible hardware, which they have tested and approved.

Hello, installing Proxmox on SATA-DOMs is a valid option? I saw older threads where it was not recommended. I thought to use two SATA-DOMs in mirrored configuration, which are 64 GB in size and rated at 1 DWPD, shouldn't they be reliable enough only for the OS? Regards, Thomas

Ah, no we are not backing up with Proxmox. We do a backup internal on the VM at this time. Sorry for the confusion.

Installed the latest updates for PVE as I have seen that qemu was updated, hoped that it helped. Added a little script which wrote the 'rss' column of the 'ps -eo rss,command' output to a file, every second. I made a primitive graph attached to this post where we see clearly that around 4 or 5...

Could it be some remains from XenServer where the VMs where imported from? But other VMs which are working normally where also imported from XenServer.....