Hi PJ,

I am still getting the errors.

A silly question... Do I need to reboot the server that has had the SMB Session Timeout fix applied to it for it...

pjmahoneyit (7/17/2011)

---

I use SQL log shipping for disaster recovery to a DB server in our DR subnet. I also use log shipping to have an hour old report server...

I have two production servers, prod a has the primary database, prod b has the secondary. The agent on prod a backups the logs from prod a to SAN A,...

If you can't understand the above errors from a log shipping process I don't think you can help solve my problem (Sorry) ...so back to the original question... is there...

I have investigated the errors quite thoroughly however I am not in a position to vouch for the 100% accuracy of the errors. Although here they are;

BackupIoRequest::ReportIoError: write failure on...

It is an awkward situation... every night I do a full backup of the database whilst the log shipping continues but every night the log shipping writes one bad trn...

I totally agree. 🙂

I totally agree with installing it again and comparing the db's from another machine.

Thanks

I have used all my grace trials... and it is on a production server.

I dont really want to install anymore 3rd party apps on it that will take up...

I did try to backup data to the local disk and try to allow for the secondary agent to pull data from the disk on the primary server but I...

All I can say is that it is in the errors.

If I hadn't opened up a command prompt and checked out the error messages it wouldn't have made me look...

Just use a dedicated network share on another server/SAN that both database servers can read/write data from/to. You should be able to achieve this by running your Log Shipping MSSQL...