Planning Combined / Archive Storage Tiers

Archive (COLD) tier can be implemented using either the combined storage class or archive storage class options. Choose an appropriate option for your use case using the following table:

Storage Class	Combined Storage Class	Archive Storage Class*
Storage Classes	Amazon S3 Standard/Glacier (Combined Storage Tiers) Standard-IA/Glacier (Combined Storage Tiers) One Zone-IA/Glacier (Combined Storage Tiers) Intelligent-Tiering/Glacier(Combined Storage Tiers) Standard/Deep Archive (Combined Storage Tiers) Standard-IA/Deep Archive (Combined Storage Tiers) One Zone-IA/Deep Archive (Combined Storage Tiers) Intelligent-Tiering/Deep Archive (Combined Storage Tiers)	Amazon S3 Glacier Deep Archive
	Microsoft Azure Storage Hot/Archive (Combined Storage Tiers) Cool/Archive (Combined Storage Tiers)	Microsoft Azure Storage Archive
Deduplication	Deduplication Supported. Combined storage class is recommended for deduplicated backups. For deduplicated data, make sure to seal the DDB every 6 months, to make sure that the data is periodically pruned. This can be done by setting the value of Create new DDB every [] days option to 180 in the Storage Policy Copy Properties dialog box. For more information about Deduplication Database Creation settings, see Deduplication - Settings. For more information about accessing this option, see Modifying the Deduplication Properties for a Storage Policy Copy. In addition, as a DDB reconstruction will require all the data to be recalled, it will be very expensive. Hence, choose the Seal and Start new DDB automatically on detection of inconsistency option. For more information about the DDB Availability Option, see Deduplication - Settings. For more information about accessing this option, see Modifying the Properties for Deduplication Database Recovery. Micro-pruning is not supported. Hence, ensure that micro-pruning is disabled. For more information on disabling micro-pruning, see Configuring Micro Pruning.	Deduplication Supported. Ensure that the following options are configured on these storage classes: For deduplicated data, make sure to seal the DDB every 6 months, to make sure that the data is periodically pruned. This can be done by setting the value of Create new DDB every [] days option to 180 in the Storage Policy Copy Properties dialog box. For more information about Deduplication Database Creation settings, see Deduplication - Settings. For more information about accessing this option, see Modifying the Deduplication Properties for a Storage Policy Copy. In addition, as a DDB reconstruction will require all the data to be recalled, it will be very expensive. Hence, choose the Seal and Start new DDB automatically on detection of inconsistency option. For more information about the DDB Availability Option, see Deduplication - Settings. For more information about accessing this option, see Modifying the Properties for Deduplication Database Recovery. Micro-pruning is not supported. Hence, ensure that micro-pruning is disabled. For more information on disabling micro-pruning, see Configuring Micro Pruning.
	Non deduplicated data is not recommended. All the data will remain in the regular tier and archive tier will not be used.	Non deduplicated data is supported.

* Archive storage as the primary copy for the following Exchange agents is not recommended:

Exchange Compliance Archiver
Exchange Database
Exchange Mailbox
Exchange Mailbox (Classic)
OnePass for Exchange Mailbox (Classic)