A Policy consists of Classifications that specify what data is to be protected and Operations that specify how that data is to be protected.
Physical classifications specify the data by directly naming the path, logical device/volume or disk type to be protected, whereas Application classifications specify the data indirectly by naming the application instance such as databases or virtual machines to be protected, Ops Center Protector then discovers the volumes that the application's data resides on. The following table shows which classifications can be used in conjunction with a particular type of source node.
| Source Node Type | Policy Classifications | ||||
|---|---|---|---|---|---|
| Oracle Database | Oracle RMAN | Disk Type | Block | Path | |
| OS Host | Yes | Yes | |||
| Oracle | Yes | Yes | |||
| VMware | Yes | ||||
| Hitachi Block Device | Yes | ||||
| Hitachi Logical Block Device | |||||
| Hitachi Block Host | Yes | ||||
| Generation 1 Repository | A Generation 1 Repository can act as a source node in a cascaded data flow, where one generation 1 repository is backed up to another generation 1 repository. The policy classification is effectively the same as the one applied to the original data source in the cascade. | ||||
| Generation 2 storage nodes (HCP, Amazon S3 and Repository) | Can act as a source node in a cascaded data flow, where one generation 2 node is backed up to another generation 2 node. The policy classification is effectively the same as the one applied to the original data source in the cascade | ||||
The Operations in a policy define the methods to be used to create backups of the primary data. Operations can be implemented using Protector software methods (e.g. Backup), or by orchestrating the hardware storage devices (e.g. Hitachi Block) to implement operations in hardware (e.g. Thin Image and Universal Replicator). The following table shows which operations can be used in conjunction with a particular type of source or destination node.
| Node Type | Policy Operations | |||||||
|---|---|---|---|---|---|---|---|---|
| Backup | Access | Replicate | Snapshot | Mount | ||||
| S/W | S/W | S/W(1) | H/W | S/W(2) | H/W(3) | H/W | ||
| OS Host | S | S | S | D | ||||
| Oracle | S | S | S | D | ||||
| VMware | S | S | S | |||||
| Hitachi Block Device | S or D | S | ||||||
| Hitachi Logical Block Device | S or D | S | ||||||
| Hitachi Block Host | S | S | ||||||
| Repository | S or D | |||||||
| HCP | S or D | |||||||
| Amazon S3 | S or D | |||||||
| (1) |
(2) Software Replication is not currently supported. (3) Software Snapshot is not currently supported. (4) Snapshots are local operations, so the source is always the same as the destination on a data flow. |
|||||||
Operations defined in a Policy work in conjunction with Movers placed on a Data Flow. When a policy is assigned to a source node, all the operations in that policy are assigned to that node. The policy is then routed by a mover and the contained operations assigned to one or more destination nodes. The following table shows which operations can be used in conjunction with a particular type of mover:
| Policy Operation | Implementation | Batch Mover | Continuous Mover |
|---|---|---|---|
| Backup | Software | Scheduled or on-demand incremental backups are created on a repository HCP or Amazon S3 node, based on RPO. | N/A |
| Replicate | Software |
Not supported. |
N/A. |
| Hardware | Hitachi Block: Scheduled or on-demand replicas of the P-VOL are created on an S-VOL using Refreshed Thin Image, ShadowImage, TrueCopy or Universal Replicator. |
Hitachi Block: Live changes to the P-VOL are replicated to an S-VOL using ShadowImage, Universal Replicator or Global-Active Device. |
|
| Snapshot | Software | Windows: Not currently supported. |
N/A |
| Linux/AIX: Not currently supported. |
|||
| Hardware | Hitachi Block: Scheduled or on-demand local snapshots are created using Thin Image. The batch mover is implied but not shown on the data flow since the operation is local to the storage device. |
N/A | |
| Mount | Hardware |
Automatically mounts a Hitachi Block LDEV based on a schedule. The mounted LDEV can then be used for repurposing or proxy backup. |
N/A |