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.
NOTE For GCP, the hard limit of total throughput per instance is 120 MB/s. The HDD disk cannot meet this requirement.
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
NOTE If DDVE in GCP uses the incorrect instance type, an incorrect virtual hardware configuration alert appears.
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
NOTE If DDVE in GCP uses the incorrect instance type, an incorrect virtual hardware configuration alert appears.
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
NOTE The metadata requirements that are listed for supported virtualization platforms are based on 10X deduplication ratio and 2X compression. Your system configuration may require a higher storage ratio. Expand the storage if required.
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.
Data is not available for the Topic
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: <>()\