Deleteing temp .edb after Defrag fail as disk is full

[TomHD]

Hello All,

 

I have had the defrag fail on me twice today due to me not checking free space properly! Second time it was about 500mb from finishing

 

I believe the script copies the de-fragmented .edb to a temp location then overwrites the fragmented one? So this means I can delete the 2 failed temp .edb right? As I have 2 locked disks at the moment :/

 

Cheers, Tom

[Homer]

What version of Exchange? Are they being modified still? If not I'd guess safe to delete although I'd be bloody nervous doing it... stop the information store service before doing anything though. Hope you have a recent backup just in case!

 

Is the box virtual? Thinking if it was expand the disk and then re-defrag

Edited October 12, 2015 by Homer

[TomHD]

Got backups I've moved them to C:\ on my office desktop for now, can put them back if there are any issues. I did look to extend the volume but not enough unallocated to do the job either so again, I have the temp .edb on C:\ all good so far.

 

Takes so long doing it over the network though!

[john]

By default it will run the process in the directory you ran the powershell from if I recall when I last had to do this so worth checking that and you can put switches in to force it to use other locations etc...

[TomHD]

Thanks John, I'm aware of that and I think the switch to run the process in a different location is /t

 

To clarify, I have deleted the failed temp edbs with no ill affects