Activity overview
Latest activity by jeffn
Any update on this. It would be helpful for my environment.
My setup:
Primary SQL Server
Local LogShip Standby SQL Server
Remote LogShip Standby SQL Server
If I use the Mirror Option to copy the files to both Standby Servers:
If one of the machines is inaccessible briefly then the server will be missing the log files. Obviously I could write something to make the copy happen again but it would have to be smart enough to know whether the .trn had been applied and moved to the post restore location or if it was never copied to the pre restore location.
If I use the CopyTo option to copy the file to a second location and the CopyTo server is inaccessible briefly then the LogCopy tasks will start to backup. If the first server applies the log and then moves it to another directory the Log Copy task will fail as it cannot find the source file.
I would like to use the second option and just have the restore task be smart enough to only attempt the log backups which have not been restored, and not move them to a post restore location.
I have found a workaround although I don't use it as it causes the jobs to run much longer. You can use the MoveTo command on the log restore and just point the MoveTo location to the source location. In effect you don't move the files and the log restore eats the 4326 error. I don't know if this has ill effects since I don't use it but I just wanted to make others aware of it as a possible solution if you aren't worried about the restore log taking more time. / comments
Any update on this. It would be helpful for my environment.
My setup:
Primary SQL Server
Local LogShip Standby SQL Server
Remote LogShip Standby SQL Server
If I use the Mirror Option to copy the f...