Loading...

Results of the Conversion of Storage Policies to Plans and Important Considerations

The following are the results for the storage policy copies when their associated storage policies are converted to plans:

  • The storage policy copies that are not associated to a global policy are converted to a network storage pool. For more information about network storage pool, see Network Storage Pool.
  • The storage policy copies are converted as follows:
    • The storage policy copies on which deduplication is enabled are converted to a global deduplication storage policy copy. The copy is associated to a global deduplication storage policy.
    • The storage policy copies on which deduplication is not enabled are converted to a global storage policy copy. The copy is associated to a global storage policy.

    The name of the copy changes to the format Global_{StoragePolicyName}_{CopyName}. The libraries, the mount paths, and the MediaAgents of the storage policy copies do not change. If you want to change them after the conversion, you must change them in the global storage policies to which they are associated.

The following are the results of conversion of a storage policy that is not associated to any subclient policy:

  • The software creates a base plan along with three subclient policies one for each agent type - Windows, Unix and Mac.
  • The base plan name is same as the storage policy name.
  • The subclient policy name follows the format Storage_Policy_Name Agent_Type Subclient policy.

    For example: The storage policy SP1 converts to a base plan with name SP1 and three subclient policies SP1 Windows Subclient policy, SP1 Unix Subclient policy and SP1 Mac Subclient policy.

  • The subclients of each agent type are associated to their corresponding subclient policy.
  • Any subclients associated to the storage policy that are already deconfigured are not associated to the plan.

The following are the results of conversion of a storage policy that is associated to subclient policies:

  • The software creates a base plan for each agent type that the subclient policies are associated to.

    For example, if the storage policy is associated with subclient policies of the agent types Windows, Unix, and Mac, then the software creates three base plans, one for each agent type.

  • For each agent type, the subclient policy with the highest number of associated entities gets associated with the base plan. The other subclient policies are convert to the derived plans that are created from the base plan. For more information, see Base Plans.
  • For each storage policy, backup frequency of schedule policy with the highest number of associated entities will be used as the backup frequency for the base server backup plan that will be created from the storage policy. Other schedule policies associated to the entities that back up to the storage policy are disabled during the conversion. To use the backup frequencies of the disabled schedule policies, you can create derived plans.
  • The base plan name is same as the storage policy name.
  • The subclient policy name follows the format Storage_Policy_Name Agent_Type Subclient policy. The derived plan name follows the format Storage_Policy_Name_Derived_nth of derived plan.

    For example: The storage policy SP1 is associated to three Windows subclient policies SubPolicy1, SubPolicy2 and SubPolicy3 that are associated to 250, 200 and 150 entities, respectively. After conversion, the software creates a base plan with the name SP1 that has a subclient policy with the name SP1 Windows Subclient policy (for SubPolicy1). From the base plan, two derived plans are created with the names SP1_Derived_1 (for SubPolicy2) and SP1_Derived_2 (for SubPolicy3).

  • The subclients that are associated to the storage policy and not associated to any subclient policy are associated to the base plan after the conversion.
  • The subclients associated to the storage policy that are already deconfigured are not associated to the plan.

Last modified: 3/8/2021 8:12:42 AM