I have configured two 2003 servers, each with SQL Server 2005 and configured them for log shipping through the wizard. I was able to get the jobs loaded on the secondary server, but the jobs are not showing up under sql server agent jobs on the primary server, thus, the log shipping is not working. When I run the wizard the first time it does connect to the secondary server and it does save the configurations w/out error. Anything I should look for? Thanks for any help?
asked Feb 24 '10 at 06:32 PM in Default
Follow the steps below
1)Make sure that SQL server agents running in both the machines.
2)Create a folder(should be network shared) on primary server to hold the scheduled backups of primary database.
2)Create a backup job run on primary server which takes transaction log backup according to schedule.
3)Create a copy job,and executed on secondary server which copies the transaction log files from network shared folder(primary server folder) into secondary server folder(need to be create)
4)Create a restore job executed on secondary server which will apply the copied transaction log backup's to the secondary database.
you can have a monitor server to monitor the log shipping for better performence..
answered Mar 18 '10 at 04:04 PM
Firstly you check that the SQL server Agent is working fine and log in with the Account that you have login the machine
Then create a folder 3 folder that must be access from Both Secondry and primary server..
answered May 31 '10 at 05:44 AM
This may be too simple, but is the SQL Agent in the running state on the primary server?
The wizard will happily create the secondary database and the jobs on both servers, but they won't show up or execute unless the agent is running.
answered Feb 25 '10 at 12:00 AM