Activity overview
Latest activity by mat.raftree
I am getting the exact same problem with SQLBackup 6.3 running on a number of clusters. TLog backups set to copy to a network share
From reading the previous back and forth on this, I ran this:
EXEC master..sqbdata 'SELECT id, name, copyto, overwrite, count, diskretryinterval, diskretrycount, mailto, mailto_onerror, created, lastattempt FROM backupfiles_copylist WHERE status = ''P'' ORDER BY count DESC, created'
And I have a lot of rows returned, the paths are correct, but the "lastattempt" column is null. It is like something is not running to even attempt to perform the copy.
I can confirm that the Diff and Full backups are not impacted by this issue in our environment (Fulls and Diffs copy over to our network share after a local backup is performed with no issue, and I assume this is using the network resiliency features). Our current interim solution is to change all tlog backup jobs to use the "USESIMPLECOPY" param which basically disables network resiliency, but does work most of the time.
Is there anything in the works to resolve this issue or is there anything i should be looking at to further diagnose the problem? / comments
I am getting the exact same problem with SQLBackup 6.3 running on a number of clusters. TLog backups set to copy to a network share
From reading the previous back and forth on this, I ran this:
EX...
We are seeing the same errors on a 4 node cluster with 3 sql instances running on it. Is there a proper fix for this available or in the works? I am disabling key replication for now, but I'd like to know when/if a permanent fix will be available. / comments
We are seeing the same errors on a 4 node cluster with 3 sql instances running on it. Is there a proper fix for this available or in the works? I am disabling key replication for now, but I'd lik...