To check the access status data synchronization configuration status, execute the esfast heatmapsync status command.
Note
If the synchronization target Tier pool is changed due to changing the Storage Cluster settings while synchronizing the access status data, the access status data synchronization processing is interrupted. To restart the synchronization process, re-executing Automated Storage Tiering for the synchronization target Tier pool is required.
If the access status data currently being synchronized in the synchronization target Tier pools have a one-to-N relationship, the access status data synchronization process continues temporarily between the currently synchronized Tier pools. However, when service restarts or Automated Storage Tiering is re-executed, the access status data synchronization no longer starts. For this reason, in order to start the access status data synchronization process, reviewing the Storage Cluster environment settings so that there is a one-to-one relationship with the synchronization target Tier pools is required. Refer to "3.9.2 Starting Access Status Data Synchronization" for the conditions for starting the access status data synchronization process.
If communication is lost with the storage device during an access status data synchronization, the access status data synchronization process is suspended. After that, if communication is restored, the access status data synchronization process is restarted.
If the TFO group where FTVs in a Tier pool belong was created/recreated after Automated Storage Tiering was started, the access status data synchronization of that Tier pool is not performed. To perform access status data synchronization, Automated Storage Tiering on either of the synchronization target Tier pools must be restarted.
See
Refer to "Operation Method" described in "Storage Cluster Function" in the ETERNUS SF Storage Cruiser Operation Guide for the method to check the status of the TFO groups for the Storage Cluster function.
