NetBackup™ Web UI Cloud Administrator's Guide
- Introducing the NetBackup web user interface
- Monitoring NetBackup
- Managing and protecting cloud assets
- About protecting cloud assets
- Limitations and considerations
- Configure CloudPoint servers in NetBackup
- Managing intelligent cloud groups
- Protecting cloud assets or intelligent cloud groups
- Cloud asset cleanup
- AWS and Azure government cloud support
- About protecting Microsoft Azure resources using resource groups
- About the NetBackup Accelerator for cloud workloads
- Configuring backup schedule for cloud workloads
- Backup options for cloud workloads
- Snapshot replication
- Configure AWS snapshot replication
- Using AWS snapshot replication
- Support matrix for account replication
- Protect applications in-cloud with application consistent snapshots
- Discovering PaaS assets
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
Troubleshoot cloud workload protection issues
Review the following log files to troubleshoot any issues with protection of cloud assets:
During troubleshooting, ensure that you have also reviewed the limitations. See Limitations and considerations.
For troubleshooting issues, see the NetBackup Status Codes Reference Guide.
To view the CloudPoint log files, see the CloudPoint logs topic in the NetBackup CloudPoint Install and Upgrade Guide.
Use the following logs to troubleshoot cloud configuration issues.
Table: Log files for configuration
Process | Logs |
|---|---|
tpconfig tpconfig command is one way for registering CloudPoint in NetBackup. | Windows
UNIX
|
nbwebservice Plug-ins are configured using NetBackup REST API. | Windows
UNIX
|
nbemm nbemm stores the CloudPoint server and plug-in information in EMM database | Windows
UNIX /usr/openv/logs/nbemm |
Use the following logs to troubleshoot asset discovery issues.
Table: Log files for asset discovery
Process | Logs |
|---|---|
ncfnbcs Verifies if discovery was completed or not. | Windows
UNIX
|
Picloud Provides the details of discovery operation. | Windows
UNIX
|
nbwebservice To get details about the asset database workflows that are part of the discovery operation. Note: Refer to the same log files for details of assets that are added to protection plan. | Windows
UNIX
|
Use the following logs to troubleshoot snapshot creation issues.
Table: Log files for snapshot creation
Process | Logs |
|---|---|
nbpem nbpem PID for given job is available in the NetBackup activity monitor. | Windows
UNIX
|
nbjm nbjm PID for given job is available in the NetBackup activity monitor. | Windows
UNIX
|
nbcs nbcs PID for given job is available in the NetBackup activity monitor. | Windows
UNIX
The nbcs logs are available at the following location: Windows
UNIX
|
nbrb nbrb is requested to provide a media server for a given job. For Cloud, a particular media server is picked up from the associated list of media servers for a CloudPoint server. | Windows NetBackup install path/bin/vxlogview - o 118 UNIX
|
Use the following logs to troubleshoot restore issues.
Table:
Process | Logs |
|---|---|
nbwebservice The snapshot restore operation is triggered by NetBackup REST API. | Windows
UNIX
|
bprd The NetBackup REST API communicates with bprd to initiate restore | Windows
UNIX
|
ncfnbcs nbcs PID for given job is available in the NetBackup activity monitor. | Windows
UNIX
|
Use the following logs to troubleshoot snapshot deletion issues.
Table: Log files for snapshot deletion
Process | Logs |
|---|---|
bpdm The snapshot delete or clean-up operation is triggered by bpdm. | Windows
UNIX
|
ncfnbcs nbcs PID for given job is available in the NetBackup activity monitor. | Windows
UNIX
|
When attempting to perform recovery of a VM from a backup image copy, if you do not have the required privileges assigned to your role to perform alternate location restore, you encounter the error during the pre-recovery check operation.
This may happen when you have privilege to perform only original location recovery, and you are trying to do alternate location recovery.
Workaround
While doing original location restore, do not change any pre-populated fields in the pre-recovery page.
If you want to perform alternate location recovery, ensure that you have the required privileges.