Availability Group Secondary Node Backups
cmthomas68
Posts: 8 Bronze 1
in SQL Backup
Hi, I'm trying to run a backup from a secondary node in new cluster, however when I run the backup command, it is failing with a connection error to the primary node, even though I am running it on the secondary.
I'm not sure why it is even trying to talk to the primary when running from the secondary?
We do run a custom port number for our SQL connections, so if it is trying to connect on the default port, it will fail. I have also tried setting this parameter:
Which doesn't seem to have made a difference. Is there something additional I need to do? We can run sql native backups from the secondaries without a problem, just not redgate backups like we would like to use.
I'm not sure why it is even trying to talk to the primary when running from the secondary?
We do run a custom port number for our SQL connections, so if it is trying to connect on the default port, it will fail. I have also tried setting this parameter:
Which doesn't seem to have made a difference. Is there something additional I need to do? We can run sql native backups from the secondaries without a problem, just not redgate backups like we would like to use.
Tagged:
Answers
If your secondary replica does not allow connections, SQL Backup attempts to get those details from the primary replica. As you pointed out, this is failing because the instance the primary replica is running on a non-default port.
Can you confirm that your secondary replica does not allow connections? Thanks.
So we don't have read enabled on the secondaries, intentional design for licensing/etc. Just wondering can we change the way it connects to the primary so that it uses the non standard port number? I've checked the documentations and can't find anything...