Converting storage policies to plans has various effects that are important for you to understand.
General Effects
-
After you convert a storage policy to a server plan, the storage policy remains active in the CommCell Console.
-
After the conversion, you can use the Command Center and the CommCell Console together. But 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, use the CommCell Console. Server plans in the Command Center include only the most common settings.
Effects on Storage Policy Copies That Are Associated with a Storage Policy
The effects of conversion on storage policy copies that are associated with a storage policy are as follows:
-
Storage policy copies that are not associated with a global policy are converted to network storage pools. For more information about network storage pools, see Network Storage Pool.
-
Storage policy copies are converted as follows:
-
Storage policy copies that have deduplication enabled are associated with global deduplication storage policies and converted to global deduplication storage policy copies.
-
Storage policy copies that do not have deduplication enabled are associated with global storage policies and converted to global storage policy copies.
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 those settings after the conversion, you must change them in the global storage policies that the copies are associated with.
-
Effects on Storage Policy Copies That Are Not Associated with a Storage Policy
The effects of conversion on storage policy copies that are not associated with a storage policy are as follows:
-
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 is converted 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 with their corresponding subclient policy.
-
Any subclients that are associated with the storage policy that are already deconfigured are not associated with the plan.
Effects on Storage Policies That Are Associated with a Subclient Policy
The effects of conversion on storage policies that are associated with a subclient policy are as follows:
-
The software creates a base plan for each agent type that the subclient policies are associated with.
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 that has the highest number of associated entities gets associated with the base plan. The other subclient policies converted 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 with 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.
-
If a subclient associated with the schedule policy has a particular job start time, then after the policy conversion to plan, the job start time is added to the subclient. For more information, see Configure Job Start Time.
This is not applicable to log schedules and continuous schedules.
-
The plan created from a converted storage policy will have a schedule that triggers backups in the client time zone. To modify the time zone of a server plan, see RPO section of Modifying Server Plan.
-
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 with three Windows subclient policies SubPolicy1, SubPolicy2 and SubPolicy3, which are associated with 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 with the storage policy and not associated with any subclient policy are associated with the base plan.
-
The subclients that are associated with storage policies that are already deconfigured are not associated with the plan.