Skip to main content

Posts

Showing posts with the label Log Shipping

Frequently Raised Errors in Log-Shipping

1. Question : IS it possible to log ship database between SQL 2000 & SQL 2008?  Answer: No, thats impossible, In SQL 2008 transaction log architecture is changed compared to SQL 2000 and hence you won’t be able to restore tlog backups from SQL 2000 to SQL 2008 or vice versa. 2. Question:I’m getting the below error message in restoration job on secondary server, WHY? [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4305: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set begins at LSN 7000000026200001, which is too late to apply to the database. An earlier log backup that includes LSN 6000000015100001 can be restored. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally. Answer: Was your sql server or agent restarted Y’day in either source or destination ? because the error states there is a mismatch in LSN. A particular tran log was not applied in the destination server he...

Pre - Requisites of Log Shipping

The following are the prerequisites to configure Log Shipping SQL 2008 1. SQL Server 2008 Enterprise Edition, SQL Server 2008 Workgroup Edition, or SQL Server 2008 Standard Edition must be installed on all server instances involved in log shipping. 2. The servers involved in log shipping should have the same case sensitivity settings. 3. Enable Remote connections to the server in SQL Server surface are configuration, by navigating to start menu--->All Program--->Microsoft SQL 2008--->Configuration tools--->Surface Area Configuration tool--->Select Surface Area configuration for Services and Connections option--->Select Remote Connections--->Select Local and Remote connections by using TCP and Named Pipes option or else you can also use local and remote connections using TCP\IP only and click OK. 4. The SQL Services in both the primary and secondary server should be the same with same password. Pr...

Log Shipping

What is Log Shipping Log Shipping is one of the methods for creating a Standby server, by god forbiddeen if something happens to our production server we need a standby server and Microsoft has come up with this idea and introduced Log Shipping in SQL 2000 itself. But in SQL 2005 it has been enhanced further by making it more user friendly. It is mainly used in OLTP environment (Online Transaction Processing). It is used as a High Availability Solution and also in Disaster recovery situations. Overview of Log Shipping Let’s discuss the overview of log shipping. The basic idea is nothing but backup and restore of the database and transaction logs sequentially from the primary server to secondary or standby server. We might be having some extremely critical databases in our production environment and need them to be online 24*7.If the production server is down due to some natural disasters or in some cases we need to reboot the server after apply...