A log file is created every time a job is run within Veritas Backup Exec for windows server and the results are sent to the Job History log file. The Job History log file is a report of what happened during the processing of the job (statistics, errors, and so on).  

Configuring the Job History Log:

To configure the Job History defaults, go to Tools | Options and select the Job Logs option on the left hand tasks(Figure1).

Go to Tools | Options |Job logs.

Figure 1
 

Here the following options can be set:
 

Options	Defaults
Information to include in log	Summary information to be included in the Log File (directories, files and file details). The lowest setting still records any errors, warnings or notifications such as skipping files.
Prefix for the job log file name	In this field you can specify a log file base name #.txt. The #starts at 00. The default is BEX#.txt.
Email job log attachments	Selects the Job log format to sent by Email : HTML or TEXT
Job Log path	path where job logs are saved. By default this is the installation directory.

Viewing Job History Files:

The Log File window contains detailed information about the completed job. The Completed Job Information window appears, with two tabs:

The Job History tab is displayed as follows (Figure 2):

Figure 2
 

The Job History tab contains the following information:
 

Field	Description
Job Name	The job entered during the initial setup of the job.
Job Type	The type of operation that was performed (File Grooming, Backup, Catalog, Restore, Verify)
Job log	The associated log file.
Job Status	The status of the operation.
Server Name	The backup server that processed the job.
Device Name	The name of the device that processed the job.
Directories	Total number of directories processed.
Files	Total number of files processed.
Total Bytes	Total number of bytes processed.
Volumes	Total number of drives and/or shares processed.
Rate	Number of megabytes processed per minute.
Start Time	Time the operation started.
Elapsed Time	Length of time the operation took.
Files in Use	Number of open files encountered during the operation.
Corrupt Files	Number of corrupt files encountered during the operation.
Skipped Files	Number of files skipped during the operation.

To view the Log File window, select the Job Log tab.
 


The Job Log tab contains the following information:
 

Job Log Fields	Field Description
Job Name	The job name entered during the initial setup of the job
Job Type	The type of operation that was processed (Backup, Catalog, Restore, Verify)
Job log	The name of the displayed log file
Job Server	The backup server that processed the job
Device and Media Information	Describes the information about the Device and media used along with the Overwrite and append details.
Job Operation - Backup	Display all information about what server and resources were backed up with date, time and size information
Job Operation- Verify	Displays information about verification of backup data
Job Completion Status	Displays information whether the job was successful, failed, canceled or recovered
Expand all / Collapse all	allows to expand or collapse the job log
Print	Click on the button if you wish to print the complete job log
Save as	Save the log on the desired location
.DR file information	"The disaster recovery information file C:\Program Files\Veritas\Backup Exec\Data\Server.DR has been successfully updated." This .DR file includes metadata required for simplified Disaster Recovery option.

The "Log" files are accessible, even if Backup Exec is not started. By default the log files are saved in  [drive]:\Program Files\Veritas\Backup Exec\Data\ directory in XML format.

Understanding Job History Log File Status:

There are three possible job completion statuses: Successful, Canceled, and Failed.
Successful: Job completed without errors.

Canceled: Job did not complete. Here are some reasons a job might be aborted:

·
Failed: The operation took place, but one or more significant errors occurred. The log file should indicate what caused the errors so that you can decide if you want to run the job again. For example, if you get a job failure occurred due to a lost connection during job processing, you could choose to resubmit the job when the connection becomes intact.

What happens to jobs with errors?
A once-only job that ends in an Aborted or Failed status is put on hold so you can resubmit it later. Scheduled jobs will be re-scheduled for their next execution time.

Deleting Job History Log Files:
To delete completed job entries and their associated log files from the Job Monitor tab, right-click the completed job and select Delete from the shortcut menu. To delete more than one entry, click and highlight the first item you want to delete and then while holding down the key, click and highlight other entries to be removed. After your entries are selected, click Delete.

Note: You can configure automatic deletion of the oldest job records and their associated log files by configuring the Database maintenance in the Tools | Options | Database maintenance option.