Hi, I've created my cluster in test with 7 cluster volumes all happily
migrating and failing over. However, are there any precautions I need to
take with regard to trustees on the volumes. When I move to production I
will be clustering heavily used NSS volumes with many trustee assignments.

Any and all guidance from the Guru's here is well received.

Cheers,
Ben.

On 22/07/08 Ben Johnston wrote:
> precautions I need to
> take with regard to trustees on the volumes

I'm not sure what you mean by this. What have you read or heard that
makes you ask? Precautions against what?
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://forums.novell.com/
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.

I remember seeing a discussion thread regarding the loss of trustees on a
cluster volume in either this forum or in another somewhere else, may have
been an earlier version of both Netware and/or NCS. Also in one of the
threads in this forum there was talk about backing up the trustees on the
volume before cluster enabling it.

So in regards to precautions, is there anything I need to do/worry about
when cluster enabling nss volumes?

>>> On 22/07/2008 at 10:31 am, in message
<WT9hk.10148$g35.3579@kovat.provo.novell.com>, Andrew C
Taubman<ataubman@no-mx.forums.novell.com> wrote:
> On 22/07/08 Ben Johnston wrote:
>> precautions I need to
>> take with regard to trustees on the volumes
>
> I'm not sure what you mean by this. What have you read or heard that
> makes you ask? Precautions against what?

On 22/07/08 Ben Johnston wrote:
> I remember seeing a discussion thread regarding the loss of trustees
> on a cluster volume in either this forum or in another somewhere else, may
> have been an earlier version of both Netware and/or NCS.

That would be NW 5.x, so that memory would be 5+ years old.


> Also in one of the
> threads in this forum there was talk about backing up the trustees on
> the volume before cluster enabling it.
>
I can't imagine why, cluster-enabling a volume does nothing to the
actual volume.


> So in regards to precautions, is there anything I need to do/worry
> about when cluster enabling nss volumes?

No.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://forums.novell.com/
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.

Adding to what Andrew said:

I have many clients with clustering working. Trustees have been zero
issues for my clients over the last 4 years, except for self generated
ones......(e.g. removing a trustee assignment via ConsoleOne).

Another change from NW5.x clustering is that clustering is now
separated at the pool level. I have several schools that put all the
student volumes (1 per grade level) on one pool. When a class
graduates, that volume is deleted and a new one for the up and coming
grade is created. This is a very quick way for a K12 to reallocate
storage.

The only issue the schools have seen is by the MACs. When you move a
cluster volume PCs easily reconnect. MACs do not.

Good luck, and you will like clustering.

--
Timothy Leerhoff

Thanks Andrew, I didn't realise it had been that long!
I appreciate your help.
Cheers,
Ben.

Andrew C Taubman wrote:
> On 22/07/08 Ben Johnston wrote:
>> I remember seeing a discussion thread regarding the loss of trustees
>> on a cluster volume in either this forum or in another somewhere else,
>> may have been an earlier version of both Netware and/or NCS.
>
> That would be NW 5.x, so that memory would be 5+ years old.
>
>
>> Also in one of the
>> threads in this forum there was talk about backing up the trustees on
>> the volume before cluster enabling it.
>>
> I can't imagine why, cluster-enabling a volume does nothing to the
> actual volume.
>
>
>> So in regards to precautions, is there anything I need to do/worry
>> about when cluster enabling nss volumes?
>
> No.

Ah Macs, my next question was around Cifs. I'm going to re-read the cifs
clustering because I'm not fully understanding it. I'll do that before
posting the question in the hope that it becomes clear.

thanks for your help Tim.

Cheers,
Ben.

Timothy Leerhoff wrote:
> Adding to what Andrew said:
>
> I have many clients with clustering working. Trustees have been zero
> issues for my clients over the last 4 years, except for self generated
> ones......(e.g. removing a trustee assignment via ConsoleOne).
>
> Another change from NW5.x clustering is that clustering is now
> separated at the pool level. I have several schools that put all the
> student volumes (1 per grade level) on one pool. When a class
> graduates, that volume is deleted and a new one for the up and coming
> grade is created. This is a very quick way for a K12 to reallocate
> storage.
>
> The only issue the schools have seen is by the MACs. When you move a
> cluster volume PCs easily reconnect. MACs do not.
>
> Good luck, and you will like clustering.
>

> Ah Macs, my next question was around Cifs. I'm going to re-read the
> cifs clustering because I'm not fully understanding it. I'll do that
> before posting the question in the hope that it becomes clear.

That is an easy answer. Setup CIFS the same on all servers. Make sure
you turn on CIFS when you create the resources (I normally do this in
NSSMU).

--
Timothy Leerhoff

I don't get the option to enable this during the virtual server and virtual
volume object creation in consoleOne, so I've been enabling this after the
fact in NRM. Is that the same or have I stuffed something up?



>>> On 23/07/2008 at 6:36 am, in message
<6xrhk.10573$g35.8656@kovat.provo.novell.com>, Timothy
Leerhoff<tleerhoffNO@SPAMqwest.net> wrote:
>> Ah Macs, my next question was around Cifs. I'm going to re-read the
>> cifs clustering because I'm not fully understanding it. I'll do that
>> before posting the question in the hope that it becomes clear.
>
> That is an easy answer. Setup CIFS the same on all servers. Make sure
> you turn on CIFS when you create the resources (I normally do this in
> NSSMU).

Using NSSMU to create the Pool you will see a screen similar:

+------------------------------------------------------------+
| Create Pool |
|------------------------------------------------------------|
| Pool Name: TEST |
| Pool Size: 9206 MB |
| |
| Activate on Creation: Yes |
| Cluster Enable on Creation: Yes |
| |
| Shared Pool Clustering Parameters |
| Virtual Server Name: 197C1_TEST_SERVER |
| CIFS Server Name: 197C1_TEST_W |
| IP Address: 10 .10 .10 .10 |
| |
| Advertising Protocols |
| NCP: Yes |
| CIFS: Yes |
| AFP: No |
| |
| Create Cancel |
+------------------------------------------------------------+

Note the CIFS server name and Advertising Protocols. I fill these in.

--
Timothy Leerhoff

And in the cluster resource script you should see something like...

CIFS ADD .CN=C1_TEST_SERVER.OU=Tech.O=ORG.T=Tree.


--
Timothy Leerhoff

What if my pools are existing and I'm migrating these to the cluster?

I have 7 pools that I have shared for clustering. Can I add this manually?

>>> On 24/07/2008 at 6:30 am, in message
<WxMhk.10969$g35.7254@kovat.provo.novell.com>, Timothy
Leerhoff<tleerhoffNO@SPAMqwest.net> wrote:
> And in the cluster resource script you should see something like...
>
> CIFS ADD .CN=C1_TEST_SERVER.OU=Tech.O=ORG.T=Tree.
>

Yes you can.

As a template you might want to create a small new pool in the cluster
and copy the start/unload scripts to the original pools. remember to
change the volid (must be unique in the cluster), the IP(s), volume
names, etc in both scripts

--
Timothy Leerhoff

Ben Johnston wrote:
>>> So in regards to precautions, is there anything I need to do/worry
>>> about when cluster enabling nss volumes?

While I have used cluster enabled volumes for many years an not had any
problems with loosing trustee assignments, still it's very easy to
make a backup of your trustee's in the off chance that you may need to
restore them.
So, I recommend make a backup of trustees any way. It's a small step that
can return BIG rewards if ever needed.
BB