freaktechnique
IS-IT--Management
Hey all,
I have exchange 5.5 sp4 running on nt4 sp6a.
The setup is logs on c: and dbs d:. The problem is the dbs grew 500M in 3 days and I didn't notice. Now there is 5.4M free on d: and the MTA service stopped itself and won't restart. I can't run optimizer to move the dbs because it gets an error when polling the d drive.
I have tried deleting email but the db doesn't free up the drive space when the mail disappears.
My idea is to stop the other services and manually move the dir.edb to c: then with the freespace available I am hoping optimizer will start so I can then properly move the dir.edb to c:
What I am wondering is will optimizer run if it doesn't find the dir.edb where it expects it. If it does open can I move the dir.edb when it is not there. And is it possiable that I will completely destroy exchange by doing this.
Any input will be appreciated, I am screwed right now.
I have backups and can wax the server, reinstall exchange, setup the dbs properly and perform a complete restore but I figure that is a last resort.
I have exchange 5.5 sp4 running on nt4 sp6a.
The setup is logs on c: and dbs d:. The problem is the dbs grew 500M in 3 days and I didn't notice. Now there is 5.4M free on d: and the MTA service stopped itself and won't restart. I can't run optimizer to move the dbs because it gets an error when polling the d drive.
I have tried deleting email but the db doesn't free up the drive space when the mail disappears.
My idea is to stop the other services and manually move the dir.edb to c: then with the freespace available I am hoping optimizer will start so I can then properly move the dir.edb to c:
What I am wondering is will optimizer run if it doesn't find the dir.edb where it expects it. If it does open can I move the dir.edb when it is not there. And is it possiable that I will completely destroy exchange by doing this.
Any input will be appreciated, I am screwed right now.
I have backups and can wax the server, reinstall exchange, setup the dbs properly and perform a complete restore but I figure that is a last resort.