Skip to content

Knowledgebase

Putting a SolusVM 2 compute resource into maintenance

servers, performance

Maintenance mode in SolusVM 2 limits customer operations while an administrator performs planned work on a compute resource. It does not itself shut down guests, move them elsewhere or make disruptive host work safe.

What you need before you begin

List affected servers and customers, pending provisioning and backup tasks, and the expected interruption. Confirm independent host access and a tested recovery path. If high availability is configured, review remaining failover capacity before changing a member resource.

01 Put a SolusVM 2 compute resource into maintenance

  1. Notify affected users of the window and which controls will be unavailable. Check for active tasks that should finish before maintenance begins.
  2. Open Compute Resources, identify the exact host and enable its maintenance toggle. Confirm the host name and address rather than relying on list position.
  3. Verify the expected restrictions from an ordinary customer role. Administrators or users with the special maintenance-access permission may still perform otherwise restricted actions.
  4. Carry out the approved work with a separate guest shutdown, migration or service-continuity plan when needed. Maintenance mode alone does not drain workloads.
  5. After the host and guests pass their checks, disable maintenance mode and verify normal customer operations. Close the window only after provisioning, console and management access are healthy.

Does maintenance mode keep HA protection active?

For an HA-enabled resource, maintenance changes evacuation eligibility. Review the installed-version HA behavior and available peer capacity. Plan guest continuity explicitly before taking a host offline.

Confirm the expected result

Check existing guest workloads during the change, the host agent connection and any queued tasks afterward. Verify HA status when applicable. Confirm the resource is again eligible for the intended placement and failover behavior before accepting new work.

Troubleshoot unexpected results

If controls remain unavailable, inspect maintenance permissions and the actual toggle state. If a host fails during the window, follow its recovery plan; do not assume HA will evacuate it. Preserve the maintenance state while diagnosing rather than re-enabling customer actions on an unstable resource.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support

Powered by WHMCompleteSolution