SQL Server Performance

Logshipping question

Discussion in 'SQL Server 2005 Log Shipping' started by california6, May 11, 2007.

  1. california6 New Member

    I am about to setup logshipping and here's what i am going to do. I would like you folks to take a look at my steps and tell me, if i am doing something different:

    Steps:

    1) On primary server, create a shared folder. Eg: c:log
    2) Backup the database on primary server. (The database is running under fullrecovery)
    3) Go to secondary server and create a shared folder too. Eg: c:log
    4) Restore the database on secondary server with standby option.
    5) Configure the database on primary server for logshipping with 15 minutes of
    logshipping frequency.
    6) Do some DML on primary and this should be applied to secondary on the next log backup.

    Is there anything missing here? Appreciated if you guys please let me know.

    Many thanks,
    Cali
  2. techbabu303 New Member

  3. california6 New Member

    Thanks for confirmation. The provided link is much better and talks in greater detail.

    Thanks,
  4. MohammedU New Member

  5. california6 New Member

    Thank you MohammedU for the links. they are very helpful.
  6. satya Moderator

    Are you looking to implement Log shipping in 2000 or 2005?

    Satya SKJ
    Microsoft SQL Server MVP
    Writer, Contributing Editor & Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
  7. Deepak Rangarajan New Member

    Hi,<br /> I think there is a small change in what you said <img src='/community/emoticons/emotion-1.gif' alt=':)' /><br /><br />1) On primary server, create a shared folder. Eg: c:log<br />2) Backup the database on primary server to shared folder. (The database is running under fullrecovery)<br />3)Ensure that SQL SERVICE ACCOUNT of the secondary server has modify privileges on the shared folder of primary server,as copy job will run from secondary server accessing the shared folder in primary server <br /><br />4) Go to secondary server and create a shared folder too. Eg: c:log ----&gt; IS NOT REQUIRED<br /><br />5) Restore the database on secondary server with standby option.<br />6) Configure the database on primary server for logshipping with 15 minutes of <br />logshipping frequency.<br />7) Do some DML on primary and this should be applied to secondary on the next log backup.<br /><br />NOTE:<br />****<br /> A shared folder should be created in primary server.No need to create a share folder in secondary server<br />Pls correct me if i am wrong<br /><br /><br /><br />Regards<br />Deepak<br />SQL DBA

Share This Page