...

Note: For version 4.1, SmartTiers™ only supports storage tiers residing in the same cloud.  Configuration of tiers that span multiple clouds is not supported. Note: Dual Controller HA™ is not supported in conjunction with a SmartTiers™ deployment, even should the deployment consist of only object storage. 

• Preliminary Steps
• Configuring SmartTiers™
• Managing an Existing SmartTiers™ Migration Policy
• Increase Capacity of SmartTiers™ 
• Cool or Infrequently Accessed Storage

Preliminary Steps

To begin creating your SmartTiers™ solution, several preliminary tasks should be completed:

...

Note: If leveraging object storage (such as S3 or Azure Blob) for your infrequently accessed tiers, it is best practice not to use software RAID configuration for those tiers, as you will see limited performance gains, if any at all. If leveraging HDD block devices, RAID can be leveraged to improve performance.

Configuring SmartTiers™

1. As mentioned above, if SmartTiers™ is to be leveraged, it is configured when creating the storage pool. To begin creating a SmartTiers™ Configuration, select Storage Pools in the Storage Administration pane. 
   
   
   
   
   
2. Click Create, and then select the SmartTiers™  radio button. Click Next to begin the process.
   
   
3. First, we will be configuring the primary tier, also referred to as the Hot tier. This is the tier which will be most frequently accessed, and should provide a high performance index. 
   1. Assign a name to your Hot tier. 
   2. Select the RAID configuration that you planned for. In the below example software RAID is not leveraged (No RAID,JBOD). If leveraging RAID, additional disks would be selected, based on the RAID selection. 
   3. Select the desired Disks for your configuration. To be leveraged in Software RAID, disks must be of the same type and size. Ensure that the disks selected are those with the best performance index.
   4. Click Next. 
      
      
   
   
   
4. SmartTiers™ requires a minimum of 2 tiers to be configured. The second tier is referred to as the "Warm" tier to differentiate it from later "Cold" tiers in more complex configurations. As you can see, the second tier operates the same as the primary.
   1. Provide the second tier a name.
   2. Determine the RAID level.
   3. Select disks of the storage type designated for your secondary tier.
   4. If you plan to only have 2 tiers, select Next to proceed to the next step of the SmartTiers™ creation. To add additional tiers, select Add another tier.
      
      
   
   
   
5. For simplicity's sake, we will stop here at two tiers. The process continues in the same manner. In other words, if mirroring the described configuration, click 'Next' to proceed, rather than Add Another Tier. If you wish to add more tiers, select Add Another Tier. You will now assign a name to the SmartTiers™ configuration. This will be the name used when creating the Volume to be used.  Select Finish to proceed.  If you need to make changes, you can select Back to return to the previous panel.
   
   
   
   
   
6. The final step in creating your SmartTiers™ configuration is to establish the migration policy that will be used to govern each of the tiers. 
   
   1. Maximum Block Age refers to the amount of time a block of data has not been accessed, and is therefore eligible to be migrated to the next tier.
      
      
   2. Reverse Migration grace period refers to when blocks of data that have been accessed by a read inquiry will be moved back up the hierarchy.
      
      Note: Maximum Block Age does not apply to the last tier in the hierarchy. Nor does the Reverse Migration Grace Period apply to the Hot Tier.
      
      
   3. The Migration interval in Device options controls the frequency that SmartTiers™ will check for blocks needing to be migrated, based on the specific tier policies.
      
      
   4. Hot Tier Storage Threshold allows you to set a high-water mark on the tier which will force a migration to be done to move blocks to the secondary tier. In other words, if the data on the Hot Tier reaches the specified percentage, the blocks accessed the least frequently will be moved to ensure the Hot tier does not fill its available space.
      
      
   5. The Alternate Block Age is used when the “Hot Tier Threshold” has been met.  This will override the Maximum Block Age value specific to determine which blocks will be moved.
      
      
   6. You can also set a specific daily schedule for migrations to be allowed.  This is in a 24hour format.
   
   Both Maximum Block Age and Reverse Migration Grace Period are calculated to the second. The default time period for Maximum Block Age is 24 hours which, counted in seconds, equals 86400. The default for Reverse Migration Grace Period is by the same token 12 hours. To determine your settings, use these default values to calculate the time frame for each tier.
   
   

   Note: During the 100TB data grow test performed by QA on a SmartTier pool the following issue was noticed:
   
   

   • During a large data transfer to the SmartTier pool a high number of s3backer timeouts were noticed when an aged blocked migration occurred. These timeouts resulted in an impact to the data transfer speed and stability.

   Based on this behavior it was determined that the Maximum block age for all tiers should be set to 2592000 (30 days) for the Tiered device, to avoid an automatic migration from occurring while the initial large data transfer is in progress. Once the initial data has been transferred to the SmartTier pool, this value can be change to one more appropriate for the environment.

   
   
   

Managing an Existing SmartTiers™ Migration Policy

Now that SmartTiers™ has been configured, let's look at how to view and change settings for the Migration Policy on an existing SmartTiers™.

1. To open the Migration Policy, return to Disk Devices from the Storage Administration pane where you will see the disk listed as /dev/sdtiera, with the make and model of SoftNAS SmartTiers™ Storage Device.
   
   
   
   
   
2. When this disk is selected from the Disk Device list,  the Configure option will become available. Select Configure to open the Tiered Storage Configuration Wizard.
   
   
   
   
   
3. In the Tiered Storage Configuration Wizard you can alter the migration policy as well as set specific parameters for the Hot tier.
   
   
   
   
   1. The Migration interval in Device options controls the frequency that SmartTiers™ will check for blocks needing to be migrated, based on the specific tier policies.
      
      
   2. Hot Tier Storage Threshold allows you to set a high-water mark on the tier which will force a migration to be done to move blocks to the secondary tier. In other words, if the data on the Hot Tier reaches the specified percentage, the blocks accessed the least frequently will be moved to ensure the Hot tier does not fill its available space.
      
      
   3. The Alternate Block Age is used when the “Hot Tier Threshold” has been met.  This will override the Maximum Block Age value specific to determine which blocks will be moved.
      
      
   4. You can also set a specific daily schedule for migrations to be allowed.  This is in a 24hour format.
      
      
4. Select Save once all the changes have been applied.

Increase Capacity of SmartTiers™ 

Increasing the capacity of your SmartTiers™ configuration is simple:

...