1) It is a Microsoft requirement and a VSS function that we must have the Exchange database set in "dirty shutdown". We cannot change that.
2) The scope of Replication Manager is to present and integrity check the Exchange database only. This is what we do successfully.
3) If you modify a mounted replica and perform a recovery on the database, you absolutely will affect the ability to restore. You will not be able to roll forward from the latest set of transaction logs on the host.
4) My recommendation to you is to either a) Make a copy of the replica and modify that or b) Do an Exchange Copy Replica job.
Vince, I'm in the same situation with my RM/SE 3.1. When ever I need to go back to my RM/SE backups I need to run ESEUTIL /R Exx /I /D to gte me .EDB file in a clean shutdown state. I've been using RM/SE for over 2 years I haven't had the need to restore from the previous nights backup.
JamesBEMC
257 Posts
0
June 29th, 2007 02:00
To clarify some things
1) It is a Microsoft requirement and a VSS function that we must have the Exchange database set in "dirty shutdown". We cannot change that.
2) The scope of Replication Manager is to present and integrity check the Exchange database only. This is what we do successfully.
3) If you modify a mounted replica and perform a recovery on the database, you absolutely will affect the ability to restore. You will not be able to roll forward from the latest set of transaction logs on the host.
4) My recommendation to you is to either
a) Make a copy of the replica and modify that
or
b) Do an Exchange Copy Replica job.
Hope it helps
James.
mkonstas
1 Message
0
December 6th, 2007 12:00
-Mike-