# The Effects of Converting Storage Policies to Plans

Converting storage policies to plans affects several components within the CommCell environment. Review the following details before starting the conversion.

## General Effects

- After you convert a storage policy to a backup plan, the storage policy remains active in the CommCell Console.

- After the conversion, you can use both the Command Center and the CommCell Console together.

  However, do not create new storage policies or new schedule policies in the CommCell Console.

- To configure advanced options for storage policies, subclient policies, and schedule policies, continue using the CommCell Console.

  The backup plans in the Command Center include only the most common configuration settings.

- The plan created from a converted storage policy does not include data schedule policies.

  Existing associations between workloads and their schedule policies remain unchanged and continue to trigger backups according to their configured schedules.

- You can choose to manage schedule policies from the Command Center after converting storage policies to plans.

  For details, see Managing Schedule Policies in Command Center.

  However, it is recommended that you add schedules directly to the converted plan to manage both storage and schedules as a single entity.

- Any deconfigured subclients associated with the storage policy are not linked to the new plan.

  These subclients remain associated with the original storage policy.

## Effects on Storage Policy Copies

When you convert storage policies that include associated copies, the following effects apply:

- Storage policy copies that are not associated with a global policy are converted to network storage pools.

  For more information, see Network Storage Pool.

- Storage policy copies are converted as follows:

  - Copies with deduplication enabled are associated with global deduplication storage policies and converted to global deduplication storage policy copies.

  - Copies without deduplication enabled are associated with global storage policies and converted to global storage policy copies.

    The copy name changes to the format Global_StoragePolicyName_*CopyName*.

    The libraries, mount paths, and MediaAgents associated with the copies remain unchanged.

    To modify these settings after conversion, update them in the global storage policies linked to the copies.

## Effects on Storage Policies Associated with Subclient Policies

When storage policies are associated with subclient policies, conversion has the following effects:

- The software creates a base plan for each agent type linked to the subclient policies.

  For example, if a storage policy is associated with subclient policies for Windows, Unix, and Mac agents, three base plans are created—one for each agent type.

- For each agent type:

  - The subclient policy with the highest number of associated entities becomes associated with the base plan.

  - Other subclient policies are converted to derived plans created from the base plan.

    For more information, see Base Plans.

- The base plan name is the same as the original 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

  Example:
  The storage policy SP1 is associated with three Windows subclient policies:

  SubPolicy1, SubPolicy2, and SubPolicy3, which are linked to 250, 200, and 150 entities, respectively.

  After conversion:

  - The software creates a base plan named SP1, associated with a subclient policy named SP1 Windows Subclient policy (for SubPolicy1).

  - Two derived plans are created: SP1_Derived_1 (for SubPolicy2) and SP1_Derived_2 (for SubPolicy3).

- Subclients associated with the storage policy but not linked to any subclient policy are associated with the base plan after conversion.

×

Loading...