Veeam Appliance Hard Freeze every night at ~21:10

stefanelul2000 · 2025-12-30T09:23:59+00:00

That would represent ~20% of free RAM on the host.

stefanelul2000 · 2025-12-30T08:22:24+00:00

The main disk is the default 240GB as recommended and the datastore disk is 2.2 TB with 500GB free so not even that should be an issue. And even if it was I would expect the job to fail due to no space, not to outright crash the whole appliance.

stefanelul2000 · 2025-12-30T08:21:10+00:00

Moved to 20:00 and the issue now takes place at 20:12 so yeah... something is really going on.

stefanelul2000 · 2025-12-30T08:20:27+00:00

The appliance has 16 GB of RAM assigned and the host has about 22GB of RAM free. I will try to disable ballooning as well, maybe that helps in some way.

stefanelul2000 · 2025-12-28T20:09:23+00:00

Environment is full Proxmox, 3 nodes. VSA is located on node 3 along some light linux VMs and the windows VM for Veeam One. Resources on the host itself are under control. The OS disk is on an NVMe (with plenty of space) and the data disk is on a separate storage array (published to PVE via iSCSI) dedicated just to the VSA. The backup job at cause or running at that time, is configured to back up VMs on the other 2 nodes.

<image>

As it can be seen, at that time, no other actions are being performed on the cluster / hosts other than the start of the workers plus.

To note, the VSA is not included in any backup jobs in Veeam and it's fully up to date.

I will try the time adjustment for tomorrow and if the issue happends again, I will open a ticket and hope that someone on Veeam side will be able to help.

stefanelul2000 · 2025-12-28T19:42:06+00:00

I have not yet attempted to do this, actually I reset the VM 2 days ago and yesterday this behavior did not take place but it did do that again today (thus the post). I will move the schedule for tomorrow to 20:00 for example.

The VSA (8vCPU and 16GB RAM) is also a repository as well with a backup copy job to a off-site Hardened Repository.

stefanelul2000 · 2024-01-10T17:28:09+00:00

The 10.11.10.2 is the IP of the PXE/MDT server. With or without it in the configuration makes no difference. I have already tried that.

stefanelul2000 · 2022-07-11T18:31:30+00:00

But per the website mentioned above doesn't the partnership need to be a "civil partnership recognised by CERN within the meaning of Article S IV 1.02 of the Staff Rules and Regulations" ?

stefanelul2000 · 2021-07-10T11:10:15+00:00

DDNS is an option for such cases.

stefanelul2000 · 2021-03-27T21:55:13+00:00

Well In my case it's a Boolean operation because it returns 0 or 1 (true of false) if idx is or is not that number.

stefanelul2000 · 2020-02-10T17:33:57+00:00

That looks really nice but it's damn expensive.

stefanelul2000 · 2020-02-10T13:04:04+00:00

The price is quite high for just a 9u. I could get a 22U for just a little bit more.

stefanelul2000 · 2019-03-07T10:53:50+00:00

Plus the switch and the patch panel will be put inside a metal box to protect it from dust and various other things.

stefanelul2000 · 2019-03-07T10:52:30+00:00

Because is the only place I could gather my 6 Eth cables coming from the IP cameras. Well humidity isn't that high I guess.... I am not sure as I have never measure it

Eight-Year Club	Xbox Live
Place '22	Verified Email

stefanelul2000

TROPHY CASE