Recovery of a renamed exchange database with eseutil

Hi

I have noticed that for an Exchange .edb and log files, if I rename the .edb filefirst and then run the following command -

eseutil /r E00 /i /d"<Path>" /l"<Path>"

The command succeeds but the database stays in dirty shutdown state.

Should the .edb file have the same name as before i.e. same as the database name? Is this a recent behavior change in Exchange 2010 and 2013?

A related question to this is about a redirected restore to an exchange database target, consider the following steps in an Exchange VSS recovery-

1. Unmount target database.
2. Copy .edb files and some log files(to _restoredLogs folder)
3. Call SetRestoreOptions with proper XML of the original and target exchange db GUIDs.
4. Call AddNewTarget with proper target folders
5. Call SetAdditionalRestores to true to indicate more restores will take place
6. Let the restore take place and mount the data base
7. Unmount target database.
8. Copy additional log files
9. Call SetRestoreOptions with proper XML of the original and target exchange db GUIDs.
10. Call AddNewTarget with proper target folders
11. Call SetAdditionalRestores to true to indicate more restores will take place.
12. Let the restore take place and mount the data base

Recovery does not happen in step 12. To me it seems that SetRestoreOptions in step 3 renames the database edb file in the first recovery, this causes the delayed recovery (because SetAdditionalRestores has be set to true in step 5) to fail and causes the database to remain in a dirty shutdown state, causing the mount to fail in step 12. Can an some one clarify if the usage of SetRestoreOptions and the sequence of steps are correct here?

Thanks

- NYA