backup of clustered novell volumes does'nt work

[svenix71]

Hello, recently we have clustered our Netware servers, since that moment we can’t do backup of clustered volumes. Volumes that aren’t clustered, backup works fine. The version Networker client that we use is 7.2.1, Netware server version is 6.5 SP6. The Servers have two nic’s, one for production and the other to a LAN dedicated for backup. The communication between Networker server and clients are correct (we see that save module loads itself ), but it gives the following error: “Invalid save set or save set not available <volumename:>”

 

[605]

The disk will be available 'locally' whichever node it has been mounted to by the cluster software.

Try to run a manual backup of this filesystem first.

 

[svenix71]

Yes, you are right, we can see the volumes "locally" as far as the novell server. But from the NW client we can only access this volumes (as locally) if the module TSA is loaded with the mode cluster disabled. Then we can run a backup manually without problems.
If the TSA module is loaded in cluster mode, when we run the manually backup, and choose the client, only appears the name of the physical node (not the virtual resources) and then with this client we only see the not clustered volumes...

 

[a060463xyz]

You have to create a new client object in Networker with the name of the virtual Server name.
Avoid using saveset all !
Use the names of the Disk for the saveset name.
Best practice is to only shedule one Disk at a time so if your cluster has e.g. three disks build three client objects in three groups for backing up the cluster.
Take into account that there is no cluster client for netware so every virtual server need one client coonection license.

 

[svenix71]

a060463xyz,thanks for your indications, we are following all of them except for the best practice...we will try it
On the other hand, what do you mean "use the names of the Disk for the saveset name" ? In the saveset client definition we use the name of the volumes as presented by the Novell server (see it with the Novell command Volumes..)

 

[a060463xyz]

You are right, i menat the novell volume name

 

[svenix71]

OK, we already do this definition...but it doesn't work.
We have applied too the last "oficial" path 7.2.1 LGTsc02878 26.3.2007, because we have read there is some issue related to cluster issues...

 

[a060463xyz]

did you enter the physical cluster nodes AND the virtual servers in the SYS:ETC/hosts file on every cluster node ?

Maybe your dedicated backup-lan will confuse nameresolution of the virtual servers.

Please check and attach the rendered daemon.raw or daemon.log files to this thread.

 

[svenix71]

Yes, a060463xyz , we have the physical cluster nodes and the virtual servers names.
Which daemon.log do you want, from de Novell client or from the Networker server??

 

[Till]

Hi Svenix

I guess a060463xyz means the daemon log passage from the Networker server.
In which way did you specify the save set in the client resource ?

cheers Till