I am following the instructions laid out in the MSDN articlehttp://msdn2.microsoft.com/en-us/library/ms190640.aspx
and am finding results that are confusing me. The primary server's database's log-shipping settings is set to copy the Transaction Log backups to a UNC share on the secondary server. The secondary server does not have an instance of the backup database yet, so I specify "Yes, generate a full backup of the primary database and restore it into...." in the Initialize Secondary Database tab.
Under the Copy Files tab, i make the secondary server additionally copy the original log file location (e.g. \\secondary\logship - d:\logship) to another extra location (e.g. d:\logship\restore).
When the processed is kicked start, it appears to report everything is successful. However the primary database properties show that "Enable this as a primary database in a log shipping configuration" is checked off. There is no SQL Server Agent job to back up its Transaction logs. Over at the secondary server, there are the three expected Copy, Restore, and Alert SQL Server Agent jobs. The resultant database is in a perpetual Restoring... state and nothing can be done to it.
I also noticed the Restore job ran before the Copy job when i checked the Job History of those jobs. I would have thought Copy should be done before attempting a Restore.
Can anybody explain what behaviour is being observed here? Thanks.
The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral