Dell EMC PowerProtect DDVE on Amazon Web Services 7.9 Installation and Administration Guide

Storage best practices

Use the appropriate storage type

Use GP3 EBS volumes for the root disk, NVRAM disk, and metadata disks.

Migrate from GP2 to GP3

Amazon EBS Elastic Volumes enable you to modify the volume type from GP2 to GP3 without detaching volumes or restarting instances, which means that there are no interruptions to your applications during modification.

To modify an Amazon EBS volume using the AWS Management Console:

Open the Amazon EC2 console.
Choose Volumes, select the volume to modify, and choose Actions, Modify Volume.
The Modify Volume window displays the volume ID and its current configuration, including type, size, IOPS, and throughput. Set new configuration values as follows:
- Volume Type: Select GP3
- IOPS: Set 3000
- Throughput (MB/s): Set 125
Select Modify. When prompted for confirmation, select Yes.
NOTE The recommended IOPS and throughput values for a GP3 volume are 3000 and 125, respectively. These values represent the baseline performance of a GP3 volume. If you set higher IOPS and throughput values, an additional fee is charged: $0.005 per IOPS per month over 3,000, and for throughput, $0.04 per MiB/s per month over 125 MiB/s.

Object storage specifications

The following table lists the supported instance types and their storage configuration for object storage.

Metadata disk storage is recommended to be 10% of the total capacity. Each metadata disk is recommended to be 1 TiB.

Table 1. Storage size specifications
DDVE configuration	Instance type	Root disk (GP3)	NVRAM disk (GP3)	Metadata disk (GP3)	Metadata disks required
16 TB	M5.xlarge	250 GiB	10 GiB	1024 GiB	1-2
32 TB	M5.2xlarge	250 GiB	10 GiB	1024 GiB	1-4
96 TB	M5.4xlarge	250 GiB	10 GiB	1024 GiB	1-10
256 TB	M5.8xlarge	250 GiB	10 GiB	2048 GiB	1-13

NOTE

If the incorrect instance type is used, the system displays an alert for an unsupported virtual hardware configuration.
The metadata requirements that are listed above are based on a 10x deduplication ratio and a 2x compression ratio. For workloads with a higher deduplication ratio, more metadata storage is required.
The maximum number of metadata disks that you can add to a DDVE instance in AWS is 24.

Block storage specifications

The following table lists the instance types and storage types that are required for block storage.

Table 2. Storage configuration types for DDVE in AWS (block store)
DDVE configuration	Instance type	Root disk type/size	NVRAM disk type/size	Data disk type/size
16 TB	M5.xlarge	GP3/250 GB	GP3/10 GB	GP3/1024 GB

NOTE

DDVE with block storage supports a maximum capacity of 16 TB. The recommended size of each data disk is one TiB.
If the incorrect instance type is used, the system displays an alert for an incorrect virtual hardware configuration.

Table 3. Supported stream and Mtree counts
System capacity	Instance type	vCPU	Memory (GiB)	Max Mtree	Stream counts
System capacity	Instance type	vCPU	Memory (GiB)	Max Mtree	Read	Write	Replication in	Replication out	Combined
16 TB	M5.xlarge	4	16	6	30	45	45	42	60
32 TB	M5.2xlarge	8	32	14	50	90	90	82	90
96 TB	M5.4xlarge	16	64	32	50	180	180	100	180
256 TB	M5.8xlarge	32	128	128	110	540	540	220	540

Metadata disk storage expansion notes

Dell EMC recommends to use 10% of the system capacity as the metadata storage, where each metadata disk size is one TiB. This metadata storage recommendation is based on 10X deduplication ratio and 2X compression. For workloads with a higher deduplication ratio, more metadata storage may be required. If metadata storage usage exceeds 80%, an alert is generated. Add a metadata disk to the DDVE immediately to avoid running out of space.

The DDOS Administration Guide provides a procedure for expanding storage. Dell EMC recommends that you always use 1 TiB metadata disks.

Spindle group

You are not required to specify a spindle group when adding metadata disks. The spindle group assignment is balanced automatically when adding storage. Do not set or change the spindle group settings manually. Run the storage show all command to verify that each data volume is assigned to a different spindle group.

Object storage bucket configuration notes

The bucket that is provided during file system creation must be empty, otherwise file system creation fails.
When the file system is destroyed, the associated bucket and the objects it contains are not automatically deleted or removed. The bucket must be intentionally deleted to avoid incurring the cost for the content stored in the bucket.
Do not enable S3 versioning on the bucket. Doing so incurs additional cost because older versions of the objects are retained, although they are removed by the GC cycles.
Do not configure any life-cycle policy on the bucket as it might result in loss of critical data.

Converting from evaluation to production

Rather than convert an evaluation version of DDVE to a production version, Dell EMC recommends a fresh deployment. If you decide to convert from an evaluation version to production version, Dell EMC recommends that you:

Destroy the existing file system
Delete any small data disk (not the root or NVRAM disks)
Configure new disks according to the recommendations in this guide

AWS Server-side encryption

AWS provides three server-side encryption options depending on how you choose to manage the encryption keys:

Server-Side Encryption with Amazon S3-Managed Keys (SSE-S3)
Server-Side Encryption with KMS keys Stored in AWS Key Management Service (SSE-KMS)
NOTE This is not recommended as there will be additional charges for using this service and performance may be impacted if AWS KMS throttles the request when you exceed an API request quota.
Server-Side Encryption with Customer-Provided Keys (SSE-C)
NOTE This option is not supported by DDVE.

For more information, see Protecting data using server-side encryption.

Welcome

Welcome to Dell