In the realm of enterprise data management, few events induce as much anxiety as a failed backup. For system administrators relying on Veritas Backup Exec, the appearance of a hexadecimal error code often signals a disruption in the digital safety net. Among the most common and frustrating of these is error 0xe00086cc. Far from being a cryptic random number, this error serves as a specific diagnostic signpost, pointing to a fundamental breakdown in the communication between the backup software and the storage hardware. Understanding the technical meaning, root causes, and systematic resolution of error 0xe00086cc is essential for maintaining the integrity of any data protection strategy.
At its core, error 0xe00086cc translates to a storage communication failure, often accompanied by the description: "The device is not ready" or "The request could not be performed because of an I/O device error." This indicates that while Backup Exec successfully initiated a job, it lost reliable contact with the target destination—typically a tape drive, a disk-based storage folder, or a deduplication disk. In technical terms, the software’s SCSI (Small Computer System Interface) or network commands are being rejected by the physical or virtual storage layer. This is not a corruption of the data itself, but rather a disruption of the conduit through which that data must flow.
The causes of this error are multifaceted, often requiring a methodical diagnostic approach. The most frequent culprit lies within the hardware stack, specifically the connection between the media server and the storage device. For tape-based backups, a failing SCSI terminator, a loose Fibre Channel cable, or an outdated tape driver can easily trigger 0xe00086cc. Similarly, for disk-based backups, a failing USB or eSATA controller, a network-attached storage (NAS) suffering from packet loss, or a local hard drive with bad sectors can produce identical symptoms. Another common cause is a resource conflict within Windows, where the operating system’s volume mount manager or a third-party filter driver (such as an antivirus real-time scanner) temporarily locks the target volume, making it appear "not ready" to Backup Exec.
Resolving error 0xe00086cc requires a disciplined, layered troubleshooting strategy. The initial step should always be hardware verification. Administrators should check physical connections, replace suspect cables, and consult the storage device’s native diagnostic tool (e.g., tape library’s front panel or vendor-specific utility) to confirm operational status. Next, one must examine the Windows System Event Log for concurrent disk or controller errors. If hardware is cleared, the focus shifts to Backup Exec’s configuration: updating device drivers to the latest Veritas-certified versions, cleaning the tape drive heads, or running a "TDI (Tape Diagnostic Information) test" from within the Backup Exec console. In many cases, simply restarting the Backup Exec Remote Agent service or performing a rescan of the storage devices through the "Devices" tab can flush transient communication locks. A more advanced solution involves adjusting the SCSI timeout values in the Windows Registry or disabling "write caching" on the target disk drive to prevent command timeouts.
The persistence of error 0xe00086cc in Backup Exec environments underscores a critical lesson in data protection: the backup system is only as reliable as the weakest link in its communication chain. While modern backup software includes sophisticated retry logic and error handling, it cannot compensate for failing hardware, misconfigured drivers, or resource contention. Administrators who master the interpretation of codes like 0xe00086cc move beyond reactive firefighting to proactive system hardening. Ultimately, resolving this error is not merely about clearing a job failure; it is about restoring confidence that when data is needed most, the path from storage to software will be clear and ready. In the high-stakes world of disaster recovery, where every byte counts, understanding the language of these error codes is not a technical luxury—it is an operational necessity.
The Backup Exec error code 0xe00086cc typically surfaces during the installation or upgrade of the Remote Agent for Windows (RAWS). This error generally indicates a compatibility or environment conflict, often occurring when the Backup Exec server attempts to push an agent to a remote machine that has a mismatched or corrupt previous installation. Common Causes of Error 0xe00086cc
Understanding the root cause is the first step toward a resolution. The most frequent triggers include:
Unsupported Upgrade Paths: The version of the agent already on the target computer may be too old to be directly upgraded by your current version of Backup Exec.
Corrupt Installation Files: Residual files from a failed or partial uninstallation can block new installation attempts.
Security & Permissions: Insufficient local administrator rights or restrictive firewall settings (blocking WMI or NDMP ports) can prevent the push installation from completing. 0xe00086cc backup exec
Environmental Conflicts: Third-party applications, such as antivirus software or other backup agents, may be locking files required for the Backup Exec installation. Step-by-Step Troubleshooting Guide 1. Perform a Manual Uninstallation
If a push installation fails with this error, the most effective fix is to manually clean the target machine. Log into the remote server directly.
Use Add/Remove Programs to uninstall any existing Backup Exec Remote Agent.
If the standard uninstall fails, you may need to manually remove the installation folder (typically located in C:\Program Files\Veritas\Backup Exec\RAWS) and clear related registry keys under HKLM\Software\Veritas or HKLM\Software\Symantec. 2. Verify Service Account and Permissions
Ensure the account you are using for the installation has full administrative control.
Confirm that the Backup Exec Service Account (BESA) is not locked out in Active Directory.
Verify that the account has Full Control over the target installation directories.
Check that the Remote Registry service is started on the target machine. 3. Check Network Connectivity and Ports
Backup Exec relies on specific ports to communicate with its agents. In the realm of enterprise data management, few
WMI and NDMP: Ensure Windows Management Instrumentation (WMI) is enabled and not blocked by a firewall.
Port 10000: This is the default port for the Network Data Management Protocol (NDMP) used by Backup Exec. Ensure it is not being used by another application. 4. Run a Manual Agent Installation
If push installation continues to fail, bypass the media server's push mechanism.
Copy the agent installation files (found on the media server in the Agents folder) directly to the remote server. Run setup.exe locally as an Administrator. 5. Establish Trust Relationships
For modern versions of Backup Exec, a security trust must be established. Solved: Backup exec access is denied - Experts Exchange
The hexadecimal code 0xe00086cc corresponds to a specific error message in Veritas Backup Exec: "The Virtual Machine is not synchronized with the Virtual Machine Manager."
While an error message might not seem like a "feature" at first glance, the resolution for this error introduces a helpful feature designed to maintain data integrity during backups.
Here is a breakdown of the error and the "helpful feature" involved in resolving it.
0xe00086cc corresponds to:
"The media server was unable to mount the storage device because the device name may be missing or invalid, or the device may be offline or not ready."
In human terms: Backup Exec cannot access the backup storage device (tape drive, disk folder, deduplication folder, etc.) during a backup or restore job.
A full or corrupted shadow storage area can cause I/O write failures.
On the failing volume (e.g., C:):
vssadmin delete shadows /for=C: /all
vssadmin resize shadowstorage /for=C: /on=C: /maxsize=10GB
Warning: Deleting shadows removes existing restore points. This is safe for backup servers but ensure you don’t need local shadow copies for restore.
After resizing, rerun the backup job.
If the error persists, gather logs for Veritas support:
Backup Exec uses AOFO to grab open files. However, if the target disk is an iSCSI drive, a ReFS volume, or a deduplication drive, AOFO sometimes fails with 0xe00086cc.
Before jumping into fixes, you must identify the root cause. The error typically stems from one of the following scenarios: "The media server was unable to mount the