Jump to content

Log shipping: Difference between revisions

Add links
From Wikipedia, the free encyclopedia
Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
m –{{Software-stub}}, +{{Software-type-stub}} using StubSorter
 
(40 intermediate revisions by 28 users not shown)
Line 1: Line 1:
'''Log shipping''' is the process of automating the backup of [[transaction log]] files on a primary (production) database server, and then restoring them onto a standby server. This technique is supported by [[Microsoft SQL Server]],<ref name="logshipping">[http://www.sql-server-performance.com/articles/clustering/log_shipping_70_p1.aspx How to Perform SQL Server Log Shipping] {{webarchive|url=https://web.archive.org/web/20090104025209/http://www.sql-server-performance.com/articles/clustering/log_shipping_70_p1.aspx |date=2009-01-04 }}, "What is Log Shipping". Retrieved on 2008-12-16.</ref> [[4th Dimension (software)|4D Server]],<ref>{{Cite web|url=http://doc.4d.com/4D-Server-Reference-14/Using-4D-Server/Setting-up-a-logical-mirror.300-1242118.en.html|title=Setting Up a Logical Mirror|publisher=4D Server v14 Documentation}}</ref> [[MySQL]],<ref>{{cite web|url=https://dev.mysql.com/doc/refman/5.7/en/replication-configuration.html|title=MySQL :: MySQL 5.7 Reference Manual :: 17.1 Configuring Replication|work=mysql.com}}</ref> and [[PostgreSQL]].<ref>{{Cite web|url=http://www.postgresql.org/docs/8.2/enwiki/static/warm-standby.html|title=Warm Standby Servers for High Availability|publisher=PostgreSQL 8.2.19 Documentation}}</ref><ref>{{Cite web|url=http://wiki.postgresql.org/wiki/Hot_Standby|title=Hot Standby|publisher=PostgreSQL Wiki|accessdate=2011-01-25}}</ref> Similar to [[Replication (computer science)|replication]], the primary purpose of log shipping is to increase database availability by maintaining a backup server that can replace a production server quickly. Other databases such as [[Adaptive Server Enterprise]] and [[Oracle Database]] support the technique but require the [[Database Administrator]] to write code or scripts to perform the work.
{{Wikify|date=December 2008}}


⚫
Although the actual [[failover]] mechanism in log shipping is manual, this implementation is often chosen due to its low cost in human and server resources, and ease of implementation. In comparison, SQL server [[computer cluster|cluster]]s enable automatic failover, but at the expense of much higher storage costs. Compared to database replication, log shipping does not provide as much in terms of reporting capabilities, but backs up system tables along with data tables, and locks the standby server from users' modifications.<ref>{{cite web|url=http://www.sqlservercentral.com/articles/Replication/logshippingvsreplication/1399/|title=Log Shipping vs Replication|work=SQLServerCentral.com|accessdate=2009-08-07|last=Ibison|first=Paul}}</ref> A replicated server can be modified (e.g. [[view (database)|view]]s) and is therefore unsuitable for failover purposes.
'''Log shipping''' is the process of automating the backup of database and transaction log files on a production SQL server, and then restoring them onto a standby server<ref name="logshipping">[http://www.sql-server-performance.com/articles/clustering/log_shipping_70_p1.aspx How to Perform SQL Server Log Shipping], "What is Log Shipping". Retrieved on 2008-12-16.</ref>. Similar to [[Replication_(computer_science)|replication]] <ref name="replication">[http://www.sqlservercentral.com/articles/Replication/logshippingvsreplication/1399/ Log Shipping vs. Replication] Retrieved on 2008-12-16.</ref>, the primary purpose of log shipping is to increase availability of the production server by maintaining a backup server that can be failed-over to quickly. This [[Failover|failover]] however is a manual process.

⚫
Although the actual failover mechanism in log shipping is manual, businesses often choose this implementation due to its low cost in human and server resources, and ease of implementation. As comparison, using SQL server clusters enables automatic failover but is expensive to implement due to server and license costs. Compared to replication, log shipping does not provide as much reporting capabilities but is much more suitable for failover due to the fact that log shipping also backs up system tables, and the standby server is locked from editing by users in general.<ref name="replication" /> A replicated server, on the other hand, can be modified (e.g. views) and therefore not suitable for failover purposes.


==References==
==References==
{{reflist|30em}}
<references/>

==External links==
⚫
* [http://msdn.microsoft.com/en-us/library/ms190016(SQL.90).aspx Log Shipping], MS SQL Server implementation
* [http://wiki.postgresql.org/wiki/Hot_Standby Hot Standby], PostgreSQL implementation

{{Database}}


{{DEFAULTSORT:Log Shipping}}
[http://www.example.com link title]==External Links==
⚫
[[Category:Databases]]
⚫
* [http://msdn.microsoft.com/en-us/library/ms190016(SQL.90).aspx Log Shipping], MS SQL Server implementation.
[[Category:Data synchronization]]
[[Category:Fault-tolerant computer systems]]


[http://surat-user-group.org/LinkClick.aspx?link=68&tabid=58&mid=409] What is Log Shipping
⚫
{{software-stub}}


⚫
{{Software-type-stub}}
⚫
[[Category:SQL]]

Latest revision as of 12:12, 27 December 2023

Log shipping is the process of automating the backup of transaction log files on a primary (production) database server, and then restoring them onto a standby server. This technique is supported by Microsoft SQL Server,[1] 4D Server,[2] MySQL,[3] and PostgreSQL.[4][5] Similar to replication, the primary purpose of log shipping is to increase database availability by maintaining a backup server that can replace a production server quickly. Other databases such as Adaptive Server Enterprise and Oracle Database support the technique but require the Database Administrator to write code or scripts to perform the work.

Although the actual failover mechanism in log shipping is manual, this implementation is often chosen due to its low cost in human and server resources, and ease of implementation. In comparison, SQL server clusters enable automatic failover, but at the expense of much higher storage costs. Compared to database replication, log shipping does not provide as much in terms of reporting capabilities, but backs up system tables along with data tables, and locks the standby server from users' modifications.[6] A replicated server can be modified (e.g. views) and is therefore unsuitable for failover purposes.

References

[edit]
  1. ^ How to Perform SQL Server Log Shipping Archived 2009-01-04 at the Wayback Machine, "What is Log Shipping". Retrieved on 2008-12-16.
  2. ^ "Setting Up a Logical Mirror". 4D Server v14 Documentation.
  3. ^ "MySQL :: MySQL 5.7 Reference Manual :: 17.1 Configuring Replication". mysql.com.
  4. ^ "Warm Standby Servers for High Availability". PostgreSQL 8.2.19 Documentation.
  5. ^ "Hot Standby". PostgreSQL Wiki. Retrieved 2011-01-25.
  6. ^ Ibison, Paul. "Log Shipping vs Replication". SQLServerCentral.com. Retrieved 2009-08-07.
[edit]


Stub icon

This article related to a type of software is a stub. You can help Wikipedia by expanding it.

Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=Log_shipping&oldid=1192066910"