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

Tera2 Zero Clients in Horizon: A Support and Migration Decision Record

Documentation-based decision guide. Revised September 12, 2026. The earlier healthcare fleet story, latency percentage, and fixed firmware recommendation were not supported by an attributable test. They have been removed. This article is not a completed migration case.

A Tera2 fleet should be evaluated device by device and workload by workload. A device that still connects is not automatically a supported long-term endpoint. Conversely, one slow call does not justify replacing every device. This guide is a support and purchasing decision record; the separate conferencing pilot covers workload measurement.

Start with an inventory that can be verified

Record the OEM model, processor family, firmware build, update source, support entitlement, monitor configuration, current Horizon Client/Agent environment where applicable, and intended user tasks. Confirm that the hardware is actually a Tera2 PCoIP zero client rather than a thin client running a software client. Product-family names are not interchangeable.

Answer three separate questions

  • Support: can the owner document a supported firmware and server combination, security-update path, and recovery method? Obtain release-specific confirmation; an acquisition announcement is not an end-of-support notice.
  • Function: does the actual endpoint support the authentication, peripherals, monitors, and collaboration features required by the user? Check the exact feature matrix rather than treating successful desktop login as full compatibility.
  • Capacity: does a representative task meet an agreed usability target? Compare the existing device and a supported alternative using the same workload and route. Record observations without inventing a universal bandwidth or latency threshold.

Choose a bounded outcome

Retain: requirements are met and the support evidence is current. Name an owner and reassessment trigger, such as a planned Horizon upgrade or new collaboration requirement.

Temporary exception: the security owner accepts documented limitations, affected users, network scope, and expiry. “It still works” is not an exception approval.

Migrate: a required function or support condition cannot be satisfied. Pilot an alternative, including peripheral use, login, reconnect, and recovery, before buying at fleet scale. Keep a controlled fallback where it remains safe.

Avoid two migration shortcuts

Do not assume a hardware zero client can be converted by installing a thin-client operating system; verify the specific device's capabilities. Repurposing a PC is a different project. Do not describe HP Anyware as a drop-in connector for an existing Horizon deployment without a supported design and validation of agents, authentication, licensing, and endpoint compatibility.

The final decision record should contain evidence links, tested build combinations, unmet requirements, pilot results, security sign-off where needed, cost assumptions, and rollback ownership. Leave unknowns explicitly open. That record supports a defensible purchase decision more effectively than a generic claim that all legacy endpoints are obsolete.

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