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

CAD Artifacts in Horizon VDI: Isolate Rendering, Remoting, and Endpoint Problems

Persistent CAD artifacts in VDI need a rendering-to-display comparison, not an immediate vGPU purchase. A stale viewport may involve the application renderer, guest graphics driver, remoting/encoding path, endpoint decoding or display. Duration alone does not identify the faulty layer.

Correction, September 12, 2026: The previous article treated persistent ghosting as definitive SVGA failure and vGPU as the only direct fix. It also generalized graphics API support and cost advantages. Those claims are withdrawn. This is a proposed diagnostic and acceptance plan, not a measured hardware comparison.

Capture a reproducible workload

Use a sanitized model that reproduces the problem. Record application version, renderer, guest OS/driver, virtual graphics configuration, Client/Agent versions, protocol, endpoint GPU/driver and display layout. Record the exact action—rotation, redraw, window movement or selection—that creates the artifact.

Pilot comparisonUseful observationLimitation
Supported application renderer changeDoes the same model redraw correctly?Improvement does not prove a vendor-wide driver defect.
Another supported remoting protocolDoes artifact behavior change with the display path?More than one encoding/transport variable may change.
Another endpoint, same session configurationDoes the issue follow the endpoint?Keep resolution and monitor layout comparable.
Supported GPU-backed pilotCorrectness and workload performanceOne successful model does not qualify every application.

Do not equate screenshot evidence with the whole pipeline

Compare an application export, a permitted in-session capture and the endpoint view where these are available. Different capture methods can use different rendering paths, so treat differences as diagnostic clues. Do not bypass capture protections or use confidential engineering models in public evidence.

Omnissa's Blast optimization guide explains encoding and workload trade-offs. Use the NVIDIA vGPU support matrix for the exact release and hardware when evaluating NVIDIA-based acceleration. Verify application-vendor certification separately; a supported hypervisor/GPU combination does not establish CAD application certification.

Choose and validate one correction

Test one documented renderer, driver or protocol change in a pilot. Preserve original settings and compare image correctness, input response and resource usage using the same workload. Roll back if the change fixes one artifact but breaks another view or application. Do not force lossless modes or codec presets globally without measuring bandwidth and user impact.

Evaluate GPU-backed VDI against a managed workstation only after defining required features, user count, support, licensing and measured acceptance results. Neither is automatically cheaper. Escalate a reproducible defect with the small test model and configuration, retaining uncertainty about the failing layer until the evidence resolves it.

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