Unsolved

This post is more than 5 years old

8 Posts

2547

October 21st, 2019 07:00

Backups getting failed with "Unable to close save session: Save session with saveset id xxxxx terminated

Hi All ,

 

Backups getting failed with below error , please help if someone experiencing the same problem .

--- Job Indications ---
Unable to close save session: Save session with saveset id 7c1f5080-00000006-e8ad6425-5dad6425-4e199dd8-da092b67 terminated

4 Operator

 • 

1.3K Posts

October 21st, 2019 08:00

@PRASAD R,

Can you in more details? Like -

What is the backup of?

How long has it been running?

Is it a partial Failure or complete client failure?

Is there a firewall between the client and the server?

 

8 Posts

October 22nd, 2019 04:00

Can you in more details? Like -

What is the backup of? - its a file-system backup 

How long has it been running?- runs for usually 10-15 mins and fails with below error 

Is it a partial Failure or complete client failure?- yes its a partial failure , some clients do succeed , and sometimes when we re-trigger these failed Clients it gets succeeded .Also when we completed stop/start the networker services , we see these is a getting backed up .

Is there a firewall between the client and the server?

No,  runs on a backup VLAN .

2.4K Posts

October 22nd, 2019 06:00

It looks as if this points towards a connectivity issue. Why? - because there is no feedback any more.

NW usually controls everything hut he can't if there is a network problem. Assuming that, it is most likely that you will already see that when you run a manual backup.

So I want you to execute a standard "save -s nw_server large_file" at the client (bigasm) and verify the issue.

If it persists I would add debug information to the process like "save -D5 -s nw_server large_file > outfile" and check from here.

 

8 Posts

October 22nd, 2019 08:00

@bingo.1 

 

Thanks for your response , but looking at the error now some are getting timed out .

this is really bizarre behaviour we are facing .

when i run a probe - nsradmin -s clinet_name -p nsrexecd , everything looks fine and after that when i re-run the backup , the failed clients are successful again . 

considering the behaviour , i feel this is a TCP timeout  and connectivity issue as you said .

PS: we are seeing this behaviour after we deployed / migrated backups to DD9800 with 6.1 DDOS .

not really really sure if this is a DD issue .

 

2.4K Posts

October 22nd, 2019 09:00

We have had multiple/various DDs over the years - with no such problems.

However, I vaguely remember 'similar' issues some years ago before we used DD boost devices.

 

No Events found!

Top