Hi All,
We are using logshipping for DR plan. My secondary database is in out of sync due to missing of log backup files. So we deciseded to reconfigure the Logshipping. we disable the logshipping configuration on the primary database. But it did not removed the copy job and restore job.
So Manualy we tried to remove the restore job, but it took more 2 hours time to delete the job. In the same manner we tried to remove Copy job, again it was taking time. after 30 min we cancelled the deleting of copy to identify this abnormal behaviour. then rollback happend for 1 hour.
We have high end configuration i.e 125 GB physical memory., 750 GB disk space. database size is of 300 GB.
OS: window server 2008 R2
SQL server version: SQL server 2008 R2 with SP1
Below are our findings:
msdb size is high which is 51 GB. When we were restarting the instance, the msdb is taking more than 5 min time to recovery.
Please provide your suggestion/steps to check and overcome this abnormal behaviour of the msdb.
And also why deleting of a job is taking more time.
Thanks
K