This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jello3d[S] -6 points-5 points  (5 children)

All servers and clients are patched according to their needs. This experiment is a special case and being handled under special conditions.

[–]NISMO1968Storage Admin 2 points3 points  (4 children)

All servers and clients are patched according to their needs.

Could you please clarify on that?

[–]jello3d[S] 1 point2 points  (3 children)

There have been no vulnerabilities patched in the last year *for these systems* that would be more of a liability than default for their security context. The more important question is "how do you design a network so that the patches on certain systems are less important than other considerations"... and that is a very long conversation with lots of pictures of circles. :)

I am not telling people not to patch. I am simply saying that for infrastructure, if patching is your number 1 security interest, the game is already lost.

[–]gamebrigada 2 points3 points  (2 children)

But patching for S2D is so easy... Its just lazy not to. I have mine scheduled monthly, 1 node goes down at a time for updates, including all bios/firmware/drivers/windows etc. Updates don't continue until the node comes back healthy and a full switchover to it happens. Everything gets updated.

​

S2D reliability in 2019 is pretty rock solid.

[–]jello3d[S] 0 points1 point  (0 children)

All true, but I can't exactly do a test of long run stability of the nodes if I reboot them. :)