Skip to main content
  • 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.

PowerProtect Data Manager 19.14 Storage Direct User Guide

Configuration file requirements

When you create a VMAX Storage Group protection policy, a configuration file is automatically created in the C:\Program Files\DPSAPPS\ppfsagent\config directory. This configuration file contains information about the VMAX and DD system attributes and the storage groups protected by the policy. This file is required for self-service backup and restore procedures.

To ensure that PowerProtect Data Manager can use your existing configuration files, review the files and ensure that the contents and your environment satisfy the following requirements:

  • For existing Storage Direct agent users who are updating, the asset configuration file must be provided during the update. No option is provided to add the file once the update is completed.
  • For existing Storage Direct agent users, if you have backup copies for which the expiration is set to "never", an BACKUP_EXPIRE variable must be added to the configuration file prior to setting up the Storage Direct agent host in PowerProtect Data Manager. The value set for BACKUP_EXPIRE will be applied to those existing backup copies and read automatically by PowerProtect Data Manager, and displayed as the copy retention time within the PowerProtect Data Manager UI. If no value is set for this variable, a retention value of 0 will be used for any protection policies run from PowerProtect Data Manager, and the UI will display a retention date that has passed.
  • To import a single configuration file, all backup vDisks on the DD system must belong to the same pool.

    You can create more than one device group. For example, for two source storage groups (SG1 and SG2), you can create one device group for the backup vDisks of SG1 and another device group for the backup vDisks of SG2.

    To import multiple configuration files per host, vDisks can belong to different pools.

  • The file must contain only storage groups. It must not contain IDs of the source LUNs.
  • The file must contain the Ddboost and DdVdiskUser with their corresponding passwords in the lockbox.
  • The Ddboost and DdVdiskUser specified in the configuration file must have the admin role.
  • The Devicepath cannot start with a forward slash (/).

Additionally, the file must be in the following config file format:

  • One entry exists for RESTORE_DEVICE_GROUP and VMAX_FASTX_RESTORE_SG for all source storage groups.
  • All storage groups map to a single RESTORE_DEVICE_GROUP and VMAX_FASTX_RESTORE_SG.
  • Only one of the RESTORE_DEVICE_GROUP or VMAX_FASTX_RESTORE_SG attributes is used. Enclose the one not in use in a comment.
    • For RESTORE_DEVICE_GROUP, the corresponding pool information for RESTORE_DEVICE_POOL must be provided and the attribute must not be enclosed in a comment.
    • For VMAX_FASTX_RESTORE_SG, enclose the RESTORE_DEVICE_GROUP and RESTORE_DEVICE_POOL attributes in a comment.

Example:

[PRIMARY_SYSTEM]
  DDBOOST_USER = <boost_user>
  DEVICE_HOST = <dd_host>
  DEVICE_PATH = <ddboost_devPath>
   DDVDISK_USER = <vdisk_user>
  # RESTORE_DEVICE_POOL = <device_pool>
  # RESTORE_DEVICE_GROUP = <device_group>
  # DD_BOOST_FC =
  # DD_PORT =
    VMAX_FASTX_RESTORE_SG = <restore_sg>
  # SELECT_VISIBLE_RESTORE_DEVICES =
              |
              |
              |
[BACKUP_SOURCE_DEVICES]
  #  SRC_DEVICE1 = 000196700638:00F1A
  # SRC_DEVICEn =
  SRC_GROUP1 = <symmId:SourceGrp1>
SRC_GROUP2 = <symmId:SourceGrp2>
SRC_GROUP3 = <symmId:SourceGrp3>
  # SRC_GROUPn =

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: <>()\