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

Video Conferencing on Legacy VDI Endpoints: A Capacity and Migration Pilot Plan

For video conferencing on legacy VDI endpoints, run a workload pilot before tuning or replacing the fleet. This article covers the pilot and capacity decision; the separate Teams compatibility guide addresses the “Not Optimized” status. The two questions are related but different: a supported configuration can still have inadequate capacity or a poor network path.

Correction — September 12, 2026: The previous version presented a financial-company incident with 100% CPU and 15 Mbps per-user traffic without a supporting record. It also confused remote-display decoding with application-specific media offload and suggested unverified replacement hardware. Those claims have been removed. This is a proposed test plan, not a completed customer case.

Identify where media is processed

Record whether the application is using its supported VDI optimization, a fallback path, or another supported audio/video configuration. Do not treat RTAV and application-specific media optimization as interchangeable. The Horizon 2312 Teams documentation explicitly distinguishes its Teams media optimization from RTAV. Use the documentation matching the deployed version for an implementation decision.

Likewise, a Tera2 endpoint's ability to receive a PCoIP session is different from its ability to execute a Teams or other conferencing application's endpoint component. Check the HP platform documentation and the application's endpoint support requirements separately.

Define the pilot before measuring

ScenarioKeep fixedObserve
Audio-only callHeadset, application version, session routeCall setup, audio gaps, reconnect behavior
Camera callCamera, agreed video settings, participantsDesktop and endpoint load, visible degradation
Screen sharingShared application, resolution, test actionsText legibility, input delay, bandwidth observations
Representative concurrencyApproved user count, duration, other workloadsHost headroom, network congestion, other users' experience

Agree acceptance criteria with actual users and the service owner. A receptionist, a meeting-heavy manager, and a text-only operator may need different endpoints. Preserve raw measurements and timestamps; averages can hide short periods of severe call disruption.

Separate the bottlenecks

  • If only the unoptimized configuration shows high desktop processing load, investigate a supported offload path before increasing every VM's resources.
  • If several endpoint types degrade only at one location, inspect that location's network evidence before concluding that the chipset is responsible.
  • If degradation begins only with concurrent users, compare host and shared-network utilization with the single-user baseline.
  • If the call stays healthy but peripheral access fails, investigate the device path separately rather than treating it as general video performance.

Tune conservatively and retest

Change one documented setting on a pilot group and record the original value. Reduced frame rate or image quality may help one use case while making another unusable; do not publish a universal numerical preset without workload evidence. Omnissa's challenging-network guide provides broader context for trade-offs, not a performance guarantee for your site.

Restore the previous setting if audio, readability, peripherals, or other applications regress. Hardware replacement should follow a compatibility check and a measured pilot, including management, patching, certificate, and support requirements. A codec listed on a datasheet does not establish full conferencing compatibility.

What to put in the decision record

Summarize the tested configuration, required workload, observed limitation, change tested, measured result, and unresolved risks. If no configuration meets the agreed criteria, retain the evidence and escalate rather than declaring a vendor-wide failure. Publish only sanitized, attributable observations when the pilot has actually been completed.

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