May 8, 2007 at 5:24 am
I have configured log-shipping in sql2005. I am facing problem when full
database is taken in primary database, restoration of logs takes a long time
and gives out of syn error in secondary database.
Please let me know how I can rectify this problem.
May 8, 2007 at 8:03 am
You need to clarify what you mean. Your posts doesn't quite make sense. Do you mean a full database backup of the primary restored to the secondary?
If the timeouts are occurring on the restore, can you give us the exact error?
May 9, 2007 at 11:02 pm
I have a production database in SQL 2005 in which both full database backup and logshipping is configured.Full database backup is scheduled to run everyday at 10 p.m. Transactional log backup is generated,copied and restored in standby server database(schedule for backup/copy/restore is 10 mins).During full database backup in the production server,transactional logs are generated and copied to standby server,but restoration of logs gives out of syn error(Event ID 14421).
My concern is why logs are not restored in the standby database.Is there any configuration changes need to be done.
Now i have configured logshipping in such a way that transactional logs are not generated during full database backup(ie:for nearly an hour no logs are generated).This setup run perfectly.
I want to know why transactional logs generated during database backup is not restored.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply