Symcli Server

Question

If we are trying to bring up a new symcli server we have to mask vcmdb device to this server right?

The new symcli server we are trying to bring up is one of the server's in a windows cluster environment. I know that we need the gatekeeper size to be atleast 8MB if we are running symcli on a cluster environment but since we are using only one of the servers in the cluster does the rule still hold? or a 3MB device would suffice???

xe2sdc · Accepted Answer

Have a look at primus solution 1.0.62760877.2557086

In a clustered environment devices without a signature MAY not be available (no further details on this issue).. There are a couple of fixes from M$ however since you can use any small device as a GK, you can avoid hotfixes and create "bigger" gatekeepers. Please note that you need however to put a signature on the gatekeepers before being able to use them since M$ cluster installs a driver that hides devices without a signature. Please note that Disk Administrator forbids to put a signature on volumes smaller then 8Mb .. and that's the main reason for having "bigger" gatekeepers (or fixes from M$)

So in a word .. yes you need big gk since your host is clustered.

xe2sdc · Answer

VCMdb is a very special device that is always visible, regardless of actual masking.
There are exceptions to the above mentioned rule, however generally speaking VCMdb device is always visible, thus you have only to create zones for your new server. When your "symcli server" can see the VCMdb you use Solution Enabler to add more gatekeepers to your "symcli server" (something we already covered in another thread).

I suspect that the "issue" with smaller gatekeepers may come from windows disk administrator and cluster services thus you need "big" gatekeepers. Can you please quote a primus solution dealing with bigger gatekeepers and M$cluster ??

protoss · Answer

It is writtten in 'Installing Solutions enabler' document that we need 8MB devices as gate keepers in case of windows cluster enviroment. That was what I was refering to.

protoss · Answer

So do we really need 8MB devices in my case as we are not using both the servers in the cluster?

I do not have much experience working on windows clusters so really do not have an idea how things work over here. Excuse if it is a silly question.

xe2sdc · Answer

It's M$ stuff .. ask your Windows administrators what a signature is

A little googling reveals this page .. maybe it isn't the best one .. however it's a starting point ....

http://windowsitpro.com/article/articleid/2825/windows-nt-disk-administrator.html

Maybe someone else may give better details on "signatures"

protoss · Answer

Thank you Stefano for being patient. I appreciate your quick responce. I did a bit of googling and went through some stuff. Thanks for posting the link though.:)

protoss · Answer

What does putting a signature mean? How to do that? Is there any document where I could get that information?

xe2sdc · Answer

We are always interested in updates

protoss · Answer

Yes, I figured that out. Stefano I found an other Primus solution which stated that this problem was resolved in Windows 2000 SP2. I spoke to other members of my team and they said that they have never used signature on their disks( I am a new employee here ). We are going to use 3MB devices for now. I will keep you guys posted ( If some1 is Interested)

It might take some time as the some work is going on at the server end.

protoss · Answer

Will do but as I said it is going to take some time.

Symmetrix

Symcli Server

Was this post helpful?