Ops Center Protector Microsoft SQL Server Application Guide

Version: 7.6.x
Audience: anonymous
Part Number: MK-99PRT009-04

Before you begin
Supported configurations
Prerequisites
Application prerequisites
Hitachi Block prerequisites
Microsoft SQL Server Backup workflows
About Microsoft SQL Server Policy Classifications
Block based workflows
How to create database restore points with block snapshots
Howto create a database restore point using remote replication
How to create database restore points for a selected availability group replica with block snapshots
How to create database restore points for a primary availability group with multiple storage arrays
Microsoft SQL Server Restore workflows
About mounting Microsoft SQL Server block-based backups
About reverting Microsoft SQL Server block-based backups
How to mount a database from a block-based backup and attach it to an existing instance.
How to revert multiple databases from a block-based backup.
How to revert a user database online without affecting other databases in the same instance.
How to revert a user database and prepare it to apply transaction logs.
Reference
Nodes UI Reference
Microsoft SQL Server Node Wizard
Policies UI Reference
Microsoft SQL Server Classification Wizard
Microsoft SQL Server Database Selection Wizard
Microsoft SQL Server Instance Credentials Dialog
Microsoft SQL Server User Privileges
Restore UI Reference
SQL Server Mount Wizard
SQL Server Revert Wizard
Troubleshooting
Troubleshooting Microsoft SQL Server
Cannot trigger a revert or revert fails without a force revert option.
Clustered SQL Server instances does not list all nodes.
Database(s) are not listed in Microsoft SQL Management Studio after offline revert.
Databases are not listed for when creating a SQL Server classification.
Invalid Credentials; Unable to connect to instance.
Issues with snapshots of mounted databases.
Mount Error - Database(s) already exists in instance.
No cluster nodes returned from cluster during node creation.
Online Revert option is disabled.
Unable to apply transaction log backups after successful online revert.
One or more availability group databases are skipped during backup.
Copy only backups are created for Availability Group databases instead of full backups.

Back to home page