I have upgraded my Master server (running Solaris 11) from 7.7.3 to 8.1.2, at which time I transferred the Smart Meter data generated by the nbdeployutil. The nbdeployutil is running every 7 days and generating the files on the master server. Is there something that needs to be automated or enabled to then upload this information?
your Netbackup master server needs to have connectivity over 443 port to send the data to Vertias (smart meter) , if it does not have the connectivity, you need to uploaded the nbdeployutil files manually
see below notes
The required telemetry information is uploaded to Veritas in two different ways. Your upload method choice depends on your preference.
By default, the data is uploaded automatically every day. This method requires the least user intervention and ensures the Smart Meter data is current. This method requires an open port on your firewall to transmit HTTPS traffic. The default port for HTTPS traffic is port 443.
If your environment does not allow for automatic uploads, you can manually upload the required telemetry information.
Thank you for your response. Do you happen to know what the server name or IP address this would connect to? My security would like to tie down the outgoing connection to a specific server or address.
The server is telemetry.veritas.com - this is a host living behind a load balancer in AWS, so you would need to use a DNS query each time to get definite IP addresses. It only uses HTTPS protocol, so port 443.
This information is contained (though well hidden) in the Smart Meter Getting Started Guide.
I have verified that there are no firewall rules blocking coonectivity between the servers (I was able to telnet to port 443 to all servers defined at AWS). Is there something else that needs to be running or configured to allow this data to be sent?
I sugest you have a look at FAQ section of the Smart Meter Getting Started Guide. It has some hints about what to look for to troubleshoot the issue you appear to be having.
Also have alook at this article to see if it helps https://www.veritas.com/support/en_US/article.100044028.html
If all else fails, then I'd log a support call to have them investigate further.
I am finding that the running of nbdeployutil ( even after getting the updated hotfix version) for the first time after upgrading to 8.1.2 takes several days. It is possible that it is still processing.
If you look in the /usr/openv/var/global directories you should be able to find the files and check the logs - mine is STILL updating the first time since I started it on Tuesday 6/25
Thank you for your response. I upgraded the Master server at the end of May. I see the following files in /usr/openv/var/global/incremental:
-rw-r--r-- 1 root root 1520749 May 30 00:51 nbdeployutil-report-capacity-20190530_000011.log
-rw-r--r-- 1 root root 2397385 Jun 6 00:43 nbdeployutil-report-capacity-20190606_000015.log
-rw-r--r-- 1 root root 5268285 Jun 13 00:47 nbdeployutil-report-capacity-20190613_000015.log
-rw-r--r-- 1 root root 6967885 Jun 20 00:47 nbdeployutil-report-capacity-20190620_000015.log
-rw-r--r-- 1 root root 9069754 Jun 27 00:49 nbdeployutil-report-capacity-20190627_000015.log
which shows that the information is being collected weekly but not being sent out. As I stated previously, I can connect to the Smart Meter update servers over port 443.
These are the last few lines from the latest log file:
Jun 27 00:49:02 +0100 (mesg ) Report created at: /usr/openv/var/global/incremental/report-capacity-20190627_000015.xls
Jun 27 00:49:02 +0100 (notice ) Moving old reports to archive directory: /usr/openv/var/global/incremental/archive
Jun 27 00:49:02 +0100 (debug: incremental) Archive directory present, moving report(s) to archive
Jun 27 00:49:02 +0100 (notice ) Moved all reports to archive directory: /usr/openv/var/global/incremental/archive, except: /usr/openv/var/global/incremental/report-capacity-20190627_000015.xls
Jun 27 00:49:02 +0100 (mesg ) Analysis DONE
Jun 27 00:49:02 +0100 (mesg ) Execution time: 48 mins 47 secs
Jun 27 00:49:03 +0100 (debug: exit) running cleanup routine CODE(0xf4e020), cleanup temporary files
Jun 27 00:49:03 +0100 (debug: exit) running cleanup routine CODE(0x2c8548), undef
Also, here is some log information from the telemetry/status directory:
Just to update this discussion, I have a case open with Tech Support for over 2 months now. They have been working to resolve the issue but they are still stumped as to what / where the issue is. I will post an update after it is resolved.