SQL Server Performance

logshipping

Discussion in 'SQL Server 2005 Log Shipping' started by srikanthamk, Feb 18, 2010.

  1. srikanthamk New Member

    hi,
    when logshipping goes out of synch we need to disable the backup jobs that are running in the primary server why do we need to do this? if we do that the database may go into suspect mode? is it true?
    awating for reply
    Thanks and regards
    srikanth
  2. ghemant Moderator

    When database in log shipping on secondary server goes out of sync some people disable the job, the reason is, if it contiue backing up t-log the number of files to be restored manually will increase. But at the same time, it is necessary to have t-log backups else your t-log will grow much bigger, you have to be cautious when you are configuring the latency (consider network speed etc to copy t-log backup file on secondary server) .
    Databse would go suspect because of many reasons, and one of them is out of space. So, partially its true but thats not the only reason of database becoming suspect.
  3. dineshasanka Moderator

    it depends on the fequency of the backup job. if you are having backing up job for say for every 15 mins it is better disable it and enable another backup log for 1 hr so that you have your backup logs in place.
    if you have a log shipping backup for around 1 -2 hr time schedule, you better leaev it

Share This Page