N-central Help

Veritas service

The Veritas service determines the success or failure of a Veritas backup by locating and reviewing the log files generated by the backup software.  

The Veritas service looks for system-specified status codes in the XML log file. If these status codes match specified job status values, the agent displays the Failed status on the status dashboard. If the agent does not find a match, it displays the Normal state to the central server.

Service Type Log Appended
Instances on a Device 1
Supported Systems/Applications Symantec Backup Exec version 10 and earlier
Device Class Server - Windows
Monitored By Windows agent
Keyword The keyword is how SolarWinds N-central determines whether or not a Veritas backup succeeded or failed. If the keyword is found, the Veritas service will transition to a failed state. The default value is "Fail".
Log File Prefix

The log file prefix is a string used to find log files within the log file directory. If the log file directory exists, the agent strips the prefix from the file names and looks for the file with the newest timestamp.

If you use the defaults, the agent selects all of the files matching bex*.txt for consideration.

For example:

If you change the prefix to veritas and log.txt, the agent selects all of the files matching veritas*log.txt for consideration. The prefix cannot contain spaces or use wildcards. If the agent cannot find a file with the specified prefix, it reports the Failed state to the SolarWinds N-central server. If the log file has a .xml suffix, then SolarWinds N-central processes this file as a Veritas 9 or 10 file.

Log File Suffix

The log file suffix is a string used to find log files within the log file directory. If the log file directory exists, the agent strips the suffix from the file names and looks for the file with the newest timestamp.

If you use the defaults, the agent selects all of the files matching bex*.txt for consideration.

For example:

If you change the suffix to veritas and log.txt, the agent selects all of the files matching veritas*log.txt for consideration. The suffix cannot contain spaces or use wildcards and must include the period. If the agent cannot find a file with the specified suffix, it reports the Failed state to the central server. If the log file has a .xml suffix, then SolarWinds N-central processes this file as a Veritas 9 or 10 file. The suffix for Veritas 9 and 10 is not case-sensitive.

Log File Directory

The file where the service searches for log files. The default value is a full path and can contain spaces. The trailing backslash is required.

For example:

C:\Program Files\Veritas\Logs\

Time Offset

The maximum allowable age, in hours, of the Veritas log file. The agent will calculate the time that has passed between the current time and when the Veritas log file was last modified. If the difference is more than the time offset, the log is considered out of date, and the Veritas service will report a Failed state.

Scan Interval Daily at 4:59 am.
Repeat Weekly on Days Repeat the log file scan weekly on the specified days.
Repeat Monthly on Days Repeated the log file scan monthly on the specified days.

Metrics

Metric Name Description
Veritas Service Availability

SolarWinds N-central determines the quality of performance by comparing the monitored data to the thresholds. The availability range is 0-255, which corresponds to:

  • Normal = 1,
  • Warning = 2-255, and
  • Failed = 0.
Backup duration (Seconds) How long the backup took to complete.
Data amount backed up (Bytes) The amount of data backed up by the Veritas backup job.
Job Status for Veritas 9 and 10 You can view the return values for the associated job status on the status screen for the Veritas service. These values represent specific critical issues. They are returned by Veritas Backup Exec and reported by the agent. For the return values: 1, 5, 6, 7, 8, 9, 10, 11, 12, 14, 16, 20, 21, 22, and 23, the agent reports the Failed state to the central server. For the value 3, the agent reports the Warning state.
Veritas Service Details

Describes the results of the latest scan.

For example:

Job start time is beyond the offset, this log file c:\Program Files\Veritas\Backup Exec\Nt\Data\BEX01586.xml is an old log file

Return values of Veritas 9 and 10 job statuses and critical issues

Return Value Job Status Description of Critical Issue
1 Canceled Job is terminal due to cancellation.
2 Completed Job has been completed by the engine and is waiting final disposition.
3 Successful with exceptions Job is terminal with success but there are some exceptions.
4 Dispatched Job has been sent for execution.
5 Hold Job is in a hold state.
6 Error Job is terminal with an error.
7 Invalid schedule The schedule for the task is invalid.
8 Invalid time window The time window is mutually exclusive thus job will never run.
9 Missed Job is eligible for dispatch and is late.
10 Not in window Date of job makes it eligible to run, but time is not in window.
11 Ready but paused Job is ready, but dispatcher is paused.
12 Pending The job needs to be dispositioned to an actual state.
13 Recovered The system forced recovery of the job.
14 Disabled Job has been disabled in the system.
15 Resumed The job will be restarted with check point restart enabled, this value is only set in the job history summary.
16 Active Job is currently running on server.
17 Ready Job is eligible for dispatch.
18 Scheduled The job has a due date in the future.
19 Success Job is terminal with success.
20 Superseded Job is ready, but another higher precedence task is eligible to run.
21 Threshold auto-abort The job was aborted due to Abort Threshold time-out.
22 To be scheduled The job needs to have the due date calculated.
23 Linked job The job is linked to another job so will not start until the master job is finished.