You can associate CommCell entities with a copy at different granular levels. After the association, only new backup jobs of the chosen CommCell entities are copied to the copy during an auxiliary copy operation. By default, all the servers associated with a plan are associated with the copy.
If a parent entity is selected, then by default all the child entities are selected and if any child entity is added later in the backup cycles, then that child entity is also automatically added to this association. However, you can also choose to exclude any entity from this association.
When you associate a new subclient to a secondary copy, the auxiliary copy operation automatically picks up the backup jobs that are run after the association.
However, if the job is an incremental backup job, the software picks up any previous incremental backup jobs and full backup job from the current cycle.
Procedure
-
From the Command Center navigation pane, go to Manage > Plans.
The Plans page appears.
-
From the Plans list, click the plan that has the copy you want to update.
The Overview page of the plan appears.
-
Click the Storage Policies tab.
The Regions page appears.
-
Expand the region that has the copy you want to update.
The Copies tile opens.
-
Click the secondary copy for which you want to update the subclient associations.
The copy page appears.
-
On the Subclient associations tab, in the Association summary area, click the edit icon.
The Edit storage policy association dialog box appears.
-
Select the entities that you want to associate with the copy.
When any child entities are associated with the plan, they are automatically selected on the copy.
-
To dissociate or exclude an entity, unselect entity by clearing the checkbox.
When any child entities are associated with the plan, they are not selected on the copy.
-
To view selected and excluded entities, select the Show selected and Show excluded checkboxes respectively.
-
Click Save.
The Confirm dialog box appears.
-
Click Yes to confirm.
-
If you select Yes, association changes are applied to the jobs that are already waiting to be copied. Also, for the jobs that are waiting to be copied to which entity association is changed to "excluded", the jobs are marked as disabled. However, if you change the entity association to "included" again, the software does not repick the disabled jobs. To copy such jobs, you must manually mark such jobs.
-
If you select No, association changes are not applied to the jobs that are already waiting to be copied. The changes apply only to the new jobs.
-
Points to Remember
When associating entities with a copy, remember to keep the following points in mind:
-
Once you exclude an entity from the list of associations, the copy will no longer automatically associate any newly created child entities under the excluded entity to the copy.
-
If a parent VSA client is associated, then all the children VMs are automatically associated to the copy.
-
If a parent VSA client is associated and some children VMs are excluded, then only these children VMs are excluded from the association with the copy. All the other VMs that are linked with the parent VSA client remain associated with the copy.
-
If a parent VSA client is excluded and a child VM is associated, then the exclusion is honored and the child VM is not accounted as associated with the copy.
-
For VSA servers, if you have rights on VMs in a server group, then servers and server groups that are associated with the copy are displayed.
-
If you exclude an entity that belongs to multiple server groups, then the entity is excluded from the copy association for all the server groups that it belongs to.
-
If you have user rights on all server groups, then you can view and edit the associations of all the server groups including the root server group node.
-
If a VM with active backup jobs that is on an excluded subclient is moved to a new included subclient, then the software does not pick any new backup jobs of the VM for copy till the previous subclient is excluded.
-
If you have user rights on limited number of server groups, then you can view and edit associations of only those selected server groups. With limited rights, you cannot edit the root server group node.