Creating a copy subrule
To exercise granular control over copy-to-tape operations, you can create a copy subrule. A copy subrule specifies exceptions to a parent copy storage rule for the specified subrule members.
Before you begin
About this task
The properties of a copy subrule
include the following information:
- The name of the parent rule. This property is inherited and cannot be changed.
- The server that runs the parent rule. This property is inherited and cannot be changed.
- The target pool of the parent rule. The target pool is the storage pool to which
eligible data is copied. This property is inherited, but you can change the value.Tip: By specifying a different target pool, you can copy data from the subrule members to a different target pool than the parent rule.
- One or more source pools of the parent rule. The source pools are the container storage pools whose data is copied to tape. This property is inherited and cannot be changed.
- The name of the copy subrule. You must specify a name that is unique to the server and is no more than 30 characters.
- Whether data is copied for the subrule members. You can specify one of the following options:
- All data
- Specifies that the data that was backed up to the source pools by the subrule members is copied to the target pool.
- None
- Specifies that the data that was backed up to the source pools by the subrule members is not copied to the target pool.
- The members of the copy subrule. The members are the clients and virtual machine (VM) file spaces to which the copy subrule applies. You can select individual clients, specify VM name patterns, or both. You can also create a copy subrule with no members and edit the subrule later to add members.
Procedure
To create a copy subrule, complete the following steps: