That's not very large.  Does it abort after same amount of time group has been started or same amount of time session has been running?

it aborts as soon as the file backup finishes.

can it be a nsrindexd problem ?

I mean a session being aborted

This is the default behavior when backing up to an AFTD and the save set could not be completely transfered due to whatever reason.

As the index backup is a local backup, it has nothing to do with the client data. It just runs afterwards.

The question is after which amount of data the client backup will be aborted. But as a manual backup runs fine i assume there is something wrong with the sequencing during the savegrp command..

Go and start the group from the command line with added verbosity - it will most likely return more info. And check the daemon.raw files (server & client).

As Castern hinted, it sounds as this is index or bootstrap backup which fails somewhere (as that is the part which happens after file system backup).  Is it possible to show us completed daemon.log for the run of this group?

Hi

sorry for the delay,

if I remove the big saveset ( a single big file) teh backup succeeds and the index backup succeeds but with the dump file, the backup fails as soon as it finishes the big file and remove it.

it am right as soon as a file is backed up the nsrindexd process will write an index entry in the CFI database? is that true?

does this mean that the nsrindexd is being stopped for a reason?

Actually nsrindexd fills the CFI during the backup. That's why you must have a good network connection to the server (at least for small files) even if you run local backups at the storage node.

nsrindexasm will not stop for the index backups. Otherwise you would not be able to backup a client while another one's CFI will be saved simultaneously.