2 Intern

 • 

1.1K Posts

April 21st, 2009 02:00

Clusters can do weird things sometimes... have you tried explicitly specifying the volumes for physical and virtual nodes and seen what happens?

April 21st, 2009 06:00

Yes, we tried saveset All and explicit volumes. We tried backup command
save and save -c virtnode. No difference.

4 Operator

 • 

14.4K Posts

April 21st, 2009 07:00

This is known issue - contact support for patch.

2 Intern

 • 

1.1K Posts

April 21st, 2009 07:00

I'm not going to pretend to be an expert on Netware (something which salespeople have tried doing on my behalf in the past :) ) but this may be the expected way of backing up the Netware cluster volumes. With other operating system clusters you backup data from the virtual node use save -c virtualhostname, then when you do a recovery you do it from the physical node directing it to the virtual node.

1 Rookie

 • 

70 Posts

April 22nd, 2009 04:00

[STRIKE]This might be an problem the way you load your TSAFS.NLM
There are parameters like NOCLUSTER

If I remeber corectly you have to load the TSAFS.NLM like:

TSAFS.NLM /NOCLUSTER[/STRIKE]

I have to read better next time.
I second Hrvoje, its an known issue.

Message was edited by:
Antoine Schokker

Message was edited by:
Antoine Schokker

Message was edited by:
Antoine Schokker
No Events found!

Top