Hi Yassine,

Try backup from the client with this command

save -s nw_server -b pool -D9 /etc

save -s nw_server -b pool -vvvvv /etc

Regards,

Luis Rogerio

You can check daemon.raw to see why client has failed.  If there is nothing meaningfull there, go to /nsr/tmp/sg/GROUP_NAME and check files inside if any of those contains any additional info.  If not, you can check client side log.  Abandoned saveset is just to general - can be aborted by server because of timeout, can be network error, can be client something... in short too much to list here.

Hi

when initiating a manual save it works

but server side backups fails, the logs say nsrindexd : timeout connection aborted,

The problem is only with large files (30GB)

but small files succeed for example etc/hosts

Hi,

Check if backing up some small amount of data also fails.  If only large backups fail, you could have a firewall timeout.  If small backups fail also, it's more likely a connection problem.

In this case, you should check the connection between the two machines with the following commands:

From the server: nsradmin -s -p 390113
From the client: nsradmin -s
From the client: nsradmin -s -p 390113

If this gets through to the nsradmin prompt, then the connection is ok, otherwise it is not.  If you do  not get the
nsradmin prompt, it means you have a connection problem and you will have to ensure that the name resolution is
correct between the two machines. Ensure that the FQDN,shortname and IP Address are present in the hosts file
on both sides and that Reverse DNS lookup works for all names and the IP.

-Bobby

the client is directly attached to the server, could it be the antivirus? how to confirm that

You could confirm that by excluding what you're backing up from the antivirus and testing, but I'd think it more likely that a firewall is cutting the communication between the two machines at some stage.  This should help:

Setting Keepalives to Prevent Firewall Timeouts During Backups

-Bobby