Backup Exec agents and the central backup server must maintain a certain level of compatibility. Each version of Backup Exec is designed to be compatible with a specific number of legacy agent versions for upgrades. If a remote system has an older agent version that is not supported by the newer Backup Exec server version, connection attempts fail. This is particularly relevant during rolling upgrades, where some systems may retain older agents while the central server is updated.

If files or registry keys are missing or corrupted, the built-in repair tool can fix them.

If a reboot is not feasible or you have confirmed a reboot was done, you can delete the registry keys causing the block. Editing the registry is risky. Always back up the registry before making changes.

The account must have specific rights on the target server to perform backups: Veritas Technologies Backup files and directories Restore files and directories Logon as a service Logon as a batch job (required for newer Windows Server versions). Veritas Technologies 4. Application-Specific Issues (Exchange/SQL)

When passwords change in Active Directory, they must be manually updated inside the Backup Exec services manager. Launch the .

This article provides a comprehensive guide to understanding, diagnosing, and resolving the 0xe00086cc error in Backup Exec. What Causes the 0xe00086cc Error?

The article will cover:

After resizing, rerun the backup job.

For NAS or networked storage, ensure the Backup Exec service account has Full Control on the share and NTFS permissions.

Verify that a valid exists. If it is missing, create a new one and mark it as the Default Logon Account .

If the resource was deleted, remove it from the selection list entirely. Save and re-run the job. 3. Re-establish Trust with the Remote Agent

Many antivirus tools lock VSS files (e.g., ..System Volume Information\GUID ), causing .

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.

Overzealous firewalls, antivirus software, or strict intrusion prevention systems can mistake backup streams for malicious data. Step-by-Step Troubleshooting Guide