Hey guys
I came back from holiday... and during my whole holiday the logshipping went cracy (didnt run for 3 weeks now) ... the transactionlog is now 40GB large and we dont have that much diskspace left to write a 40GB transaction log to the disk... so i thought i could make a fresh fullbackup from the primary and then restore it in the DR system. I hoped that the logshipping would realize that the Systems are now both up to date... i started the transactionlog backup job, but it tried again to write the full 40gb trasnactionlog on the disk... i really hoped that sql server realized that all this transaction are allready done on the DR site... (becuase of the FULLBACKUP restore)... any idea what i could to to acitivate the logshipping again ? that it only "backups" the transaction which arent in DR site ? )(should be around 3 mb)
thanks a lot for your help
my DR DB is in "StandBy / readonly" mode