Help!! Has anyone ever come across this problem. I am running MS exchanger 5.5. My Priv.edb got corrupted and i had to restore it from a back. After restoring it, i did a little cleaning up like deleting old accounts. After that i ran the esutil defrag to clean up the DB. After that was completed i had 570 MB of free memory on my hard drive. I brought up exchange and it was working fine. Next i decide to create a back up at this point since everything is working fine. At the end of the backup there was only 48 MB of memory on my hard drive. Does anyone know what may have caused this? Because now i have to restor again and i don't want the same thing happening again.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Corrupt Database
- Thread starter r007mvi
- Start date
Wow, that's a lot of history, although we're missing some vital info. Let me ask you a few questions:
How did you diagnose the db corruption?
How much free space did you have on your db drive before you started restoring?
Are your transaction logs on a seperate drive?
Why did you feel the need to defrag the restored database? How much white space did it have before the defrag (event 1221)?
Are there any temp files left over from your offline defrag taking up lots of disk space?
Online backups should actually free up disk space, although only on the transaction logs volume - the size of the data on the db drive should be the same as before the backup (assuming you're backing up to tape and not to a file on the same disk!)
And finally, the big question: why do you have to restore again??
How did you diagnose the db corruption?
How much free space did you have on your db drive before you started restoring?
Are your transaction logs on a seperate drive?
Why did you feel the need to defrag the restored database? How much white space did it have before the defrag (event 1221)?
Are there any temp files left over from your offline defrag taking up lots of disk space?
Online backups should actually free up disk space, although only on the transaction logs volume - the size of the data on the db drive should be the same as before the backup (assuming you're backing up to tape and not to a file on the same disk!)
And finally, the big question: why do you have to restore again??
- Thread starter
- #3
1)I did not do anything to diagnose the db. Waht i did notice is that when i back up the Priv.edb it would say it backed up anywhere from 18-28 files on the last back up it jumped to 93 so i assumed there is a corruption problem with the db, I may be wrong.
2)There was only 48kb when i did the restor it went well.
3)My logs are on the e drive and the data on the f drive
4)I did not check event 2121 before defraging. I ran out of disk space so i had to defrag to free up some space
I now believe my hard drives may be failing. So i have an extra server with windows 2000 on it i want to see if i could move everything over to that new server. any advise on doing that?
2)There was only 48kb when i did the restor it went well.
3)My logs are on the e drive and the data on the f drive
4)I did not check event 2121 before defraging. I ran out of disk space so i had to defrag to free up some space
I now believe my hard drives may be failing. So i have an extra server with windows 2000 on it i want to see if i could move everything over to that new server. any advise on doing that?
Lots of things still aren't making sense here. The Exchange database is just 2 files, priv.edb and pub.edb (mailboxes and public folder data respectively). I'm a bit confused about your statement regarding the number of files backed up.
Also, running out of space on the data drive is a big issue itself - you should have monitoring in place to stop this happening on a production exchange server, if this happens you are generally screwed and the information store service stops.
All an offline defrag does is remove the white space in a store, but it does so by creating another copy of the database and moving all the contents there first before removing the original copy of the db. You shouldn't be attempting an offline defarg unless you have 110% of the size of the db as free space, is Microsoft's recommendation. Also, you shouldn't be doing an offline defrag without knowing beforehand how much white sace the db had (the 1221 events). Lots of this info is already in the FAQs of this forum (have you read them??)
Finally, doing a 'hardware DR' (ie moving a production server to new server hardware) is a non-trivial task, not something you should be doing to a production server unless you are fully sure what you are doing. I'm not being funny, but if I perceive your level of Exchange experience correctly, I suggest you engage an external consultant to come in and do this for you.
Also, running out of space on the data drive is a big issue itself - you should have monitoring in place to stop this happening on a production exchange server, if this happens you are generally screwed and the information store service stops.
All an offline defrag does is remove the white space in a store, but it does so by creating another copy of the database and moving all the contents there first before removing the original copy of the db. You shouldn't be attempting an offline defarg unless you have 110% of the size of the db as free space, is Microsoft's recommendation. Also, you shouldn't be doing an offline defrag without knowing beforehand how much white sace the db had (the 1221 events). Lots of this info is already in the FAQs of this forum (have you read them??)
Finally, doing a 'hardware DR' (ie moving a production server to new server hardware) is a non-trivial task, not something you should be doing to a production server unless you are fully sure what you are doing. I'm not being funny, but if I perceive your level of Exchange experience correctly, I suggest you engage an external consultant to come in and do this for you.
- Thread starter
- #5
Hi
Thanks for the advise. I am down in th U.S.V.I. and getting a consultant here may take a while, so sometime i have to do what i got to do. Any ways I was able to install exchange 5.5 sp4 on a windows 2000 server i had here and move over the mail boxes. Everything is working fine for now.
Thanks
Thanks for the advise. I am down in th U.S.V.I. and getting a consultant here may take a while, so sometime i have to do what i got to do. Any ways I was able to install exchange 5.5 sp4 on a windows 2000 server i had here and move over the mail boxes. Everything is working fine for now.
Thanks
- Status
Similar threads
- Locked
- Question
- Locked
- Question