Status 1 Logs

Hello everybody.

 

I'm having the following issue, after NB finish a specific backup, it show me this.

error.png

What I need to know is if there is some log that shows me which files are not backed up to send that info to the auditory department.

 

Thanks.

 

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Thanks for telling us that

Thanks for telling us that this is SQL backup. This changes the picture once again. You need to look at all the jobs that are running for this Db client. If multiple databases are backed up, then there will be a parent job and a child job for each Db. If one of the child jobs fail, the parent job will exit with status 1. You need to look at that particular failed child job for failure reason. The db name can be seen in Overview tab. More info about the failure will be logged in dbclient log on SQL client. This log folder does not exist by default and must be created.

View solution in original post

12 Replies
Highlighted

I believe the issue is the

I believe the issue is the failed email attempt. It is considered a part of the job and since it failed on it then you got a 1.

Highlighted

Yes, that is right. But at

Yes, that is right. But at the end, say that some files were busy or unaccesible.

I need to know which of those files weren't backed up to audit them.


Thanks for your prompt answer.

Highlighted

Scroll up in the Detailed

Scroll up in the Detailed Status window to see the files that could not be accessed.  I'm with Andrew, there may be none in this event. 

 

Highlighted

You can also run Problem

You can also run Problem Report for this client to see filenames that were skipped (if any).
Highlighted

I had another look at the

I had another look at the screenshot - nothing was backed up and the process on the client that reported issue is bphdb. So - this is a database backup? This means a failure. Backup script failed with status 1 and this was passed on to NBU with same status code and incorrectly interpreted as 'partially successful '. You need to work with dba on the client to check script and output.
Highlighted

Yup. Missed that one

Yup. Missed that one Marianne. The eyes are getting weak.

Highlighted

Whoa, I can't read that tiny

Whoa, I can't read that tiny print?  8Smiley Happy

 

Highlighted

Yes, this is a DB backup. If

Yes, this is a DB backup.
If I'm not misunderstanding what you say is that NB receive with error the script execution.
I'll talk with the DBA to run manually the backup script on the SQL to check if it fails.

Highlighted

Check log file on the SQL

Check log file on the SQL client:

Program Files\Veritas\NetBackup\logs\mssql_backup_failures

 

Highlighted
Accepted Solution!

Thanks for telling us that

Thanks for telling us that this is SQL backup. This changes the picture once again. You need to look at all the jobs that are running for this Db client. If multiple databases are backed up, then there will be a parent job and a child job for each Db. If one of the child jobs fail, the parent job will exit with status 1. You need to look at that particular failed child job for failure reason. The db name can be seen in Overview tab. More info about the failure will be logged in dbclient log on SQL client. This log folder does not exist by default and must be created.

View solution in original post

Highlighted

Thanks for all your

Thanks for all your answers.

I'll check this out with the DBA and then post an update about the situation.

Highlighted

The problem was solved taking

The problem was solved taking into consideration what Marianne said.

One of the SQL Server backups was failing and that's why the job ended with status 1.

After we solved that problem, the job started to end with status 0.

 

Thanks to everybody for your help.