Job Failed while LOG looks OK, what's wrong?

[RoGx]

Hello Experts,

Back-ups were perfoming perfectly in 2003. Now, all the back-ups status in 2004 are "job failed". I did NOT change ANYTHING. Also, im not a pro, but the logs seem perfect except for the last line that says the job failed. But I don't know why and I don't have a clue what to look for. I tried cleaning cassettes 2 times. No change.

I'm using Backup Exec version 8.50 rev 3571 on Windows 2000 Server 5.00.2195 Service Pack 4

Here's the log for one of the job that failed (I repeat, all 2004 jobs to date failed):

THANKS A LOT!

Ray

======================================================================
Job server: CH03CHCSVR00003
Job name: Quotidien
Job started: Monday, January 05, 2004 at 10:00:08 PM
Job type: Backup
Log file: BEX01.txt
======================================================================

Drive and media information from media mount:
Changer Name:
Drive Name: HP 1
Media Slot: 0
Media Cartridge Label: 4MM000011
Targeted Media Set Name: Media Set 1

======================================================================
Job Operation - Backup
Media operation - overwrite.
Hardware compression enabled.
======================================================================

Media Name: "Media created 1/5/2004 10:00:08 PM"
Backup of "C: NOSPART"
Backup set #1 on storage media #1
Backup set description: "Backup"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 1/5/2004 at 10:00:48 PM.
Directory not found. Can not backup directory \Exported Reports and its subdirectories.
File "scepol.log" in use - Backed up.
File "dnary.ldb" in use - Backed up.
File "ias.ldb" in use - Backed up.
File "ias.mdb" in use - Backed up.

Backup completed on 1/5/2004 at 10:09:20 PM.
Backed up 8774 files in 327 directories.
4 files were in use
1 item was skipped.
Processed 1,224,488,956 bytes in 8 minutes and 32 seconds.
Throughput rate: 136.8 MB/min
----------------------------------------------------------------------

Media Name: "Media created 1/5/2004 10:00:08 PM"
Backup of "D: Data"
Backup set #2 on storage media #1
Backup set description: "Backup"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 1/5/2004 at 10:09:20 PM.
File "sfm40log" in use - Backed up.
The item \MSSQL\DATA\clinical_data.mdf in use - skipped.
The item \MSSQL\DATA\medipharm.ldf in use - skipped.
The item \MSSQL\DATA\medipharm.mdf in use - skipped.
The item \MSSQL\DATA\medipharm_clinical_test_Data.MDF in use - skipped.
The item \MSSQL\DATA\medipharm_test.mdf in use - skipped.
The item \MSSQL\DATA\medipharm_user_data.mdf in use - skipped.
The item \MSSQL\DATA\medipharm_user_test_Data.MDF in use - skipped.
The item \MSSQL\DATA\mph_control_data.mdf in use - skipped.
The item \MSSQL\LOG\clinical_log.ldf in use - skipped.
The item \MSSQL\LOG\medipharm_clinical_test_Log.LDF in use - skipped.
The item \MSSQL\LOG\medipharm_test.ldf in use - skipped.
The item \MSSQL\LOG\medipharm_user_log.ldf in use - skipped.
The item \MSSQL\LOG\medipharm_user_test_Log.LDF in use - skipped.
The item \MSSQL\LOG\mph_control_log.ldf in use - skipped.

Backup completed on 1/5/2004 at 10:23:41 PM.
Backed up 7943 files in 187 directories.
1 file was in use
14 items were skipped.
Processed 7,493,540,340 bytes in 14 minutes and 21 seconds.
Throughput rate: 498.0 MB/min
----------------------------------------------------------------------

======================================================================
Job Operation - Verify
======================================================================

Verify of "C: NOSPART"
Backup set #1 on storage media #1
Backup set description: "Backup"
Verify started on 1/5/2004 at 10:24:25 PM.

Verify completed on 1/5/2004 at 10:29:11 PM.
Verified 8774 files in 327 directories.
0 files were different.
Processed 1,224,488,956 bytes in 4 minutes and 46 seconds.
Throughput rate: 245.0 MB/min
----------------------------------------------------------------------

Verify of "D: Data"
Backup set #2 on storage media #1
Backup set description: "Backup"
Verify started on 1/5/2004 at 10:29:11 PM.

Verify completed on 1/5/2004 at 10:42:30 PM.
Verified 7943 files in 187 directories.
0 files were different.
Processed 7,493,540,340 bytes in 13 minutes and 19 seconds.
Throughput rate: 536.7 MB/min
----------------------------------------------------------------------

======================================================================
Job ended: Monday, January 05, 2004 at 10:43:29 PM
Job completion status: Failed
======================================================================

 

[kippy13]

Why is it saying it cant find this directory?Backup of "C: NOSPART"
Have you compared successfuly logs with failed ones and check for any differences?

"Sometimes I do not know but I try hard"- R.F. Haughty 1923

 

[SQLBill]

None of the SQL files were backed up (they were SKIPPED), therefore the job failed.

It sounds like your Agent for SQL is missing or the license has expired.

Or have you just started backing up the SQL Server?

I suggest using the native SQL Server commands and doing backups to the hard drive and then using Backup Exec to copy the backup files to tape.

-SQLBill

 

[kippy13]

Hi Bill,
I assumed that once a file was in use it wouldnt be backed up...particularily database files. If the license is correct fo the agent for sql then it'll be okay?
Maybe the SQL server is scheduled to shutdown but this is not happening any more?

"Sometimes I do not know but I try hard"- R.F. Haughty 1923

 

[SQLBill]

When SQL Server is in use backup programs cannot back it up. BE requires the Agent for SQL Server to be able to backup an active SQL Server database.

Yes, if you have the correct license for Agent for SQL Server AND the agent is installed, it should work properly.

Yes, it is possible that SQL Server was shut down prior to the backup running. That would work and the agent wouldn't be needed.

But to your real question....any time a file is skipped, that counts as a failure for the whole job. BE uses FAILED to let you know not everything was done as you requested.

-SQLBill

 

[LawnBoy]

Here's another reason for a Fail flag:
"Directory not found. Can not backup directory \Exported Reports and its subdirectories."

You've told BE to backup a directory that it can't find.

BE 9.0 doesn't fail a job because of a skipped file, it just reports "xx files skipped". It may be because I'm configured to just skip any open files, rather than retrying.

 

[SQLBill]

Good point LawnBoy, I completely missed that line.

-SQLBill

 

[RoGx]

Hi,

I found the problem in another thread.

Problem was the 2 directories that couldnt be found have been deleted before being removed in the selections tab in backup exec.

I re-created those 2 directories temporarly and then i could see them in selections tabs. Then I unchecked them, saved settings then re-delete the 2 directories and everything works fine since then..


Im still thinking its weird backup exec dont show "checked" directories or just remove this selection when it cant find the directory.

Thank all!

RoGx

 

[justin2000]

Rogx

What you have described is a new feature of 9.1 - if you open a selection list in 9.1 and it can't find a directory or server, it will tell you this and ask if you want to keep it.

Also, you are selecting your backups wrong.
What you need to do first is select the drive - then unselect any directories you don't want to be backed up.
Check the text view of the selection list and you will see what I mean.
If you do selections like the above the issue you are having above won't happen again and any new directories you add to the server automatically get backed up.