Can you attach the daemon.log file (after render) and give me the client name? It is the first time it got corrupted or you notices it on other clients also?

I hope that  you are storing data on tape and not on AFTD. If you are using AFTD then root cause is clear - aborted save sets are immediately removed.

I believe there might be a way to retain aborted data from disk devices too - there is setting in newer versions which instructs NW to retain aborted backup sets (didn't test it myself, but I guess this is what is used for).

thx

In server properties, under Configuration tab, you have something called Keep Incomplete Backups.  Now, according to NMC help I just checked, this is supposed to be valid for cloud backups only, but I assume it extends to disks too - you will just have to check it yourself.

I got the command to start backup from last known checkpoint from client .

{save -k "checkpointID" -s backup_server_name -g grp_name.}

But still it is not starting from last known checkpoint ID. Tommorrow i will start backup in D9 mode and will attach the daemon and d9 mode logs.

No i am restoring in tape.

Hi All,

In NMC logs, i am getting "SSID <..> not in media db". When I manually stopped backup, it is showing “backup Failed and will not be restarted” and also saveset status is "Checkpoint, aborted, suspect".

Manually i am stopping the tape backup and restarting again because few full backups are getting hang in 2KB/Sec.

Any help.....