Windows server backup, reboot the server during consistency check

Hi,

I have a bizarre  problem and I was wondering if anyone could help me.

I recently moved my active mailboxes to the new Windows 2008 R2 located in Amazon cloud.  Originally the databases were located on Windows 2008 R2 in the office.  I was backing up the server using windows server backup without any issues.  But since I moved the databases to the new server EVERYTIME the server does windows consistency check during the backup suddenly the servers reboots.

On the same server if I make the server the passive database server it backs up fine, it only does this when the server has active databases and it only does this on the servers that are located on EC2 Amazon cloud.  

I have no idea where to start, I do not know this is a Windows issue or not if someone has any idea I really appreciate all the support here.

FYI- I checked all the contentIndexstate and they all 'Healthy'.

Thanks
FundFireAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sumit GuptaSystem and Virtualization EngineerCommented:
First, stop the active backup. Then, simply go to the properties of each database, and enable Circular Logging. With Exchange 2010, you do not need to dismount the mailbox store and then mount it again for this to take effect. It should take less than an hour, but ultimately you will see the log files evaporate into the ether. Once that happens, you can disable circular logging and then run your backup again. This time, you should see it pass by the “Running consistency check for application Exchange” step much more quickly.

If that doesn’t resolve it, you might have a problem with the VSS writers. If you run the following command from an elevated command prompt you can check that all of them are in “Stable” state.

vssadmin list writers

Open in new window


If it looks like you have a problem, you can increase your logging level by using the following command in the Exchange Management Shell.

Set-EventLogLevel "MSExchangeIS\9002 System\Exchange Writer" -Level Expert

Open in new window


For good measure, I would also suggest restarting the Microsoft Exchange Server Extension for Windows Server Backup service.

The enhanced logging should point you in the right direction if there are deeper issues. If you do have deeper issues, I would suggest a full server reboot first. before taking any further troubleshooting steps. If you have a chronic issue that keeps coming back though, I would highly recommend troubleshooting it to resolution rather than just rebooting every time.

When finished, don’t forget to return it to the default logging level:

Set-EventLogLevel "MSExchangeIS\9002 System\Exchange Writer" -Level Lowest

Open in new window

0
FundFireAuthor Commented:
What disadvantages I have to have circular logging on?
0
nashim khanExchange AdministratorCommented:
Hi,

When enabled, you can only perform full backups of the Exchange database. You cannot perform incremental or differential backups.

FYI see the below article.

http://searchexchange.techtarget.com/tip/Clearing-the-confusion-around-Exchange-Server-circular-logging
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

FundFireAuthor Commented:
HI,

I followed the instructions and I got the same results.  I enabled the circular logging.  Tried again.    Actually the servers goes to blue screen of death during consistency check.  This happens on 2 servers on EC2 cloud.  Again this happens only when the server is active database on passive the server backs up.  Really strange.
0
FundFireAuthor Commented:
I am waiting for Amazon to respond.
0
FundFireAuthor Commented:
This issue has been duplicated by Amazon and it is a bug.
0
FundFireAuthor Commented:
I am closing this ticket.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
FundFireAuthor Commented:
This is bug.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.