#SnapMirror of cloud tiered volume
1 messages · Page 1 of 1 (latest)
are you using system manager to administer teh system
you can see that info from system manager
If I'm understanding it correctly: If you are replicating to another system every day none of your replicated blocks should be read from the cloud tier because they would all still the hot.
Only after 2 days they get cold but you already replicated them.
Of course you would need to make sure you are actually replicating a new snapshot every day (or the active file system). That way all new blocks would be read from the performance tier.
Of course if other processes read cold blocks and modify them they would get hot, moved to the performance tier and since these are changed blocks they would get replicated to the destination system.
System Manager only shows the total data there have been transfered, now how much of these data there is from Local Tier and Cloud Tier.
The data we rsync is old data. I can see that data is moved to the cloud tier.
Before I changed the tiering policy it took lets say 20 minutes to snapmirror 70GB to the other system. now it can take 12 hours to transfer 35GB.
open a tech support case with NetApp
as i suspect this will involve some troubleeshotting sa change in policy could be a coincidence and to find the true cause few additional steps such packte traes etc.. will be requied
Are you looking for something along the lines of "aggr show -fields composite-capacity-tier-used" OR "storage aggregate object-store show-space"?