NetBackup™ Self Service Configuration Guide
- Configuring a Self Service solution
- Configuring a NetBackup primary server
- About configuring the NetBackup primary server
- Enabling communication with a Windows NetBackup primary server
- Enabling communication with a UNIX NetBackup primary server
- Enabling communication with a NetBackup appliance
- Enabling communication with a NetBackup primary server using the REST API
- Creating NetBackup Template Policies
- Configuring Self Service
- Customizing Self Service
- User authentication methods
- Troubleshooting
- Appendix A. NetBackup policy types
- Appendix B. Dashboard traffic light status and usage
- Appendix C. Synchronizing data from NetBackup
- Appendix D. NetBackup Self Service data caching process
- Appendix E. Integration settings
- Appendix F. REST API
- Appendix G. Glossary
Where to find troubleshooting information
On the Backup Servers page the button tests the connection to each backup server in the system. Any failures show as a red cross which can be clicked to show error information.
Various log files, including the Error Log, are found in %ProgramData%\Veritas\NetBackupSelfService. This directory is also where the Integration, Audit, and Email logs are found. Errors can contain a System Reference which can be used to tie it back to a specific Request, and hence an Action.
If trying to locate failed NetBackup commands, performing a search for the text /bin or \bin can be helpful.
Self Service works by running NetBackup Commands on the command line of the primary server. If there is a problem running a command, it is included in the error in Self Service. Locating these errors is very helpful. Once you have an error with a NetBackup Command line, you can copy the command and try running it manually on the primary server. This technique is useful for troubleshooting.
Check for any errors on the NetBackup Activity Monitor especially against Job IDs that are identified.
Template Policies must be configured in certain ways to function correctly. When you check policy templates, refer to the Protection page in Admin. Click from the cog button to generate a summary of outstanding changes.
An amber or a red cog in the Assets page highlights the problem assets.
A red cog indicates that a synchronization or an activity failure error has occurred previously.
An amber cog indicates that a synchronization or an activity failure error has occurred previously but that an activity is currently in progress.
From the details pop-up select the Details tab which provides you with the last error and the stack trace.
Can be viewed as an MSP admin user in computer detail pop-up.
In the case that image or protection details don't seem correct for an asset, run for the asset using the button.
Tracing can be configured to analyze problems on a more detailed level. This method is a more advanced troubleshooting method. Do not attempt this method without the assistance of support. See the ReadMe.txt in Services Site\Logs and Panels Site\Logs.