First time upgrading - checking my steps
Hi All Looking to do my first EV upgrade, normally this has been actioned by another colleague who has since retired. Currently we're on EV 12.1.2 and looking to go to 12.5.3. Our environment is: 4x Win2012 servers (2 x storage/task servers and 2 x indexing servers), SQL 2012 server, Storage is handled by CIF shares. We're currently running onprem Exchange 2016 servers. We don't use EV reporting, discovery or any smtp/journal archiving Pre-change: Confirm backups of application servers and SQL Confirm AV off Confirm disk space Run deployment scanner check Get new clients packaged ready to deploy Change Day: Stop all EV services and set to manual Check all MSMQ are empty Copy and backup EV folder forwebapp.ini and web.config files Upgrade all 4 servers but DO NOT reboot until all are done Run cmdlet Start-EVDatabaseUpgrade to upgrade SQL db 12.5.3 install on all 4 servers a) have I got the above steps correct? b) my previous colleague would also put the Vault Stores in Backup mode, is this necessary since I'm stopping the EV services and changing them to Manual startup for the duration? c) he also noted something aboutCheck Statistics have been dropped on Vault SQL Databases, what is this? d) Do I need to upgrade OWA extensions on each Exchange server as well? e) the client app deployment is handled by another team, does it matter if the server is 12.5.3 but the client is 12.1.2 for a short duration? f) any other step I'm missing? Thanks in advance.
Move archive in different EV directory?
Hi, i have a EV 9.02enviroment with100 users and 400 GB data in Physical HW (this physical HW will be shutdown after this process) i have to migrate existing old EV environemnt to new virtual 2012 environment.I will install EV 11.01 latest version(without HW migration process) what is your advice for move archive feauture for carrying old archived data to new EV server? my new server ready to installation.but if i install new binary with new directory name and new site name ; then i have 2 different EV server witin same domain.i can move archives old EV server archives to new one? or what is your other suggestions? -installing under same directory ; can couse problems when deleting old Ev server? - 2 different directory and 2 different site name is better ?then move archive for 80-90 user (i know that move archive works slowly..) can i work with 2 different EV server within same domain? i can see other ev server name in mpvearchive wizard easly?(no need to trust because they are in same domain) thanks...
MySQL 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.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.eDiscovery Platform 9.0 General Availability
Hello Everybody, I am excited and proud to announce the General Availability of eDiscovery Platform 9.0 as of December 22, 2017. This is a major release that incorporates many significant feature, product and security enhancements, improvements and fixes. With GDPR (General Data Protection Regulation) as the primary theme around this release, new features for data classification, improved performance, resiliency, scalability and workflow have been added to enhance the eDiscovery experience. Some of the highlights of the release include the following: Information Classification Starting with version 9.0, the eDiscovery Platform lets you automatically classify sensitive and critical case data based on a set of built-in and custom policies. Note: The Information Classification feature can only be enabled for cases created in version 9.0 and later. Cases created before version 9.0 are not supported. The platform integrates with Veritas Information Classifier (VIC) to analyze and classify eDiscovery data. VIC uses both predefined and user-defined policies to assign classification tags to your eDiscovery data during the processing phase. Once these tags have been applied,users can view pre-selected classification filters (system tags) in the Analysis and Review mode to quickly identify documents that match the VIC tags. Bulk Redaction and Delete Bulk Redaction Bulk redaction provides the ability to redact multiple documents in a Redaction Set without having to individually open and review each and every document in the Native Viewer. You can easily specify the redaction text along with the reason code that needs to be applied on theredacted text to all selected documents. Bulk redaction works on redaction sets with preset reason codes and with free-text reason codes. The delete bulk redaction option makes it easy to delete all redactions and annotations for a set of documents in a redaction set. Redaction sets with preset reason codes Currently, case reviewers can add free text as a reason for redaction while redacting a document. New functionality is available so the Case Administrator can define preset reason codes. Reviewers will then be able to redact documents by applying reason codes consistently. The Case Administrator can create redaction sets with either predefined reason codes or free text reason codes. Case reviewers can apply the preset reason codes to redaction markups. Case reviewers can search, filter, or export documents based on the preset reason codes. Annotations in review mode In addition to the existing capability to redact a document, this release adds the ability to annotate a document in review mode. Case reviewers can annotate a document by adding comments or graphical stamps, or strike out some text. Case reviewers are also allowed to delete annotations. Case reviewers can also search the document for the Redacted Tag. Once annotated, the document can be reviewed by another reviewer, who can also add annotations. Case Backup Integrity During an eDiscovery Platform backup, empty directories may be created in the backup structure. If a case backup directory is then moved and empty directories are not copied, a restore job will subsequently fail. With this release, restore job for a case backup with empty directories does not fail. With the Case Backup Integrity feature, a checksum of the case backup directory is created during both the backup and the restore job. The checksum file created during the restore job is compared with the checksum file created during the backup job. If any empty directory is identified, then these empty directories are created at their specific paths during restore. This results in the success of the restore jobs. Automatically convert OST to PST Data Files for processing The eDiscovery Platform can now seamlessly convert OST files to PST files for processing. 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 Veritas eDiscovery Platform supports Integrated Windows Authentication (IWA) Single Sign-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 deprecated support for RPC over HTTP on October 31st 2017. With this release, the Veritas eDiscovery Platform will now use MAPI/HTTP to connect to Office 365 in support of this change. The eDiscovery Platform 9.0 installer automatically installs the KB3114941 updates for Outlook 2013 32-Bit Edition that enables the MAPI/HTTP protocol required to collect data from Office® 365 mailboxes. See the 9.0 Identification and Collection Guide for details and troubleshooting steps. Refer eDiscovery Platform 9.0 Release documentation as follows: Late Breaking News for eDiscovery Platform 9.0 http://www.veritas.com/docs/100041303 New Features Overview 9.0 https://www.veritas.com/content/support/en_US/doc/edp90_NFO_guide_v1_v90_00 Veritas eDiscovery Platform 9.0 Release Notes https://www.veritas.com/content/support/en_US/doc/edp90_release_notes_v1_v90_00 eDiscovery Platform 9.0 - Documentation http://www.veritas.com/docs/100040616 As with any upgrade, please first refer tothe upgrade support documents: Supported upgrade paths for eDiscovery Platform http://www.veritas.com/docs/000095769 eDiscovery Platform Compatibility Matrix 9.0 http://www.veritas.com/docs/000019811access enterprise vault 12 media for upgrade
Hi all I've got just a couple of EV installs so I attend to this not too often. But now I need to upgrade one of the installations to version 12. But is there anyway to download version 12 - we have maintenance. Or do I have to request media from sales/support?
Enterprise Vault 12.2.1 released.
All, EV 12.2.1 has been released and can be found here -https://www.veritas.com/support/en_US/article.000127352 This has many fixes including one for File Server Archiving where file server shares would become inaccessible for a period of time during large file recalls. This was due to an SMB thread issue that has been resolved. Regards, Patrick
