Probe job had severe indication

[Till]

Hi @All

In order to avoid backup data going though our Firewalls we equipped our Backup Server (W2K3, NW7.3.2 Jumbo) with a additional nic to save two clients in a different subnet.
While one of the two clients works fine, the other one fails with strange error indications like these from a savegrp -p output :

savefs -s bpbackup01.bonprix.de -c bpvgsh02 -g Test -p -l full -R -v -F c:\
02/15/07 09:49:51 savegrp: command 'savefs -s bpbackup01.bonprix.de -c bpvgsh02
-g Test -p -l full -R -v -F c:\ ' for client bpvgsh02 exited with return code 1.

02/15/07 09:49:51 savegrp: job (15562) host: bpvgsh02 savepoint: bpvgsh02robe
had SEVERE indication(s) at completion.
02/15/07 09:49:51 savegrp: bpvgsh02robe abandoned.

Of course we specified the network adapter in the client resource but no one so far had a clue why one client works fine and the other fails

Thx in advance,

cheers Till

 

[605]

Did you adjust the "server network interface" for the client resource?

 

[Till]

Hi 605

Yes I did...thouigh the hostname is recommended there I also tried the Ip adress but without a change to the better

cheers Till

 

[605]

Does a manual backup work at all? - If not you should not try an automatic bu.

 

[Till]

Yes, manual backups and recovers work fine. And what I do not understand that a second client in the problematic subnet works without problems.

 

[605]

Did you open ports 7937 & 7938 ?

 

[Till]

No this is not necessary, in order to avoid going through a firewall I installed a dedicated nic in the backup server

 

[mblm07]

Have you check Account permissions?, had a similar problem recently and we thought it was drive permissions initially but it turned out the local admin service account didn't have the necessary permissions and by using a domain account with necessary permissions it worked.

 

[Till]

Thanks mblm07

Good tip, account permissions were OK but I have added the windows domain into the remote user field in the client resource i.e domain\useraccount and it worked fine ;-)
But I guess it will be a secret forever why I had to do this on one of two clients in this subnet only

Cheers Till