After upgrading to OneFS 8.0.0.3 we have reconfigured the protection from +2d:1n to +3d:1n1d. How can we verify this new level is fully implemented. After 24H we don't see any increase in used disk space. FlexProtect did also not run after this change.
FlexProtect isn't the correct job, it's job is re-protecting data in the event of a failure. SmartPools is what would change the protection level if you changed the cluster. Be sure you changed it in the right place, however. That would be in the default file pool policy.
"isi get" is the tool of choice for this kind of inspection; practically one can take some samples rather than checking the whole cluster. After SetProtectPlus or other jobs have finished successfully, one basically should trust it...
reprotect may sound scary, but is not -- repair status is scary...
reprotect simply means full protection is there as requested, but usually not in the most efficient way (using less nodes than available).
You would probably have noticed if there had been a node reboot during the SetProtectPlus run. Something I would check is wether the reprotect files have been modified (by regular client writes, check mtime) while SetProtectPlus was running.
Peter_Sero
6 Operator
•
1169 Posts
2016
0
Posted February 24th, 2017 07:00
Chris, good catch! Clearly SmartPools does the job, and in absence of a SmartPools license it would be SetProtectPlus, but not FlexProtect.
Gerard, sorry for that, cancel FlexProtect and run SetProtectPlus (or SmartPools with a license).
-- Peter