11-30-2011 07:16 AM
Hello.
I'm having this error: NDMP backup failure(99).
Here's the more detailed log:
30-11-2011 04:55:30 - begin writing
30-11-2011 05:17:28 - Error ndmpagent(pid=9698) cannot log message to error database, error = text exceeded allowed length,
30-11-2011 05:17:28 - Error ndmpagent(pid=9698) NDMP backup failed, path = /FS03
30-11-2011 05:17:29 - Error bptm(pid=9699) none of the NDMP backups for client fc-fs01.dev.pt completed successfully
30-11-2011 05:17:45 - Info bptm(pid=9699) EXITING with status 99 <----------
30-11-2011 05:17:45 - Info ndmpagent(pid=0) done. status: 99: NDMP backup failure
30-11-2011 05:17:45 - end writing; write time: 00:22:15
NDMP backup failure(99)
Can anyone help me with this?
I'm running netbackup 7.1.0.1 on a RedHat Linux Server 5.7 64 bits.
Thanks.
Regards,
Ricardo Vilhena
11-30-2011 08:02 AM
11-30-2011 08:38 AM
The paths are well defined.
This backup always ends end a successful status, but about a week ago it started with the 99 error. Nothing changed in the master nor client configuration.
Thanks.
Regards,
Ricardo Vilhena
11-30-2011 09:14 AM
Sounds to me something in the path/filesystem structure has changed.
like a link to the same link /link/link/link/link........
or some strange character as been added to a file name or dir name or group name that is being interrupted and makes the path too long. start looking for anything created on the date it started failing.
11-30-2011 09:28 AM
This seems to be causing the problem:
Error ndmpagent(pid=9698) cannot log message to error database, error = text exceeded allowed length,
Was logging level perhaps increased at some point in time?
Check logging level for OID 134 in nblog.conf on the NDMP host:
<install_path>\NetBackup\nblog.conf on Windows server
/usr/openv/netbackup/nblog.conf on Unix/Linux server
12-02-2011 03:28 AM
Hello Marianne.
That also seemed the problem to me, but doing a search for that error I couldn't find anything :\
This is the OID 134 conf in the nblog.conf:
# 134. NDMP Agent
134.L10nResource=ndmpagent
134.OIDNames=ndmpagent
134.LogDirectory=ndmpagent
Thanks.
Regards,
Ricardo Vilhena
12-02-2011 09:57 AM
What about the default logging levels?
Default.DiagnosticLevel=?
Default.DebugLevel=?
Probably best to open a support call with Symantec.
12-05-2011 02:57 AM
Here's the default logging levels:
Default.DiagnosticLevel=6
Default.DebugLevel=1
Is this correct?
Thanks.
Regards,
Ricardo Vilhena
12-05-2011 03:05 AM
Change you diagnostic level to 1 and see if that helps
12-05-2011 06:47 AM
Hello again.
It didn't work :\
Any other suggestion besides opening a service request?
Thanks.
Regards,
Ricardo Vilhena
12-05-2011 06:59 AM
I have not been able to find anything about this error.
Symantec Support Engineers have access to case history that us 'plebs' don't have access to.
We are wasting valuable time with our guesswork - best to open a support ticket.
12-20-2011 10:35 PM
You need to log a call with symantec support as for this we need to collect the NDMP LOGS OID 155 and ndmpagent OID 134, bpbrm from the media server and if this is NetApp filer then off course ndmpd logs from the filer.