Backup Exec 8.0 trouble shooting guide.

Subject:   Isolating Problems with Veritas Backup Exec 8.0              
Categories: BackupExec 8, Windows 2000 & Windows NT 4.0           

Symptom: 

How to determine why a Backup Exec for Windows NT and Windows 2000 job failed? 

Solution: 
The following is a comprised list of words that can be used to search for what 
caused a job to fail.  This list does not necessarily represent ALL words that 
may fail a job.  If any one of the words below is searched for and found in a 
Backup Exec for Windows NT and Windows 2000 job log file, there will be more 
information following it regarding why the job failed. The log files are found 
on the Job Monitor tab, by double-clicking the instance of the failed job and 
selecting the "Log" tab.

Note: Most errors in Backup Exec 8.0 and later versions can be found by looking 
for caret symbols (^ ^ ^ ^ ^) in the failed job log.

1. Aborted
2. Attach
3. Connections
4. Corrupt
5. Denied
6. Error
7. Failed
8. Initialize
9. Insufficient
10. Memory
11. Not Found
12. Not Responding
13. Refused
14. Terminated
15. Unable

Hardware related errors:

16. Tape Alerts - (Note: Tape Alerts come from the Tape Device itself.  
VERITAS reports these errors for the convenience of the customer.)
17. Physical Volume Library Media, Drive, or Changer Not Found - 
(Note: There are many variations to how this phrase can appear and many causes.)
18. Cyclic Redundancy Check  (CRC)
19. I/O Device errors
20. Semaphore (SCSI) Timeout 
21. Unable to acquire device or media.
22. Mount Failed/Mount Failure
23. The device is busy.

Agent related errors:

24. OFO (Open File Option) initialization failures - 
(Note: This does not include the error stating the Open File Option was selected 
for use, but not installed.)
25. Intelligent Disaster Recovery Path not found/Unable to Generate Intelligent 
Disaster Recovery Information
26. Agent Accelerator not present - performing standard backup 
(Windows 2000 servers only, see complete error below.)
WARNING: Backup servers cannot completely protect remote Windows 2000 servers 
or workstations unless the Backup Exec Agent Accelerator for Windows NT/2000 
is installed and running on each remote Windows 2000 server or workstation to 
be protected. Data loss can occur if the Agent Accelerator for Windows NT/2000 
is not running while backing up remote Windows 2000 computers.


**Additional information regarding the failed job may be found in the Windows 
Event Viewer Application and/or System Log(s).      


Note: The following list will NOT cause a job to fail.

1. Remote Agent Not Present - Performing Standard backup. (Nt. 4.0 only.)
2. In use/Skipped files.

Tech Note Summary: 

Tech Note Title: How to determine why a Backup Exec for Windows NT and Windows 2000 
job failed? 
Tech Note ID: 191165 
Last Updated: February 20 2001 07:38 PM GMT 
This information in this TechNote applies to: 
Products: 
Backup Exec Network Storage Executive    8.0, 8.5 
Backup Exec for Windows NT/2000    6.11, 7.0, 7.01, 7.2, 7.3, 8.0, 8.5, SBS7.3 
 
Subject: Application - Backup - Backup Exec for Windows NT/2000
Application - Documentation - Backup Exec for Windows NT/2000
Application - Faq - Backup Exec for Windows NT/2000 
Languages: English 
Operating Systems: 
Windows 2000 Professional    5.00.2195 
Windows 2000 Server    5.00.2195 
Windows 2000 Advanced Server    5.00.2195 
Windows 2000 Datacenter Server    5.00.2195 
Windows NT    4.0 Serv, 4.0 Wkst 
 
--------------------------------------------------------------------------------

Search or Choose a Link from this page.

Webmasters & Visitors, please don't throw away your old whitepapers or Faq's or let them fade away, we are happy to put them here and host them on our site, even if they are old antiquated or outdated!

Enter your search terms Submit search form   Web CpuCare.net

Search or Choose a Link.  Free Anti-Virus and Anti-Spyware Software click here...