Networker 6.1.1:doesn`t backup

[RobinPiepjohn]

Hello

Dince last week suddenly the Networker 6.1.1 Backzuüp does not work for one Client.

In Savegroup Details the following message appears for a backup with savegroup Stetings:All

Unsuccessfull savesets:
*nodename:All 1 retry attempted
*nodename:All nsrexec: authtype nsrexec
*nodename:All type: NSR client description.


If I want to save only C:\ or D:\ all looks fine
If I backup from the client it is running also fine ... but if I try to backup Savset All I getz the message above.

Anyone with an Idea

It is only one of 30 Nodes where this effect appears

Regard

 

[wallace88]

What has changed during the time backups to the clients started failing last week?

Are you using Windows NT or 2000? What is the service pack?

Are use using Compaq Gigabit Ethernet card? There is a known problem with Compaq Gigabit Ethernet NIC Driver for Windows 2000 v3.63.363. If this is your scenerio, then:
deinstall GE driver 3.63, reboot the system, install GE driver V2.87

 

[RobinPiepjohn]

Thanks, I will try it. But first some answers

I am running W2k SP2 and a driver version you named
I Think nothing was changed since last week on the system

Any other possible answers ?

 

[wallace88]

Could be a lot of possibilities, but without further examination of log files, it's hard to say in this forum.

You said it works if you only specify one saveset, right?
what if you specify more than one, for example: c:\ and d:\?

If the problem happens when you have more than one saveset listed, then it is more likely caused by the NIC driver, as I described before. You can contact Conmpaq for further information on this issue. You'll need to get the driver from them anyway.

You can also try debugging with the

savegrp -vvv -l f -c <client_name> <Group_name> > test1.log 2>&1

savegrp -D9 -l f -c <client_name> <Group_name> > test2.log 2>&1

and then examiming the output files to see the point of failure.

 

[RobinPiepjohn]

Hallo

I have tried thje debugging mode and get the following:clientName:C:\ clu_init_lc(): Can't build fspath_vhost_map...
* clientName:C:\ 11/06/02 14:12:22 nsrexec:
* clientName:C:\ dump_map_lc(): ENTRY ...
* clientName:C:\ 11/06/02 14:12:22 nsrexec:
* clientName:C:\ dump_map_lc(): EXIT ...
* clientName:C:\ 11/06/02 14:12:22 nsrexec:
* clientName:C:\ clu_is_cluster_host_lc(): ENTRY ...
* clientName:C:\ 11/06/02 14:12:22 nsrexec: Clu_cluster_type = NONE (forced)
* clientName:C:\ 11/06/02 14:12:22 nsrexec: port = 10512, res = 0, errno = 2
* clientName:C:\ 11/06/02 14:12:22 nsrexec: port = 10513, res = -1, errno = 148
* clientName:C:\ 11/06/02 14:12:22 nsrexec: port = 10514, res = 0, errno = 148
* clientName:C:\ 11/06/02 14:12:22 nsrexec: port = 10515, res = -1, errno = 148
* clientName:C:\ 11/06/02 14:12:22 nsrexec: port = 10516, res = 0, errno = 148
* clientName:C:\ 11/06/02 14:12:22 nsrexec: port = 10517, res = 0, errno = 135
* clientName:C:\ 11/06/02 14:12:22 nsrexec: port = 10518, res = 0, errno = 135
11/06/02 14:14:10 savegrp: Nodenamerobe will retry 1 more time(s)
11/06/02 14:14:10 savegrp: current token = save
11/06/02 14:14:10 savegrp: using `D:\nsr\bin\nsrexec.exe' as execpath for `nsrexec'
11/06/02 14:14:10 savegrp: nsrexec started, pid 2788
11/06/02 14:18:14 savegrp: waitchild reaped, pid 2788
11/06/02 14:18:14 savegrp: current token = save
11/06/02 14:18:14 savegrp: using `D:\nsr\bin\nsrexec.exe' as execpath for `nsrexec'
11/06/02 14:18:14 savegrp: nsrexec started, pid 2720

What is, and where can I find a description of the errno ??

Our workaround: We change the 1 GB Card to a 100 Mb card and it is running now.
An downgrade of the driver had no effect.
any more ideas of making the system running constant??

 

[wallace88]

The errno that you see in the debug output does not mean there is a problem. You would see those numbers in a successful backup as well. You need to contact support if you really want to know what they mean.

You answered your own question in your last paragraph: the problem went away after replacing the Gigabit Ethernet card and replacing with the 100 Mbit Ethernet card. This proves that it is an issue with the type of GE NIC card that you are using and you should pursue this with either Compaq or whoever supplied that card.

 

[RMinNJ]

wallace88

I'm in the mist of this problem now. We uninstalled Compaq
support page 5.50, (driver 3.63..) and brought the system
down to 5.40a driver 2.87...

We still get the same error. Backups do work if we
run nsrexecd.exe from the command line.

I think we have this driver problem but bringing the driver
back down doesn't seem to fix it. Any ideas... Are there
extra steps to the uninstall that we forgot?


rmaiello

 

[wallace88]

rmaiello wrote:

>We still get the same error. Backups do work if we
>run nsrexecd.exe from the command line.

Did you start nsrexecd by typing: nsrexecd, or net start nsrexecd?

There is a difference between starting nsrexecd from command line and starting it up as a service, one example would be the account being used. The NetWorker Remote Exec Services (which starts up nsrexecd) is started up using the system account by default. Assuming you were logged in as Administrator, there could be permissions and rights differences. However not sure if this is enough to explain why backups work when nsrexecd is started from command line.

As for the GE NIC issue, you should contact Compaq about this issue. The *work around* (not solution) was to downgrade the driver. This is not guareenteed to work for all users.

Simple test: replace the GE NIC with 100Mbit NIC. If problem goes away, then there is a problem with the GE NIC or it's driver.

 

[RMinNJ]

wallace8,

The backups work if from the c: prompt we type
\program files\nsr\bin\nsrexecd

and leave it in the forground..

Yes, the problem now is even though we put the old driver
back and Compaq Support Paq it still doesn't work as a
service.

I've asked to replace the NIC or switch to 100Mbps but was
told that some software is tied to the MAC address of this
card and it would a lot of work...its been a lot work trying
to figure this out too.

Is there another account I can try running the service as?


rmaiello

 

[wallace88]

Instead of replacing the NIC, can you just add a 100Mbit NIC to the system, and use that NIC for backup purposes?

 

[jenspuller]

It may help to deinstall the compaq driver and use the Intel driver instead.
We Robin and I moved to the 100Mbit card and were successfull. But with other clients we do not have this option. We will try the Intel Driver 3.63 and post the result later here.
jens

 

[RobinPiepjohn]

Hello

Here is another hint:

May be its helpfull to disable Compaq services like Insight Manager and so on.
I heard this was installed on my machine last week.
Sinc that day I have my problem.
Maybe its random but a tip.
Bye

 

[muc]

I know this Problem also with Compaq NIC 7131 it will not work relace it to a 100MBit Card

 

[RMinNJ]

I'd love to replace the NIC. Unfortunately I've been told
there is some software dependent on the MAC of the this
NIC. I was also told the software on the box has problems
with &quot;muli-homing&quot; ..ie I cannot add a second 100 mbit NIC
to the box to do backups..

In short, I cannot back this client up. The downgrade of the
Compaq driver (I must assume was done correctly) has not
fixed the problem. I still have the intel driver to try,
after that I believe I'm out of options..

rmaiello

 

[jagroep]

Hi,

I experienced the same problem here... But the Wallace88 trick did the job. A downgrade of the 3.63 driver did not work. A deinstall of the 3.63 driver, reboot, and install of the old driver (2.xx) worked for me.

Regards
J.

 

[wallace88]

Jagroep: good for you. Nice to know yours is working.

Again, if you can't replace the Giga Ethernet card or get the driver working, then just *add* then 100Mbit NICcard into the system, configure the new NIC with i.p. and host name. Then on the backup server, just create a new client with the new host name associated for the 100Mbit NIC card and back up as you would any other client.

 

[wirre]

Solution: Compaqs NIC driver 3.63.363. have a bug that would not be in there.
Compaq/HP is working on a fix.

We had the same problem but removed three registry parameters and now its working fine.
(this parameters is for XP/.NET and should not be there)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\xxxxxxxxxxxxx&quot;VlanFiltering&quot;=&quot;x&quot;
&quot;TransmitMode&quot;=&quot;x&quot;
&quot;TcpSegmentation&quot;=&quot;x”

delete above value on all NIC cards and reboot.
(use search to find the right &quot;hive&quot; under \class\)


We tried to uninstall our 7131 NIC card and install the old 2.87.xxx driver BUT the parameters i the registry was still there soo when we removed them it worked fine..

 

[RMinNJ]

wirre,

Thanks,

We actually added/changed the registry key for TransmitMode
from a 3 to a 0 to get it to work.

Its good to get backups again although I have no idea
what any of these parameters do.


rmaiello