Proxmox Backup to NAS: NFS vs SMB Setup and Restore Checklist

Preparation date: September 17, 2026. Scope: This is a documentation-based implementation and verification guide, not a claim about a completed customer incident. It covers ordinary Proxmox VE VZDump backups written to NAS storage. A Proxmox Backup Server datastore is a different architecture and is called out separately. The short answer is: choose NFS when Proxmox is the main consumer and your NAS can restrict the export to the Proxmox node addresses. Choose SMB/CIFS when the same share must also fit a Windows-oriented operating model or your NAS administration is already built around named users and SMB permissions. The protocol choice matters, but the restore test matters more. A green backup task proves that an archive was written; it does not prove that you can recover a VM on replacement storage. Proxmox backup to NAS verification flow A Proxmox node writes a VZDump backup over NFS or SMB to a NAS, then a separate restore test validates recovery. ...
Post a Comment

Horizon Agent Unreachable: Registration and Desktop-Health Triage

Start an “Agent Unreachable” investigation by separating desktop health, Agent registration, and session traffic. Do not begin with a pool rebuild. This documentation-based triage guide helps decide which team should act and what evidence to preserve.

Correction, September 12, 2026: The earlier guide mixed display ports with Agent communication, tested Blast against the Connection Server, and offered generic service restarts and image rebuilds. Those instructions have been replaced with path-specific investigation.

First-response decision table

CheckEvidenceInvestigation owner
Is the guest responsive?Approved console access, OS health, resource and disk observationsDesktop/virtualization team if the OS is unavailable.
Is this one desktop or a whole image family?Affected pool, image revision, Agent version, start timeImage owner if failures align with a deployment.
Does registration fail?Agent and Connection Server events for the same desktop and timeHorizon team, then network or identity owner as evidence indicates.
Is the desktop available but launch fails?Assigned desktop and selected protocolFollow the separate protocol-path investigation.

Record the control path

Identify which component initiates each failing connection and which destination is expected. Use Omnissa's Horizon port tables rather than one universal list. In particular, a display-protocol destination on an Agent must not be treated as a Connection Server registration test. USB redirection ports are not generic Agent health checks.

Record exact versions and the configured broker address. Check name resolution from the affected guest and compare it with a known-good desktop. If logs indicate a certificate problem, investigate the relevant connection and trust chain; do not turn off validation or enable protocols indiscriminately.

Preserve evidence before repairing the image

  1. Record the console state and timestamp, then collect the relevant Agent/Connection Server diagnostics using the procedure for the installed release.
  2. Inspect service state and startup failures without assuming that a running service means successful registration. Service names and paths differ across product generations.
  3. Compare the effective firewall and endpoint policy with a working desktop from the same image.
  4. Correlate failures with image rollout, domain changes, network policy, or resource exhaustion. Do not infer corruption from a single stopped service.

Omnissa's connection troubleshooting guide provides the connection-stage context. Use a support bundle appropriate to your release instead of relying on one legacy log filename.

Make a scoped correction

A confirmed rule mismatch goes to the policy owner. A confirmed missing or failed Agent component goes to the image owner. Test any repair on an approved pilot desktop with the original configuration retained. Do not reinstall the Agent, restart VMware Tools, or recreate a production pool merely because the console reports this state.

Verify both stable Agent availability and an actual user launch/reconnect. If registration recovers but launch still fails, treat that as a separate stage rather than reopening every earlier hypothesis. Roll back an unsuccessful pilot change and escalate with the comparison and timestamps.

Related, distinct investigations

Comments

Post a Comment

Popular posts from this blog

Horizon vdpConnect_Failure: Connection-Stage Triage Before Reinstalling

vdpConnect_Failure is a starting symptom, not a root-cause diagnosis. Before reinstalling Horizon Agent or opening firewall ports, establish whether the failure occurs during authentication, desktop launch, or an established session. This documentation-based triage guide does not report a reproduced incident or a universal fix. Corrected September 12, 2026: The earlier guide suggested restarting the Windows RPC service and treated a local netstat listing as a test for blocked ports. Those instructions have been removed. A socket listing does not demonstrate end-to-end reachability. Classify the failure before making changes Observation First evidence to collect Avoid assuming Authentication never completes Exact login error, identity provider or broker event, timestamp That the display protocol is the failing component. Desktop selection succeeds, launch fails Assigned desktop, chosen protocol, Client/Agent and gateway logs That a successful HTTPS login proves the session path ...
Read more

Horizon Protocol Error: Trace the Display-Session Handoff

A desktop can authenticate successfully and still fail to establish its display session. This guide investigates that handoff. Use it after identifying the actual console/client error, not as a claim that every “Protocol Error” means a firewall failure. Correction, September 12, 2026: The previous version combined a general checklist with an unverified incident narrative, conflated gateway and desktop port directions, and recommended blanket endpoint-security exclusions. Those instructions have been removed. This is a documentation-based diagnostic plan. Draw the attempted connection Record the selected protocol, assigned desktop, Client and Agent versions, gateway route, and attempt time. Distinguish a direct internal connection from an external UAG connection or a Connection Server tunnel. Use Omnissa's connection guide to identify where the failed handoff occurs. Stage Question Useful comparison Authentication Did the user receive desktop entitlement? Failed login versus ...
Read more