My employer has a OLTP database that's on a SS2014 Standard Edition server that's been overwhelmed by ad hoc queries, reports, and data mining queries. I have attempted to offload all the non-OLTP work by implementing a log shipping solution (to provide a read-only copy of the database on another server, a SS2016 Standard Edition server). Everything I've read about log shipping says that log shipping from an older version of SQL Server (the primary) to a more current version of SQL Server (the secondary) will work well. I've not been able to make it work, either by:1) having the Log Shipping setup GUI executed on the primary server, backup and seed the read-only database to the secondary server, or2) by seeding the database on the secondary server myself. What is working:1) The initial, full backup of the OLTP database is successful.2) The subsequent transaction log backups (produced by a Log Shipping (SQL Agent) job) is working. What is not working: Nothing beyond the 2 items that work. The full copy of the database backup file is never copied nor restored to the secondary server. That step must happen for anything else to work. The messages in the failure report, verbatim:1) SQL Server Management Studio restore database "TestLogShipping" (Microsoft SQL Server Management Studio)Additional Information:2) An exception occurred while executing a Transact-SQL statement or batch (SqlManagerUI).3) Cannot open backup device "\\serverName\TestLogShipping\TestLogShipping.bak"4) Operating system error 5(Access is denied.).5) RESTORE FILELIST is terminating abnormally. (Microsoft SQL Server, Error: 3201).I've had 3 other people including another DBA and a Windows sysadmin involved to ensure proper share and permissions implementations. We all agree that they've been implemented correctly.Has anyone experienced this(these) problem(s) and either solved it(them), or determined that what I’m attempting to do, cannot be done?Could the problem be as simple as this cannot be done, from SS2014 to SS2016?
↧