How to create VM restore points with block snapshots

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 Hyper-V 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 Hyper-V 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 Hyper-V user has been created that provides the required privileges as detailed in Microsoft Hyper-V user privileges. This user will be required when creating the Hyper-V node in the steps that follow.

This task describes the steps to follow when snapshotting VMs that reside on a Hitachi Block storage device. The data flow and policy are as follows:

Figure. Hyper-V Block Snapshot Data Flow

Table. Hyper-V Snapshot Policy
Classification Type	Parameters	Value
Hyper-V	Include / Exclude	Refer to About Hyper-V policy classifications for details on how to specify VMs that are to be included in a backup.
Hyper-V	Virtual Machine Consistency	Application consistent checkpoints.

Operation Type	Parameters	Value	Assigned Nodes
Snapshot	Mode	Hardware	Hyper-V application node
	Hardware Type	Hitachi Block
	Run Options	Run on RPO
	RPO	2 hours
	Retention	2 days

Locate the source OS Host node in the Node Inventory and check that the nodes are authorized and online

These nodes represent the Protector Clients installed on your Hyper-V environment.
Create a new Hyper-V node (unless a suitable one already exists) using the Hyper-V Node Wizard.
The Hyper-V node type is grouped under Hypervisor in the Node Type Wizard.
1. Select one node which is part of your Hyper-V environment
2. Specify the Username and Password of a user having the required privileges as detailed in Microsoft Hyper-V user privileges.
3. Select which configuration you want to the Hyper-V node to represent. In case of a standalone Hyper-V system you will only have one option. In the case of a clustered system, you must choose if the application node should represent just this host or the complete cluster.
Locate the node in the Nodes Inventory that will control the Hitachi Block Device (via a CMD) where the Hyper-V data is located. Check that the node is authorized and online.
This node is used by Protector to orchestrate snapshot creation and is identified as the Proxy Node when creating the Hitachi Block Device node in the next step. This node is known as an ISM (Intelligent Storage Manager) node. The ISM node does not appear in the data flow.
Create a new Hitachi Block Device node (unless one already exists) using the Block Storage Node Wizard and check that it is authorized and online.
The Hitachi Block Device node type is grouped under Storage in the Node Type Wizard. Note that this node does not appear in a Hyper-V snapshot data flow diagram, but is identified when assigning the snapshot policy.
Define a policy as shown in the table above using the Policy Wizard, Hyper-V Classification Wizard and Snapshot Operation Wizard.
The Hyper-V classification is grouped under Hypervisor in the Policy Wizard.
Draw a data flow as shown in the figure above, that shows only the Hyper-V source node, using the Data Flow Wizard.
At this stage the snapshot icon is not shown.
Assign the Snapshot operation to the Hyper-V source node. The Hyper-V-Snapshot policy will then be assigned automatically.
The Block Snapshot Configuration Wizard is displayed.
Select the Storage Node corresponding to the Hitachi Block storage device where the Hyper-V Server's data is located. Then select a Snapshot Pool from one of the available Thin Image or hybrid pools.
Leave the remaining Advanced Configuration options at their default settings, then click OK.

CAUTION:
If you want to preserve Hyper-V snapshots after restoring from VMs them, use Cascade mode (the default setting) when assigning the snapshot operation on the data flow. This will enable the Mount duplicate option in the Hyper-V Restore Wizard when performing a restore.

The snapshot icon is now shown superimposed over the source node.
Compile and activate the data flow, checking carefully that there are no errors.
Locate the active data flow in the Monitor Inventory and open its Monitor Details.
The policy will be invoked automatically to create a snapshot repeatedly according to the RPO specified in the policy. The policy can also be manually triggered from the source node in the monitor data flow.
Watch the active data flow via the Monitor Details to ensure the policy is operating as expected.
You should periodically see:
- Backup jobs appearing in the Jobs area below the data flow that show progress percentage, ending in Progress - Completed.
- Information messages appearing in the Logs area below the data flow indicating rules activation and snapshot events.
Review the status of the Hitachi Block Device to ensure snapshots are being created.
New snapshots will appear in the Block Snapshot Inventory periodically as dictated by the RPO of the policy. Old snapshots will be removed periodically as dictated by the Retention Period of the policy.