I assume when you say total capacity you refer to the size of the SQL database you are backing up? Is that correct? It might be an issue with network or perhaps firewall - do you see anything in logs?

Manual (client initiated) backups are updating index db, but they do not trigger index db save for that client after data has been saved - this is default behaviour.

Hi Jackson,

When you configured your backup client on the NetWorker server what was the string you used in the backup command? Also did you fill in the correct username and password? What error is the group giving?

Also have you confirmed that file system backups of the clustered client work?

It's hard to believe username/password would be related for something that breaks after 120GB has been sent already...

Hi Kevin,
The backup command I use as " nsrsqlsv -a virtual_name" and if I don't have the correct username and password, how can it backup around 120GB? The error message I can get from group start is "about due to inactivity timeout'. And I can backup the clustered file system well.

Hi,
I also cannot believe that I cannot backup it well. I had config lots of the system after all.
I can monitor a situation. When the backup start, the data is through the real server's NIC to send backup data to backup server(use Linux iptraf command monitored), but near the break point, the NW server and client has another tcp hand shaking via the real server's ip and the virtual server's ip and both of them are all reset. Then the backup throughput stop. After a while(3 minutes, I set the inactivity timeout to 3), the group giving "abort inactivity timeout" message.

Hi,
I mean the total backup capacity is, I can backup it from client using NMSQL GUI successful and alfter that I check the media of the saveset capacity. There is no any firewall between NW server and client. And I must correct my previous post, I can see the CFI index after manual bakup successful. Backup start from Group just failed and the only one reason is "abort due to inactivity timeout". But the most strange thing is, before the inactivity timeout, the backup speed still stand on 40~70MB/sec.

The command you are using is accurate. The next thing to do is set the incactivity timeout on the group resource to 0 and see how long the backup takes.

Kevin

Message was edited by:
Kevin Buis

Do you see anything in applogs on client?

Also, make another test from server. When it breaks, check if nsrsqlsv is still active and perhaps just to make sure that both client and server can communicate with each other via RPC (you can use rpcinfo like rpcinfo -t 390113 1

Hi,
The most strange thing is, there is no message in xbsa.message and the nsrsqlsv.raw without any error in it. And I had tried the "rpcinfo -p remote_host" command from NW server and client and there are 7939 tcp port active on NW client. Maybe I should try your suggestion, let you know after the test complete.

If there is nothing inside it might have died (check Dr.Watson log too).