I am testing out eseutil /p in my Exchange 2007 lab and had some further questions just in case I am ever forced to use this.
1. If I had a 100GB database, is there any way to work out how long the /p, the /d, and the isinteg fixes will take individually? Or does this all depend on the damage to the DB, the server resources etc?
2. When running both the /p and /d, is there anyway to find out how the progress is going or if it's hung?
3. If I'm running out of space on the drive for /p, I know I can use /t to specify the location of the temp database ESEutil uses,can this be used for both ESEUtil /p *and* ESEUtil /d? And is this the location of the TEMP database only, so nothing actually ends up there, the file in this location automatically is copied back?
4. If I don't have any spare space on the server at all, is it advisable to use /t for both /p and /d to point to a network share?