Topics | How To | Support | Related Topics
Support Information - Subclient Policy
Subclient Policies provide a means through which you can configure multiple file system subclients within a CommCell from a centralized template. This alleviates the need to manually configure each file system subclient that shares a similar configuration. Subclient Policies are especially useful in large enterprise environments where configuring many similar subclients individually would be both time-consuming and impractical.
A Subclient Policy consists of one or more Subclient Templates which contain a common configuration that you want applied to Target Subclients within a CommCell. During Subclient Policy creation, you configure the templates and establish an association to desired file system backup sets. Once the backup sets are associated to a Subclient Policy, the subclients of those backup sets (now considered to be Target Subclients) inherit configuration properties from the Subclient Templates. Subsequent configuration changes can be made to the templates as needed and then easily applied to the targets.
The Subclient Policy dialog displays the list of clients associated with the Subclient Policy. Note that all the components within the client may not support Subclient Policy. For a complete list of components supporting Subclient Policy, see Support Information - Subclient Policy |
This section discusses the shortcut menu operations and property tabs available for Subclient Policies.
The following operations are supported for Subclient Policies:
You can create a Subclient Policy in the CommCell Console from the Subclient Policy level. See Create a New Subclient Policy for step-by-step instructions.
The Cloning Policies feature allows you duplicate a Subclient Policy that retains all of the properties of the original Subclient Policy. See Cloning Policies for an overview.
You may decide to delete a Subclient Policy if you determine that you no longer need the capability to implement or change configuration settings on multiple subclients simultaneously from a common policy. The Target Subclients will revert to ordinary subclients once the associated policy has been deleted, and will retain any properties that were inherited through the policy or locally defined. See Delete a Subclient Policy for step-by-step instructions.
You can view or change the policy name and/or association through this operation. See Modify the Properties of a Subclient Policy for step-by-step instructions.
The following configuration property tabs are supported for Subclient Policies:
The General tab allows you to enter a name and select an iDataAgent type for your policy, as well as define the Subclient Templates during Subclient Policy creation. After creation, this tab allows you to modify the name or view general information for the Subclient Policy.
The Association tab allows you to specify which client backup sets you want to associate with the Subclient Policy.
This section discusses the types, shortcut menu operations and property tabs available for Subclient Templates.
The Subclient Template types supported by a given Subclient Policy are the same types of subclients supported by the respective File System iDataAgent. Listed below are the types of Subclient Templates that can be defined for a Subclient Policy:
The following operations are supported for Subclient Templates:
You may decide to delete a Regular type of Subclient Template from a Subclient Policy if you determine that you no longer need that type of Subclient Template in your Subclient Policy. Keep in mind that the Delete operation is not available for Default and System State types. See Delete a Subclient Template from a Subclient Policy for step-by-step instructions.
You can change the configuration properties of all Subclient Template types through this operation. See Modify the Properties of a Subclient Template for step-by-step instructions.
The following configuration property tabs are supported for Subclient Templates:
Allows you to add, modify or view general information for the Subclient Template.
Allows you to add, modify or view the content that you want backed up.
Allows you to add, modify or view the data that you want excluded from data protection operations.
Allows you to add, modify or view pre/post commands that you want run for specified phases of the data protection operation.
Allows you to associate, change the association of, or view the Data Storage Policy for the subclient. You can also enable or disable data compression and establish the data transfer options.
Target Subclients are generally designed to inherit the configuration properties of their associated Subclient Templates. However, there are certain exceptions to this rule and overrides that you should be aware of when implementing Subclient Policies. Listed below are the properties that are inherited/not inherited from Subclient Templates, as well as property overrides available on the Target Subclient and filtering rules.
The following properties are inherited by Target Subclients, if applicable for a given subclient type:
Several configurable options to efficiently use available resources for transferring data secured by data protection operations are provided in the subclient. This includes the following:
Although the Data Compression setting is editable on the Target Subclient, once it is changed there, that Target Subclient will override or ignore any further Data Compression settings specified or changed in the associated Subclient Template.
Certain subclient properties are not established by the Subclient Policy, but are defined at the Target Subclient level. These properties include the following:
In the event that you want to specify a different configuration setting on the Target Subclient than what is specified in the Subclient Policy, you can override the inheritance of certain properties by entering localized changes on the desired Target Subclient. Properties that can be overridden on the Target Subclient are listed below.
Subclient Policies support the ability to filter data from backups when defined as part of the Subclient Template. Since filters can be set on both the Target Subclient and Subclient Template, it is important to understand how the filtering rules are applied. These rules are explained below.
The way these rules are applied is best illustrated by way of example. For the purpose of these examples we will be filtering "objects", which can either be files, folders or wildcard patterns. Consider the following scenarios:
|
In the Subclient Policy, you have selected Always Use for the Include Global Filters option (which is set to filter out object C). You have also entered object D to the exclusion list so that it will be filtered out as well.
In the Target Subclient, you have selected the Include Policy Filters option (which will inherit the filter for objects C and D). You have also entered object E to the exclusion list so that it will be filtered out as well.
Given the above configuration, the next time a backup is run for that particular Target Subclient, objects C, D and E will not be backed up.
In the Subclient Policy, you have selected Always Use for the Include Global Filters option (which is set to filter out object C). You have also entered object D to the exclusion list so that it will be filtered out as well.
In the Target Subclient, you have NOT selected the Include Policy Filters option (so no inheritance will take place to filter out objects C and D). You have also entered object E to the exclusion list so that it will be filtered out.
Given the above configuration, the next time a backup is run for that particular Target Subclient, object E will not be backed up.
In the Subclient Policy, you have selected Do not use for the Include Global Filters option (which would have filtered out object C). You have also entered object D to the exclusion list so that it will be filtered out.
In the Target Subclient, you have selected the Include Policy Filters option (so that it will inherit the filter for object D). You have also selected Always Use for the Include Global Filters option (which is set to filter out object C) and entered object E to the exclusion list so that it will be filtered out.
Given the above configuration, the next time a backup is run for that particular Target Subclient, objects C, D and E will not be backed up.