“No *tmp.log found for database ‘Microsoft Exchange Server\Microsoft Information Store\SERVER\Mailbox Database’

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

The error is caused when the circular logging option of the affected mailbox database was previously disabled, and then enabled again.

When circular logging is enabled, the *.tmp (temporary workspace) file is not spooled to the temporary directory, causing this error.

To resolve the problem, you need to disable circular logging for the affected mailbox database. For Exchange 2010 you need to follow these steps:

• Start Exchange Management Console
• Expand Microsoft Exchange On-Premisis (Server), then expand Organization Configuration
• Select Mailbox, and right click on the affected mailbox database shown in the middle panel.
• Select Properties, and the Maintenance tab
• Un-check the Enable circular logging checkbox:

When circular logging is disabled you will need to perform a full exchange server backup manually (below). This backup will complete with the same error but the *tmp.log will be newly uploaded. You need to perform an incremental backup afterwards to check if problem is solved.

For more information refer to: http://msdn.microsoft.com/en-us/library/aa579094%28v=exchg.140%29.aspx

Please read our Disclaimer and Copyright notice

Click on the Chat logo on the bottom left corner of the page to start a session. Enter your name and subject and click ‘send’ to start a session.

You can also request the Backup-Connect team to call you, or send us an e-mail. Chat is available from 09:00 to 17:00 CET.

The Backup-Connect Team

What types of databases are you able to backup with Online backup Manager (Server Backup)?

Answer:

Backup-Connect OBM comes with specialized backup modules for all commonly used databases, ensuring complete protection of critical data. These modules include:

• Microsoft Exchange Server 2000 / 2003 / 2007/2010
• Microsoft SQL Server 7.0 / 2000 / 2005 / 2008
• Lotus Domino / Lotus Notes 5.0 or above
• Oracle 8i or above
• MySQL 3.2.4 or above

Any other databases can be backed up within a file backup, if you are able to create a backup file. Use the command line tool to run a post command which is able to create a backup file or stop the database.

Please read our Disclaimer and Copyright notice

Go to our website: http://www.backup-connect.nl/ and click the login button in the top right corner.

Select the correct backupserver and click on the ‘forgot password’ button.

In the following screen, enter your userid. Click request and the password will be sent to the same e-mail address which receives backup reports

You can also enter your e-mail address, however it must the same address which also receives backup reports.

A ‘hashed’ password will be sent to your mail. You can use this to log on to OBM/PCS and change your password. You can however not restore data with it. If you want to create another encryption key, please read the following document: http://support.backup-connect.com/2011/05/27/faq-create-new-encryption-key/

Please read our Disclaimer and Copyright notice

You can create a new key by creating a new backupset with the same backupsource (in PCB you have to remove your old backupset first). If you want to use a key which is different than your password, select ‘custom’ . (Also see the encryption section in: http://support.backup-connect.com/2011/01/12/how-to-install-windows/).

If you reinstall the software (this is necessary for upgrading the software), it is important to remember your key well. After installation you will be prompted to enter a new encryption key. Use custom if your key is different from you password to prevent the backup from containing 2 keys.

 To reset your password see: http://support.backup-connect.com/2011/05/27/faq-reset-password/

We would like to remind you that it is very important to keep a record of your password an encryption key.

Please read our Disclaimer and Copyright notice

[Microsoft][ODBC SQL Server Driver][SQL Server]Write on ‘Directory_Path\Backup_ID\(local)\*.bak.YYYY-MM-DD-hh-mm-ss.ADD’ failed, status = 112. See the SQL Server error log for more details.

The message suggests that the disk space on the MS SQL server has ran out.

In order to perform a MS SQL database backup, you need to have sufficient free space on the disk to temporary store .bak files. To resolve the issue, please free up some disk space on the local drive configured as temporary directory.

You can also configure the temporary directory to another (network) drive.

In the cases where the temporary directory is on a FAT32 volume, the maximum possible size for a file on a FAT32 volume is 4GB minus 1 bytes . If you want to backup database files which exceed 4GB, please convert the FAT32 volume to NTFS.

For more information about NTFS conversion:

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

or

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

Please read our Disclaimer and Copyright notice

[BackupSetIndex.init]@371bed71 Index corrupted ”C:\Backuptask\backupserver\UserID\Folder’ Backup finished with error(s).

The message may suggest that there is a corrupt index, but actually there is a problem reaching the destination folder which is being set in the local backup setting. The problem can be caused by the following:

• There is a technical issue with the drive where data is being copied to. Check if there are no I/O errors (event viewer) and if there is sufficient free disk space. If this is a network drive it could be a network problem. You can also change the folder to another drive.
• If the destination folder is set on a networkdrive, insufficient permissions can also prevent data from being copied. This instruction will guide you in how to grant the online backup scheduler sufficient permissions: http://support.backup-connect.com/2010/01/26/backup-connect-online-backup-scheduler-cant-access-files/

Please read our Disclaimer and Copyright notice

When you perform a MS Exchange backup, you can receive the following message in the backup report:

CExBackup::backupFile:WriteFile Path=\Temporary_Directory\Backup_ID\SERVER\Microsoft
Information Store\Mailbox Store (SERVER)\File: Error Number 0×70: There is not enough
space on the disk.

The message suggests that the disk space on the MS Exchange server has ran out. OBM is then unable to copy the database files to the temporary directory.

This could be caused by a previously interrupted exchange backup, leaving the (old) database files in the temp directory. When you are creating space, make sure you check the temp directory first.

You can also simply change the temp directory to another drive or network path. In the latter it is important that the online backup scheduler has sufficient permissions. To change do the following:

• go to configure backup
• Select the affected backuptask
• click ‘options’
• change the patch of the temporary directory (see example):

In some cases the temp directory is on a FAT32 volume. When the database file exceeds 4g it will be unable to copy it to the directory. To solve you need to convert your drive or partition to NTFS:

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

Please read our Disclaimer and Copyright notice

[Error][New Mail] Mail=”Server\Mailbox Store\Mailbox\
Subfolder\
AAAAAOr6JSVgEwNCgfXMST0yfGsHAN3e0L8d_tlNgyBzTffk6NMAACoYAvEAAN3e0
L8d_tlNgyBzTffk6NMAM_tgQ24AAA==.msg” Error=”C:\Users\
User\.obm\cache\1294849386751\1302721722605.msg (The
system cannot find the file specified)”

The message suggests that certain items cannot be found in the temp directory (usually Users\user\.obm\). What actually happens is that these items are flagged as spam, and placed in quarantine by your virus scan software. OBM does copy these items to the temp dir, but being  flagged as spam, OBM is not allowed to upload these through the internet.

To resolve the issue you can either:

• Exclude the temp folder which OBM uses from being scanned by your virus scan software.
• Delete the spam items.

Please read our Disclaimer and Copyright notice

Error yyyy/mm/dd hh:mm CExBackup::backupService:HrESEBackupSetup: Error Number 0x50d

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.

To solve the problem you can perform one of the following action:

• 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.
• Each backup operation generates a set of events. Each of these events corresponds to a particular phase of the backup operation. The following events indicate that backup was canceled or aborted after PrepareBackup and before DoSnapshot:

Event ID 9840 is logged when a VSS backup operation fails in Exchange 2007.

You can resolve this issue by restarting Microsoft Exchange Information Store service. To restart the Microsoft Exchange Information Store service, follow these steps:

1. Click Start, point to All Programs, point to Administrative Tools, and then click Services.
2. Right-click the Microsoft Exchange Information Store service, and then click Restart.
3. Try to perform the backup operation that resulted in event ID 9840.

For more information see: http://support.microsoft.com/kb/910250

Please read our Disclaimer and Copyright notice