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.Solved1.9KViews0likes5CommentsNetBackup 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.5KViews0likes3CommentsNetBackup 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: ThistypeofbackupisnotsupportedonthisversionofExchange theclienttypeisincorrectintheconfigurationdatabase (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.3KViews0likes18CommentseDiscovery Platform 8.3 Cumulative Hotfix 4 Release
Hello Everybody, I wanted to let you all know that as of April 9, 2018, eDiscovery Platform 8.3 CHF4 has been released eDiscovery Platform 8.3 CHF4 Release https://www.veritas.com/support/en_US/article.100042225 This release addresses several issues intheInfrastructure, System Administration, Legal Hold,Identification and Collection,Case Administration,Print/Exportcomponentsidentified with theeDiscoveryPlatform 8.3release or earlier. This release also provides a few significant featureenhancement highlights: Improvements in archive filtering for Enterprise Vault Collection, Search, and Hold tasks 8.3 CHF4 provides an enhancement in archive selection while creating Enterprise Vault Collection, Search, or Hold tasks. When archives are deleted on Enterprise Vault after you perform the Enterprise Vault discovery on eDiscovery Platform, these deleted archives do not appear in the Archive Picker while selecting archives to add to the Collection, Search, or Hold task. This enhancement prevents the Collection, Search, or Hold tasks resulting into Partial Success when vault store is selected instead of individual archives as the deleted archives are correctly filtered from the vault store. Enhancements in collection set management Earlier, the default option on the Create Collection Set screen was “Metadata only.” Now you can change the default collection set type by setting the esa.icp.collection.set.create.default_type property using the Property Browser. The values can be set to set the default collection set type to METADATA_ONLY or METADATA_AND_CONTENT. The hotfix by downloading from the aforementioned link and installing from the exe file. As with any upgrade, please first refer tothe upgrade support documents: Supported upgrade paths for eDiscovery Platform https://www.veritas.com/support/en_US/article.000095769 eDiscovery Platform Compatibility Matrix https://www.veritas.com/support/en_US/article.000019811 Make sure to bookmark and subscribe to Updates, Patches and Late Breaking News for eDiscovery Platform 8.3 https://www.veritas.com/support/en_US/article.100039146 for all future updates on eDiscovery Platform 8.3. Attached are the eDiscovery Platform 8.3Cumulative Hotfix 4Release Notes for your review.1.4KViews0likes0CommentsMySQL 5.6.39 Upgrade for eDiscovery Platform 8.3 and 9.0
Hello Everybody, I wanted to let you all know that as ofMarch 29, 2018,MySQL 5.6.39 Upgrade for eDiscovery Platform 8.3 and 9.0has been releasedMySQL Upgrade for eDiscovery Platform 8.3 / 9.0https://www.veritas.com/support/en_US/article.100034299 The Veritas eDiscovery Platform MySQL Upgrade installer has been created to allow customers to upgrade their eDiscovery Platform 8.3 and 9.0 installs to the latest tested version of MySQL to meet security needs. This installs MySQL version 5.6.39. The upgrade includes both the MySQL Server software as well as the MySQL connector library used by the eDiscovery Platform. If you're not already, make sure you subscribe to the article to get notified of future MySQL upgrades as they're released. The upgrade can be applied by downloading from the aforementioned link and installing from the exe file. Please make sure to follow the steps listed in the article, especially the step of performing a full node backup.1.4KViews0likes0CommentseDiscovery Platform 8.3 Cumulative Hotfix 3 Release
Hello Everybody, I wanted to let you all know that as of October 2, 2017,eDiscovery Platform 8.3 CHF3has been releasedeDiscovery Platform 8.3 CHF3 Releasehttps://www.veritas.com/support/en_US/article.000128033. Besides a good many fixes, this release containsthe following new feature: Users may now download a zip file in DA environment Previously users in a Distributed Architecture environment were not able to download requested export packages, such as production, metadata, and native exports. The user was given an info bubble with a location for the zipped file. In a DA environment, not all users will have permissions allowing them access to the designated location on the specified appliance. In this fix users will have a choice. Selecting the Create downloadable (zip) file radio button gives the user the option to download the export package, instead of accessing it from the specified appliance location. You can apply the hotfix by downloading from the aforementioned link and installing from the exe file. As with any upgrade, please first refer tothe upgrade support documents: Supported upgrade paths for eDiscovery Platformhttps://www.veritas.com/support/en_US/article.000095769 eDiscovery Platform Compatibility Matrixhttps://www.veritas.com/support/en_US/article.000019811 Attached are theeDiscovery Platform 8.3Cumulative Hotfix 3 Release Notesfor further review.1.1KViews2likes0CommentseDiscovery Platform 8.3 Cumulative Hotfix 2 Release
Hello Everybody, I wanted to let you all know that as of October 2, 2017, eDiscovery Platform 8.3 CHF2 has been released eDiscovery Platform 8.3 CHF2 Release https://www.veritas.com/support/en_US/article.000128033. Besides a good many fixes, this release contains several highlights: Automatically convert OST to PST Data Files for processing The eDiscovery Platform can now seamlessly convert OST files to PST files for processing. Starting with 8.3 CHF2, OST data files are converted to PST data files during the discovery phase. Upon successful completion of this operation, normal PST processing is applied to the files for easy access, review, and analysis. See technical article for details: https://www.veritas.com/support/en_US/article.000128050 Integrated Windows Authentication Single Sign-On for Legal Hold Starting with 8.3 CHF2, Veritas eDiscovery Platform supports Integrated Windows Authentication (IWA) SingleSign-On (SSO) for Legal Hold authentication. When IWA SSO is configured, the logged-in Windows credentials of the custodian are used for authentication, and the custodian is subsequently directed to the Legal Hold Confirmation page without the need to enter login credentials. To use the SSO option, LDAP must be configured and enabled against the Active Directory domain from which Windows users will be authenticating. See technical article for details: https://www.veritas.com/support/en_US/article.000128049 Office® 365 connection using MAPI/HTTP Microsoft is deprecating support for RPC over HTTP on October 31st 2017. With 8.3 CHF2, the Veritas eDiscovery Platform will now use MAPI/HTTP to connect to Office 365 in support of this change. After the 8.3 Cumulative Hotfix 2 is installed, Administrators who want to collect data from Office® 365 mailboxes must also download and install the KB3114941 updates for Outlook 2013 32-Bit Edition that enables Office® 365 connection using MAPI/HTTP to the eDiscovery Platform servers connecting to Office 365. Administrators can download the KB3114941 Outlook update from https://www.microsoft.com/en-us/download/details.aspx?id=51720 and then manually install it. See technical article for details and troubleshooting steps: https://www.veritas.com/support/en_US/article.000128048 You can apply the hotfix by downloading from the aforementioned link and installing from the exe file. As with any upgrade, please first refer tothe upgrade support documents: Supported upgrade paths for eDiscovery Platform https://www.veritas.com/support/en_US/article.000095769 eDiscovery Platform Compatibility Matrix https://www.veritas.com/support/en_US/article.000019811 Attached are the eDiscovery Platform 8.3Cumulative Hotfix 2Release Notes for your review.1.4KViews2likes0Comments