Soldato
- Joined
- 22 Aug 2005
- Posts
- 8,845
- Location
- Clydebank
Hi all
Anyone familiar with this.?
I have a 2 node cluster setup hooked up via iSCSI to our SAN, which is acting as a fileserver, serving out 100+ shares among other things.
Now, I don't fully understand this so let me explain
The cluster server has 2 groups - cluster group, and main fileserver group. This contains physical hard disks, network name (FILE-cluster, ip address, and a whole bunch of shares.
I understand that splitting these down can improve performance which moving or falling back, and my tests have shown this to be the case.
I created a 3rd group called FTP-cluster and created new net name, gave a different ip address and added the FTP Iscsi disk, and added in the FTP home directory root, and shared out all subdirectories.
My FTP servers can mount this share and everything is hunky in that respect.
But - the problem is if i visit \\FILE-cluster I can see the shares in the \\FTP-cluster group and vice versa. I can use either IP to directly access either one.
It appears using groups only has any benefit/meaning on the admin/cluster admin side of things (can specify more granular fall back/failover etc) but has NO effect on the 'user' side of things. i.e. I don't want people using resources on FILE-cluster to see anything that's shared out via FTP-cluster. FTP-cluster is to be seen by FTP servers only , not humans (unless they explicitly veiw it by visiting FTP-cluster.
Can anyone advise?
Anyone familiar with this.?
I have a 2 node cluster setup hooked up via iSCSI to our SAN, which is acting as a fileserver, serving out 100+ shares among other things.
Now, I don't fully understand this so let me explain
The cluster server has 2 groups - cluster group, and main fileserver group. This contains physical hard disks, network name (FILE-cluster, ip address, and a whole bunch of shares.
I understand that splitting these down can improve performance which moving or falling back, and my tests have shown this to be the case.
I created a 3rd group called FTP-cluster and created new net name, gave a different ip address and added the FTP Iscsi disk, and added in the FTP home directory root, and shared out all subdirectories.
My FTP servers can mount this share and everything is hunky in that respect.
But - the problem is if i visit \\FILE-cluster I can see the shares in the \\FTP-cluster group and vice versa. I can use either IP to directly access either one.
It appears using groups only has any benefit/meaning on the admin/cluster admin side of things (can specify more granular fall back/failover etc) but has NO effect on the 'user' side of things. i.e. I don't want people using resources on FILE-cluster to see anything that's shared out via FTP-cluster. FTP-cluster is to be seen by FTP servers only , not humans (unless they explicitly veiw it by visiting FTP-cluster.
Can anyone advise?