Search results

Indem du ein Storage hast das als Content auch Backups konfiguriert hast und dann entweder über das <node> -> <vm> -> Backup Panel oder das Datacenter -> Backup Panel. Das kann entweder ein lokales Storage sein, von dem du dann die Backupdateien weg kopierst bevor du neu aufsetzt oder ein...

Soweit ich weiß nicht, bin jetzt aber auch nicht der GlusterFS Experte. Ceph könte für dich als Alternative interessant sein, wenn es mit Hardware und Netzwerk zusammenpasst.

am einfachsten indem du ein backup machst und wieder zurückspielst.

apt install --reinstall pve-manager This should install everything again for the web GUI to work as expected. Consider buying a community subscription if you are that annoyed by that pop up and feel good that you are supporting the project and help to pay the developers' salary as well as for...

If you edit a storage, you can limit it to certain nodes only. In the edit window top right. This way the PVE tooling will know on which node it can expect which storage and the migration should work.

Hmm, I would try to see what happens if you try to install the latest updates: apt update apt full-upgrade full-upgrade is important in order to resolve new and changed dependencies.

Did you install some updates recently? Do you see anything in the browsers Console tab in the developer tools?

Ich glaube da hat sich ein Missverständnis eingeschlichen. PVE setzt auf Debian auf. Man kann dann laut verlinkter Anleitung PVE nachträglich installieren. Abgesehen vom Festplatten / partitionslayout sollte es kaum von einer PVE Installation mit dem PVE eigenem Installer unterscheidbar sein.

AFAIK this should be possible

This is usually caused by repositories not configured correctly. Can you run apt update and show the output? This is the quickest way to determine which repositories are set.

Wenn die Platten wieder erkannt werden sollte ein zpool import den Pool darauf wieder finden.

This can happen if there is too much load on the zpool. IO gets high and the time until the snapshot for the next replication run is taken is too long -> time out. Check the IO delay graph in the node summary if you have peaks that correlate with the timeouts

This is very much a problem! Use different shares so that each cluster has its own and cannot interfere with the other cluster.

Do you use the same share on multiple separate PVE instances? If you use the same share in a cluster everything should be okay. If you have separate PVE instances, not clustered, you should never share the exact same network storage. Use different shares in that case. Each PVE instance (if...

Can you open a new thread (to not pollute this one) and show the output of the command apt update?

Should be in the no-subscription repository.

ah okay, that's what you mean. Well, as I said, you can create partitions yourself and use those to create the zpool. But honestly, if you fear that your SSDS won't last, check out the TBW or DWPD values in the specs of your SSDs to get an idea how long they will probably last. Additionally you...

How does some free space at the end of the disc help you with over provisioning? What is usually meant with over provisioning is that you you can have VM disks which when summed up are larger than the underlying storage. This works as long as they don't all use all their space. Once you hit the...

Or, as netstat isn't installed that often nowadays, you can use ss -tulpn.

If you use the integrated backup tool (vzdump on the CLI) and create backups of your guests, you will have all needed configs for that guest. Try restoring a backup to a new VMID and it will all be there. The PVE node specific settings are all found at /etc/pve (even the VM configs) and the...