Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

PowerProtect Data Manager 19.14 Storage Direct User Guide

PDF

Remove assets from an existing storage group protection policy

Use the PowerProtect Data Manager UI to edit a protection policy to remove storage groups.

Steps

  1. Select Protection > Protection Policy.
    The Protection Policy window appears.
  2. Select the protection policy that you want to modify, and click Edit.
    The Edit Policy window opens on the Summary page.
  3. In the Assets row, click Edit.
    The Assets page appears.
  4. To remove a storage group from the protection policy, select the asset and click Remove.
    NOTE:During backup, storage groups that you added to a protection policy are grouped in a transaction. When deleting storage groups, it is recommended to delete all the storage groups that are part of this transaction simultaneously.
    The Assets page updates with the changes.
  5. Click Next to save the changes and go to the Summary page.
  6. In the Summary page, click Finish
    An informational dialog box appears.
  7. Click OK to exit the dialog box, or click Go to Jobs to open the Jobs window to monitor the backup of the new protection policy.

Results

Configuration of assets occurs in four steps:
  • Step1: Configure ProtectPoint vDisks.
  • Step 2: Encapsulate vDisks.
  • Step 3: Create copy.
  • Step 4: Configure host.
If the four configuration steps for the assets that are marked for removal completes successfully, a Removing Storage Groups from Configuration File job is initiated. Upon completion, the entry for these assets is removed from the BACKUP_SOURCE_DEVICES section of the configuration file, and the assets will no longer be backed up as part of the policy. Existing backups of these assets remain on the system and continue to be available for recovery. If you want to protect these assets again, you can create another Storage Groups policy for the assets, add them again to the previous policy, or add them to an existing policy that has the same vDisk pool.

If configuration fails at step 2 or earlier, the configuration for the assets is removed. If the configuration fails at step 3 or later, the configuration is retained.

NOTE:If asset configuration is only partially successful for a protection or replication objective, asset removal is handed differently based on the following scenarios:
  • If configuration of a protection objective is only partially successful, the configuration of these assets is removed based on the step at which configuration failed. For example, if configuration fails at the first step Configure ProtectPoint vDisks, the vDisks are deleted. If configuration fails at the second step Encapsulate vDisks, the storage_groups vDisks are deleted.
  • If configuration for protection and replication objectives is incomplete, the configuration is removed for the protection and replication objectives, based on the step at which the failure occurred.
  • If configuration for a protection objective is incomplete but successful for a replication objective, the configuration is removed for protection, based on the step at which the failure occurred, and the replication configuration remains intact.
  • If configuration for a protection objective is completed successfully but incomplete for a replication objective, the configuration for both protection and replication are retained. You can restart jobs for replication to complete the configuration.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\