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

Dell PowerProtect Cyber Recovery 19.16 Product Guide

PDF

Creating the Avamar DD Boost account and UID for Cyber Recovery

Before performing an Avamar recovery, create the DD Boost account that is associated with the copy in the Cyber Recovery vault.

Steps

  1. To determine the UID required for recovery:
    1. Log in to the CRCLI by typing the following command:
      crcli login -u <Cyber Recovery user>
    2. Type the following command on the management host:
      crcli policy list-copy --policyname <policy name> -c <copy name>

      For example:

      # crcli policy list-copy -n policy1 -c cr-copy-policy1-2020120914175 

      Note the output from this command, as shown in the following code example:

      Source Storage UID     : 65534

      Where 65534 is the UID that you associated with this policy.

  2. To determine if the account exists for this UID, log in to the DD system in the Cyber Recovery vault and type the following command:
    user show list
    • If the output lists the UID, you can proceed with the recovery procedure.
    • If the output does not show that the UID exists, go to the next step.
  3. Create the UID:
    1. When adding the application asset, if you defined a tag, reference the tag to determine the production system DD Boost username.
    2. If you are running DDOS version 7.7 or later, create the username and account by typing the following command:
      user add <username> uid <UID> role admin
      For example:
      # user add avdd uid 500 role admin

      where the UID value is the UID that you identified in step 1.


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