Announcement

Collapse
No announcement yet.

Log Shipping

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Log Shipping

    Dear Team,

    I would be glad to know more about Log Shipping and is this something you guys can help me with.

    Thanks & Regards

  • #2
    Re: Log Shipping

    Originally posted by Maldwyn View Post
    Dear Team,

    I would be glad to know more about Log Shipping and is this something you guys can help me with.

    Thanks & Regards
    Hi!

    MSSQL Server Log shipping method provides a disaster-recovery real-time-data-replication-mirroring solution between a primary & secondary site, each on a separate instance of MSSQL Server, supporting limited read-only access to secondary databases (during the interval between restore jobs). This method allows you to automatically send transaction log backups from a primary database on a production server instance to one or more secondary/backup databases on separate secondary/remote server instances. The transaction log backups are applied to each of the secondary databases individually.

    So it goes like this:

    1) Back up the transaction log at the primary server instance.
    2) Copy the transaction log file to the secondary server instance.
    3) Restore the log backup on the secondary server instance.

    An optional third server instance, known as the monitor/witness server, records the history & status of backup & restore operations, optionally, raises alerts if these operations fail to occur as scheduled.
    Rock _a.k.a._ Jack Daniel

    Follow eUKhost on Twitter || Join eUKhost Community on Facebook

    Comment


    • #3
      Re: Log Shipping

      Thank you for the reply Rock

      So it would need at least 2 or 3 servers to get this solution working. And what should be the resources for the server for such setup?

      Thanks & Regards

      Comment


      • #4
        Re: Log Shipping

        Originally posted by Maldwyn View Post
        Thank you for the reply Rock

        So it would need at least 2 or 3 servers to get this solution working. And what should be the resources for the server for such setup?

        Thanks & Regards
        You are welcome

        It'd be 2 dedicated/VM servers & the 3rd one is optional (a very small one, VM can do too). The hardware configuration purely depends on the MSSQL server's consumption, ie: the DB size, number of connections, size of data being modified, etc. eg: 4GB+ RAM is one basic requirement for any MSSQL setup
        Rock _a.k.a._ Jack Daniel

        Follow eUKhost on Twitter || Join eUKhost Community on Facebook

        Comment


        • #5
          Re: Log Shipping

          Thanks for the information Rock and sorry for the delayed reply.

          We are still in development phase and may take few more weeks to finish. The solution suggested looks promising and we would sure consider it once we are ready to go ahead.

          Thanks once again (y)

          Comment


          • #6
            Re: Log Shipping

            Originally posted by Maldwyn View Post
            Thanks for the information Rock and sorry for the delayed reply.

            We are still in development phase and may take few more weeks to finish. The solution suggested looks promising and we would sure consider it once we are ready to go ahead.

            Thanks once again (y)
            You're welcome!
            Rock _a.k.a._ Jack Daniel

            Follow eUKhost on Twitter || Join eUKhost Community on Facebook

            Comment


            • #7
              Re: Log Shipping

              Real good info ..

              Comment

              Working...
              X