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

Zero Client Fails Through a Horizon VIP: Endpoint vs. Broker Comparison Worksheet

A zero client failing through a VIP while another client succeeds does not prove a firmware regression. The clients may reach different broker nodes or use different connection paths. This worksheet isolates endpoint and node-selection variables before a firmware change.

Correction, September 12, 2026: The previous post named firmware/release combinations, quoted an AI probability, and asserted a failed-node diagnosis without publishable test records. These are no longer presented as verified findings. The useful diagnostic question is retained: did the compared clients actually reach the same service?

Build a client-by-path comparison

TestHold constantRecord
Zero client through approved VIPAccount, pool, time windowExact firmware, protocol, selected member, result.
Supported software client through VIPSame account and pool where authorizedClient version and selected member, not merely success.
Approved node-specific diagnostic pathIdentity and intended serviceTrusted hostname, node health and result.

Use the Horizon architecture guidance for topology and load balancing. The connection troubleshooting guide helps separate login and session paths. Different products called NSX Load Balancer and NSX ALB/Avi have different configuration interfaces; identify the deployed product before changing settings.

Keep certificate and access controls intact

Do not enter a raw server IP and click through a certificate warning to create a comparison. Ask the platform owner for an authorized diagnostic route that preserves trusted names, certificate validation and access policy. A direct path may bypass load-balancer behavior and therefore is a diagnostic comparison, not automatically an acceptable permanent user configuration.

Interpret the matrix

  • If failed attempts consistently reach one unhealthy member, investigate that member and its eligibility before attributing the problem to firmware.
  • If both clients reach the same healthy member but only one fails, investigate endpoint support, firmware configuration and protocol evidence.
  • If the member is unknown, keep the result inconclusive and obtain distribution logs rather than inventing an affinity explanation.
  • If a certificate or negotiation error is explicit, investigate it; a previously plausible AI explanation is neither proof nor disproof.

From comparison to controlled change

For a firmware hypothesis, establish a supported test combination and approved rollback before updating an endpoint. For a member-health hypothesis, assess remaining capacity and session impact before draining a node. Change one variable and repeat the same matrix. Record exact outcomes rather than a confidence percentage with no measurement basis.

The companion load-balancer health-monitor article addresses detection and failover acceptance; this page focuses on avoiding a false endpoint-version diagnosis. Preserve sanitized results and unresolved questions for vendor escalation. Do not weaken TLS or permanently bypass the VIP simply because a direct diagnostic test succeeds.

Related troubleshooting guides

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 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 Check Evidence Investigation owner Is the guest responsive? Approved console access, OS health, resource and disk observations Desktop/virtualization team if the OS is unavailable. Is this one desktop or a whole image family? Affected pool, image revision, Agent version, start time Image owner if failures align with a deployment. Does registration fail? Agent and Connection Server events for the same desktop and time Horizon team, then netw...
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