"This Backup Set may not contain any data" is reported in the Backup Job log from an attempted file backup of Exchange Information Store data through the Exchange data directories.

Article:TECH38221  |  Created: 2010-01-01  |  Updated: 2012-01-24  |  Article URL http://www.symantec.com/docs/TECH38221
Article Type
Technical Solution


Issue



"This Backup Set may not contain any data" is reported in the Backup Job log from an attempted file backup of Exchange Information Store data through the Exchange data directories.


Error



Backed up 0 files in x directories. This backup set may not contain any data.


Solution



The informational message referenced "This Backup Set may not contain any data" will be reported in a backup job log when Exchange database files were selected in the Exchange data directories through the file system even though the Exchange Stores for that Storage Group are all dismounted, or the Exchange services have been stopped. Programming logic in the Remote Agent service for Backup Exec 10.0 requires that the Remote Agent service be stopped and restarted after any changes to the Exchange databases or services, for those changes to be recognized by Backup exec. The additional step of cycling the Backup Exec Remote Agent service was not necessary with previous versions of Backup Exec.

Microsoft Exchange Information Store data can be protected by several different methods. While backing up Information Store data online through the backup, Exchange Agent offers the simplest, most flexible, and robust recovery solution. It is also useful to back up the Exchange databases as "flat" files as part of a comprehensive Exchange data protection scheme. In Backup Exec 10.0 for Windows Servers, this is accomplished by performing the following steps:

1. Dismounting all of the stores for a particular Storage Group, or by stopping the Exchange Information Store and System Attendant services

2. Cycling the Backup Exec Remote Agent service on the Exchange Server

3. Selecting and backing up the .edb, .stm and .log files from the Exchange data directory or directories

Typically the Exchange database files are located in the x:\Program Files\Exchsrvr\MDBDATA directory. Transaction log files for those databases are typically in the same path but are often placed on a separate drive for performance reasons. However, Exchange System Manager will allow the Exchange database files to be placed in a user-defined location as well. The data path should be checked to be sure all files necessary for recovery are properly protected (see figure 1 and figure 2). Please review the referenced Microsoft Knowledge Base article for additional information regarding ways to make certain that all of the appropriate files required for recovery are protected.

Figure 1
 

Figure 2
 

When using Backup Exec 10.0 to perform a "flat file" backup of Exchange database files, it is necessary to perform the additional step of stopping and restarting the Backup Exec Remote Agent service in order for Backup Exec to recognize any status changes to the Exchange database services or database stores. Once all stores in a particular storage group have been dismounted, or the Exchange Information Store and System Attendant services have been stopped using the Services application, simply stop and restart the Backup Exec Remote Agent service. This will allow Backup Exec to be made aware of the offline status of the Exchange database and the backup job will then be able to access the files to be written to the backup media. Then, in the Backup Exec backup job properties window, select the appropriate Exchange database files (see figure 3). Following this procedure will ensure a proper offline backup of the Exchange database files. As always, please be sure to check that the byte count for this job contains the expected amount of data.

Figure 3
 

 

Supplemental Materials

SourceETrack
Value323384
Description

Active File Exclusions for Exchange do not function as expected



Legacy ID



276229


Article URL http://www.symantec.com/docs/TECH38221


Terms of use for this information are found in Legal Notices