New feature - temporarily deactivating a Hyper-V standalone server

[brainpointer]

One feature we miss is to temporarily deactivating a Server. In one of our infrastruktures is a standalone Hyper-V server that has a problem with the Hyper-V role. It will be available again shortly; however, jobs are not running in the meantime. Access to job settings is limited to impossible, as the server is currently inaccessible via Veeam and VM discovery failes. Sometimes Veeam crash and has to be restartet.
In end we delete the host from the infrastruktur - This is a new feature request: Remove a host directly without having to manually remove it from all jobs and configurations. Like - do you want to remove all linked elements?

Did anyone facing the same problem? It is possilbe to add a disable?

[david.domask]

Hi brainpointer, welcome to the forums.

Just to make sure I get it right, you have two requests here?

1. Allow marking hypervisor hosts in a "maintenance mode" when there is expected maintenance to avoid errors / warnings in the Veeam jobs?
2. Allow option when removing hosts to "force" remove and ensure the host is properly cleared from all jobs it currently is added to?

For the 2nd one, we have discussed this in the past as it is a headache to manually go through and edit jobs like this, so will add your feedback to that discussion.

[brainpointer]

Hi David Domask,

thank you verry much for replay that fast. Yes you get it right.
1. Exactly - In this particular case, processing jobs is difficult because adding/removing the VM of the faulty host leads to timesouts and, of course, to error messages for the end customer.
Regarding the second point, I figured we weren't the only ones. Can you give me a link so I can follow the discussion?

[david.domask]

Understood, will consider your request internally.

As for the discussions, these are ones we're having internally so won't be able to give you visibility, but point is more that the pain is understood on removing, we want to make this more graceful.