8.3: nbcertcommand -signCertificate fails on solaris with "-noPrompt" not valid when used with ...
Hi, I'm in the middle of upgrading my 8.1.2 Solaris 10 and 11 Sparc clients to v8.3, but because some/most of the clients are behind firewalls or in the DMZ, I can't seem to run the nbcertcmd on them to get a certificate. So now I'm trying to do the dance of: on client: nbcertcmd -createCertRequest -requestFile /tmp/cert-req -server nbu-server then I copy the /tmp/cert-req file to my "nbu-server" and run on the "nbu-server" (which is running: Solaris 11.2 sun4v sparc) the nbcertcmd to sign the request, but the **bleep** thing fails. # /usr/openv/netbackup/bin/nbcertcmd -signCertificate -validFor 2D -requestFile /tmp/cert-req -certificateFile /tmp/cert-signed Option '-noPrompt' is not valid when used with operation '-signCertificate'. Option '-file' or '-validFor' is mandatory to complete operation '-signCertificate'. Usage: nbcertcmd -signCertificate -validFor | -file <authorization_token_file> -requestFile <request_file_name> -certificateFile <certificate_file_name> Description: Reads the certificate signing request from the specified request file and sends it to the master server to get a NetBackup CA-signed certificate. The signed certificate is stored in the specified certificate file. The command must be executed on the NetBackup host that has connectivity with the master server. Options: -certificateFile certificate_file_name Specifies the path of the certificate file. -file authorization_token_file Path of the file containing authorization token on the first line. -requestFile request_file_name Specifies the path of the certificate request file. -token Indicates that an authorization token is used for the request. Prompts the user to securely specify a token. EXIT STATUS 20: invalid command parameter I don't use the "-noPrompt" flag anywhere. And I can't figure out how to make this work. Do I really need to also regenerate a token for this client? I have to say that this entire move to security has been a total pain in the ass, because it's makes things so fragile. I wish I could just turn this off for internal only hosts.Solved2KViews0likes5CommentsNetBackup 8.3 WebUI Instant Access feature not enabled
Hi all, The latest episode on my epic adventure into the excitingly exotic world of NetBackup WebUI... After creating a MSDP storage server and disk pool for a Red Hat 8.2 media server (done inside the WebUI), when I click the MSDP storage server to drill down in to the properties, Instant Access is shown to be disabled, as shown in the image. Indeed, after a successfull backup of a VM in to the MSDP, the WebUI Instant Access feature cannot be used on the VM, only VM image or file-folder restores are possible for the VM. I've tested this on both Red Hat 8.2 and CentOS 7.6, and this issue happens in both cases. According to the documentation WebUI Instant Access for Red Hat based MSDP for VM backups should simply just work. Not sure what else to check. I'm wondering if this is because the Red Hat and CentOs Media Servers are VMware VMs? It's going to be a pain to have to prepare a physical Red Hat server just to test and possibly enable Instant Access if that's the case. Any ideas? Thanks all.Solved2.6KViews0likes3CommentsNetBackup 8.3 - Exchange Policy Bugs
Hi All, Just upgraded my NetBackup environment from 8.2 to 8.3 and I noticed the following bugs with Exchange policies. 1. When I try to create a new policy I simply can't finish the procedure because of the following error: Please select a valid snapshot method using 'Snapshot Client Options'. Now when I hit the corresponding "Options" button on the policy screen, nothing happens and I'm not able to see the usual screen where the VSS method is chosen by default with it's corresponding parameters. Everytime I hit the "Options" button literally nothing happens and the only way to save the policy is by unticking the "Perform snapshot backups" checkbox which at least will let you hit the "OK" button at the bottom. When I reopen the same policy, the "Perform snapshot backups" checkbox is once again ticked but still there is no way to modify anything within the "Options" section. 2. When I run the newly created policy, I receive the following error message: This type of backup is not supported on this version of Exchange the client type is incorrect in the configuration database (72) By my best knowledge both Windows Server 2019 and Exchange 2019 CU6 are fully supported and my policy is set just as per the expected rules according to the NBU documentation. So all in all right now it is impossible to backup Exchange with the new NBU 8.3 version. Any suggestions you may have are highly welcome. For the record I don't have active support contract with Veritas therefore I can't open a support ticket with the vendor.5.4KViews0likes18Comments