Hi,
We've a SQL Server 2016 cluster Always-On running on Windows Server 2016.
Current situation:
- SQL1 (Secondary node)
- SQL2 (is currently Primary node & backup job running fine on this node)
Backup preference option is: Prefer Secondary
When a failover happens, SQL1 takes the lead and becomes Primary but all backup jobs fail subsequently even the backup preference is Secondary.
Can someone explain why the backups fail on the secondary node SQL2 (when it becomes secondary) where it contains all the backup history (full, differential and log)?
I appreciate your help.
Thanks,
AB
AB