“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 restart the Microsoft Exchange Information Store Service, for the changed to take effect.  Within backup-Connect OBM you need to perform a full exchange server backup manually (below). This backup will complete with the same error but the *tmp.log file 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

• Checksum errors
• A lot of access denied messages on files

There are a few other ways to recognize this problem.

Check if you recieved two backupreports of the same job in your mail. Otherwise log into the webgui and check ‘reports’ to see if two (or more) backups started at the same time:

When you receive one backupreport with earlier mentioned errors, open it  and check the first rows of the backup log to see if the backup started twice:

To solve the problem, follow the next steps:

• Open the following file: “C:\[Installation Folder]\OBM\home.txt”
• Check if there are multiple users. You will usually see a path like: C:\Users\administrator\.obm
• If there are two or more paths, delete any additional users. We recommend to keep your ‘administator’ folder as the only path. Save when finished.
• Delete the .obm folder from the users you just removed from home.txt.
• go to administrative tools>services
• restart the ‘online backup scheduler’ service.

Run a scheduled backup to see if the problem is solved.

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