UNSOLVED
B
BerndG_42aac9
22 Posts
0
769
April 21st, 2009 01:00
Netware cluster client uses wrong networker index
Hallo,
Netware is a source of mystery.
We have a netware 6.5 cluster with NW 7.2.1 latest build and NW 7.4.4 HP-UX
as backup server. Netware client was setup according to the instructions in
the install guide. It is not possible to backup the virtual node. We get the
error message: Invalid save set or save set not available
When the phys node is backed up it saves the cluster volumes but the meta data are registered in the index of the virtual node. Cluster volumes belong to the virt node. Name resolution is correct for server and client.
I would appreciate some suggestions to get a true cluster backup working.
regards
Bernd
Netware is a source of mystery.
We have a netware 6.5 cluster with NW 7.2.1 latest build and NW 7.4.4 HP-UX
as backup server. Netware client was setup according to the instructions in
the install guide. It is not possible to backup the virtual node. We get the
error message: Invalid save set or save set not available
When the phys node is backed up it saves the cluster volumes but the meta data are registered in the index of the virtual node. Cluster volumes belong to the virt node. Name resolution is correct for server and client.
I would appreciate some suggestions to get a true cluster backup working.
regards
Bernd
266
0
Posted April 21st, 2009 06:00
Yes, we tried saveset All and explicit volumes. We tried backup command
save and save -c virtnode. No difference.266
0
Posted April 21st, 2009 07:00
This is known issue - contact support for patch.266
0
Posted 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.
266
0
Posted 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
DavidHampson
2 Intern
•
1080 Posts
266
0
Posted April 21st, 2009 02:00