HI

even i have faced this complicated issues after dc dr drill

[switch over and switch back ] secondary database is corrupted and gone on into suspect mode uanble to recover

steps i followed

1. primary database size is 100gb nearly so it is difficult to copy and restore [or ] by using file transfer from unix box etc... the backup file from primary to secondary it will take so much of time and users might effected the downtime of business

2. created a device backup in primary server and divided the backup file in to 10 parts of 10Gb [total 100gb and more ]

3.created a maintenance plan job for present and future use also and executed the device backup maintenance plan.. after completing your backup disable the JOB

3. collect all divided backup files and try to copy one by one from primary to secondary location which might not cause network break for transferring the file [if file size is large it might cause network link fail ]

4. delete old database and restore the backup files in the secondary with stand-by/read-only mode and try to synchronize the logshipping database