Maybe.
Did you check if "/etc/sysctl.conf" does (not) actually exist?
The error was generated by tar, called in your "/etc/cron.daily/pvehost-backup". Don't you think it would be a great idea to post that script, to give us a chance to grasp...
Nicht ganz, tteck ist an Krebs verstorben, das Projekt wird seitdem unter http://community-scripts.github.io/ fortgesetzt. Bei allen Respekt für seine Leistung und Pietät gegenüber Verstorbenen finde ich aber, dass es sich nicht für Anfänger...
Select the correct storage in the upper-right corner (after Storage: ). Currently, the storage named local is selected/ You need to select your PBS, which appear to be named proxmox-backup-server.
Select the container (or VM) under the Proxmox node (lab in your case), go to the Backup pane and click the Restore button. Please note that any virtual disks (also those that are not part of the backup) are deleted automatically before the...
You have a single vdev and you are adding a new, empty, second one. No resilvering, no rebalance, no nothing will happen. Everything is fine as it is.
As already said: all data is on the old vdev, at first. Technically that is fine! Seen from a...
Das ist allerdings von der Performance nicht ganz das Gelbe von Ei. Wenn man schon eine NAS dafür nehmen will, würde ich, die NAS es erlaubt VMs einzurichten (was beim OP allerdings nicht der Fall ist) würde ich immer den PBS als VM auf der NAS...
Calling "running a script as root from the internet" a solution is a little bit of stretch in my book. In the end the script do following: Installing dependencies and afterwards glances, you can (and should) do this yourself. Even worse: It does...
What I see is a mesh: every node has direct contact to each other nodes. To add a fourth node every node needs an additional (third) NIC (or bond) dedicated exclusively for this.
If you configure it as a ring instead (which does work) then yes...
Well..., after adding that second vdev everything will work and the added capacity is available immediately. There is no additional step required.
But all "old" data is still stored on the old vdev. There is no automatic rebalancing. Last time I...
Thanks for the insight! Yea as I've been thinking about it I actually feel like the two 12 disks Vdevs in the pool would be better than 1. If I simply create the new vdev and add it to the pool, should I do anything after that to optimize the new...
Hi @Eesli , welcome to the forum.
Can you attempt to try to be any more descriptive?
Cheers
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
In that case you might be better served by a desktop virtualization solution: virt-manager, vmware, virtualbox. PVE is pitched as an enterprise solution and that comes with certain expectations of the users. Those other solutions claim to be easy...
Not directly. ZFS is a combination of file system and volume manager, you can think of a dataset as something like a partition although more flexible.
You can save zfs volumes on it (that's the thing ProxmoxVE uses for vm images) but also usual...
Your Plan sounds good, you should do an backup anyhow. Don't you have them at the moment?
Lnxbils proposal will be faster than a complete restore though.
I would backup the vms and lxcs togethwe with /etc/pve. Than reinstall and restore the...
If the data is extern as you described, the easiest method of "recreating" the VMs is to backup /etc/pve/qemu-server and/or /etc/pve/lxc and copy them back after reinstall. Those are the config files. Best to also have a full backup of /etc/pve...
No, no, no - do not do this.
I see that this is tempting, but a 12 disk wide vdev is already considered "wide".
Additionally: two vdevs will double IOPS, which is always a good idea ;-)
Disclaimer: I've never setup a 24 wide vdev, not even...
Read https://pve.proxmox.com/pve-docs/chapter-ha-manager.html#_requirements
"
at least three cluster nodes (to get reliable quorum)
shared storage for VMs and containers
"
Then look at this table...