In the Log Offloading Configuration with SQL2005, the Primary Server Backup Job is not added
I am creating a log shipping configuration between two sql server 2005 instances. I am shipping logs to the same database and I am not using the monitoring service yet. When I run the SQL Server Log Shipping Wizard on the database, the script runs as it should and asserts that there are no errors. But when it is finished, the secondary server will have the correct job list (copy / restore), but the primary server, I think, should have a "backup" job. This is not true.
So it either fails or I am misunderstanding how the shipping works. Does anyone know a) if there should be a job added to the main server, and b) if it is supposed to be a job, what are some of the likely reasons for not adding it?
Thank.
source to share
It turns out that the silent crash was caused by the fact that the secondary server was actually a virtual machine that was a clone of the primary server. Even though I changed the computer name and sql server name. I am guessing there is something else that identifies the instance that has not been modified and that caused the crash. This is only a guess, however.
source to share