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

Dell EMC PowerProtect DDVE in the Azure Cloud 7.8 Installation and Administration Guide

PDF

Configuring DDVE in Azure using the CLI

Use this procedure to configure DDVE in Azure with the Command Line Interface (CLI).

Steps

  1. Use SSH to log in to the DDVE instance with sysadmin credentials.
    If you did not specify a password during deployment, when you log in for the first time, you must change the password.
    The initial configuration wizard starts.
  2. Press Enter to dismiss all wizard options, exit the wizard, and complete the configuration by using CLI commands.
  3. Proceed as shown in the following figure: 
    $ ssh -l sysadmin <DDVE ip address>
The authenticity of host '**.**.**.** (**.**.**.**)' can't be established.
ECDSA key fingerprint is SHA256:CSbkxaW7hqCnF1S27WKjM01BJISYxs7XejBdKHUs+wE.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '**.**.**.**' (ECDSA) to the list of known hosts.
EMC Data Domain Virtual Edition
Password:
Welcome to Data Domain OS *.*.*.*-******
----------------------------------------
Press any key then hit enter to acknowledge the receipt of EULA information: q

Security Officer
Do you want to create security officer ? (yes|no) [no]:
Do you want to configure system using GUI wizard (yes|no) [no]:

Network Configuration
Configure Network at this time (yes|no) [no]:

eLicenses Configuration
Configure eLicenses at this time (yes|no) [no]:

System Configuration
Configure System at this time (yes|no) [no]:

Storage object-store profile Configuration
Configure Storage object-store profile at this time (yes|no) [no]:

Configuration complete.
  4. To update the eLicense on DDVE, copy the license file to /ddvar and use the file name as follows: # elicense update <filename>.lic. 
    # elicense update atos_cap_96_TB.lic

Existing licenses:

Capacity licenses:
##   Feature    Capacity   Type                   State    Expiration Date   Note
--   --------   --------   --------------------   ------   ---------------   ----
1    CAPACITY   0.45 TiB   unexpired evaluation   active   n/a
--   --------   --------   --------------------   ------   ---------------   ----

Feature licenses:
##   Feature                     Count   Type                   State    Expiration Date   Note
--   -------------------------   -----   --------------------   ------   ---------------   ----
1    REPLICATION                     1   unexpired evaluation   active   n/a
2    DDBOOST                         1   unexpired evaluation   active   n/a
3    RETENTION-LOCK-GOVERNANCE       1   unexpired evaluation   active   n/a
4    ENCRYPTION                      1   unexpired evaluation   active   n/a
--   -------------------------   -----   --------------------   ------   ---------------   ----

New licenses:

Capacity licenses:
##   Feature    Capacity    Type              State    Expiration Date   Note
--   --------   ---------   ---------------   ------   ---------------   ----
1    CAPACITY   87.31 TiB   permanent (int)   active   n/a
--   --------   ---------   ---------------   ------   ---------------   ----

Feature licenses:
##   Feature       Count   Type              State    Expiration Date   Note
--   -----------   -----   ---------------   ------   ---------------   ----
1    DDBOOST           1   permanent (int)   active   n/a
2    ENCRYPTION        1   permanent (int)   active   n/a
3    REPLICATION       1   permanent (int)   active   n/a
--   -----------   -----   ---------------   ------   ---------------   ----

        ** New license(s) will overwrite all existing license(s).

        Do you want to proceed? (yes|no) [yes]: yes


eLicense(s) updated.
    Use the # elicense show command to verify. 
    # elicense show
System locking-id: V4MXYV1S7R6VZVRWW6T9JTMPPBZEGY4CL25FSPX775WJC8GM6P57YKTD
HGYDGR9AJZ4Y66CSH152YJRS6UPHFUZ2PP6VATMY2FMWSSKKZ8SHD

System software-id:   Not available
Instance software-id: Not available

Licensing scheme: EMC Electronic License Management System (ELMS) node-locked mode

Capacity licenses:
##   Feature    Capacity    Type              State    Expiration Date   Note
--   --------   ---------   ---------------   ------   ---------------   ----
1    CAPACITY   87.31 TiB   permanent (int)   active   n/a
--   --------   ---------   ---------------   ------   ---------------   ----

Feature licenses:
##   Feature       Count   Type              State    Expiration Date   Note
--   -----------   -----   ---------------   ------   ---------------   ----
1    REPLICATION       1   permanent (int)   active   n/a
2    DDBOOST           1   permanent (int)   active   n/a
3    ENCRYPTION        1   permanent (int)   active   n/a
--   -----------   -----   ---------------   ------   ---------------   ----
License file last modified at : 2018/05/07 18:56:36.
  5. Use # storage object-store enable to enable object store. 
    # storage object-store enable
Object-store is enabled.
  6. Enter values for the following to create the Object store:
    1. System Passphrase—Required to encrypt the object store credentials. It will also will be used to encrypt keys if file system encryption is enabled. If the passphrase has already been set, the user is not prompted to enter a passphrase.
    2. Account Name—If no account exists, create one first.
    3. Primary Key—Storage account > access keys (not required if using OAuth 2.0 mode).
    4. Container Name—Create a container under the storage account. The container must be empty or the operation fails.
    5. Baltimore Cyber Trust Root—This certificate is required to communicate with the object store. Import it for the profile creation to succeed.
      NOTE The Baltimore Cyber Trust Root might not appear when object-store is enabled (because all certificates are imported once).
    # storage object-store profile set 
    # storage object-store profile set
A passphrase needs to be set on the system.
Enter new passphrase: <enter-passphrase-string-meeting-requirements>
Re-enter new passphrase: <re-enter-passphrase-string>
Passphrases matched.
The passphrase is set
        Enter the account name: <name-of-the-account-name>
        Enter the primary key: <name-of-the-primary-key>
        Enter the container name: <name-of-the-container-name> 

        Object-store endpoint needs the Baltimore CyberTrust Root certificate to be imported.
        Do you want to import that certificate with below fingerprint?
        D4:DE:20:D0:5E:66:FC:53:FE:1A:50:88:2C:78:DB:28:52:CA:E4:74  (yes|no) [yes]: yes

        Profile is set.
    OAuth 2.0 example: 
    # storage object-store profile set
A passphrase needs to be set on the system.
Enter new passphrase: <enter-passphrase-string-meeting-requirements>
Re-enter new passphrase: <re-enter-passphrase-string>
Passphrases matched.
The passphrase is set
                OAuth is the recommended way of authentication to the object store. Do you want to choose OAuth? (yes|no) [yes]: 
        Enter the account name: <name-of-the-account-name>
        Enter the container name: <name-of-the-container-name>

        Profile is set.
  7. Use # storage add tier active dev4 to add the metadata storage. 
    # storage add tier active dev4

Checking storage requirements...done
Adding dev4 to the active tier...done

Updating system information...done

dev4 successfully added to the active tier.
    Multiple devices can also be added as metadata storage using the # storage add tier active dev4-6 command. This command is useful in when adding dev4, dev5, and dev6 to the DDVE. 
    # storage add tier active dev4-6

Checking storage requirements...done
Adding dev4 to the active tier...done

Updating system information...done

dev4 successfully added to the active tier.


Checking storage requirements...
done
Adding dev5 to the active tier...done

Updating system information...done

dev5 successfully added to the active tier.


Checking storage requirements...
done
Adding dev6 to the active tier...done

Updating system information...done

dev6 successfully added to the active tier.
    NOTE Use the # storage show all command to view the disks that are attached. 
    # storage show all
Active tier details:
Device        Device   Device
Group                  Size
-----------   ------   ----------
(available)   4        1023.0 GiB
(available)   5        1023.0 GiB
(available)   6        1023.0 GiB
-----------   ------   ----------

Spindle   Devices   Count   Total Size
Group
-------   -------   -----   ----------
2         4         1       1023.0 GiB
3         5         1       1023.0 GiB
4         6         1       1023.0 GiB
-------   -------   -----   ----------

Current active tier size: 2.9 TiB
Active tier maximum capacity: 35.2 TiB**
** The maximum capacity supported by system memory.



Capacity License:
License    Total       Used       Remaining
--------   ---------   --------   ---------
CAPACITY   87.31 TiB   2.70 TiB   84.61 TiB
--------   ---------   --------   ---------
  8. Use # filesys create to create the file system. 
    # filesys create
A filesystem of approximate size 2.71 TiB will be created.
        Do you want to continue? (yes|no) [yes]: yes

ok, continuing.

This will take 5 - 10 minutes.

Provisioning storage...
########################################### [100%]

Initializing filesystem...
########################################### [100%]

snapshot schedules deleted

You now have a freshly initialized filesystem.
 Enable the filesystem using 'filesys enable'.
  9. Use # filesys enable to enable the file system. 
    # filesys enable
Please wait..............................
The filesystem is now enabled.

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