Did you add the cluster name in to the physical boxes as an alias?

You need to add in also to Remote Access under global 2 of 2 for the Cluster Virtual name.

system@gandalf1.sap.orkla.pl

system@gandalf2.sap.orkla.pl

on the physical boxes you need to add in the global 2 of 2 under remote access

system@gandalf1.sap.orkla.pl

system@gandalf2.sap.orkla.pl

system@sappop.sap.orkla.pl

Thats a copy of my config and it works for me.

Just also if you using windows and it's 2k8 make sure your adding the windows cluster Virtual name and not a culster resource cluster name as they can be different names.

Also the physical boxes do not need to be part of your goup only the cluster name needs to be part of the goup as this is where you want to backup from as all the resources will be only to this name.

good luck hope this helps.

Hi,

I added 

system@gandalf1.sap.orkla.pl

system@gandalf2.sap.orkla.pl

to the cluster client resource : sappop.sap.orkla.pl as Remote Access and resource have beeen created sucessfully .

I also added as you suggested :

system@gandalf1.sap.orkla.pl

system@gandalf2.sap.orkla.pl

system@sappop.sap.orkla.pl

as Remote Access to both physical nodes.

When I tried to backup sappop.sap.orkla.pl I got another error :

1 retry attempted
No full backups of this save set were found in the media database; performing a full backup
39078:save: SYSTEM error: client `gandalf1.sap.orkla.pl' is not properly configured on the NetWorker Server

5777:save: Cannot open save session with plwawp0206srv.presspublica.pl
:  Failed with error(s)

It drives me crazy  Netbackup was far more friendly ..

BTW. I cannot add alias : sappop.sap.orkla.pl for both physical nodes as i got warning that alias already exists ( even it is not listed )

Ok so it sounds like this cluster is configured.

What about your storage node? is it part of the networker server or seperate?

if it is seperate confirm you cluster virtual client is configured to talk/push backup data to this box.

check nslookup

and run through these things

https://solutions.emc.com/emcsolutionview.asp?id=esg67632

Hi,

jaroslawnowicki wrote: Hi, I have Networker 7.6 SP1 . I need to backup MS Cluster - 2 nodes. Physcial nodes names are : gandalf1.sap.orkla.pl gandalf2.sap.orkla.pl Virtual name is : sappop.sap.orkla.pl When I try to create virtual client resource sappop to backup shared cluster disks I got error : "Found alias:gandalf1.sap.orkla.pl client map using client id:7ca7eca3-00000004-4db6c8e8-4db81b54-011c1500-1c43d617. If renaming client:gandalf1.sap.orkla.pl to SAPPOP.sap.orkla.pl specify this client id. Otherwise, re-apply to create a new client id"

What happens here is that while creating sappop.sap.orkla.pl account is finds that this names is already an alias for gandalf1.sap.orkla.pl.  So, first thing is to check if sappop.sap.orkla.pl is there.  Also, if you had it once and then it was removed, it is still in cache and the only way to empty the cache is to restart backup server application.

If, (and this is really only if), you never had sappop.sap.orkla.pl listed as alias for gandalf1.sap.orkla.pl then you have some sort of naming resolution issue where sappop.sap.orkla.pl gets returned as gandalf1.sap.orkla.pl (on backup server side).

I too have a windows cluster environment (consisting of two 2008 windows nodes) and am running networker 7.4 sp4.

I originally configured the networker clients (physical servers) and was able to perform backups.  Odd thing was

it wanted the name of the cluster node name in the alias field as well as the physical node name.  But for some

reason after the nodes would switch to be active, my backups were not working. 

I removed the cluster node within the alias field as previous mentioned from both physical client nodes.  I then created a networker client for the cluster node name, with the remote access field being system@node1 and system@node2.

I included all three networker clients in one backup group and started the backup and it worked.

Hope this helps.  I am sure the versions of networker are different with the cluster configuration.