Search results

Wish I can mass change the entire datastor to the new owner in the PBS's WebGUI. Especially if I can do this via namespace. I can't imagine someone changing hundreds of backup groups one at a time. I'd figured a for loop script may do the trick. Get a list of your vms and cts root@pbs:/#...

Yep, that would do it. One of the reasons why I upgrade the firmware on everything via the Dell's LifeCycle tool whenever I can. I will do this again before I upgrade to PVE 8.2.x as I am currently on PVE 7.4-17 on production servers at work. I am using PVE 8.2.2 at home.

You can actually change the mode on those Mellanox Infiniband to Ethernet. You'd be paying more to have Infiniband support.

This is a known issue with major kernel updates. It's not a ProxMox thing but a Debian thing. I agree the warning of this breaking change should be pinned to the top on the what's new in PVE 8.2. There are instructions on how to pin the interface names based on mac address so it doesn't...

Yep, we're still running 7.4-17 at work in production as it's been incredibly stable. No issues. Now the dev team just released PVE 8.2.2 (congratz btw!) and was like holy cow. I'm a bit behind. I already upgraded my home lab and test PVE servers to 8.2.2 and it's been running great. Lots of...

No but if I run across one I will let you know.

Sounds like they use a PowerShell script to make the necessary changes before the VM gets imported over. There might be open source scripts out there that does the same thing.

Ya, I've used the CLI method a year ago to move several VMs over from vmware to ProxMox. All went through without issues. I was using vSAN at the time so CLI made it easy to export the vms out.

You have to create a small disk and then use that to load those drivers. It's all explained in https://support.tuxis.nl/en/knowledgebase/article/convert-windows-boot-disk-from-virtio-to-scsi Once Windows loads the virtio-scsi drivers it will get loaded whenever it encounters those disks.

Yep. Same here. Everything is working as expected. Awesome work by the ProxMox devs!

So far I didn't have any issues running PBS 3 against PVE 7 servers. I was able to restore really old backups from PBS 3 to PVE 7. Also did new backups to PBS 3. It did created new dirty bitmap which is expected. My next thing is checking the remote sync jobs between PBS 2 and PBS 3. I...

Thank you for the link. I've followed through the other links as well and seems I can go ahead and upgrade the PBS from version 2 to 3 while I work on upgrading the PVE from 7 to 8 whenever I can. I will test this scenario on my secondary cluster and backup server to make sure it works fine...

At work we're still using 7.4-17 and PBS v2 as they are both very stable. Eventually I want to upgrade both to newest versions. But the upgrades are going to be slow in phases as I have three clusters all running the same version. I have a test and dev clusters I can use a test bed to...

Same thing happened to me this morning. Host is running but anything to do with ProxMox services I can't stop or restart. So I was forced to reboot the server. Not something I'd like to do.

Nice!! Do we know when it'll be added via updates?

I wonder does it now report if the ZFS pool has degraded? Not just when it failed?

It's probably because of the I/O that is overwhelming the disk sub-system on PBS so by limiting the bandwidth it matches to what the disks can handle.

ZFS and CEPH are software defined storage so it doesn't matter. It only matters the speeds the HBAs are capable of.

If that HBA is working then I'd stick with it. It doesn't need anything fancy other than faster speeds if newer card supports it.

I would check your server's RAM. I've had this happened to two of my servers a few years ago till I was able to trace it to bad RAM. Took forever to figure out why as nothing reported in syslogs.