Does anyone have a good set of recommendations for a datastore naming convention?
That is why we did it.
And yes, it could cause issue if you are replicating, because the name wouldbe duplicated on the other side
In that case, you could do arrayIDpair like this:
DMX-0595_0445-T1-R to say that this is a Tier1 replicated device on DMX between array 0595 and 0445.
I tend to use something like this:
<TYPE> - <TIER> - <UNIQUE ID> - <Replicated>
Examples:
DAS-T3-VOL01 = Direct attached, Tier 3, Vol 1
EQL-T1-VOL01-R = EqualLogic SAN, Tier 1, Vol 1, Replicated
Would be interested to hear what others use as well...
can use something like
TYPE DATASTORE# LUN#
ie. Prod_01_001
Dev_05_005
I always used someting nearly identical (although we didn't replicate, so no -R).
We did:
TYPE-ARRAYID-LUNID
So, for example:
DMX-0595-0ABC
Thanks for the input. So the idea of the array ID being that I would be able to give the storage team quick identification of what LUN is associated with my datastore. Would that cause any issues if I'm replicating the datastore using SRM to a site with a different array ID behind the datastore?
That is why we did it.
And yes, it could cause issue if you are replicating, because the name wouldbe duplicated on the other side
In that case, you could do arrayIDpair like this:
DMX-0595_0445-T1-R to say that this is a Tier1 replicated device on DMX between array 0595 and 0445.
OK great thanks again.