robertdana Posted September 15, 2008 Report Share Posted September 15, 2008 We upgraded to 7.6 recently, and have been having a combination of strange problems with our proactive exchange server backup script. First, there's a recently deleted mailbox that started throwing a "Scanning incomplete, error -3407". It also says: Reported by function kMsg_DirScan Mailbox provider error. There is a problem connecting to the mailbox. Check: 1. Microsoft Exchange may not be running. 2. The mailbox may not exist. If the mailbox has been deleted, this is normal. 3. The mailbox store for this mailbox may not be mounted. Check its status in the Exchange manager. No problem, no big deal. Except that this error caused the proactive backup script to attempt to backup the mailboxes multiple times each night. Reading elsewhere in the forums, it looks like I can probably correct this by relicensing the exchange server, and I will do so. However, the error should be a softer one that doesn't cause proactive backups to consider the backup failed. This pushed our backups to exceed the normal backup window, and caused another problem. The backup of the hard drives on the server has several separate volumes, but I have not listed them individually in the proactive backup script (I just put the entire server in the script). The backup script finished the first hard drive (C:) but then stopped between volumes because the wrap-up time had been reached. The next night, despite the fact that these volumes had not been backed up, they were again scheduled for the end of the backup window, as if the backup had been completely successful. Without intervention, those volumes would not be backed up. I will work around this by listing the volumes separately, but this is not what I expect from proactive backup... it's supposed to be "smart" about this kind if thing, and if a volume has not been backed up recently, prioritize it higher on the list... Quote Link to comment Share on other sites More sharing options...
Mayoff Posted September 15, 2008 Report Share Posted September 15, 2008 You can change the script options to increase the retry after failure time period. That might help safe you time. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.