It is assumed that the following tasks have been performed:
- The Protector Master software has been installed and licensed on a dedicated node.
- The Protector Client software has been installed on all nodes of the Microsoft SQL Server setup which should be protected.
- The Protector Client software has been installed on the node that will act as a proxy for the Hitachi storage device where the SQL Server data is located. Note that for a Thin Image snapshot, the source and destination LDEVs are located on the same device.
- The block storage device has been set up as per the Protector requirements and prerequisites. Refer to Hitachi Block prerequisites.
- Permissions have been granted to enable the Protector UI, required activities and participating nodes to be accessed. In this example all nodes will be left in the default resource group, so there is no need to allocate nodes to user defined resource groups.
- A user has been created that provides the required privileges as detailed in Microsoft SQL Server User Privileges. This user will be required when creating the SQL Server classification in the steps that follow.
This task describes the steps to follow when snapshotting databases that reside on a Hitachi Block storage device. The data flow and policy are as follows:
Figure. Microsoft SQL Server Node
Classification Type | Parameters | Value |
---|---|---|
Microsoft SQL Server Database | Node | Microsoft SQL Server application node hosting the instance. |
Instance | Instance hosting the databases | |
User | User for backup | |
Included Items | Refer to Microsoft SQL Server Database Selection Wizard on how to include database into the backup | |
Backup Mode | Full Copy | |
Replica Backup Preference | Selected Replica |
Operation Type | Parameters | Value | Assigned Nodes |
---|---|---|---|
Snapshot | Mode | Hardware | SQL Server application node |
Hardware Type | Hitachi Block | ||
Run Options | Run on RPO | ||
RPO | 2 hours | ||
Retention | 2 days |