0xe00086cc Backup Exec

Blog Title:

Deep Dive: Conquering the Backup Exec 0xe00086cc (V-79-57344-39628) Error

The 0xe00086cc error in Veritas Backup Exec typically indicates a communication failure between the Backup Exec server and the Remote Agent. This occurs when the media server cannot establish a secure connection or loses synchronization with the target machine during a job. Understanding Error 0xe00086cc 0xe00086cc backup exec

0xe00086cc

The error code in Veritas Backup Exec typically occurs during a push installation or upgrade of the Agent for Windows (RAWS). It is often closely related to error 0xe00086c0 , which indicates that the version of the agent already on the target computer is not supported for a direct upgrade by your current Backup Exec media server. Primary Cause This error is usually triggered because: Blog Title: Deep Dive: Conquering the Backup Exec

version of Backup Exec

If you are currently troubleshooting this, I can help further if you let me know: What you are using? If you recently updated or changed credentials ? If this is happening to one server or all of them ? Open Backup Exec console

The Windows Firewall or a third-party firewall may be blocking the necessary ports for WMI, file/printer sharing, or Remote Registry. Permission Denied:

  1. Open Backup Exec console.
  2. Go to Tools > Options > Advanced File Open Option.
  3. Increase the VSS snapshot timeout from 60 seconds to 300–600 seconds.
  4. Enable "Retry failed VSS snapshots" and set retries to 3 with 30-second intervals.
  5. For virtual environments: Under Hyper-V or VMware settings, increase snapshot timeout to 15 minutes.

. Backup Exec operates on a client-server model where the media server must establish a stable handshake with the Remote Agent for Windows Servers (RAWS) or Linux Servers (RALUS). When the media server attempts to initialize a job—be it a backup, restore, or simple browse—and finds that the target volume, database, or virtual machine is unreachable, it throws the 0xe00086cc exception. Primary Triggers The root causes generally fall into three categories: Network and Connectivity Issues:

Network/storage layer (if applicable)