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
  3. Veritas NetBackup™ CloudPoint Install and Upgrade Guide
  5. Section I. CloudPoint installation and configuration
  7. CloudPoint application agents and plug-ins
  9. Restore requirements and limitations for Microsoft SQL Server
Veritas NetBackup™ CloudPoint Install and Upgrade Guide

Restore requirements and limitations for Microsoft SQL Server

Consider the following before you restore a SQL Server snapshot:

  • Ensure that you close SQL Management Studio before you restore a SQL Server snapshot.

    This is applicable only if you are restoring the snapshot to replace the current asset (Overwrite existing option) or restoring the snapshot to the same location as the original asset (Original Location option).

  • In case of a SQL instance disk-level restore to a new location fails if the target host is connected or configured.

    In such a case, to complete the SQL Server snapshot restore to a new location successfully, you must perform the restore in the following order:

    • First, perform a SQL Server disk-level snapshot restore.

      Ensure that you restore the disk snapshots of all the disks that are used by SQL Server. These are the disks on which SQL Server data is stored.

      See Recovering a SQL database to the same location.

    • Then, after the disk-level restore is successful, perform the additional manual steps.

      See Additional steps required after a SQL Server snapshot restore.

  • CloudPoint does not support discovery, snapshot, and restore operations for SQL databases that contain leading or trailing spaces or non-printable characters. This is because the VSS writer goes into an error state for such databases.

    Refer to the following for more details:

    https://support.microsoft.com/en-sg/help/2014054/backing-up-a-sql-server-database-using-a-vss-backup-application-may-fa

  • Before you restore a SQL Availability Group (AG) database, perform the pre-restore steps manually.

    See Steps required before restoring SQL AG databases.

  • New location restore of system database is not supported.

  • If destination instance has AG configured, restore is not supported.

  • If database exists on new location destination and the overwrite existing option is not selected, the restore job will fail.

  • If the overwrite existing option is selected for database that is a part of an AG, the restore job will fail.

  • For system database restore, the SQL Server version must be same. For user databases, restore from a higher SQL version to a lower version is not allowed.

Feedback

Was this page helpful?
Previous

Process for restoring SQL AG databases

Next

Restore requirements and limitations for Oracle

Feedback

Was this page helpful?