Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Backup may have caused Mail store to unmount

Created: 10 Jul 2013 | 10 comments

Hello

First the basic information: I am running Backup Exec 12.5 Rev 2213 with Service Pack 4 on a Widnows 203 Enterprise SP2 server. The Exchange server is a Windows 2003 SP2 server also. I am running Exchange 2003 ver 6.5.7638.1

Saturday night I had a full backup of the Exchange server running when the Mail Store 1 was unmounted, and the error 1159 showed up in the Event Log. This is the error whereby the transaction logs hit a 1008 maximum and then automatically unmount the store. According to Microsoft forums, this could be caused by the backing up of the server. I have the default settings on my full back up, which should handle the transaction logs created. Is there something else I need to do to prevent this from happening again. It's the first time it has ever happen, although of late I have had issues with the backup failing because it could not access the directory. I have been backing up each mailstore to a new disk set, and the access problem appears to have been solved. The backup I ran on Saturday was the old job, now pointed to the new disk space. Should I delete the old job and setup a new one? Attached is the job log from the failed backup.

Thanks

Stephen Keating 

Operating Systems:

Comments 10 CommentsJump to latest comment

CraigV's picture

Hi,

Check the Exchange settings under Tools --> Options --> Microsoft Exchange and make sure the option to dismount the IS isn't selected.

if you're using the Exchange agent, this would allow you to backup the IS while live and mounted.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Stephen Keating's picture

thanks for the reply. I have looked where you indicated, but do not see an option to dismount the store. Is there somewhere else to look in 12.5? See attached.

Backup1.JPG
CraigV's picture

...my bad. This is only for restores. However, using the agent to backup the IS should not dismount the Information Store, so this information still stands.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

CraigV's picture

Stephen: Checked the error log you attached and you have 2 errors:

B2D out of disk space:

http://www.symantec.com/business/support/index?pag...

Error accessing Exchange:

http://www.symantec.com/business/support/index?pag...

Check those and try resolving them.

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

CraigV's picture

...and there is 1 more error to check out:

http://www.symantec.com/business/support/index?pag...

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Stephen Keating's picture

CraigV

thanks for the replies.

I have checked the backup-to-disk space and theres no problem there as it is a TB of free space. Not sure why it needs more. I think the unable to access message came after the dismount of the store. And I did not get any ESE errors, except that the backup stopped prematurely (Error 226) .

Stephen Keating's picture

Also, there is no Microsoft Site Replication Service to choose in my Backup Job properties.

CraigV's picture

...best bet now is to log a call with Symantec and get them to check this out as it shouldn't be happening.

Post back with an update.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Colin Weaver's picture

If it is caused by a maximum of 1008 transaction logs, then Backup Exec won't be the direct cause. (BE does nto cresate transaction logs Exchaneg does that)

Although failing to run a regular backup which allows the logs to build up without truncation might be,.

As such do not let your Exchange backups fail too many days in a row and make sure they are run regularly and are truncating the logs.

mustansir's picture

As per your post u have mentioned tat u back up mail stores to different disk..its exchange 2003 as per your post...could u please tell us if you are backing up storage groups or individual mailbox stores separately....
Backing up entire storage group should get the logs flushed and this issue should not be reoccured....
Please mark this as solution if this resolves your issue....