We have an Always-On SQL cluster with 3 servers.
Active/Passive - site 1
Passive (async replication) - site 2
We're using the SQL Plugin and a repo at the primary site, we also ship this off to Wasabi.
But we're also looking to do a copy-only snapshot at the secondary site. We don't want to replicate backup, due to bandwidth constraints, and a copy-only at that facility is sufficient for the requirements.
We have an HPE/Nimble SAN that we already do snapshots on that are facilitated by Veeam.
My question is what are the appropriate settings I should be using in the snapshot only job to facilitate this copy-only backup of SQL. If I were to let the SAN itself do it without the help from Veeam, we could just setup a snapshot and enable application synchronization and it should be good. Since there are no transaction logs on the passive node, there's no need to truncate the logs. Nor would we want to since that's being handled by the SQL Plugin at the main site.
I'm assuming I'd just use the Application Aware processing and select the do not trunace logs option under SQL.
But I wasn't sure if just VMware Quiescense wouldn't accomplisht he same feat. Or which was the appropriate solution here.
Active/Passive - site 1
Passive (async replication) - site 2
We're using the SQL Plugin and a repo at the primary site, we also ship this off to Wasabi.
But we're also looking to do a copy-only snapshot at the secondary site. We don't want to replicate backup, due to bandwidth constraints, and a copy-only at that facility is sufficient for the requirements.
We have an HPE/Nimble SAN that we already do snapshots on that are facilitated by Veeam.
My question is what are the appropriate settings I should be using in the snapshot only job to facilitate this copy-only backup of SQL. If I were to let the SAN itself do it without the help from Veeam, we could just setup a snapshot and enable application synchronization and it should be good. Since there are no transaction logs on the passive node, there's no need to truncate the logs. Nor would we want to since that's being handled by the SQL Plugin at the main site.
I'm assuming I'd just use the Application Aware processing and select the do not trunace logs option under SQL.
But I wasn't sure if just VMware Quiescense wouldn't accomplisht he same feat. Or which was the appropriate solution here.
Statistics: Posted by jmbi — Feb 06, 2025 9:46 pm