I'm struggling to find a workaround for my shortage of drive letters when I try to get cluster/cluster storage replication ready:
I have my 2 clusters, each with 16xDATA LUNs and 16xLOG LUNs ready to be configured for 16 SRPartnerships. So there is no way to assign a drive to volume. Each cluster has the DATA LUNs configured as CSV and mounted at the default location C:\ClusterStorage\... and I can successfully use "-SourceVolumeName C:\ClusterStorage\DATA01. So far so good :-)
I followed the same logic and mounted all my LOG LUNs at C:\SAN\... . When I try to create the SRPartnership, I use "C:\SAN\LOGx" for the source/destination LogVolumeName (that works for TEST-SRTopology after all). But half way thru the new-srpartnership cmdlet, I see the LOG disk changing into a CSV too and I assume its path changes to C:\ClusterStorage\LOGx? Anyway, I then get "New-SRPartnership : Unable to create replication group RG-DATA01, detailed reason: Unable to resolve log path C:\SAN\LOG01\ on this computer".
I assume I could start assigning drive letters for the 16 LOG volumes I have? But with 16 of ~20 available drive letters already used at day 1, that seems to be a bit limiting for our future here. Manually mounting the LOG volumes into C:\ClusterStorage before running New-SRPartnership, feels a bit risky and may be a supportability issue waiting to happen? Any better ideas? What's the preferred/supported way to handle this?
thanks a lot tips, tricks and solutions of any kind.
I have my 2 clusters, each with 16xDATA LUNs and 16xLOG LUNs ready to be configured for 16 SRPartnerships. So there is no way to assign a drive to volume. Each cluster has the DATA LUNs configured as CSV and mounted at the default location C:\ClusterStorage\... and I can successfully use "-SourceVolumeName C:\ClusterStorage\DATA01. So far so good :-)
I followed the same logic and mounted all my LOG LUNs at C:\SAN\... . When I try to create the SRPartnership, I use "C:\SAN\LOGx" for the source/destination LogVolumeName (that works for TEST-SRTopology after all). But half way thru the new-srpartnership cmdlet, I see the LOG disk changing into a CSV too and I assume its path changes to C:\ClusterStorage\LOGx? Anyway, I then get "New-SRPartnership : Unable to create replication group RG-DATA01, detailed reason: Unable to resolve log path C:\SAN\LOG01\ on this computer".
I assume I could start assigning drive letters for the 16 LOG volumes I have? But with 16 of ~20 available drive letters already used at day 1, that seems to be a bit limiting for our future here. Manually mounting the LOG volumes into C:\ClusterStorage before running New-SRPartnership, feels a bit risky and may be a supportability issue waiting to happen? Any better ideas? What's the preferred/supported way to handle this?
thanks a lot tips, tricks and solutions of any kind.