Error log is :

Backup detected log corruption in database Wss_Content. Context is Bad Middle Sector. LogFile: 2 'D:\Data\xxxx_log.ldf' VLF SeqNo: x280d VLFBase: x10df10000 LogBlockOffset: x10efa1000 SectorStatus: 2 LogBlock.StartLsn.SeqNo: x280d LogBlock.StartLsn.Blk:...

Yes its a production server and already executed DBCC CHECKDB command but there was no error found.

64bit OS and max work thread is set to default '0'

Thanks.

history retention is 3 days only, everything is working fine before domain migration.

Why becuase our primary and seconday servers is running under the same domain account but monitor server...

Thanks.

Hi,

Will it log shipping work without interrupt the below points did?

SQL server's service account changed to new domain account and log shipping shared folder permission is re-added to users.

Thanks.

I got alert once monitor server is down.

The log shipping secondary database XXXX\XXXX.<Database Name> has restore threshold of 45 minutes and is out of sync. No restore was performed for...

Yes, in both servers all databases getting alert in log shipping status report

No, its get down all the log shippings once monitor server is down.

I shrink the MSDB data file but size is not reducing but i can able to shrink log file size also reduce.

Thanks.

Yes, now i can able to restore via GUI...Many thanks.

but MSDB database size still 50GB how can i reduce the size after cleanup backup history table.

So what is the impact...

Shrink msdb data file or log file?

why because i already shrink log files, meanwhile log shipping is configured on this server.

So if i shrink the data file (If i...

After creating index i can successfully deleted old history records from backup tables but MSDB database size is remains same.

I almost delete 50 Lakh records from in below respective tables...