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. NetBackup™ for Microsoft SQL Server Administrator's Guide
  3. Performing backups and restores with the NetBackup MS SQL Client
  4. About performing a SQL Server page-level restore (NetBackup MS SQL Client)
NetBackup™ for Microsoft SQL Server Administrator's Guide

About performing a SQL Server page-level restore (NetBackup MS SQL Client)

Note:

Page-level restores are only applicable for batch file-based policies.

Use page-level restore to recover only the pages that are corrupted. If many pages are corrupt, then a full database recovery may be faster.

When you select the page restore option, NetBackup for SQL Server creates a page restore template.

This template includes the following parts:

  • A page restore operation that you can modify by inserting the IDs of the pages that you want to restore.

  • A series of transaction log images for recovering the database to the current point in time.

  • A tail-log backup and recovery operation, which is required to bring the database online.

About SQL page-level restore requirements and limitations

The following requirements and limitations exist when you perform SQL Server page-level restores:

  • Pages can be restored from the following backup types: Database, filegroup, file, read-write filegroups, and partial database.

  • Your SQL Server must use either the full or bulk-logged recovery model.

  • SQL Server sometimes cannot recover the specific pages that you request if they contain critical information about the definition of the database itself. For example, you cannot use page-level restore for the first page in a database file. When you detect that page-level restore does not work, you need to use full database recovery.

  • A maximum of 1000 pages can be recovered from a backup image through a page-level restore.

Perform a SQL Server page-level restore (NetBackup MS SQL Client)

This topic describes how to perform page-level restores. Note that the Microsoft SQL Server service must have full access permission to the folder install_path\netbackup\dbext\mssql\temp.

To perform a SQL Server page-level restore

  1. Open the NetBackup MS SQL Client.
  2. Obtain a list of corrupt pages in the database.
  3. Browse for the backup images you want to restore.

  4. Expand the database instance and the database.
  5. Select the database backup image that contains the pages you want to restore.
  6. From the Scripting list, select Create a page restore template.
  7. Click Restore.
  8. Type a file name for the page restore script and click Save > Yes.
  9. Edit the page first operation the page IDs that you want to replace.

    For example, replace:

    #
    # Create one or more page restore requests. These use the following format
    #PAGE file-id:page-id

    with

    #
    # Create one or more page restore requests. These use the following format
    PAGE 1:14
    PAGE 1:20
  10. When you finish modifying the template, save it.
  11. Select the script you created and click Start > Yes.

More Information

Browsing for SQL Server backup images (NetBackup MS SQL Client)

Feedback

Was this page helpful?
Previous

Perform a SQL Server database move (NetBackup MS SQL Client)

Next

Redirect a SQL Server database to a different host (NetBackup MS SQL Client)

Feedback

Was this page helpful?