Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ CloudPoint Install and Upgrade Guide
  3. Section I. CloudPoint installation and configuration
  4. CloudPoint application agents and plug-ins
  5. Additional steps required after restoring SQL AG databases
Veritas NetBackup™ CloudPoint Install and Upgrade Guide

Additional steps required after restoring SQL AG databases

You must perform the following steps after restoring a SQL Availability Group (AG) database:

Note:

If you are restoring the AG database to multiple replicas, perform the entire restore process on the primary replica first, and then repeat the steps for each secondary replica.

  • Add the restored database to the AG on the primary replica.

    From the SQL Server Management Studio, right-click on the AG entry and select Add Database. In the wizard workflow, select the database, and on the Initial Data Synchronisation page, select the Skip Initial Data Synchronization option. You can select the other options depending on the requirement.

If you restoring the same database to a secondary replica, perform the following steps:

  1. Restore database to the secondary SQL instance in "Not recovered" state. Restore with no recovery should be successful.

  2. Join the database to the AG on the secondary replica.

    From the SQL Server Management Studio, connect to the secondary replica node, then right-click on the database and select Join Availability Group.

    Observe that the database status on the secondary replica change from (Restoring...) to (Synchronized), indicating that AG database snapshot restore is successful.

You must repeat these steps for each replica where you wish to restore an AG database.

Feedback

Was this page helpful?
Previous

Steps required after a SQL Server disk-level snapshot restore to new location

Next

SQL snapshot or restore and granular restore operations fail if the Windows instance loses connectivity with the CloudPoint host

Feedback

Was this page helpful?