Veritas NetBackup™ CloudPoint Install and Upgrade Guide
- Section I. CloudPoint installation and configuration
- Preparing for CloudPoint installation
- CloudPoint host sizing recommendations
- Deploying CloudPoint using container images
- Deploying CloudPoint extensions
- Installing the CloudPoint extension on AWS (EKS)
- CloudPoint cloud plug-ins
- CloudPoint storage array plug-ins
- NetApp plug-in configuration notes
- Nutanix Files plug-in configuration notes
- Dell EMC Unity array plug-in configuration notes
- FUJITSU AF/DX plug-in configuration notes
- NetApp NAS plug-in configuration notes
- Dell EMC PowerStore plug-in configuration notes
- Dell EMC PowerStore NAS plug-in configuration notes
- Dell EMC PowerFlex plug-in configuration notes
- Dell EMC XtremIO SAN plug-in configuration notes
- Pure Storage FlashArray plug-in configuration notes
- Pure Storage FlashBlade plug-in configuration notes
- IBM Storwize plug-in configuration notes
- HPE RMC plug-in configuration notes
- HPE XP plug-in configuration notes
- Hitachi plug-in configuration notes
- Hitachi (HDS VSP 5000) plug-in configuration notes
- InfiniBox plug-in configuration notes
- Dell EMC PowerScale (Isilon) plug-in configuration notes
- Dell EMC PowerMax and VMax plug-in configuration notes
- Qumulo plug-in configuration notes
- CloudPoint application agents and plug-ins
- Oracle plug-in configuration notes
- Additional steps required after a SQL Server snapshot restore
- Protecting assets with CloudPoint's agentless feature
- Volume Encryption in NetBackup CloudPoint
- CloudPoint security
- Preparing for CloudPoint installation
- Section II. CloudPoint maintenance
- CloudPoint logging
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Troubleshooting CloudPoint
CloudPoint logs
CloudPoint maintains the following logs that you can use to monitor CloudPoint activity and troubleshoot issues, if any. The logs are stored at <install_path>/cloudpoint/logs
on the CloudPoint host.
Table: CloudPoint log files
Log | Description |
---|---|
| This log file contains all the product logs. |
| This log file contains all the CloudPoint installation related logs. |
| This log file contains all the IPv6 related logs. |
Navigate to: /cloudpoint/openv/dm/datamover.<id>
Here, logs can be found in the following directories: logs
, opt
and the netbackup
.
nbpxyhelper
andnbsubscriber
logs can be found inside thelogs
directoryVRTSpbx
logs can be found inside theopt
directorybpbkar, bpcd, bpclntcmd, nbcert, vnetd, vxms
and all other services logs can be found insidenetbackup
directory
To increase logging verbosity, bp.conf
and nblog.conf
files can be updated on CloudPoint server at /cloudpoint/openv/netbackup
. See NetBackup Logging Reference Guide
Changes to the bp.conf
and nblog.conf
files come to effect when the next backup from snapshot or restore job runs.
The default configuration for datamover logs is as follows:
Log retention maximum period is 30 days. Logs older than 30 days are deleted.
The default configuration for high and low water marks for datamover logs is 70% and 30% of the size of "/cloudpoint" mount point. For example, if the usable size of the
/cloudpoint
folder is 30 GB, then the high water mark is 21 GB (70%) and low water mark is 9GB (30%). In case, the logs directory (/cloudpoint/openv/dm/
) size reaches to high water mark, older logs for which the datamover containers are cleaned up and no longer running are considered for deletion. The logs are deleted for such datamover containers until low water mark is reached or no logs are remaining for the datamover containers cleaned up or no longer running.
Modifying the default configuration:
You can modify the default configuration for log retention by adding such a section in the flexsnap.conf
on the primary CloudPoint server. Open the flexsnap.conf
file from the path /cloudpoint/flexsnap.conf
and add the following section:
[datamover] high_water_mark = 50 low_water_mark = 20 log_retention_in_days = 60
In case of CloudPoint extensions, the configuration from the primary server are used. Once the configuration is changed in primary CloudPoint server, the configuration is updated on each CloudPoint extension within one hour. It is not possible to have separate custom configurations for primary CloudPoint or the CloudPoint extensions and configurations should only be changed in the primary CloudPoint server. Though the configuration is same for primary as well as CloudPoint extensions, the high water mark and low water mark for log size are calculated based on the /cloudpoint
mounted on each primary or CloudPoint extensions.
Each CloudPoint extension maintains the logs under its own /cloudpoint/logs
location.
VM-based extension logs: Under the directory
/cloudpoint/logs
.Managed Kubernetes cluster-based extension logs: Under the directory
/cloudpoint/logs
which belongs to a file share.