Usually daemon.log should include the error message. If you search with group/client name on the date you are looking for, it will should show you information related to this. Look at both NetWorker server and client logs.

If you have enabled, group completion notification, look at the notification mails received on particular dates. It will also have some information.

Also you can look in event viewer logs (event viewer in windows) or under /var/log/messages in case of non windows host, which might also hold some information related to this.

Hi Prajith,

Thanks for the reply, I have checked daemon logs also, In below details 13th backup has restarted but it has failed after 2 hours,I didn't find particular error details.

42506 09/13/14 13:37:01  2 0 0 1 23808 0 camebrp5 nsrd savegroup info: restarting beavertn-svr-dq_nt_weekly (with 1 client(s))

42506 09/13/14 13:37:04  2 0 0 1 23808 0 camebrp5 nsrd savegroup info: Group beavertn-svr-dq_nt_weekly waiting for 1 jobs to complete

4690 09/13/14 13:37:04  2 0 0 1 20626 0 camebrp5 savegrp Group beavertn-svr-dq_nt_weekly waiting for 1 jobs to complete

77561 09/13/14 15:19:48  2 0 0 1 20626 0 camebrp5 savegrp command 'save -s camebrp5 -g beavertn-svr-dq_nt_weekly -LL -m beavertn-svr-dq -o "vss:*=off;" -l full -q -W

78 -N "C:\\" "C:\\"' for client beavertn-svr-dq exited with return code -1

77567 09/13/14 15:19:48  2 0 0 1 20626 0 camebrp5 savegrp beavertn-svr-dq_nt_weekly * beavertn-svr-dq:C:\  See the file /nsr/tmp/sg/beavertn-svr-dq_nt_weekly/sso.bea

vertn-svr-dq.KgaqsO for output of save command.

42506 09/13/14 15:24:55  2 0 0 1 23808 0 camebrp5 nsrd savegroup warning: Inactive files in group beavertn-svr-dq_nt_weekly occupy 82.00 percent of the used space, w

hich exceeds threshold of 30 percent configured for this group

38758 09/13/14 15:24:56  2 0 0 1 23808 0 camebrp5 nsrd savegroup failure alert: beavertn-svr-dq_nt_weekly Completed/Aborted, Total 1 client(s), 0 Clients disabled, 0

Hostname(s) Unresolved, 1 Failed, 0 Succeeded, 0 CPR Failed, 0 CPR Succeeded.

38758 09/13/14 15:24:56  2 0 0 1 23808 0 camebrp5 nsrd savegroup alert: beavertn-svr-dq_nt_weekly completed, Total 1 client(s), 1 Failed. Please see group completion

details for more information.

12662 09/13/14 15:24:59  2 0 0 1 23808 0 camebrp5 nsrd runq: NSR group beavertn-svr-dq_nt_weekly exited with return code 1.

42506 09/13/14 16:59:01  2 0 0 1 23808 0 camebrp5 nsrd savegroup info: skipped starting beavertn-svr-dq_nt_weekly

42506 09/14/14 16:59:00  2 0 0 1 23808 0 camebrp5 nsrd savegroup info: skipped starting beavertn-svr-dq_nt_weekly

42506 09/15/14 16:59:00  2 0 0 1 23808 0 camebrp5 nsrd savegroup info: skipped starting beavertn-svr-dq_nt_weekly

42506 09/16/14 16:59:00  2 0 0 1 23808 0 camebrp5 nsrd savegroup info: skipped starting beavertn-svr-dq_nt_weekly

bash-3.00$

In general may i suggest that you increase the retention period for the jobsdb. This will make it easier to follow up issues if you are not permanently monitor your system. For example, we are using 30 days.

However, first determine the size of your logs directory (especially /nsr/logs/sg) and estimate how big it can grow. Then ensure that you have enough disk space.

Hi,

In TSM all the error logs saved in dsmerror.log same way is there any file or path where we can get failure details. I have checked daemon.log not getting exact info.

For example- I am able to get backup failure details from the NMC,but unable to get failure history, Is there any path where we can find out same details.

8.0 is the 'area' - I do no really remember the exact version.

Bingo,

This is in case of NMC on NW 8.0 or later only correct ?

You can go to /nsr/logs/sg/ and inside you will find data which may give you more details (you will need to rely on timestamp).