Saravanan T (2/24/2016)
I got the same error ... Restart worked but it just an temporary solution .. I got the same error again after a while... Do I need install the SQL 2014 SP1 for a permanent fix?
This is my problem. A reboot fixes the 3013 error, but only temporarily.
We thought perhaps it was an issue with the network share, so we tried backing up locally and then using robocopy to ship the backups once complete... Backups ran for a few days, but then started failing with 3013 over the weekend again.
A reboot always fixes it, but seems like quite an annoying thing to have to reboot my SQL nodes every week or so in order to ensure backups are still continuing.
I checked permissions, read-only, everything seems to be in order... and since the reboot resolves it, I can't imagine the issue is permissions/file options related.