I have very large SQL DB on a client site. Due to it’s size the client is also a Media Agent that backs itself up and then replicates a second copy of the backup data to the secondary SQL node in the AG.
What we’d like to do is use the Secondary node to backup the SQL AG DB from itself which would allow the primary node to not be accessed.
From what I can see this is not possible. You can only run a backup copy/TLogs on the Secondary node.
I just want to confirm there is no way to satisfy this client request?
Best answer by Edd RimmerView original