Exact Error Message
Backup- \\Exchange\Microsoft Information Store\First Storage Group
Database was not found, or could not be accessed.
Database was not found, or could not be accessed.

Details:
In some cases, when a Backup Exec for Windows Servers Exchange IS backup with GRT (Granular Restore Technology) enabled is targeted to a Backup to Disk device, the job may fail with the following error: Backup- \\Exchange\Microsoft Information Store\First Storage Group Database was not found, or could not be accessed.

This error can occur on full or incremental backup types. In addition to the failure, a debug of the local Remote Agent service will display the following error: JetExternalRestore(2) - ERROR::RC = -1022 - -1022 There is a disk IO error

Potential solutions:

1: This issue will occur if the IMG folder used to store GRT related data is being scanned by anti-virus software while the backup is running. To resolve this issue, remove the IMG folder from being scanned by the local media server's antivirus. NOTE: IMG folders are located in the root of the target Backup to Disk folder.

2: The steps described in Microsoft KB article 304101 (see acknowledgements) for Registry setting 1 will need to be applied to the Backup Exec media server.  A reboot on the media server is required after making these changes.

3. This issue can also occur if the drive which hosts the Backup to Disk folder is fragmented. A disk defrag will need to be preformed for the backup to complete successfully.

NOTE: If the -1022 error in the debug is followed by: "StopVirt FAILED!  RC = 1450 (0x5aa) - Insufficient system resources exist to complete the requested service", the following suggestions should be tried:

1. For media servers with more than 3 Gb's of RAM, the 3 GB switch can be set in the boot.ini file on the Backup Exec media server (see acknowledgements)

2. Due to how Backup Exec handles mapping the Exchange database in memory, some databases (typically large databases, or databases with a large amount of logs) require more virtual memory than a 32bit server can provide. These limitations can be avoided when using a x64 bit server, and as such may require Backup Exec to be installed onto a x64bit Windows server.

Related Documents:

276646: Debug Mode Shortcut List for Backup Exec for Windows Servers
 http://support.veritas.com/docs/276646


285753: Backup Exec 11d Best Practices Guide: Agent for Microsoft Exchange Server
 http://support.veritas.com/docs/285753


287464: Backup of Microsoft Exchange Information Store (IS) or the System State to a Backup-to-Disk Folder fails with the error "'-546 The log file sector size does not match the sector size of the current volume." or with "access denied" when the Granular Restore Technology (GRT) feature is enabled
 http://support.veritas.com/docs/287464


303608: "Access denied and -1022 There is a disk IO error" occurs when running a Microsoft Exchange 2003 or 2007 GRT (Granular Restore Technology) Backup to a Data Domain Appliance Series Device.
 http://support.veritas.com/docs/303608


311195: Granular Recovery Technology (GRT) based backup of Exchange Database to a Backup to Disk (B2D) Folder fails with error "Final error: 0xe00084af - The directory or file was not found, or could not be accessed"
 http://support.veritas.com/docs/311195


321272: Granular Recovery Technology (GRT) based backup of Exchange Database to a Backup to Disk (B2D) Folder fails with error "Final error: 0xe00084af - The directory or file was not found, or could not be accessed" if compression is enabled on the B2D target hard disk
 http://support.veritas.com/docs/321272


326836: How to troubleshoot backup jobs that fail with the error message " Final error: 0xe00084af - The directory or file was not found, or could not be accessed "
 http://support.veritas.com/docs/326836


327940: Backups of Exchange 2003 or 2007 using Granular Recovery Option (GRT) fail with: "Database was not found, or could not be accessed." -1022 There is a disk IO error.
 http://support.veritas.com/docs/327940

Supplemental Material:

System: Ref.#	Description
ETrack: 866229	1022 There is a disk IO error.
UMI: V-79-57344-759

Acknowledgements
http://support.microsoft.com/kb/304101

---