big savesets saved twice

[dmpe]

I have next strange legato behaviour - big savesets with full backup saved twice.
Although small savesets (~<10Gb) on this client saved once.
This happened both 6.0 and 6.1.

03/26/04 11:47:38 nsrd: client:/bigvolume saving to pool 'ClientPool' (device01)
03/26/04 13:29:22 nsrd: client:/bigvolume done saving to pool 'ClientPool' (device01) 21 GB
03/26/04 13:29:53 nsrd: write completion notice: Writing to volume device01 complete
03/26/04 13:56:21 savegrp: client:/bigvolume failed.
client:/bigvolume: No save sets with this name were found in the media data base; performing a full backup
03/26/04 13:56:21 savegrp: client:/bigvolume will retry 1 more time(s)
03/26/04 13:56:22 nsrd: savegroup info: client:/bigvolume: No save sets with this name were found in the media database; performing a full backup
03/26/04 13:56:23 nsrd: client:/bigvolume saving to pool 'ClientPool' (device01)
03/26/04 15:19:40 nsrd: client:/bigvolume done saving to pool 'ClientPool' (device01) 22 GB
03/26/04 15:20:12 nsrd: write completion notice: Writing to volume device01 complete

 

[605]

Yes and no,
- it is in fact saved twice
- but only because the first attempt failed.
Almost finished, the save set /bigvolume failed for whatever reason.

 

[fazil1]

Hello,
Seems like your 1st backup is failing, the cleint retry attempts to backup this client again, i suspect your index is correpted or client connection is bad where by its failing in middle or towards the end of backup.
Check
1. Host entries for accuracy.
2. Reinstall client on the Networker client machine, configure with full DNS name and check name resolution.
3. Run NSRCK -L6 on cleint name from the server to check it's Index.
4. Check on Networker server failed cleints properties and verify each tab for accuracy.
5 If still failing recreate cleint on the backup server
6. Check Deamon.log and other logs
Bombay4u@hotmail.com

 

[dmpe]

It is really saved twice - always with big saveset.
I have some clients with big savesets and this happened
on each of them.
I am sure that it is not index problem - it also
happened on just installed server on first backup.
With 2-3 Gb savesets on same client everything OK..
Anybody has experience with savesets >10Gb ?

 

[605]

Run the savegroup(s) from the command line with added verbosity

"savegrp -v [-l level] -G group_name"

Let's hope that this is a bit more informative and will tell us the reason why.

 

[nandfred]

We had a 50GB saveset that did the same, it was all due to network settings, NIC's set to auto, and new cisco switches, who didn't like the 3com NIC's auto mode.
Try and go over your network equipment and see if u have any NIC's or switches set to auto and change it to 100 full or 1000 full, or what setting your equipment supports.

 

[wallace88]

Do you have a firewall between the backup server and client?

Note the difference between service and connection ports.

While the data goes across the connection ports, the service ports must stay opened. If, as in a firewall port, it should timeout and close, Networker may think the backup failed, even though the data actually got backed up.

 

[dmpe]

Yes, I have firewall CheckPoint (moreover - with NAT) in the middle.
I seem you made a right guess wallace88.
But very strange - when I twice made by hand
"savegrp -v [-l level] -G group_name"
/bigsaveset saved once each time.
What may be with firewall ?