Exchange DAG Seeding

[anything I don't mind]

I have been having a lot of problems seeding a 200gb database to our DR exchange server. Ive spent the last few weeks trying to seed db1 and ive got it too seed ok, well it goes through the process and data is transferred for 5 hours across the link. Only for it to say failed and suspended and require a reseeded.

The other database db2 seeded first time without any problems.

I've looked in to it a lot and i can't find any reason why its failed. It just fails on a specific item. I've tried changing the dag configuration and all types of network changes, but after db2 worked first time i don't think its misconfigured any more, i just think its a log of item issue on that db.

Im out of options and the only option i have left is from what i have read, dismount the database, move/rename the log folder. Then copy the edb file to the DR and mount the database at production side.

But this will require down time.

Anyone know if there is anything else i can try?

 

[anything I don't mind]

I don't think there is any configuration or network problems because the dc2 seeded first time without any problems.

I've deleted the passive db and log filse completely a number of times for db1 and attempted the reseed from a blank a number of times with the same result. It spend 5 hours replicating all the data and then ends with failed and suspended status with error message that it failed processing a specific item and requires the entire db to be reseeded.

from what i have read the only option i have is to dismount the active db, move the log files to a new location and then copy the edb file through the network and then mount the active copy and it will generate new log files and should show a healthy status.

the question is though wouldn't generating new log filse break the up? I could do it on a saturday morning after the backup from friday has gone through and there will be minimal log files.

Other question i have is around doing a public folder replica

Ive created a new pf db at the 2nd exchange server. Then i used the script command:

.\AddReplicaToPFRecursive.ps1 -TopPublicFolder "\" -ServerToAdd "2ndexchangeserver"

But i am yet to see any public folders replicate. Its only been 30mins but would have expected to see some by now. Hopefully i did it right because it seems realy poorly designed.

 

[anything I don't mind]

Does anyone have any insight on the idea of dismounting the database and then renaming the logs folder. What exactly would the implication be for this action, with regards to backup and database integrity. I have seen some advice online that this needs to be done in order to create a database copy when it fails with item processing.

Sorry to repost its just still outstanding problem.