Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Exchange 2003 Database Maintenance

Posted on 2009-04-01
4
Medium Priority
?
354 Views
Last Modified: 2012-05-06
Currently we are running Exchange 2003 Enterprise Edition SP2.  We had a need to turn off maintenance on one of our Storage Group databases - it has been one year.  We are now being close to turning maintenance back on that database.  Aside from a normal backup, and turning this on during the weekend for less disruption, any experiences in regards to this type of scenario and possible repercussions?  The edb is 140GB and the stm is 69GB.  
0
Comment
Question by:everythingbutthemoo
  • 2
  • 2
4 Comments
 
LVL 65

Expert Comment

by:Mestha
ID: 24045457
You mean the online maintenance on the database hasn't run for a year?
Well it runs on a schedule overnight, but it is going to struggle to complete that on a store of that size. You have no idea how much white space is in the store or anything.

It could take a week or more for Exchange to finish processing the database - running during the schedule window. You could set a manual window if you wished, perhaps all weekend, and then backup the server shortly afterwards.

Do you have any spare databases? Could you move the mailboxes to another store and then drop that one? It might be a quicker way of getting things back in to alignment.

Simon.
0
 

Author Comment

by:everythingbutthemoo
ID: 24055107
Lots of mailboxes plus I want to still keep my specified number of days for deleted items, etc. - although moving to another database is an option. My plans are to backup server fully, manually start the database maintenance, then back it up again afterwards.  next phase will probably be an offline defrag of the database.  Thanks for your input.
0
 
LVL 65

Accepted Solution

by:
Mestha earned 500 total points
ID: 24055524
If you moved the data to another database then you wouldn't need to do anything that puts the data at risk - including offline defrag. It would deal with both problems at once and have the data in a fresh database. Remember offline defrag is not risk free, and if that database hasn't had the routine stuff done then it is probably in a state. A new database would be the best move forwards and puts the data at least risk.

Simon.
0
 

Author Comment

by:everythingbutthemoo
ID: 24059796
Simon - thanks for the reinforcement to minimize my risk.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

580 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question