Category Archives: Hardware

Repairing exchange 2003 database

After a hardware crash, use the following to understand the state of the database and the log files; from the MDBDATA directory

cd “c:\program files\exchsrvr\mdbdata”

..\bin\eseutil /mh priv1.edb

..\bin\eseutil /ml E00.log

Then fix the problem

To Recover (play the transactions logs into the database)

..\bin\eseutil /R E00

To restore after recovering from an online backup

../bin/eseutil /CC “d:\temp\First Storage Group”

To Repair (if you don’t need to go back to a online backup, but the recover isn’t working)

..\bin\eseutil /p priv1.edb /spriv1.stm /ttemp.edb

then check the fix

../bin/eseutil /mh priv1.edb

defrag the databases
“C:\program files\exchsrvr\bin\eseutil” /d “c:\program files\exchsrvr\mdbdata\priv1.edb”
“C:\program files\exchsrvr\bin\eseutil” /d “c:\program files\exchsrvr\mdbdata\pub1.edb”

..\bin\isinteg -s eagle -fix -test alltests

Scheduling tasks for Synology NAS for Wake On Lan

In order to keep alive a server, that doesn’t come back on following a power cut, I have created a WOL task that is running on my Synology NAS. The first thing is that you need to define a script for running on the NAS, then configure the NAS to actually run this script.¬†For the script, in this case the WOL task is the key thing; but you also need to start the correct sh

ether-wake [mac address]

One of the key things is that it must be a unix file, and therefore if you edit under vi you should NOT see ^M at the end of the line

Next, is to schedule this, and this needs to include the full path for the NAS, in line with the unix path, eg, would need for example to include /volume1/  Finally, in the scheduler itself you need to call the script with a shell prefix in order to run it correct; see below


Setting everything up like this will result in your shell script running, and in my case, the server waking up if it doesn’t recover after a powercut