Backup Exec Error Log
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate backup exec exchange logs Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体)
Backup Exec Logs Filling Up Disk
English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet How to Debug Backup Exec backup exec install log - Agent & Options debug log gathering list Article:000087598 Publish: Article URL:http://www.veritas.com/docs/000087598 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas
Backup Exec Job Log
Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem How to debug Backup Exec (BE) using the steps and debug shortcut list below Solution Before a debug is done: Make sure the following backup exec job log location has been completed. Update Backup Exec and Remote Agent(s) to the latest Version\Patches: How to get updates for Backup Exec - Service Pack, Hotfix and Device Driver updatesUpdate the Remote Agent(s) - How to install Backup Exec Remote Agent for Windows System (RAWS) for Backup Exec 11d - 2010 R3How to install the Backup Exec 2012 Agent for Windows (a.k.a. Remote Agent. RAWS, AWS) Run the Veritas QuickAssist (VQA) - Run this to find problems and fix all issues that relate to the problem now. Other issues that do not relate can be fixed at a later time. Search the Knowledge Base: Perform a search using the error or UMI (the "V-" number) code and check the results generated for a solution. If performing the above steps did not help resolve the issue, proceed to debug the smallest/shortest job to reproduce the problem.Note: It is best to run the smallest job that causes the error so that the debug logs are smaller. There are many areas of Backup Exec. In order to obtain the needed debug logs/informaiton, use appropriate link(s) from below to debug the f
too many variables in a backup environment to always see an error and know immediately which part of the backup process, software, hardware, system etc. is responsible. In an email or on a support call it is likely you are going to hear collecting logs is
Backup Exec Job Log File Location
necessary to troubleshoot the issue. Some of the most common types of log gathering tools used
Backup Exec Debug Log
are the Backup Exec Debug Monitor (SGMon) and VxGather. These tools are often most effective when used in combination with each other. Here is a symantec backup exec logs sample example of a request for debugging to generate logs. 1. On the Media server and any other relevant servers open and set up the Debug Monitor (SGMon) 2. Start the Backup/Restore Job with the issue 3. Run the VxGather 4. Collect https://www.veritas.com/support/en_US/article.000087598 the logs The steps below give a typical example of the log gathering process. Steps (6 total) 1 Debugging with Backup Exec Debug Monitor (SGMon) When the Debug Monitor is opened it automatically captures debug data from the Backup Exec services and options. A valuable tool used by Symantec Technical Support to identify and resolve issues related to Backup Exec and the 3rd party applications running together. Open the Backup Exec Debug Monitor Console - SGMon on the Media Server: • For Backup https://community.spiceworks.com/how_to/24125-how-to-collect-backup-exec-logs-needed-for-troubleshooting-by-symantec-technical-support Exec version 2012 and higher: Click the Backup Exec Button > Technical Support > Collect debug output • For Backup Exec version 12.5 - 2010 R3: On the Tools menu, click Support Utilities > Run the Debug Monitor for active debugging • Or go to \Program Files \Symantec\Backup Exec\ - Run SGMon.exe To run SGMon on Remote Servers: • Go to \Program Files ) \Symantec\Backup Exec\ - Run SGMon.exe • Make sure the Job Engine, Backup Exec Server, Device and Media, Catalog and if applicable Third party debug output, along with the Capture to file check boxes are checked. • If you have other jobs you want to run before the job with the error and you don’t want the Debug Monitor to fill up with unnecessary data, SGMon can be set to run to a schedule. • In the Debug Monitor go to Tools, select the Backup Exec Debug’s Monitor Scheduler and then choose the desired Schedule option. NOTE: Keep the SGMon Console open (I usually minimize it) while the backup job runs for it to continue to collect debug output. Run the backup job with the error 2 It's not called VxGather for nothing! Some of the files the Symantec Gather Utility (VxGather) retrieves are: • Windows Event Logs • Backup Exec Installation logs • Backup Exec internal application logs • BEDIAG 3 Locate and Run • Go to: Media Server: \Program Files\Symantec\Backup Exec Windows 2008 \Program Data\Symantec\Backup Exec If applicable to the issue g
error on the symantec backup server exec server you may want to turn on http://clintboessen.blogspot.com/2010/01/enable-backup-exec-agent-debug-logging.html debug logging on the backup exec agent for the server http://searchdatabackup.techtarget.com/tip/Five-common-Backup-Exec-errors-and-how-to-resolve-them in question to help you diagnose the problem.To do this first stop the "Backup Exec Remote Agent for Windows Systems" service on the server with the problem.Edit the properties of the service and int he start parameters enter -debugNext you need to backup exec enable debugging in the registry:HKLM\Software\Symantec\Backup Exec for Windows\Backup Exec\Engine\LoggingChange the DWORD CreateDebugLog to "1" to enable debug logging:Next start the "Backup Exec Remote Agent for Windows Systems" service again.The logs will be located in this folder:C:\Program Files\Symantec\Backup Exec\RAWS\logsStart the backup and review the client log file for additional information as to what caused backup exec job it to error out. Posted by Clint Boessen at 6:05 PM Labels: Backup Exec No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Clint Boessen [MVP] clint.boessen@avantgardetechnologies.com.au Clint Boessen's Blog Clint Boessen Perth, Western Australia, Australia Microsoft Infrastructure Engineer MVP, MCSE, MCSA, MCTS, MCP MCITP: Enterprise Messaging Administrator MCITP: Enterprise Messaging Administrator 2010 MCITP: Server Administrator MCITP: Enterprise Administrator TS: SCOM My TechNet Posts Join My RSS Feed View my complete profile Awards Labels Active Directory (108) AD LDS / ADAM (11) Applications (39) Backup Exec (12) Citrix (2) Exchange 2000/2003 (67) Exchange 2007/2010 (261) Exchange 2013 (65) Exchange 2016 (9) F5 BIG-IP (1) Forefront (8) Hardware (23) IIFP / MIIS / ILM / FIM (2) Linux (11) Miscellaneous Posts (3) Networking (28) OCS/Lync (1) Office 365 (8) Outlook (43) SCCM (9) SCOM (3) Scripting (47) Security (6) SQL (16) System Center (1) Terminal Services (16) Trend Micro (7) Virtualizati
Backup software Backup tools View All Archiving Virtual server backup Cloud backup Security View All Data reduction View All Backup tools View All Archiving Backup software Virtual server backup Cloud backup Disk backup View All Remote backup View All Tape backup View All Topics Archive View All Data Backup Resources Please select a category Security Data reduction Backup tools Disk backup Remote backup Tape backup Section Problem Solve News Get Started Evaluate Manage Problem Solve Sponsored Communities peshkova - Fotolia Five common Backup Exec errors and how to resolve them byBrien Posey Symantec Backup Exec has a reputation for being reliable, but Backup Exec errors can occur within the Backup Exec Management Service or when services will not start. This Article Covers Backup software RELATED TOPICS Archiving Virtual server backup Cloud backup Looking for something else? Four data copy management misconceptions that affect your business What are some flat backup misconceptions? How an effective data archiving system can ease backup woes TECHNOLOGIES Error & error handling Storage Backup PRODUCTS Symantec Backup Exec + Show More In this Article Share this item with your network: Related Content Volume Shadow Copy Service-based backup – SearchDataBackup Troubleshooting Backup Exec 2012 synthetic full backup – SearchDataBackup Backing up Exchange Server with Microsoft VSS – SearchExchange Sponsored News How to Backup All You Want Without Consequences –SimpliVity Credit Union Thwarts Cryptolocker Attack With Smart Backup Policy –SimpliVity See More Vendor Resources Presentation Transcript: Mitigating challenges associated with virtual server ... –Hewlett-Packard Company Data Protection in a Hyper-V Environment –Dell, Inc. Symantec Backup Exec has been around in one form or another since the early 1990s and has a reputation as one of the more reliable backup products on the market. Even so, errors do occur. This tip discusses five of the most common Backup Exec errors and how to resolve them. Download this free guide Drill down into today's new backup approaches Due to the features of