OST upgrade
Hi, I need to upgrade OST plugin on Linux Media servers 7.7.2 because we have Data Domain OS upgrade lined up. Current OST version is 2.6.x and plan is to upgrade it to 3.2.5.0. As per DD Documentation i just need to stop NBU service on media server and install OST binaries and it will overwrite old OST binaries. My question is do i need to make any other change in NBU or DD for upgrading OST plugin and making it work except stopping NBU services and simply installing OST binaries?
HP StoreOnce 5100 w/ OST Driver 4.1.1.1 and job slowness?
We have been running Backup Exec 16 on 2012R2, with the OST 2.01 driver for about 5 months. I was noticing some tape not found errors, and also noticed the OST driver was updated to 4.1.1.1 and it included Server 2016 support and other additions. I updated one of our BE servers to it, and noticed the tape not found errors no longer randonly show up, however our backup times have doubled, and in some cases tripled. Same for the duplication processes as well. For both physical and virtual servers. Has anyone been noticing this? HPE just suggests allowing more streams per backup, but I think they don't realize that is a Netbackup feature, and not Backup Exec.eDiscovery Platform 9.0.1 Release
Hello Everybody, I wanted to let you all know that as ofMarch 11, 2018,eDiscovery Platform 9.0.1has been releasedeDiscovery Platform 9.0.1http://www.veritas.com/docs/100041628. This release addresses several issues intheInfrastructure, System Administration, Legal Hold,Identification and Collection,Case Administration,Processingand Production/Exportcomponentsidentified with theeDiscoveryPlatform 9.0release or earlier. This release also provides many significant featureenhancement highlights: Header-based single sign-on authentication for Legal Hold notices Earlier eDiscovery Platform supported integratedWindows authentication (IWA)single sign-on (SSO) for Legal Hold authentication. Starting with 9.0.1, header-based authentication single sign-on is also supported for Legal Hold authentication. If header-based authentication is enabled, the custom HTTP header with the username provided by the configured Identity Service Provider (ISP) is used for login through a reverse proxy. The custodian is directed to the Legal Hold notice without the need to enter login credentials. For details, see9.0.1 Legal Hold User Guide. Support for IPv6 address formats Earlier, eDiscovery Platform only supported IPv4 address format. Starting with 9.0.1, end-to-end workflow of eDiscovery Platform supports IP addresses in IPv4, IPv6, and dual stack mode. For details, see9.0.1 Distributed Architecture Deployment GuideandSystem Administration Guide. Onsite collection without user intervention 9.0.1 provides a programmatic way to runOnSiteCollectorin hidden mode without the need of any user intervention. For details, see9.0.1OnSiteCollections Reference Card.Users can use a command as shown in the following example to launch anOnSiteCollectorin hidden mode: D:\Clearwell\OnSiteCollector\exe\scandir\OnSiteCollector.exe -hwhere,<D:\Clearwell\OnSiteCollector>is the folder whereOnSiteCollectoris installed. Configurable option to process partially converted OST files 9.0.1 provides a way to process the partially converted OST files. When theesa.ost2.conversion_partial_successproperty is set to "true" usingSystem>Support Features>Property Browser, the partially converted OST files are processed successfully instead of sending them to theOST_Partial_ConvertedFilesdirectory. By default, the value of this property is set to "false" so that the existing workflow is retained where the partially converted OST files are copied to theOST_Partial_ConvertedFilesdirectory. For details, see9.0.1 Case Administration Guide. Configurable option to generate a slip sheet for excluded items Earlier a slip sheet was generated by default for the items of the document family that are not a part of the Production instead of completely skipping them. Starting with 9.0.1, users get a choice whether to include or exclude a slip sheet while setting up Production folders. For details,see 9.0.1 Case Administration Guide. Improvements in archive filtering for Enterprise Vault Collection, Search, and Hold tasks 9.0.1 provides an enhancement in archive selection while creatingEnterprise Vault Collection,Search, orHoldtasks. When archives are deleted on Enterprise Vault after you perform theEnterprise Vault discoveryon eDiscovery Platform, these deleted archives do not appear in the Archive Picker while selecting archives to add to theCollection,Search, orHoldtask. This enhancement prevents theCollection,Search, orHoldtasks resulting into Partial Success when vault store is selected instead of individual archives as the deleted archives are correctly filtered from the vault store. For details, see 9.0.1Identification and Collection Guide. Enhancements in collection set management 9.0.1 provides several improvements in collection set creation and management. For details, see 9.0.1Identification and Collection Guide. Task Description- While creating a collection set, you can hover on the task name to see its identifying information that helps to distinguish the task from the other tasks in the list. You can see "Task description: Task source: Size" if description is present in the collection task. If description for the collection task is not available, then "Task ID: Task source: Size" is displayed. Type Selection- Earlier, you could create collection sets of either“Metadataonly“or“Content and metadata” type. Now, “Content only” collection sets can also be created. Data for this collection set can only be exported in native format. The data is arranged in an appropriate hierarchy with respect to task, custodian, and source. The collection sets created using the "Content only" option do not appear in the list of collection sets on theProcessing>Sources and Pre-Processing>Manage Sourcesscreen. If you need to process the "Content only" collection sets, then you can add the data of these collection sets for processing underProcessing>Sources and Pre-Processing>Manage Sources>Add Case Folder Sourcescreen. Type Configuration- Earlier, the default option on theCreate Collection Setscreen was “Metadata only.” Now you can change the default collection set type by setting theesa.icp.collection.set.create.default_typeproperty using theProperty Browser. The values can be set to set the default collection set type toMETADATA_ONLY,METADATA_AND_CONTENT, orCONTENT_ONLY. Support for collection of additional data sources 9.0.1 supports collection ofFileShareshosted onWindows Server 2016. This release also supports directFileSharecollection ofMicrosoft Office 2016data. The supportedMicrosoft Office 2016file types areOneNote 2016,Word 2016 Documents,Excel 2016 Spreadsheets, andPowerPoint 2016 Presentations. Users may now download a zip file in Distributed Architectureenvironments Previously users in aDistributed Architectureenvironment were not able to download requestedExportpackages, such asProduction,Metadata, andNative 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 theCreate downloadable (zip) fileradio button on the Metadata tab on the export options window gives the user the option to download the export package, instead of accessing it from the specified appliance location. For details, see theExport and Production Guide. Please refer to theeDiscovery Platform 9.0.1 Documentationhttps://www.veritas.com/support/en_US/article.100040616for more detailconcerningtheaforementionedfeatureenhancements. There is a download link provided at the bottom of the article. As with any upgrade, please first refer to the 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 9.01 Release Notesfor your review.Dual NIC Media Server credentials already exist - OST / Data Domain
Hi all, I have a new Media Server with dual NICs, separate IP address and hostname for each, e.g. nbuserver-a & nbuserver-b. Both entries registered as Media Servers in the NBU domain. When attempting to add these two entities to the list of Media Servers able to address a Storage Server (OST-based Data Domain), I can add one but not the other. Error message advises 'Credentials already exist (99)'when attempting to add the second - as in picture attached. Any idea where I'm going wrong?
BE15, DataDomain optimized replication & replication to tape
We have two sites with two MBES servers on each site and a single DataDomain on each site. One site has a tape library. We also have a CASO server controlling the show. We wish to replicate backups to the DD on the other site, and write the monthly backups to physical tape (located in only one site). Site1: 2xMBES +DataDomain Site2: 2xMBES+DataDomain + Library + CASO We've got the DataDomain accessed through OpenStorage (DDBoost client) all fine. I discovered that both DD have to be presented toall BE servers - so that BE can perform a DDBoost optimized replication from one DD to the other. We configured two Server Pools, so when a backup is performed on Site1, it can be directed to just one of the Site1 MBES, and the same at Site2. Backing up to DD and replicating to the other site works fine - however I'm having issues when trying to replicate to the tape library in Site2. This works OK for backup jobs that start in Site2 since the MBES in Site2 can see both DataDomains and the tape library. However - for backups in Site1, when I try and do the same, it doesn't let me do this due to none of the Site1 MBES having access to the tape library: "The Backup Exec server specified and the device/storage devices pool specified do not share any devices". What I would like to do is configure the backup & DD replication to be performed by the Site1 Server Pool, but the replication to tape to be done through the Site2 Server Pool. How can this be done?
