Hey guys,
I'm in a bit of a pickle with something. Because of reasons we are scripting our own powershell module with which we can do all lun-management on our servers
instead of using snapdrive for windows (not supported anymore on windows server 2019). (using the data ontap powershell toolkit for this). used protocol is iSCSI
I have run into a problem when this module is used in a clustered environment (for use with Availability groups). When we use the scripted module to create
luns on storage level and then initialize them on the server, basically they get seen as shared for some reason. The thing is, in this scenario we don't need them to be shared. It's ok for these servers to have their own dedicated storage.
Because they are put to be shared, we run into the problem that disks which we create after the cluster is made, won't automatically be put online after a
rebout because of the san policy.
https://support.microsoft.com/en-us/help/2849097/how-to-set-the-partmgr-attributes-registry-value-using-powershell
So there is a number of things which i can do:
-I can bypass the problem apparantly by just adding all the storage (luns) first and then forming the cluster. (disks which are added before don't have the
issue)
-Maybe changing the san policy on the servers in question(in clustered environments they do say you should leave it on sharedoffline
-or maybe tweak the disks somehow maybe
Is there someone who knows how i can check if a disk is shared or not (preferably by using PS)?Maybe how i can tweak it too? What would your recommondations be?
thanks in advance guys!