Database Experts:Log Shipping for SQL Server 2005 disaster recovery solution

    SQL Server 2005 Log Shipping For Disaster Recovery. 


Read this for more information about database log shipping for disaster recovery.

 http://msdn.microsoft.com/en-us/library/ms187103%28v=sql.90%29.aspx

 There are three SQL Server instance for Log shipping operation.

 1.Primary Server-Source database which logs transfer to multiple secondary server.

 2.Secondary Server.Destination server for log shipping where logs apply for recovery.

 3.Monitor Server :Monitor Log shipping on this server.

 **Note:There is one shared drive where transaction logs backup moved to secondary server.

 Follow this steps for configuring log shipping.
1.Create Shared Drive.

 This share drive can be accessible by both servers.

 2.Create Shared folder to copy transaction logs on secondary server.

 Give Full Permission to SQL Server Service Account.

Here this folder is Shared in Secondary Server.


3.Go to Primary Server for Log Shipping Configuration.

 Right Click on Database which need to start log shipping.

 Go to Task-->Ship Transaction Logs.





Click on Enable this as a primary... to activate log shipping...

Configure Backup Settings in primary server SQL Server Instance.

 Set Shared Drive Path.



Schedule backup.




Configure Secondary Database.Click on Add and connect to Secondary Server SQL Server Instance.







Select Path of Secondary Server Data files.


Select Copy folder Path that shown in steps -2.

Schedule time for copy folder.

Choose Restore Transaction Logs Schedule.

 Choose Standby Mode as it useful in Reporting and Read only mode to Query on Database.

 It is Much more important to disconnect when recovery on Database.








Schedule time for Restore Job.




4.Configure Monitor Server Instance.

Click on Use a monitor server instance.

 Connect to SQL Server Instance,.


Click to Script to Configuration to Script all this steps.

 Click Ok to Start Log Shipping.


Check Success status.




Check Secondary Server Database in Standby Mode.





5.Jobs in Secondary Server for Copy and Restore Operation.

View History for Successful run of Job.

 Check Job Activity Monitor.

 Check Shared folder and Local folder for Transaction logs backup copy.

 6.Check Standard report for Log Transaction status.

  


Comments

Post a Comment

Dear User,

Thank you very much for your kind response

Popular posts from this blog

Agent Installation on Windows Server. SQL Server (Failover Cluster) target addition in OEM 12c

Image
Agent Installation on Windows Server. SQL Server (Failover Cluster) target addition in OEM 12c This document is prepared for monitoring windows server where sql server installed.Mostly used OEM for monitoring databases. In this document we will cover agent installation with target addition into OEM 12c. We will also cover prerequisite like enabling port for communication from agent to oms server Agent Installation on windows server  As a part of installation, we require to fulfil prerequisite like connectivity between OEM server and Window server. For Port opening and communication between two servers Ports required to open : 4903 , 7799 , 3872 Following steps require doing for manually installation of Agent in Windows server. Verifying if the agent exists on OMS. To begin, open your Cloud Control and go to "Setup -> Extensibility -> Self Update". Open the "Agent Software" folder and check if the Agent Software of Windows x64 is with statu
Read more

Oracle 10g/11g Linux:SMS the alert logs ORA- errors generated in timestamp

Image
SMS Alert logs ORA- errors This is something new in database administration part.Suppose DBA was out of office and got call from company manager to come to office.There is some problem in database.Generally DBA connect database and check connection possible or not then check any alert log entry.It is better if DBA and their company people got messages whenever any ORA- errors came in certain period of time. For this,I found some solution to read alert log and send sms to respective people. It is mandatory if we put database in archive log and where frequent archives generated.This is require because of the timestamp of archives used to get the start and end time of alertlogs entry. This is all done through SHELL script and on linux machine. Here it is the magical script can help to get the info of SMS by mail ans SMS. This shell designed to read alerts of last 30 minutes. #!/bin/bash #Go to bdump location cd /oracle1/oradata/pindb/bdump/ #SMS d
Read more

Oracle 11g: Install Instant Client 11.2.0.3.0 on Linux x86_64 Server.

Oracle 11g: Install Instant Client 11.2.0.3.0 on Linux x86_64 Server. ***What is Instant Client &benefits? As per Oracle docs, Oracle Database Instant Client Instant Client allows you to run your applications without installing the standard Oracle client or having an ORACLE_HOME. OCI, OCCI, Pro*C, ODBC, and JDBC applications work without modification, while using significantly less disk space than before. Even SQL*Plus can be used with Instant Client. No recompile, no hassle. ISVs and Partners   benefit greatly from packaging Instant Client along with their applications, saving customers the extra step of installing and configuring an Oracle client. Free. The same fully-featured, high-performance applications that Oracle ISVs and partners have always delivered will continue to work, untouched. Customers can try new packaged applications and Oracle client features quickly without worrying about other installations. Larger enterprises can au
Read more