Copyright © 2022 NetApp Inc. All rights reserved.
class ConsistencyGroupTieringSchema (*, only: Union[Sequence[str], Set[str]] = None, exclude: Union[Sequence[str], Set[str]] = (), many: bool = False, context: Dict = None, load_only: Union[Sequence[str], Set[str]] = (), dump_only: Union[Sequence[str], Set[str]] = (), partial: Union[bool, Sequence[str], Set[str]] = False, unknown: str = None)
The fields of the ConsistencyGroupTiering object
control POST PATCH
Storage tiering placement rules for the object.
policy GET POST
Policy that determines whether the user data blocks of a volume in a FabricPool will be tiered to the cloud store when they become cold.
FabricPool combines flash (performance tier) with a cloud store into a single aggregate. Temperature of a volume block increases if it is accessed frequently and decreases when it is not. Valid in POST or PATCH.
all ‐ Allows tiering of both Snapshot copies and active file system user data to the cloud store as soon as possible by ignoring the temperature on the volume blocks.
auto ‐ Allows tiering of both snapshot and active file system user data to the cloud store
none ‐ Volume blocks are not be tiered to the cloud store.
snapshot_only ‐ Allows tiering of only the volume Snapshot copies not associated with the active file system.
The default tiering policy is "snapshot-only" for a FlexVol volume and "none" for a FlexGroup volume. The default minimum cooling period for the "snapshot-only" tiering policy is 2 days and for the "auto" tiering policy it is 31 days.