Fsx for netapp volume capacity tiering

0
  1. How do you find out how much data has been tiered to capacity tier storage for a specific volume via ontap cli?
  2. When defining a volume size, is this space only for performance tier or is it for both performance tier and capacity tier?
demandé il y a 6 mois323 vues
1 réponse
0
Réponse acceptée

1. How do you find out how much data has been tiered to capacity tier storage for a specific volume via ontap cli? FSx for ONTAP provides ONTAP CLI. In order to monitor how much data of a volume is in Performance and Capacity tiers, the "volume show-footprint" can help. ONTAP storage has the concept of aggregates where Performance and Capacity storage are distributed into. They are typically identified by a "binX" value, where "bin0" refers to the performance tier, while "bin1" refers to Capacity tier.

With this assumption, some of the fileds of the "volume show-footptint" command specifically show "bin" names, and associated used storage.

Examples:

For all available volumes, list a subset of fields: vserver name, volume name, bin0 identifier and associated used storage, bin1 identifier and associated used storage: > volume show-footprint -fields vserver,volume,bin0-name,volume-blocks-footprint-bin0,bin1-name,volume-blocks-footprint-bin1

If the need is to see the same data for a single identifiable volume: > volume show-footprint -vserver $vservername -volume $volumename -fields vserver,volume,bin0-name,volume-blocks-footprint-bin0,bin1-name,volume-blocks-footprint-bin1

2. When defining a volume size, is this space only for performance tier or is it for both performance tier and capacity tier? FSx for ONTAP volumes are only virtual construct, and as such the size defined at creation time (and also when changing it post-creation) is a logical size that will be made up of a combination of space occupied on both Performance and Capacity tiers. Volumes themselves do not consume file system storage capacity, but only data stored in a volume consume Performance AND Capacity storage based on tiering policy. Volume size can infact be greather than File System size, and that can also be changed later, while File System size can only be increased. More information is available at https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/volume-storage-capacity.html.

AWS
répondu il y a 5 mois

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions