Extracting NetBackup logs
You can extract NetBackup logs from the Cloud Scale environment using the following options:
(Recommended) Use the NetBackup Troubleshooting APIs for log extraction requests
Copy logs out of the log-viewer using the kubectl commands
Copy logs out if the log-viewer or nbwsapp are not working
NetBackup Cloud Scale Technology introduced log extraction APIs in version 11.0 to assist in extracting logs from a Cloud Scale environment.
Table: Extract logs via APIs
Action | Command / Description |
|---|---|
In order to extract logs via the APIs you must go through a series of calls to create a request and extract the logs. All API endpoints require a valid JWT Authorization header. |
|
: The endpoint has filters that can be applied to target specific logs that the user wants to gather.
Following filters exist:
| |
directories: Legacy log directories to pull logs from. | |
fileIds: A list of UL file ID's to pull logs from. |
It is recommended to use the provided filters to be specific about log request in order to avoid timeout. Default: 60 min
Note:
All the filters are optional and have an AND relationship. This indicates that if you provide filters from multiple categories, they must match all the categories to be considered valid for extraction.
Among the filtering options specified above, is applicable to every log. But and is applicable only to logs that are part of those specific categories.
For example, if you applied a date range via globalFilters and applied a legacyLogFilter and a unifiedLogFilter then you would get all legacy logs that fit the legacyLogFilter and the globalFilters and all unified logs that fit the unifiedLogFilter and the global filters.
By default, some of the logs have long names and long paths. This can cause issues on windows when extracting the logs on a windows computer. Hence the logs would be skipped and would not be a part of the resultant unzipped folder. Hence it is recommended that you extract these logs onto a Linux based file system.
In order to extract the logs out of the log-viewer pod there are a few options. You can tar and compress the logs before extraction or extract them immediately.
(Optional) Tar up the files you want to extract. Select a folder and run:
$ tar -cvf <name of tar> <name of folder>
Copy the files out of the container. Exit the container using the command:
$ kubectl cp -n netbackup <pod-name>:/usr/openv/fluentbit/logs/<folder or tar> <output folder or tar>
(Optional) Extract the tar outside the container if necessary:
$ tar xvf <output tar>
If or pods are not working, then you need to extract logs from other pods. Use the following command to copy logs out of the pods:
$ kubectl cp -n netbackup <pod-name>:/usr/openv/fluentbit/logs/<folder or tar> <output folder or tar>
The first pod to try must be fluentbit collector pod as it also mounts the file system storing all the Cloud Scale logs. If the fluentbit collector pod is not working you will need to copy the logs directly from individual application pods such as nbwsapp or primary. Logs within application pods are usually stored at /mnt/nblogs directory.