Search results

I actually did it from the PVE: I added a new mount point to the lxc I created the share with shadow snapdir as the first post and used the mounted disk as folder i created a new snapshot from PVE with: zfs snapshot -r data/subvol-104-disk-0@$(date '+%Y-%m-%d-%H%M%S') (the new mountpoint was...

Is it possible to take zfs snapshot on an unprivileged LXC container? I created a samba service in an LXC container as it's more lightweight and even if the VM cannot boot i can simply copy the file from the bind mount from the PVE host without the hassle of mounting virtual disks, etc. (minor...

yes, i did reboot each time but i did not think about using the same MAC address of the ethernet card. It's strange as i do have other Proxmox installation and they work without problems, don't know if my provider checks the MAC at first boot or whatever but now that i know it it's simple (i...

Ok, figured out myself: i had to set the HWADDR the same as the physical ethernet card or the provider would block any request; this worked differently for the secondary ips and i did not have to set it before so i didn't thought about that.

This was a screenshot i saved before i added hwaddress (i added a line after gateway) and it worked; i do not have continuos access to the machine so it was the only screenshot available

I have upgraded one of my servers from PVE 6.4 to 7; i tried the same procedure on other servers before doing it online and i had no problems but now i cannot access the PVE server (GUI, SSH or ping) but i can still reach all the VMs. I can still have access to the machine by scheduling a KVM...

Thank you very much, really clear and to the point. The VM should only add new files in the larger datastore and write files in the database disk (mysql) so backup difference should be negligible.

I'm ruinning PBE as a backup service for my PVE systems and, as i plan to backup large set of data, i want to know what's the best approach to my problem. I have a VM with 3 disks: one system disk, one database disk and one for storage. The first two disk are reasonably small (50 and 300Gb) but...

Ok, thanks for the clarification, that was what i had in mind in option 1. For the restore procedure yes, it's not impossible or hard, but the first option may be just a little bit easier

In case of hardware fail (machine with disk intacts or unable to run local PVE) with option 1 i can put the disks on another system (only a system capable of reading ZFS is needed) and extract the backups even if the PVE is incapable of running; with option 2 i have to extract the disk image...

My network is composed of two PVE servers: one primary server where all the VM runs and one secondary backup server used to store VM backups and as a backup PVE (in case the primary server fails it must be capable of restoring and running the VMs). Both servers runs on ZFS, all the disk on the...

The 1Gb network is bound to have less than ideal performance but at least it provides a backup connection to avoid single point of faiure (if the infiniband switch goes down). I already found the article you mentioned and, as much as i can tell from my tests, it seems the only viable option is...

I tried various configuration, bonding one ib with one ethernet as active-backup does not work: even if the ib network is set as default only the ethernet nework will be used. As much as i can tell ipoib does not work well with bonding and does not work at all bonded with other network types: is...

I'm configuring a 3 node HA cluster with Ceph storage; this cluster is composed of 3 identical nodes, each node has 2x 1gb ethernet cards 2x 40gb infiniband cards (mellanox-4) The infiniband cards are connected to a 32 port infiniband switch that is used both for SAN and for public access (via...

Basic guide (may need improvments and it's not failproof) to shrink zfs disks: 1. prepare your vm disk for shrinking and shut it down 2. in pve shell set new zfs pool size $zfs set volsize=<new size>G rpool/data/vm-<vm id>-disk-<disk number> 3. edit vm config in /etc/pve/local/qemu-server/<vm...

Correction: In proxmox now it shows 120Gb both in storage and VM options but the VM (Windows server) still see it at 81tb drive... ---UPDATE:--- Found an easy fix: i edited the disk from the proxmox panel from "no cache" to "directsync" and now Windows is updated to the correct disk size; i...

Ok this command should have fixed it: $zfs set volsize=120G rpool/data/vm-100-disk-1

Hi. I'm running on Proxmox VE 5.1 on a single node, the filesystem is on ZFS (ZRAID1) and all the VM disks are on local zfs pools. When trying to expand the vm 100 disk from 80 to 160gb i wrote the dimension in Mb instead of Gb so now i have a 80Tb drive instead of a 160Gb ( on a 240gb...