Log shipping: Difference between revisions
No edit summary |
m Added retrieval date to references. |
||
| Line 2: | Line 2: | ||
{{Uncategorized|date=December 2008}} |
{{Uncategorized|date=December 2008}} |
||
'''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"</ref>. Similar to [[Replication_(computer_science)|replication]] <ref name="replication">[http://www.sqlservercentral.com/articles/Replication/logshippingvsreplication/1399/ Log Shipping vs. Replication]</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. |
'''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. Compared to using SQL server clusters, which 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. |
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. Compared to using SQL server clusters, which 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. |
||
Revision as of 08:05, 16 December 2008
 | Template:Wikify is deprecated. Please use a more specific cleanup template as listed in the documentation. |
 | This article has not been added to any content categories. Please help out by adding categories to it so that it can be listed with similar articles, in addition to a stub category. (December 2008) |
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[1]. Similar to replication [2], 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 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. Compared to using SQL server clusters, which 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.[2] A replicated server, on the other hand, can be modified (e.g. views) and therefore not suitable for failover purposes.
References
- ^ How to Perform SQL Server Log Shipping, "What is Log Shipping". Retrieved on 2008-12-16.
- ^ a b Log Shipping vs. Replication Retrieved on 2008-12-16.
 | This software article is a stub. You can help Wikipedia by expanding it. |