Search results

That works in ProxMox as well only with containers.

You can run your backups every day and when the prune schedule runs it will prune whatever you set it at. In your case if you only want weekly backups then set to keep weekly. Just set it number of weekly you want to keep. It will prune the rest. I set my prune to run on Saturday nights so...

Look into cephFS which will do what you need.

I would use Apache Gaucamole which will simplify things.

Pretty cool to see that kind of up time but patches and security updates are more important to me than up time. Plus rebooting the servers is a good way to reset the RAM especially with ZFS.

I am using local ZFS with scheduled replication to simplify my setup. I've tried CEPH in the past and always had issues with VMs running very slowly whenever there is something major going on with CEPH. With local ZFS it only impacts one node vs several. Granted I lose HA but ZFS...

For my Windows 2019 VMs I've practically set everything as defaults including KVM64. IDE with default settings. Keep in mind I am using ZFS so alot of the speed enhancements are handled by that. You can clone your VM to test out some settings.

I've migrated several Windows 2019 VMs over from vmware to ProxMox and most booted up without issues. Strange behavior that 3 VMs out of so many refused to boot properly. For testing I switched them to OVMF (UEFI) and it booted up without issues. Strange part is they never been setup to use...

When I was running ProxMox version 6 four years ago with CEPH it ran fine but the performance wasn't great. Now I'm sure with improvements it's alot better. I will revisit this later on as I have a second cluster running 7.4 to test it on. I will upgrade to 8 some time this year.

I've tried CEPH in the past and it kills the Window VMs in terms of performance. So I switched them to ZFS and they're practically the same performance as ESXi with vSAN. It loads slow at first but once it starts up the reboots of the Windows VMs are almost instant and the performance are...

If you don't have a subscription to Enterprise you have to change them to pve-no-subscription. You can change that in Repositories.

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...