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
4 Operator
•
1.2K Posts
0
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
Peter_Sero
4 Operator
•
1.2K Posts
0
February 24th, 2017 04:00
Which jobs are running or queued? If FlexProtect(LIN) or Smartpools don't show up, start by hand.
-- Peter
Gerard_vdl
1 Rookie
•
5 Posts
0
February 24th, 2017 05:00
No Jobs are running or are queued. I have started Flexprotect by hand.
We will wait and see after the weekend for the results.
Regards Gerard
Gerard_vdl
1 Rookie
•
5 Posts
0
February 24th, 2017 07:00
Gents, thanks for the update we don’t have a license so I have started SetProtectPlus.
Gerard
crklosterman
450 Posts
1
February 24th, 2017 07:00
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.
~Chris
Gerard_vdl
1 Rookie
•
5 Posts
0
March 7th, 2017 23:00
Peter, SetProtectPlus ran for 10 days and is finished.
Is there a way to check if the new setting really is reflected on the whole cluster?
Gerard
Eric_W1
33 Posts
3
March 8th, 2017 04:00
You can spot check with the cli.
ritstor-1# isi get -Dd /ifs | grep Protection
* Protection False
* Protection Policy: default
* Current Protection: 8x
* Future Protection: 0x
* Protection attributes: active
* Protection Policy: default
Peter_Sero
4 Operator
•
1.2K Posts
0
March 14th, 2017 03:00
"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...
-- Peter
Gerard_vdl
1 Rookie
•
5 Posts
0
March 23rd, 2017 00:00
In contrast to the first cluster, the second shows a lot of files and directories with the status reprotect
The SetProtectPlus job on this cluster ran for a shorter period of time but also finished successfully.
Maybe start the job again?
Peter_Sero
4 Operator
•
1.2K Posts
0
March 23rd, 2017 10:00
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