From DDOS 6.x, a new licensed feature called LTR is introduced.
For an overview/introduction to LTR in the cloud, see the KB article 487657:
Data Domain: An introduction to long term retention/cloud tier cleaning/garbage collection on Data Domain Restorers (DDRs)
For various
DDOS 6.x releases, when a cloud unit is added, each cloud unit creates 3 buckets in the cloud. The naming convention for the buckets are as follows:
- A 16 character hexadecimal string
- A dash character ('-')
- Another 16 character hexadecimal string
- Another dash character ('-')
- One of the following strings, '-c0', '-d0', '-m0'
The hexadecimal strings are the same per cloud unit and unique to the system where the cloud unit was created. They are calculated during the cloud unit creation by generating a Universal Unique Identifier (UUID) in order for them to be uniquely named should a cloud provider host multiple cloud units.
For example, from a cloud providers namespace, the following buckets are seen once a cloud unit is created:
==================================================================
e16a5e5e907683bd-4c97fbf23f7faab1-c0
e16a5e5e907683bd-4c97fbf23f7faab1-d0
e16a5e5e907683bd-4c97fbf23f7faab1-m0
==================================================================
For
DDOS 7.x and later releases, when a cloud unit is added, each cloud unit creates a single bucket in the cloud as follows:
==================================================================
80a31b61fc4c155a-b2a452f7a35f7254-d0
==================================================================
To understand what cloud unit buckets are being used by a system, the registry has to be queried. Log in to the DDR as a user with sysadmin privileges and run the the following command:
==================================================================
sysadmin@dd01 # reg show config_floating.cloud.unit.name
==================================================================
The output of the above command shows the unique hexadecimal string used (as described above) by this system for the cloud unit. For example, if there were two cloud units configured on a system, the output of the above command shows the following:
==================================================================
config_floating.cloud.unit.name.80a31b61fc4c155a-b2a452f7a35f7254 = azure-unit
config_floating.cloud.unit.name.e16a5e5e907683bd-4c97fbf23f7faab1 = ecs-unit1
==================================================================
From above output, when 'ecs_unit1' was added, system was running DDOS 6.x code, hence created three buckets named above.
Whereas, when azure-unit was added after DDOS 7.x version, it created single bucket name above.