Exchange DAG seeding copy

[anything I don't mind]

I am trying to seed an exchange DAG database copy and it keeps failing. I have come across an article that says if the source DB has had a backup already done to it, then the only way to seed a copy is to put the database in a circular logging before you start the seed process. Then run with the "deleteexistingfiles" switch when running update-mailboxdatabasecopy.

Anyone have a method that always works that doesn't require me to put it in to circular logging?

This is the article, http://blogs.technet.com/b/timmcmic...status-failed-after-seeding-is-completed.aspx

 

[Ploppy2k3]

If a database refuses to copy over 9/10 times it is because its missing a log file. The easiest way to get around this is to create a new database and then move the users in to that. turn circular logging on for both databases during he move and then off again fro the new database prior to adding it to the DAG

Obviously you do not have to put the databases in to circular login but it will save disk space during the operation.