64
Copyright © Acronis, Inc., 2000-2010
a backup policy to the group. Any server, that is added to the network and registered on the
management server, will appear in this group and the policy will be applied to it automatically.
To protect the salesmen's workstations with a different policy, the administrator creates the G2
dynamic group using the AD OU criterion. Any change in the OU membership of a machine will be
reflected in the G2 membership. The appropriate policy will be applied to the new OU members and
revoked from machines deleted from the OU.
The international sales manager's laptop is not included in the OU but it has some of the data the
sales machines have. To back up this data, the administrator has to add the laptop to G2 "by force".
This can be done by creating a static group (G3) and moving the static group into the dynamic one.
The policy applied to the parent group (G2) will be applied to the child group (G3), but members of
G3 are not considered as members of G2 and so its dynamic nature is considered intact.
In real life, the administrator would most likely prefer to protect the manager's machine by applying
the policy directly to the machine, without including it in any group, so this case is just an illustration
of nesting different types of groups. With multiple group members, nesting of the groups comes in
handy.
2.14.3.5
Operations with custom groups
You create empty groups in the generic root (Physical machines or Virtual machines) or within
existing groups and populate them by manual adding machines (static groups) or by adding criteria of
dynamic group membership. You can also
edit a group, that is:
change the group name
change the group description
change the dynamic membership criteria
transform a static group into a dynamic one by adding membership criteria
transform a dynamic group into a static one with two options:
keep the group members
remove the group members
move a group from the root to another group (any group type to any group type)
move a group from the parent group to the root
move a group from one parent group to another (any group type to any group type)
delete a group, that is, disjoin the group members that remain in the group of all machines
anyway.
Operations with groups to which backup policies are applied will result in changing the policies on
the member machines. If a machine is not available or reachable at the moment, the action becomes
pending and will be performed as soon as the machine becomes available.
For information on how to perform the operations please see Operations with groups (p. 305).
2.14.4
Policies on machines and groups
This section helps you understand the automatic deployment and revoking policies performed by the
management server when a policy or a number of policies are applied to machines and nested
groups of machines in various combinations; when a policy is revoked from machines and groups;
when a machine or a group is moved from one group to another.
