Hotfix for Discovery Accelerator 9.0.0, 9.0.1, 9.0.2, Applying of Legal Holds loop continually

Article:TECH156905  |  Created: 2011-03-30  |  Updated: 2011-07-27  |  Article URL http://www.symantec.com/docs/TECH156905
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Environment

Issue



Legal Hold Integrity Check processing loops continually.


Error



Issue 1 - Connection Time out: Sample Dtrace log entries for the AcceleratorService process, recorded during Legal Hold Integrity Check processing:

 - (AcceleratorService) <Legal Hold Thread - worker thread (5):15784> EV-H {-} {LEGALHOLD.EN_US} {C2.EN_US} LHIC: Exception in ValidateHolds for CaseID 3: [Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.] (Exception type: System.Data.SqlClient.SqlException)
 - (AcceleratorService) <Legal Hold Thread - worker thread (5):15784> EV-H {-} {LEGALHOLD.EN_US} {C2.EN_US}    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)|   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)|   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)|   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)|   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)|   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)|   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)|   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)|   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()|   at KVS.Accelerator.LegalHold.LegalHold.ChangeAllItemsLegalHoldStausToNoHold(Int32 CaseID, String vaultStoreEntryID)|   at KVS.Accelerator.LegalHold.LegalHold.ValidateHolds(Int32 CaseID, String GroupId, String ConsumerId)

Issue 2 - Count mismatch: Sample dtrace log entry for the AcceleratorService process, recorded during Legal Hold Integrity Check processing:

 - (AcceleratorService) EV-L {LEGALHOLDQUEUES.EN_US} {C2.EN_US} Legal Hold Thread - worker thread (5): Case ID 3. 'Validating Holds' started at 1/1/2011 01:01:01 AM
 - (AcceleratorService) EV-L {-} {LEGALHOLDCASES.EN_US} {C2.EN_US} Legal Hold Thread - worker thread (5): LHIC: CaseID 3 update legal hold sych StatusID from ToValidate to Validating
 - (AcceleratorService) EV-H {LEGALHOLD.EN_US} {C2.EN_US} Legal Hold Thread - worker thread (5): Case ID 3. group ID'DA_DiscoveryCustomer_5284189A-F38A-4A0E-BADA-811D1C53635C' started [validating] Holds at 1/1/2011 01:01:02 AM for all Vault Directories
 
- (AcceleratorService) EV-L {-} {LEGALHOLD.EN_US} {C2.EN_US} LHIC: Proceeding to validate holds count for case [3].
 - (AcceleratorService) EV-L {-} {LEGALHOLD.EN_US} {C2.EN_US} LHIC: IsCaseGoodToProceedForSyncValidation(3) = True.
 - (AcceleratorService) EV-L {LEGALHOLD.EN_US} {C2.EN_US} LHIC: Case [3] is associated with [1] directory server(s). Will talk to each to collect item hold info.

 - (AcceleratorService) EV-L {LEGALHOLD.EN_US} {C2.EN_US} LHIC: Proceeeding to collect item hold info from directory server [EVServer1] (Ref: ConsumerID: [{6F020B03-44DA-4E1B-A535-73EDEAA38CC7}], GroupID: [DA_DiscoveryCustomer_5284189A-F38A-4A0E-BADA-811D1C53635C])
 - (AcceleratorService) EV-L {LEGALHOLD.EN_US} {C2.EN_US} LHIC: Call to CMAPI (IHolds3.Get()) to get items hold count details from directory server [EVServer1] took: 0 hours 0 minutes 1 seconds and 187 milliseconds
 - (AcceleratorService) <Legal Hold Thread - worker thread (5):15784> EV-L {-} {LEGALHOLD.EN_US} {C2.EN_US} LHIC: Number of Items on hold in EV (Directory: [EVServer1]) are 2543555. Ref: CaseID: [3], LHGroupID: [DA_DiscoveryCustomer_5284189A-F38A-4A0E-BADA-811D1C53635C], ConsumerId: [{6F020B03-44DA-4E1B-A535-73EDEAA38CC7}]
 - (AcceleratorService) <Legal Hold Thread - worker thread (5):15784> EV-L {-} {LEGALHOLD.EN_US} {C2.EN_US} LHIC: XML content from directory [EVServer1]: [<LegalHold ConsumerGUID="{6F020B03-44DA-4E1B-A535-73EDEAA38CC7}" GroupID="DA_DiscoveryCustomer_5284189A-F38A-4A0E-BADA-811D1C53635C" TotalNumberOfHolds="2543555" CountStatus="0"><VaultStore ID="1FB6853D7B9DD654497A8854F859829311210000evserver1" Status="0" Count="2523215"/><VaultStore ID="1F5D494006212F748B22522EA5DF1B6081210000evserver1" Status="0" Count="20340"/></LegalHold>|]
 - (AcceleratorService) <Legal Hold Thread - worker thread (5):15784> EV-L {LEGALHOLD.EN_US} {C2.EN_US} LHIC: Successfully collected item hold info from directory server [EVServer1] (Ref: CaseID: [3], ConsumerID: [{6F020B03-44DA-4E1B-A535-73EDEAA38CC7}], GroupID: [DA_DiscoveryCustomer_5284189A-F38A-4A0E-BADA-811D1C53635C])
 - (AcceleratorService) <Legal Hold Thread - worker thread (5):15784> EV-L {LEGALHOLD.EN_US} {C2.EN_US} LHIC: Time taken by GetStatsOfItemOnLHoldInEV() for all directory server finished in 0 hours 0 minutes 1 seconds 781 milliseconds
 - (AcceleratorService) <Legal Hold Thread - worker thread (5):15784> EV-L {LEGALHOLD.EN_US} {C2.EN_US} LHIC: Summary of data collected from GetStatsOfItemOnLHoldInEV(): # of VaultStores from where we got data: 2. gotCompleteStatsData: True. (Ref: ConsumerID: [{6F020B03-44DA-4E1B-A535-73EDEAA38CC7}], GroupID: [DA_DiscoveryCustomer_5284189A-F38A-4A0E-BADA-811D1C53635C], CaseID: [3])
 - (AcceleratorService) <Legal Hold Thread - worker thread (5):15784> EV-L {-} {LEGALHOLD.EN_US} {C2.EN_US} LHIC: Count of item on hold [EV:2543555] [DA:5342110] (Is based on completed data from EV? [True]).
 - (AcceleratorService) <Legal Hold Thread - worker thread (5):15784> EV-L {-} {LEGALHOLD.EN_US} {C2.EN_US} LHIC: VaultStoreID: [1FB6853D7B9DD654497A8854F859829311210000evserver1], Item on hold in EV: [2523215], Item on hold in DA: [2671055]
 - (AcceleratorService) <Legal Hold Thread - worker thread (5):15784> EV-H {-} {LEGALHOLD.EN_US} {C2.EN_US} LHIC: EV has less number of items on Legal hold, in Vault Store [1FB6853D7B9DD654497A8854F859829311210000evserver1]. Items hold status in DA, for item belonging to this Vault Store, will be re-set (set to NoHold), so that all items will be put on hold again.
 - (AcceleratorService) <Legal Hold Thread - worker thread (5):15784> EV-L {LEGALHOLD.EN_US} {C2.EN_US} LHIC: Updating legal hold status of vault-store-specific items to no-hold, in DA database only. Ref: CaseID: [3], vaultStoreEntryID: [1FB6853D7B9DD654497A8854F859829311210000evserver1]
 - (AcceleratorService) <Legal Hold Thread - worker thread (5):15784> EV-L {-} {LEGALHOLD.EN_US} {C2.EN_US} LHIC: Setting case Legal-Hold-Sync-State. Ref: CaseID: 3, LegalHoldSyncStatus: Idle, setLastLegalSyncUpdateToNow: True
 - (AcceleratorService) <Legal Hold Thread - worker thread (5):15784> EV-H {LEGALHOLD.EN_US} {C2.EN_US} Legal Hold Thread - worker thread (5): LHIC: Case ID 3. group ID'DA_DiscoveryCustomer_5284189A-F38A-4A0E-BADA-811D1C53635C' finished [sync validation] with result as [Unknown], in 1 hours 23 minutes 30 seconds 50 milliseconds for all Vault Directories
 - (AcceleratorService) <Legal Hold Thread - worker thread (5):15784> EV-L {LEGALHOLDQUEUES.EN_US} {C2.EN_US} Legal Hold Thread - worker thread (5): Case ID 3. 'Validating Holds' finished in 1 hours 23 minutes 30 seconds 97 milliseconds

Environment



- Enterprise Vault 9.0.0 through 9.0.2 on any EV 9.x supported version of Microsoft Windows Server

-  Discovery Accelerator 9.0.0 through 9.0.2


Cause



The Legal Hold Integrity Check (LHIC) performs scheduled checks of all DA Cases that have Legal Hold enabled.

This check attempts to verify the numbers of items on hold between the DA Customer database and each Vault Store database used by those Cases.

If LHIC finds a mismatch between the number of holds DA has for a particular Vault Store and the number of holds EV has within the same Vault Store, a procedure is called to update the DA Customer database to correct the number of items not on hold.

There are two issues that can cause the LHIC looping condition to occur.

ISSUE 1:

If the DA Case has multiple millions of items that should be on hold, a connection timeout can expire before the procedure can complete.  A sample of a Dtrace of the AcceleratorService process recorded during such a looping condition is shown in the Error section above.

ISSUE 2:

Issue 2 has 2 possible causes.  Both causes log the same data when recording a dtrace of the AcceleratorService process during such a looping condition, as also shown in the Error section above.

- Cause 1:

The SQL stored procedure that performs the comparison is referencing an incorrect object in the database, which causes DA to compare the sum of all holds in all Vault Stores against each individual Vault Store hold count.

- Cause 2:

The SQL stored procedure that performs the comparison is referencing only the currently selected Vault Stores against which DA searches are run.  If searches are run and accepted, then the selection of Vault Stores is changed within the Case, the Vault Stores that were previously selected would not be included in the comparisons.  For example, Case 2 has Vault Stores A and B were selected, with all archives within these Vault Stores selected. A search is run against all of these archives, with the search results accepted and placed on hold.  Then, Vault Store A is unselected and Vault Store C is selected.  A new search is run against all of the archives in Vault Stores B and C, with the search results accepted and placed on hold.  When the LHIC runs, it will calculate the holds in all 3 Vault Stores, but only have Vault Stores B and C against which to compare.  This causes the count mismatch that throws the LHIC into a looping condition. 


Solution



Notes:

1) An issue exists with the StorageOnlineOpns process on the EV Storage Service server where legal hold processing can be slowed significantly if more than 2 million items are to be processed to be placed on Legal Hold.  This issue is resolved in Enterprise Vault 9.0 Service Pack 1 by installing the hotfix in Technical Note (TechNote) TECH153979, "Hotfix for Enterprise Vault (EV) 9.0.1. In some cases, certain types of archived item can cause Enterprise Vault's StorageOnlineOPNS process to fail while performing a Move Archive operation.".  See the Related Articles section below for the link to this TechNote.

If running EV 9.0 SP1, it is recommended that the hotfix in TECH153979 be installed as part of implementing the below hotfix for DA 9.0 SP1.

This StorageOnlineOpns process issue is resolved in EV 9.0 Service Pack 2.

2) As part of the Legal Hold Integrity Check repair processing, holds are reapplied to items in any Vault Store that does not match the counts in DA.  As part of the process to apply holds, the HoldSaveset table is updated with an entry for each item in the Vault Store that is to be on hold.  The HoldSaveset table has an index that is used to improve the hold application processing.  This index is the IX_HoldSaveset_SSID_HGID_HID index that is included in the HoldSaveset table since Enterprise Vault 8.0 SP4.  This table, by default, uses a 100% fill factor, meaning that the first time we add an item after this index is defragmented or rebuilt, the index is split into a new page.  This splitting to a new page can cause delays in the hold processing when applying millions of holds.

It is recommended to set the fill factor of this index to 70%.  See TechNote TECH126035, in the Related Articles section below, for instructions on how to adjust the index's fill factor.

Solution:

A hotfix has been developed to resolve Issue 1 and both causes of Issue 2 for each affected version of DA 9.  Download the hotfix below that is appropriate to the installed version of DA.

The installation and removal instructions for all versions are identical.  Only the binary files are version specific.  Installation of a hotfix for a version of DA other than that which is installed in the environment is not supported.  For example, installing the DA 9.0.0 hotfix in a DA 9.0.2 environment is not supported.

Files updated
=============

- AcceleratorLegalHold.dll
- AcceleratorDatabase.sql
- AcceleratorDatabasePrograms.sql


Preliminary steps
=============

1) Log onto a machine that can be accessed by all Discovery Accelerator (DA) servers in the environment.
2) Download or copy into a holding folder the hotfix zip file.
3) Extract all files from the zip file into the holding folder.
      The names of the files to be extracted are:

AcceleratorDatabase.sql.SAFE     - AND -
AcceleratorDatabasePrograms.sql.SAFE     - AND -
AcceleratorLegalHold.dll.SAFE     - AND -
Fix_SP_in_CustomerDB.sql.SAFE     - AND -
Hotfix_ReadMe_Document.txt     - AND -
DA 9_0_0 LHIC HF Install and Remove Instructions.txt  (included only in DA 9.0.0 version)     - OR -

DA 9_0_1 LHIC HF Install and Remove Instructions.txt  (included only in DA 9.0.1 version)     - OR -

DA 9_0_2 LHIC HF Install and Remove Instructions.txt  (included only in DA 9.0.2 version)

4) Remove the '.SAFE' extension from each file that has it.  The final names for those files should be

AcceleratorDatabase.sql
AcceleratorDatabasePrograms.sql
AcceleratorLegalHold.dll
Fix_SP_in_CustomerDB.sql

5) Ensure the holding folder is accessible by all DA servers in the environment and the SQL Server hosting the DA Customer database(s)
    or copy the extracted files into a holding folder that can be created on each of those servers.
6) Log onto each DA server as the Vault Service Account (VSA).
7) Log onto the SQL Server with an account that has sufficient permissions to modify data in the DA Customer database, such as the VSA.

Installation instructions
=========================

The following instructions must be carried out by the Vault Service Account (VSA) on all Discovery Accelerator servers in the environment:

   1) Stop the service named “Enterprise Vault Accelerator Manager Service” (EVAMS) and leave it stopped until otherwise instructed.

   2) Rename the following files, located under installation directory of Discovery Accelerator, by adding a new extension of '.save'. The default installation
     directory for 32-bit Windows Server is 'C:\Program Files\Enterprise Vault Business Accelerator', or for 64-bit Windows Server
     is 'C:\Program Files (x86)\Enterprise Vault Business Accelerator'.

 a) AcceleratorLegalHold.dll  (rename to AcceleratorLegalHold.dll.save)
 b) AcceleratorDatabase.sql  (rename to AcceleratorDatabase.sql.save)
 c) AcceleratorDatabasePrograms.sql (rename to AcceleratorDatabasePrograms.sql.save)

   3) Copy the following 3 files from the holding folder into the DA installation folder, effectively replacing the above 3 files.

 a) AcceleratorLegalHold.dll
 b) AcceleratorDatabase.sql
 c) AcceleratorDatabasePrograms.sql

The following instructions must be carried out on each SQL Server hosting a DA Customer database in the environment using an account with sufficient permissions to modify the data in the DA Customer database, such as the Vault Service Account (VSA):

   4) Open the SQL Server Management Studio and expand the Databases level in the left panel.

   5) Take a backup of each DA Customer database.

   6) In each DA Customer database, take a backup copy of the stored procedure named 'usp_LegalItemCountsPerVS_Sel' using the following steps:

a) open SQL Server Management Studio
b) expand Databases in the left panel
c) expand the DA Customer database in the left panel
d) under the DA Customer database, expand Programmability
e) under Programmability, expand Stored Procedures
f) locate and right click on Stored Procedure 'usp_LegalItemCountsPerVS_Sel'
g) select the 'Script Stored Procedure as' option
h) select the 'ALTER To' option
i) select the 'File...' option
j) navigate to the drive and folder where the file is to be kept (i.e., E:\SavedFiles)
k) enter a name for the file (i.e., 'Modify_usp_LegalItemCountsPerVS_Sel.sql') in the "File name:" field
l) click the Save button to create the file

   7) In each DA Customer database, install the new version of the stored procedure using the following steps:

a) upon completion of the file operation, right click on the DA Customer database name in the left panel
b) select the 'New Query' option
c) in the new query panel that opens, copy and paste the contents of the hotfix file 'Fix_SP_in_CustomerDB.sql'

i) open NotePad
ii) click on the File drop down menu
iii) select the Open option
iv) navigate to the holding folder
v) change the 'Files of type:' option to "All Files"
vi) select the file 'Fix_SP_in_CustomerDB.sql'
vii) click the Open button
viii) highlight all text in the document
ix) right click and select the Copy option
x) change to the New Query panel in SQL Server Management Studio
xi) right click in the panel and select the Paste option

d) change the first line in the New Query panel from

USE [Replace_With_CustomerDatabase_Name]

    to replace the '[Replace_With_CustomerDatabase_Name]' with the actual DA Customer database name.

    For example, if the DA Customer database name is EVBADiscovery, the line would be

USE EVBADiscovery

e) click the Execute button to execute the SQL statements that will drop the stored procedure and recreate it with the hotfix version.

The following instruction must be carried by the Vault Service Account out on all Discovery Accelerator servers in the environment:

   8) On each DA server, start “Enterprise Vault Accelerator Manager Service” (EVAMS).

The following instructions must be carried out on any machine using the Discovery Accelerator client with an account that has sufficient application level permissions (such as the VSA):

   9) Access the Configuration tab.

   10) Access the Settings sub-tab.

   11) Hold the Ctrl key and click on the banner where it has 'Configuration Settings' to display the hidden settings.

   12) Expand the Legal Hold section.

   13) Locate the option "Enable Legal Hold sync validation".

   14) Place a check mark in the check box in the Value column of the row for this option.

   15) Click the Save button in the lower right corner.

   16) Click the OK button to acknowledge the pop-up stating that Remoting must be restarted to complete the configuration change.

   17) Repeat Steps 9 through 16 for each DA Customer in the environment.

   18) Close the DA Client.

The following instruction must be carried out by the Vault Service Account on all Discovery Accelerator servers in the environment:

   19) Restart EVAMS.

The following instructions must be carried out on any machine using Discovery Accelerator client with an account that has sufficient permissions to view cases that have Legal Hold applied:

   20) Open the DA Client

   21) Monitor the legal holds to see if the number of Items Remaining changes from 0 to the total number of items in the Case, then cycles back to 0, then back to the total number of items in the case.

   22) Repeat Steps 20 and 21 for each DA Customer in the environment to ensure the issue is resolved.


Removal / Backout instructions
=========================

The following instructions must be carried out by the Vault Service Account (VSA) on all Discovery Accelerator servers in the environment:

   1) Stop the service named “Enterprise Vault Accelerator Manager Service” (EVAMS) and leave it stopped until otherwise instructed.

   2) Rename the following files, located under installation directory of Discovery Accelerator, by adding a new extension of '.HF'. The default installation
     directory for 32-bit Windows Server is 'C:\Program Files\Enterprise Vault Business Accelerator', or for 64-bit Windows Server
     is 'C:\Program Files (x86)\Enterprise Vault Business Accelerator'.

 a) AcceleratorLegalHold.dll  (rename to AcceleratorLegalHold.dll.HF)
 b) AcceleratorDatabase.sql  (rename to AcceleratorDatabase.sql.HF)
 a) AcceleratorDatabasePrograms.sql (rename to AcceleratorDatabasePrograms.sql.HF)

   3) Rename the following 3 files in the same folder to remove the '.save' extension, effectively returning them to their original names:

 a) AcceleratorLegalHold.dll.save  (rename to AcceleratorLegalHold.dll)
 b) AcceleratorDatabase.sql.save  (rename to AcceleratorDatabase.sql)
 c) AcceleratorDatabasePrograms.sql.save (rename to AcceleratorDatabasePrograms.sql)

The following instructions must be carried out on each SQL Server hosting a DA Customer database in the environment using an account with sufficient permissions to modify the data in the DA Customer database, such as the Vault Service Account (VSA):

   4) Open the SQL Server Management Studio and expand the Databases level in the left panel.

   5) Take a backup of each DA Customer database.

   6) In each DA Customer database, restore the original version of the 'usp_LegalItemCountsPerVL_Sel' stored procedure using the following steps:
 

a) right click on the DA Customer database name in the left panel
b) select the 'New Query' option
c) in the new query panel that opens, copy and paste the contents of the saved stored procedure modify file (i.e., 'E:\SavedFiles\Modify_usp_LegalItemCountsPerVS_Sel.sql')

i) open NotePad
ii) click on the File drop down menu
iii) select the Open option
iv) navigate to the saved files folder
v) change the 'Files of type:' option to "All Files"
vi) select the file created in Step 6k of the installation instructions above
vii) click the Open button
viii) highlight all text in the document
ix) right click and select the Copy option
x) change to the New Query panel in SQL Server Management Studio
xi) right click in the panel and select the Paste option

d) ensure any USE line in the statements in the New Query panel has the name of the DA Customer database 

For example, if the DA Customer database name is EVBADiscovery, the line would be

USE EVBADiscovery

 e) click the Execute button to execute the SQL statements that will drop the hot fix version of the stored procedure and recreate it with the original version.

The following instruction must be carried by the Vault Service Account out on all Discovery Accelerator servers in the environment:

   7) On each DA server, start “Enterprise Vault Accelerator Manager Service” (EVAMS).

The following instructions must be carried out on any machine using the Discovery Accelerator client with an account that has sufficient application level permissions (such as the VSA):

   8) Access the Configuration tab.

   9) Access the Settings sub-tab.

   10) Hold the Ctrl key and click on the banner where it has 'Configuration Settings' to display the hidden settings.

   11) Expand the Legal Hold section.

   12) Locate the option "Enable Legal Hold sync validation".

   13) Remove the check mark in the check box in the Value column of the row for this option.

   14) Click the Save button in the lower right corner.

   15) Click the OK button to acknowledge the pop-up stating that Remoting must be restarted to complete the configuration change.

   16) Repeat Steps 8 through 15 for each DA Customer in the environment.

   17) Close the DA Client.

The following instruction must be carried out by the Vault Service Account on all Discovery Accelerator servers in the environment:

   18) Restart EVAMS.

 


Attachments

Discovery Accelerator 9.0 Base only Hotfix for Legal Hold Integrity Check Etracks 2361330, 2285489 and 2328776
DA_900_Hotfix_Etrack2361330.zip (717 kBytes)
Discovery Accelerator 9.0 SP1 only Hotfix for Legal Hold Integrity Check Etracks 2380853 and 2380875
DA_901_Hotfix_Etrack2380853.zip (723 kBytes)


Discovery Accelerator 9.0 SP2 only Hotfix for Legal Hold Integrity Check Etracks 2380856 and 2380879
DA_902_Hotfix_Etrack2380856.zip (723 kBytes)

Supplemental Materials

SourceETrack
Value2285489
Description

Legal Hold counts do not match the total items in the tblIntDiscoveredItems table for some DA Cases.

- Note that this Etrack is for DA 9.0.0 only.


SourceETrack
Value2361330
Description

Legal Hold Looping when Vault Store selection changes within a DA Case.

- Note that this Etrack is for DA 9.0.0 only.


SourceETrack
Value2328776
Description

Unable to remove/apply Legal Holds

- Note that this Etrack is for DA 9.0.0 only.


SourceETrack
Value2380853
Description

Legal Hold Looping when Vault Store selection changes within a DA Case. 

- Note that this Etrack is for DA 9.0.1 only.


SourceETrack
Value2380875
Description

Under certain situations, Legal hold integrity check functionality fails to synchronize legal holds between DA and EV.

- Note that this Etrack is for DA 9.0.1 only


SourceETrack
Value2380856
Description

Legal Hold Looping when Vault Store selection changes within a DA Case.

- Note that this Etrack is for DA 9.0.2 only.


SourceETrack
Value2380879
Description

Under certain situations, Legal hold integrity check functionality fails to synchronize legal holds between DA and EV.

- Note that this Etrack is for DA 9.0.2 only.




Article URL http://www.symantec.com/docs/TECH156905


Terms of use for this information are found in Legal Notices