Knowledge Base

Microsoft Exchange Backup

• Error Number 0×70: There is not enough space on the disk (insufficient free space in temporary directory)
• Error Number 0xc8000230: The database missed a previous full backup before the incremental backup
• No *.edb or *.stm found for database (MS Exchange server backup)
• Expect log sequence 'xxx' but found 'SERVERNAME\Microsoft Information Store\First Storage Group\E000xxx.log'
• Error Number 0x50d: CExBackup::backupService:HrESEBackupSetup
• Error Number 0xc8000232: Some log or patch files are missing
• Error Number 0xc800020e: An incremental backup cannot be performed when circular logging is enabled
• Error Number 0x3: The system cannot find the path specified (MS Exchange server backup)
• The last backup jQuickbackup of *.stm and *.edb don't match ... (MS Exchange database backup)

Microsoft SQL Database Backup

• ISSUE: The statement BACKUP LOG is not allowed while the recovery model is SIMPLE (MS SQL transaction log backup)

Microsoft Exchange Backup

Error Number 0×70: There is not enough space on the disk (insufficient free space in temporary directory)

Problem Description:

When performing a MS Exchange server backup, the following error messages are received in the backup report:

Cause:

The message suggests that the disk space on the MS Exchange machine has ran out.
This error can also occurs if the following conditions are true:

1. The temporary directory specified for the MS Exchange server backup set is on a File Allocation Table (FAT32) volume
2. The server file to be backed up exceeded 4GB

Since the maximum possible size for a file on a FAT32 volume is 4GB minus 1 bytes, the error is flagged due to FAT32's limitation.

Resolution:

In order to perform a MS Exchange server backup, it is required for the corresponding machine to have sufficient free space for the spooling of the server file. To resolve the issue, please free up some disk space on the local drive.

Alternatively, you could also configure the temporary spooling of the server file to a network path.

In the cases where the temporary directory is on a FAT32 volume, and the server file to be backed up exceeded 4GB, please convert the FAT32 volume to NTFS with the following instructions:

1. Click Start, Programs, and then Command Prompt
2. At the command prompt, type CONVERT [driveletter]: /FS:NTFS
3. Convert.exe will attempt to convert the partition to NTFS

Notes
Once you convert a drive or partition to NTFS, you cannot simply convert it back to FAT or FAT32. You will need to reformat the drive or partition which will erase all data, including programs and personal files, on the partition. 

http://support.microsoft.com/kb/q214579/
http://technet.microsoft.com/en-us/library/bb456984.aspx

Also See:

http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/prork/prdf_fls_pxjh.mspx?mfr=true
Other Info: N/A

Error Number 0xc8000230: The database missed a previous full backup before the incremental backup

Problem Description

When performing a MS Exchange transaction log backup, the following error message is received in the backup report

Cause

The message suggests that a full MS Exchange server backup has not been performed before the transaction log backup.

Resolution:

To resolve the issue, please perform a full database backup on the MS Exchange database in concern before proceeding with any transaction log backup.
In the cases where a defragmentation is performed on the MS Exchange database, please also perform a full database backup on the database in concern. Earlier incremental or differential backups are no longer useful because they refer to database pages that were rearranged by the defragmentation process.

Also See

http://support.microsoft.com/kb/328804

No *.edb or *.stm found for database (MS Exchange server backup)

Problem Description

When performing a MS Exchange server backup, the following error message is received the backup report:

Errors found while validating your backup files. Please run a full backup to correct the problem.

Cause:

The message suggests that there is inconsistency found with the backups, such as missing database files which could have occurred from the previous backups.

The error can be caused if for example there was a problem with the previous backup that had failed to upload the database file correctly, or if there was any disk issues on the backup server, which has removed the files due to corruption. 

If the recent backup history from the reports shows no other backup failures, it is recommended to check the system log on Backup Server web console to ensure that there are no log entries of any indexing or disk issues that may cause the system to remove the files.

Resolution:

To resolve the issue, please perform a full MS Exchange server backup manually via the QUICKBACKUP Advanced console. Please be reminded to allow the next full server backup to run to completion even if the same error message is displayed. The problem will be resolved on the sub-sequence backup job afterward. 

Expect log sequence 'xxx' but found 'SERVERNAME\Microsoft Information Store\First Storage Group\E000xxx.log'

Problem Description

Cause

This error can occurs when:

1. The log sequence of MS Exchange database was altered by other backup software (e.g. NTBackup). 
   When QUICKBACKUP Advanced next performs a MS Exchange server backup, the log sequence would not match the one that QUICKBACKUP Advanced is expecting. With the broken sequence, the server cannot be restored to its latest state.
2. There were problems with a previous backup which failed to upload the log file(s) correctly, or if there were disk issues on the backup server, where the system removed the file due to corruption. 
   If the recent backup history from the reports shows no other backup failures, it is recommended to check on the system log for any indexing or disk issues which may cause the system to remove the transaction log file(s).
3. If the user has changed the minimum size for In-file delta to a value smaller than the corresponding MS Exchange log file size (e.g. 5 MB for MS Exchange 2000 / 2003 and 1 MB for MS Exchange 2007). 
   Deltas would be generated for transaction log, resulting in the expected log sequence error.

Resolution

To resolve this problem, you need to deactivate all other backup software that is operating on MS Exchange, and then you need to perform a Full MS Exchange database backup manually via the Backup Manager. Alternatively, instead of backing up transaction logs during the weekdays, you can consider doing Full Exchange Database backup on a daily basis with the In-File Delta option enabled. This should avoid interference from other backup software while keeping the amount of upload data to minimal.

Error Number 0x50d: CExBackup::backupService:HrESEBackupSetup

Problem Description:

When performing a MS Exchange server backup, the following error message is received in the backup report:

Cause:

The message suggests that the Exchange VSS writer has detected that an earlier Exchange snapshot backup operation is in an unfinished state. Therefore, the current backup operation and all subsequent backup operations are unsuccessful.

Resolution:

If an earlier Exchange snapshot backup operation is in progress, wait for the backup operation to finish before you start the next Exchange snapshot backup operation.

Also See:

http://support.microsoft.com/kb/910250

Error Number 0xc8000232: Some log or patch files are missing

1. Problem Description:

When performing a transaction log / differential MS Exchange backup, the following error message is received in the backup report:

Cause:

The message suggests that the corresponding information store had circular logging enabled previously.

Resolution:

To resolve the issue, please check if the Information Store has been restarted after disabling the circular logging option. Furthermore, please perform a MS Exchange server backup with In-file delta disabled, this will ensure that the data on server are all backed up properly.

Error Number 0xc800020e: An incremental backup cannot be performed when circular logging is enabled

Problem Description:

When performing a MS Exchange transaction log backup, the following error message is received in the backup report:

Cause:

The message suggests that a transaction log backup cannot be performed if the corresponding information store has circular logging enabled.

Resolution:

To resolve the issue, please disable circular logging of the corresponding information store, and restart the "Microsoft Exchange Information Store" service afterward.

Furthermore, please also perform a full MS Exchange server backup instead of transaction log backup straight after disabling circular logging. This would ensure that the data on server are all backed up properly.

Also See:

http://support.microsoft.com/kb/147524
http://support.microsoft.com/kb/258470

Error Number 0x3: The system cannot find the path specified (MS Exchange server backup)

Problem Description:

When performing a MS Exchange server backup, the following error message is received in the backup report:

Cause:

The messages suggest that QUICKBACKUP Advanced cannot access the Exchange database files spooled to the designated temporary directory.

Resolution:

To resolve the issue, please ensure that the temporary directory designated for the MS Exchange server backup is accessible during the backup process.

For manual backup, ensure that the user running QUICKBACKUP Advanced has sufficient permission to access the network path.

For scheduled backup performed by the QUICKBACKUP Advanced scheduler, check if the 'Log on' account of the scheduler service has sufficient permission right(s) to access the network path. By default, the scheduler service will log on as 'Local System', which has no permssion for network resource.

Please update the QUICKBACKUP Advanced scheduler service with a Windows account with sufficient permission:

1. Open [Control Panel] > [Administrative Tools] > [Services] > [Online Backup Scheduler (Online Backup Manager)] > [Log on]
2. Select the [This Account] option
3. Enter the Login Credentials
4. Restart the [Online Backup Scheduler (Online Backup Manager)] service

The last backup Quickbackup of *.stm and *.edb don't match ... (MS Exchange database backup)

Problem Description:

When performing a MS Exchange server backup, the following error message is received in the backup report:

Errors found while validating your backup files. Please run a full backup to correct the problem.

Cause:

For MS Exchange server backup, *.stm and *.edb file are backed up in pair. If the error message above is received, it implies that during a previous backup, there was a problem with either the *.stm or *.edb file.

The error can be caused if for example there was a problem with the previous backup that had failed to upload the database file correctly, or if there was any disk issues on the backup server, which has removed the files due to corruption.

Resolution:

To resolve the issue, please perform a full MS Exchange server backup manually via the QUICKBACKUP Advanced console. Please be reminded to allow the next full server backup to run to completion even if the same error message is displayed. The problem will be resolved on the sub-sequence backup job afterward. 

Microsoft SQL Database Backup

ISSUE: The statement BACKUP LOG is not allowed while the recovery model is SIMPLE (MS SQL transaction log backup)

Problem Description:

When performing a MS SQL transaction log backup, the following error message is received in the backup report:

Cause:

The message suggests that recovery model of the database in concern is currently set to SIMPLE. When using the simple recovery model, the log is truncated when periodic checkpoints occur. Only full database and differential database backups are allowed.

The following table summarizes the recovery models and backup types available with each recovery model:

Resolution:

To resolve the issue, please modify the recovery model of the database in concern to FULL. 

For QUICKBACKUP Advanced version prior to 5.2:
If you are using QUICKBACKUP Advanced version prior to 5.2, please open Enterprise Manager or SQL Server Management Studio (depending on the MS SQL version in concern), right click on the database name, select Properties, select the Options tab and select recovery model from the drop-down list.

       Example with MS SQL 2000:
       

       Example with MS SQL 2005:
       

If you are using MSDE, please issue the following commands:

       Example:
       >osql -E -S [Server Name] -Q "ALTER DATABASE [Database Name] SET RECOVERY FULL"

This will enable transaction logging option for the MSDE databases and allow transaction log backup to be performed.


For QUICKBACKUP Advanced version after 5.2:
If you are using QUICKBACKUP Advanced version 5.2 or after, you can simply modify the recovery mode of your database by right clicking on the corresponding database in the Backup Source menu of QUICKBACKUP Advanced, and then select Recovery Model:

       Example:
       

Also See:

http://searchsqlserver.techtarget.com/tip/0,289483,sid87_gci1069109,00.html