0xe00086cc Backup Exec !!top!! -

Error 0xe00086cc in Backup Exec: Causes, Solutions, and Prevention Strategies

Backup Exec is a popular data protection and recovery software used by organizations to backup and restore their critical data. However, like any other complex software, it's not immune to errors. One such error that has been reported by several users is the 0xe00086cc error. In this article, we'll discuss the causes, solutions, and prevention strategies for the 0xe00086cc error in Backup Exec.

What is Error 0xe00086cc?

The 0xe00086cc error is a common error code that occurs in Backup Exec, typically during the backup or restore process. The error message may vary depending on the specific situation, but it usually indicates a problem with the backup or restore operation. The error code 0xe00086cc is a hexadecimal code that represents a specific error condition.

Causes of Error 0xe00086cc

After analyzing various user reports and technical documents, we've identified some common causes of the 0xe00086cc error:

1. Corrupted Backup Exec database: The Backup Exec database stores critical information about the backup and restore operations. If the database becomes corrupted, it can cause errors like 0xe00086cc.
2. Insufficient disk space: Backup Exec requires sufficient disk space to perform backup and restore operations. If the disk space is low, it can lead to errors like 0xe00086cc.
3. Network connectivity issues: Network connectivity problems can prevent Backup Exec from communicating with the backup devices or servers, resulting in errors like 0xe00086cc.
4. Outdated or corrupted device drivers: Outdated or corrupted device drivers can cause communication problems between Backup Exec and the backup devices, leading to errors like 0xe00086cc.
5. Conflicting software: Conflicting software or services can interfere with Backup Exec's operations, causing errors like 0xe00086cc.

Solutions to Error 0xe00086cc

To resolve the 0xe00086cc error, try the following solutions:

1. Restart Backup Exec services: Restarting the Backup Exec services can sometimes resolve the issue. To do this, go to the Backup Exec console, click on the "Tools" menu, and select "Services." Then, restart the Backup Exec services.
2. Check disk space: Ensure that there is sufficient disk space available for the backup and restore operations. Check the disk space on the backup device and the server.
3. Run the Backup Exec Database Maintenance utility: The Backup Exec Database Maintenance utility can help repair corrupted databases. To run this utility, go to the Backup Exec console, click on the "Tools" menu, and select "Database Maintenance."
4. Update device drivers: Ensure that the device drivers are up-to-date and not corrupted. Check the device manufacturer's website for updates.
5. Disable conflicting software: Disable any software or services that may be conflicting with Backup Exec.

Advanced Solutions

If the above solutions don't work, you may need to perform more advanced troubleshooting:

1. Check the Backup Exec logs: Analyze the Backup Exec logs to identify the root cause of the error. The logs can provide valuable information about the error.
2. Run a diagnostic test: Run a diagnostic test on the backup device to ensure it's functioning properly.
3. Reinstall Backup Exec: If all else fails, you may need to reinstall Backup Exec.

Prevention Strategies

To prevent the 0xe00086cc error from occurring in the future, follow these best practices:

1. Regularly update Backup Exec: Ensure that you're running the latest version of Backup Exec.
2. Monitor disk space: Regularly check disk space on the backup device and server.
3. Perform regular database maintenance: Run the Backup Exec Database Maintenance utility regularly to prevent database corruption.
4. Use reliable device drivers: Ensure that you're using reliable and up-to-date device drivers.
5. Test backup and restore operations: Regularly test backup and restore operations to ensure they're working correctly.

Conclusion

The 0xe00086cc error in Backup Exec can be caused by various factors, including corrupted databases, insufficient disk space, network connectivity issues, outdated device drivers, and conflicting software. By understanding the causes and solutions to this error, you can quickly resolve the issue and prevent it from happening in the future. Regular maintenance, updates, and testing can help ensure that your backup and restore operations are running smoothly.

The error code 0xe00086cc in Veritas Backup Exec typically indicates a communication or trust failure between the media server and the Remote Agent on the target machine. This specific hex code (often paired with "Access is denied" or "The resource could not be backed up") usually stems from mismatched credentials, outdated agents, or a broken security certificate. Core Causes of Error 0xe00086cc

Trust Relationship Issues: The security certificate between the Backup Exec server and the remote computer is missing or invalid.

Credential Mismatch: The Backup Exec Service Account (BESA) or the System Logon Account has a password that has expired or does not match the credentials on the target server.

Version Discrepancy: The Remote Agent (RAWS) on the target machine is older than the version running on the media server.

Network/WMI Blocks: Firewall rules or disabled services (like WMI) are preventing the initial handshake. Step-by-Step Troubleshooting Guide 1. Establish a Manual Trust Relationship

If the trust was not established during the initial "push" install, you must do it manually:

In the Backup Exec console, go to the Backup and Restore tab. Right-click the server that failed with the error. Select Establish Trust from the menu. 2. Update the Remote Agent

Backup Exec generally requires the Remote Agent on target servers to match the Media Server’s version.

Check Versions: On both machines, go to Help and Documentation > About Backup Exec to verify the build numbers.

Push Reinstall: Right-click the server in the console and choose to update or reinstall the agent. 3. Verify and Reset Logon Credentials A common culprit is an outdated System Logon Account.

How to determine the installed version for Backup Exec - Veritas 0xe00086cc backup exec

In the landscape of modern data management, Veritas Backup Exec stands as a cornerstone for organizational resilience. However, few things disrupt the peace of a system administrator like the cryptic arrival of an error code. Among these, 0xe00086cc—often accompanied by the message "A failure occurred while connecting to the Backup Exec Remote Agent"—is a particularly common hurdle that highlights the intricate handshake required between a media server and its remote targets. The Anatomy of the Error

At its core, error 0xe00086cc is a communication failure. It signifies that the Backup Exec media server attempted to establish a secure link with the Remote Agent for Windows (RAWS) on a target machine but was rebuffed. This isn't merely a "plug unplugged" scenario; it usually points to a breakdown in the authentication or networking protocols that govern how these two entities trust one another. Primary Catalysts Several factors typically trigger this disruption:

The Trust Relationship: Modern versions of Backup Exec require an explicit "trust" to be established between the server and the remote agent. If this certificate-based handshake is revoked or expires, the connection fails immediately with 0xe00086cc.

Network Interruption: Firewalls are frequent culprits. If the required ports (traditionally NDMP port 10000) are blocked by a local Windows Firewall or a network appliance, the media server remains "blind" to the remote agent's presence.

Service Status: Occasionally, the solution is as simple as the Remote Agent service on the target machine being stopped or hung, preventing it from listening for incoming requests. Path to Resolution

Resolving the 0xe00086cc error requires a methodical approach to infrastructure troubleshooting:

Re-establish Trust: The most effective fix is often right-clicking the remote server within the Backup Exec console and selecting "Establish Trust." This refreshes the security certificates.

Verify Services: Ensure the Backup Exec Remote Agent for Windows is running on the target server and set to 'Automatic.'

Audit Connectivity: Use tools like telnet or Test-NetConnection to verify that port 10000 is open and reachable between the two machines. Conclusion

While error 0xe00086cc can temporarily halt backup operations, it serves as a vital diagnostic signal. By addressing the underlying trust and connectivity issues, administrators not only clear the error but also reinforce the security and reliability of their entire data protection strategy.

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

1. Collect context

   • Backup Exec version and build.
   • Tape library/autoloader model and firmware.
   • Tape drive model and firmware.
   • Exact error text and job log snippet.
   • OS and drivers for the tape device.

2. Quick checks (do these first)

   • Reboot the Backup Exec server and the tape library/drive.
   • Reseat SCSI/HBA/FC/iSCSI cables and power-cycle the library.
   • Confirm correct device drivers and HBA firmware; update to vendor-recommended versions.
   • Verify Backup Exec device configuration: remove and re-add the tape library/drive in Devices view.
   • Clean the tape drive with a manufacturer-cleaning cartridge (if due).
   • Try a different tape cartridge (to rule out bad media).

3. Device/driver and firmware actions

   • Update tape drive firmware to latest vendor release.
   • Update HBA/RAID/iSCSI drivers and firmware on the server.
   • Use vendor diagnostic tools to run drive self-tests; replace drive if diagnostics fail.

4. Backup Exec-specific steps

   • Ensure Backup Exec host ID and device mapping are correct; run Device Configuration Wizard.
   • Delete and reconfigure the device entries rather than using auto-detect if mapping mismatches.
   • Review Backup Exec event logs and job log for the underlying error code text (look for I/O, device not ready, or media error).
   • If using VTL, ensure VTL settings match Backup Exec expectations and that virtual tape mounts are healthy.
   • If encryption is used, ensure keys and encryption agents are available.

5. Network/storage layer (if applicable)

   • For SAN-attached tape: verify zoning, LUN masking, and that the server has exclusive access.
   • For NAS/VTL over network: check network stability, latency, and mounts.

6. When to escalate

   • Persistent I/O errors after cleaning and media swap → suspect hardware failure (drive or robotics).
   • Vendor diagnostics report errors → open RMA/repair with hardware vendor.
   • Backup Exec-specific errors after device reconfiguration → contact Veritas support with job logs and device logs.

7. Logs to gather before contacting support

   • Backup Exec job log and BESERVER logs.
   • Windows System and Application event logs (or OS-equivalent).
   • Tape drive/vendor diagnostics output.
   • Firmware versions and device model numbers.

If you provide the exact error text/hex code, Backup Exec version, and tape library/drive model, I can give targeted next steps.

4. Corrupt System State (Registry Hive issues)

If the error points specifically to System State or Registry, you may have registry corruption.

• Fix: Run chkdsk /f /r on the system drive. Afterwards, run sfc /scannow. A single bad registry key can break the entire System State backup.

What is actually happening?

When you see 0xe00086cc, the backup job usually starts successfully, runs for a few seconds or minutes, then crashes. In the job log, you’ll likely see the failure pointing to a specific Volume Shadow Copy Service (VSS) writer or a specific system state component (like the Registry or COM+ Class Database).

The core problem: Backup Exec requested a snapshot of a volume (usually C:) or a specific system component from VSS. The VSS writer responded, "I don't know where that file is," or "Someone locked this exclusively," causing the snapshot to become unstable.

5. Driver & registry fix (tape drives)

• Use the Tapeinst.exe tool (in Backup Exec install folder\Tapeinst) to reinstall tape drivers.
• Remove upper/lower filters for tape drives in registry (advanced – back up first).

Step 6: Adjust VSS Timeout and Retry Settings in Backup Exec

Sometimes, VSS operations time out due to high I/O load.

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.

Step 7: Re-register VSS DLLs (If Windows Server is Corrupted)

If none of the above works, VSS system files may be corrupted. Error 0xe00086cc in Backup Exec: Causes, Solutions, and

On the backup source server:

cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
net start vss
net start swprv

Reboot and re-test.

Specific Scenarios: Hyper-V and VMware