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

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 378
  • Last Modified:

Exchange 2003 Storage Group wont mount after reboot

Hi there

We have a Storage group that wont mount, throwing out ESE events 494 and 454.

The following has been checked:

eseutil /mh on on DBs in that store......all are in clean shut down and no logs are required

eseutil /ml e00 on the log for that SG..... all logs intact no errors

the edb and stm files seem intact and are in the correct locations

what next? we have been having issues with he backups on this SG, as a result there is a large number of log files. could this be the problem?

Help!
0
jafar54
Asked:
jafar54
  • 4
1 Solution
 
jafar54Author Commented:
is it as simple as moving out the transaction logs as detailed here..... http://www.zerohoursleep.com/2009/09/give-me-2-minutes-and-ill-save-you-hours-of-exchange-troubleshooting/ ??
0
 
Alexander KireevIT ArchitectCommented:
Hello,

Do you have enough free disk space on Drive with transaction logs? If so, a lot of logs files is not problem.

All Exchange services works?

Could you send the full error event text?

If your database not large, you can copy to temp folder and try to repair main database with "eseutil /p D:\Database\DB01.edb".
After repair you must defrag the database with "eseutl /d D:\Database\DB01.edb".

Repair: http://technet.microsoft.com/en-gb/library/aa997152%28v=exchg.80%29.aspx
Defrag: http://technet.microsoft.com/en-gb/library/aa997972%28v=exchg.80%29.aspx
0
 
gkousikanCommented:
It seems database path is missing.  Please refer this article and also check any Hard Disk bad sector issue.

http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.6940.0&EvtID=494&EvtSrc=ESE
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
jafar54Author Commented:
So this was resolved by the following:

- stop info store
- copy out all non .edb and .stm files to TEMP folder
- copy out all logs for the SG to Temp folder
- restart info store service
- mount DB
0
 
jafar54Author Commented:
Does anyone know if there is a limit as to the number of log files once can gather when using circular logging. ie if your backup doesn't run and truncate those logs, could this eventually cause such a problem?
0
 
jafar54Author Commented:
the fix
0

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now