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 Connection Failure on an Older PC: A Controlled Client-Version Test

Documentation-based comparison plan. Revised September 12, 2026. No verified CPU measurements, client builds, or reproduction logs support the old explanation. The claimed 100% CPU mechanism and recommendation to install a client several releases older have been removed.

If Horizon fails on an older PC, age is a clue about what to measure, not a diagnosis. A successful connection after a client replacement could reflect a version difference, repaired installation, reset preferences, or changed feature configuration. This article isolates those variables rather than treating a downgrade as proof of weak hardware.

Define a reproducible launch test

Record the exact error text, client and Agent builds, endpoint OS, graphics driver, configured protocol, monitor arrangement, pool, and last successful connection stage. Preserve client logs before reinstalling. Establish whether the process crashes, the session closes, or the display never opens; these outcomes need different evidence.

Use a comparison sequence

  1. Baseline: repeat one launch on the affected PC without changing preferences. Record time and observed CPU, memory, and graphics activity. A spike is a measurement, not proof of causation.
  2. Known-good endpoint: repeat against the same account, resource, and approved route. Note differences in client build and display settings rather than calling this a hardware-only comparison.
  3. Supported configuration: check the exact release's OS, driver, and feature requirements. Test one documented display-option change only if the logs and chosen protocol justify it.
  4. Client regression test: if a build regression remains plausible, use an IT-approved, supported comparison build in a pilot. Preserve the original installer and settings, and record the full before/after configuration.

Do not change network, client version, graphics options, and pool policy simultaneously. If they all change, the result may restore access but cannot identify the effective change.

Where hardware decoding fits

Blast codec selection and endpoint capabilities matter to display performance; the Omnissa optimization guide describes those choices. That does not establish that every generic connection error is a decoder timeout. Check whether the failing session even reached display initialization before spending time on codec tuning.

Temporary access without an indefinite downgrade

Prefer an approved working endpoint when available. Any temporary alternate client needs a support and security review, named owner, expiry, and restoration plan. Do not globally disable updating or install an unsupported build solely because it is old. Application settings or credentials can be affected by uninstalling; agree the recovery plan first.

A useful escalation package contains paired launch logs, exact builds, unchanged variables, changed variable, reproduction count, and outcome. If a supported build reproducibly changes the result, report that observation as a possible regression. Do not buy replacement hardware or declare a security setting defective on that observation alone.

References

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