Dell EMC PowerProtect DDVE on Google Cloud Platform 7.9 Installation and Administration Guide

Storage type

Ensure that you use the appropriate storage type. DDVE on GCP uses the standard persistent disk (HDD) for the root disk. The NVRAM disk and all metadata disks use the SSD persistent disk.

Object storage specifications for DDVE on GCP

The following table shows the instance types and storage types that are required for the Object Store. The compression ratio in your environment might require more metadata disks.

Table 1. Storage Configuration Types for DDVE on GCP

DDVE Configuration	Instance Type	Root Disk/Size	NVRAM Disk	Metadata Disk	Number of Metadata Disks	Data Storage
16 TB	e2-standard-4	SSD persistent disk/250 GB	SSD persistent disk/10 GB	SSD persistent disk/1024 GB	1-2	Google Cloud Storage (Regional is recommended)
32 TB	e2-standard-8	SSD persistent disk/250 GB	SSD persistent disk/10 GB	SSD persistent disk/1024 GB	1-4	Google Cloud Storage (Regional is recommended)
96 TB	e2-standard-16	SSD persistent disk/250 GB	SSD persistent disk/10 GB	SSD persistent disk/1024 GB	1-10	Google Cloud Storage (Regional is recommended)
256 TB	e2-standard-32	SSD persistent disk/250 GB	SSD persistent disk/10 GB	SSD persistent disk/2048 GB	1-13	Google Cloud Storage (Regional is recommended)

GCP Machine Types provides more details about GCP instance types.

Storage Specifications for Block Storage for DDVE on GCP

The following table shows the instance types and storage types that are required for Block Storage. Each instance type supports both Block Storage and Object Storage solutions, but the maximum supported capacity is 16 TB.

Table 2. Storage Configuration Types for Block Storage

DDVE Configuration	Instance Type	Root Disk/Size	NVRAM Disk	Data Disk
16 TB	e2-standard-4	SSD persistent disk/250 GB	SSD persistent disk/10 GB	SSD persistent disk/2048 GB

GCP Machine Types provides more details about GCP instance types.

Storage Size Specifications

The compression ratio in your environment might require more metadata disks.

Table 3. Storage size specifications

Capacity Configuration	Instance Type	Storage Configuration Type
		Root Disk	NVRAM Disk	Metadata Disk
Up to 16 TB	e2-standard-4	250 GB	10 GB	2 x 1024 GB
16 TB–32 TB	e2-standard-8	250 GB	10 GB	4 x 1024 GB
32 TB–96 TB	e2-standard-16	250 GB	10 GB	10 x 1024 GB
96 TB–256 TB	e2-standard-32	250 GB	10 GB	13 x 2048 GB

Supported Stream Count

Table 4. Supported stream and MTree count (Object Storage)

Capacity Configuration (TiB)	Instance Type	vCPUs	Memory	Max MTree	Stream Counts
					Read	Write	Replication In	Replication Out	Combined
16	e2-standard-4	4	16	6	30	45	45	42	60
32	e2-standard-8	8	32	14	50	90	90	82	90
96	e2-standard-16	16	64	32	50	180	180	100	180
256	e2-standard-32	32	128	128	110	540	540	220	540

Table 5. Supported stream count (Block Storage)

Capacity Configuration (TiB)	Instance Type	vCPUs	Memory	Max MTree	Stream Counts
					Read	Write	Replication In	Replication Out	Combined
16	e2-standard-4	4	16	6	30	45	45	45	60

Metadata Disk Storage Expansion Notes

You can deploy metadata disks incrementally. The minimum incremental size is 1 TiB. Add metadata disks as required up to the supported system capacity. The following table lists the recommended number of metadata disks by instance. The information is based on the assumption of 2X overall deduplication ratio (10X deduplication and 2X compression). For workloads with a higher deduplication ratio, additional metadata storage is required.

Table 6. Recommended metadata disks by instance

Instance	Recommended metadata disks
16 TB	2 (1 TB)
32 TB	4 (1 TB)
96 TB	10 (1 TB)
256 TB	13 (2 TB)

When adding the volume, there is no requirement to specify a spindle group. The spindle group assignment is balanced automatically when storage is added. It is recommended that you do not manually set or change the spindle group setting. Run storage show all to verify that each data volume has been assigned to a different spindle group.

Data Storage Configuration Notes for Object Storage Solution

• 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 deleted intentionally to avoid incurred costs with the content stored in the object store.