Search results

Management interface should always be on a dedicated network that VMs / Containers don't reside on. That way if you ever bork your network interfaces you won't lose connection to the PVE host. This is also true for any cluster environment. Depending on the server I usually pick the onboard...

Processor : 0 vendor_id : AuthenticAMD cpu family : 23 model : 49 model name : AMD EPYC 7502P 32-Core Processor stepping : 0 microcode : 0x8301055 cpu MHz : 2495.270 cache size : 512 KB physical id : 0 siblings : 64 core id...

This is by design. If you have several nodes it will start the backup job on each node at the same time. Only way around that is to create separate backup jobs to balance the load. Mine is set by pools to make it easier to manage the backup jobs.

That is normal. I see the same thing whenever I reboot my PBS server. Figured it's a boot script to import any unknown ZFS pools into ZFS automatically.

I am running all Epyc AMD processors on 14 nodes. No issues far as I can tell. CPU(s) 64 x AMD EPYC 7502P 32-Core Processor (1 Socket) Kernel Version Linux 6.2.11-2-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.11-2 (2023-05-10T09:13Z) Also, they're all running on Dell PowerEdge R7515 with 512GB of RAM.

It really depends on the hardware PBS is running on. I recently repurposed an old Dell Data Protect 4400 server to run PBS. It handles several verification jobs at the same time without too much of an issue despite all running 12gig 12TB spinning rust SAS drives on hardware RAID6 controller...

Very good points in this thread. Although it's really up to the backup admins to monitor these backup and verification jobs daily if possible. I also configured my PBS servers to send me e-mail on the backup / verification jobs so I know what is going on. Final piece is do manual restores on...

Actually any good RAID system will take care of bit rot during scrubs. I use ZFS whenever I can. Sometimes on servers I don't have that option without flashing the controller into IT mode.

This is one of the reasons why I went with ZFS with replication instead of CEPH when I rebuilt the ProxMox clusters. Much as I love CEPH's fault tolerance and able to self heal on it's own without any involvement from me the performance with regular spinning 8TB 7.2K SAS HDDs just wasn't...

Do this on the VM's hardware section. Edit Network Device that is connected to the LAN bridge and check on "Disconnect" option:

I saw that command which is cool but wanted to simply replicate the live VMs over to the remote cluster and then leave the VMs in it's current state until I manually switch them over. I suggested the command qm remote-replicate for that. And then qm remote-migrate to actually migrate them...

I have few pfsense VMs running on my PVE nodes as wireguard VPN servers. Before the initial boot up make sure you "disconnect" the network interface that is connected to your LAN bridge. Pfsense will dish out DHCP and will cause IP issues on your LAN network. Once pfsense boots up manually...

Are there any further updates on replicating the VMs between clusters using ZFS? I am looking into replicating the VMs from the cluster at the data center via WAN over to corporate office. I know this can be done using ZFS send commands but hoping in more scripted or WebGUI way of doing this...

Putting them on ZFS storage will help a great deal as it will make use of ZFS snapshots. And then the backups will save the snapshots without affecting the VMs much. So give that a try. Also, definitely make sure qemu agent is installed as it will coordinate the internal snapshot of the VM...

I back up several VMs few times a day to the PBS server without much of a slowdown regardless of VM size. The storage is all ZFS with scheduled replication. If you're using CEPH yes it will slow the VMs down a bit during backups.

I too was confused by this behavior and wanted to make sure the backups a new VMs are successful and able to restore without issues. I've already have two more PBS servers as a test and all VMs were able to restore without problems. The wording is technically correct. At first I was like...

Technically under the hood a CEPH host is the same for ProxMox just with different tools installed. I actually have thought about using three beefy servers with lots of disks just for pure CEPH without ProxMox installed for performance reasons. I've had bad performance issues whenever CEPH...

I've ran into this VSS issue with Windows 10 VM which resulted in 8194 error in the windows log. Below link is the fix without running that VSSfix64.exe. Just follow steps 1 through 11. You don't need to adjust anything else. https://kb.msp360.com/backup/errors/vss-error-8194-access-denied...

I am pretty much in the same boat. I have 4 DCs. Half are physical with FSMO role on one of them and other half as VMs. I am in the process of moving the VMs from vmware to ProxMox using the offline export OVF method. All DCs are running Server 2019 with 2008 R2 domain level. Can't raise it...

This qm remote-migrate very cool to move VMs between clusters but what if I just want it to sync the VMs as cold standby? Something like qm remote-sync where it'll sync via ZFS snapshots? This way I can have a working copy as cold standby on the remote cluster in case the primary cluster...