Sounds strange, but I haven't been able to do this. Can anyone help?
I'm doing disaster recovery testing, and in order to test procedures
for database repair (ESEUTIL, ISINTEG), I need to intentionally DAMAGE
an Exchange database.
Here's what I've done so far:
1. Delete all log files
2. Stop info store
3. Wrote the following batch file and let it run for 15 minutes:
echo awefawefwefwefwe4fwefwefwefwef >> priv1.edb
I thought for sure that this would cause damage, but it hasn't. I
can't damage this database! If anyone can give me some hints on how
to BREAK e2K, I'd appreciate it.
MCP, MCSE, CCNA