Recent content by forbin

That's terrific news, thanks for responding!

That's delightful to hear. I think we'll give it a try in our environment.

Frankly, I didn't know there was a difference. We installed Proxmox directly from ISOs. We di not install Debian first.

That's excellent to hear. Has CrowdStrike support given you any hassles about running it on Proxmox? I'm under the impression that they do not officially support it.

That is superb news. What PVE version(s) have you run CS on?

Hi, thanks for your post. It's been almost a year since you deployed CrowdStrike on your PVE hosts. How's it going? We are interested in doing the same thing.

If we did that, it would probably work, at least initially, but who knows what incompatibilities might pop up later? I'm hoping for some feedback from people who have been using it for a while.

I read a post here in January '24 from a user who said he was successfully using CrowdStrike on his PVE 8 hosts. Has anyone else had similar success? We'd really like to use it, but we want to be careful and make sure of everything first.

It cleared up on its own. I don't know why.

On my PVE 8.2.3 server, I have many replication jobs that run fine, but I have one that runs over and over and always fails with the following error in the logs. 2024-09-12T15:30:27.421629-07:00 vmhost52b pvescheduler[342902]: 4803-0: got unexpected replication job error - command 'set -o...

I can see why #1 would happen, and that is acceptable. However, #2 could be a problem. Let's explore that scenario. Node A is HA primary and replicating to B. Replication hangs, crashes, or whatever and nobody notices for days. The data on B gets very old. Node A crashes. Node B becomes HA...

zfs=yes. I put a guest VM in ha mode for testing. Thanks!

Is there a way to do it through the GUI now, or is it still just a file move from the command line as indicated in the documentation?

Lol, never mind. Figured it out.

I am using PVE 8. I have three nodes, A, B, and C. Guest VMs on A were being replicated every 15 minutes to B. Node A failed. Per the documentation here: https://pve.proxmox.com/wiki/Storage_Replication To recover... move both guest configuration files form the origin node A to node B: # mv...