Backup Exec Agent for Microsoft Exchange Server
Most Popular | Most Recent
Version : Environment :
Email messages backed up using Granular Restore Technology (GRT) are restored with a blank body.
Doc. ID: TECH50833 | 2013-11-22
"Database was not found and could not be backed up" (0xa000fe7c or 0xe000fe7c) error is returned when attempting to back up an Exchange Information Store.
Doc. ID: TECH33050 | 2013-11-22
Exchange 2010 mailbox or mailbox item restore fails with 0xe00002f8 - Cannot open one or more mail messages because of unknown MAPI error
Doc. ID: TECH175543 | 2013-11-22
Exchange GRT enabled backups will fail if Backup Exec and Exchange are installed on the same cluster but their cluster resources are running on different nodes and the backup job is targeted to a tape device.
Doc. ID: TECH157582 | 2013-11-22
Restore of individual items from a Granular Recovery Technology (GRT) enabled Exchange 2010 Information store fails with "0xe00002f8 - Cannot open one or more mail messages because of unknown MAPI errors."
Doc. ID: TECH146880 | 2013-11-22
Exchange 2003: Restore of an individual mail message completes with exceptions: WARNING: The file 'MessageName" was restored from a file that was corrupt when it was backed up, or the backup file is now missing or corrupt. Try restoring the file from another backup, or try repairing the file.
Doc. ID: TECH124598 | 2013-11-22
Using Storage Provisioning Option (SPO) backup device with Granular Restore Technology (GRT) in Backup Exec 12.5
Doc. ID: TECH69089 | 2013-11-22
How to use NTBackup to test Exchange 2003 backups/restores on Windows 2003 to compare the backup performance with Backup Exec for Windows Servers.
Doc. ID: TECH65437 | 2013-11-22
Exchange Granular Recovery Technology (GRT) based backups may receive a jet database error -528 or "Database was not found, or could not be accessed" when backing up to a remote Backup to Disk folder (B2D) that is located on a NAS device
Doc. ID: TECH61642 | 2013-11-22
How to troubleshoot the error message: "The connection to target system has been lost. Backup set cancelled."
Doc. ID: TECH71227 | 2013-11-21
Backup Exec 2012 Software Compatibility List (SCL)
Doc. ID: TECH175581 | 2013-11-21
The Backup Exec server reboots with the memory dump reporting the "VIRTFILE.SYS" to be the cause.
Doc. ID: TECH60397 | 2013-11-21
Duplicate backup fails with error 0xe0009444 - The requested source duplicate backup sets catalog record could not be found
Doc. ID: TECH43264 | 2013-11-20
Attempt to backup Microsoft Virtual Server (MSVS) Exchange 2003 Guest fails with the error " AOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status."
Doc. ID: TECH59976 | 2013-11-20
Exchange Information Store backup fails with the error "The Backup Exec Agent for Microsoft Exchange was not used to create the last full backup of this database"
Doc. ID: TECH59970 | 2013-11-20
How to troubleshoot Exchange 2007 backups that is failing due to VSS (Volume Shadow Copy Service) Issues
Doc. ID: TECH58562 | 2013-11-20
Restore of an Exchange 2010 database to the Recovery Database fails with the error "The Exchange server was not found"
Doc. ID: TECH126526 | 2013-11-20
GRT (Granular Restore Technology) enabled Exchange 2003 backups fail with: "A memory allocation request failed. The computer may be running low on virtual memory"
Doc. ID: TECH61374 | 2013-11-20
Exchange 2003/2007 GRT restores fail with "Final error: 0xe000ff12 - A communication failure has occurred with an Exchange Store resource."
Doc. ID: TECH153861 | 2013-11-20
AOFO: Initialization failure on: "\\SERVERNAME\Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot failed. Make sure that all provider services and tasks are running. Check the Windows Event Viewer for details"
Doc. ID: TECH53383 | 2013-11-20