Unsolved

This post is more than 5 years old

26 Posts

517

August 6th, 2009 03:00

Netware cluster backup problem

Hi

I have a problem with backing up virtual cluster machine on Novell Cluster 1.8.3
The Netware is v 6.5 Sp8, the NetWorker clinet installed is 7.2.1 and the NetWorker Server is 7.5.1 on Win2k3

When I try to start backup process form the backup server, there is an error:

32451:savegrp: clzen:IT: level=incr
7236:savegrp: Group will not limit job parallelism
32493:savegrp: clzen:probe started
savefs -s networker -c clzen -g AXELtest -p -l full -R -v -F IT:
64690:savegrp: savegrp:AXELtest * clzen:Probe See the file C:\Program Files\Leg
ato\nsr\tmp\sg\AXELtest\sso.000002 for output of save command.
7340:savegrp: clzen:probe unexpectedly exited.

What I found in networker Temps is:

NetWorker : Novell Cluster Service is Up and Running
SAVEFS.NLMNetWorker : Client : clzen: failed.
CLZEN is Virtual server

The Save Set i use for virtual client is "IT:"
backup command is "save -c clzen"
I have both physical nodes in Remote Access field
and remote user and password filled


When started from client side, works fine:
"save -s networker -c clzen -U user -P password IT:"

Scheduled backup for both physical cluster nodes works perfectly too.

When I changed Save Set for ex. to "IT:/" , savefs ended with success but there was an error about Save Set naming.

Please respond if you have any idea.
What does it mean "clzen: failed. CLZEN is Virtual server"? How does it affect configuration?

regards
WS

2 Intern

 • 

244 Posts

August 6th, 2009 04:00

As I remember my "adventure" with Netware there is a special switch to TSA module on NetWare which has to be set on cluster environments.

26 Posts

August 6th, 2009 05:00

I tried to use loading tsafs with both /cluster nad /nocluster switches..
Any other ideas?

WS

26 Posts

August 6th, 2009 07:00

The problem is solved, after 3 days of fighting...
NOTworker proved once again to be the most unfriendly backup software.

The problem was capital letters in Save Set name ( VOL1: instead of vol1: ) for shared volume, what is confusing because for "normal client" backup capital letters are fine.

Also "save -c VirtualClinetName" in Backup Command field provides an error.
The question is why the documentation doesn't says anything about this?

Wish you all win in your battles!
WS

2 Intern

 • 

244 Posts

August 7th, 2009 00:00

I believe that when you wright this information to EMC support it will be included in the documentation (or not - LOL).
No Events found!

Top