Welcome to your hub for Data Compliance, InfoScale, and Backup Exec discussions. Learn more about recent changes to the VOX Community here.
Forum Widgets
Recent Discussions
The file or directory is corrupted and unreadable. (Exception from HRESULT: 0x80070570)
Hello, While trying to archive with FSA following error shows up in the report file. Also happens with new FS Targets. Using EV 15. 1/16/2025 12:56:00 PM \\PATH TO FILE\Test file.txt 210 TEST 7D RET All Files ARCHIVE *** Error *** - The file or directory is corrupted and unreadable. (Exception from HRESULT: 0x80070570) Any ideas? Cheers.
License file issue
I've placed a new 14.2 license file on my EV server and get the event id 4213 stating the products I am licensed for. It also throws a bunch of error 4218's stating: Required license not active. An Enterprise Vault license is required for the following feature but the installed license is not currently active: I cannot find any information about how to even begin to resolve this. I've tried multiple new SLF files and I have been restarting the admin service each time. I need to keep this thing running until I can get it upgraded to a newer version. Any information on here to help me? I've removed all the old ones as well, backed them up to a different directory.Is it possible to query the index database?
HI there, my client has asked whether the could directly query the index database for specific content? The client has a lots of CDR's which contains phone numbers, timestamps etc! Could he for example query the database to how offen a phone number appear in the database between 2022 and 2024? Thank for your numerous response!Elasticsearch JVM heap size over 90%
Hi, We have 3 server with archiving and Indexing services, sometimes we getting Elasticsearch JVM heap size over 90%, and search stop working for the index in that server, restart the index service and work again, I create a powershell script to monitor (https://www.veritas.com/support/en_US/article.100061339), can see at the end. What can I do to prevent this to happen, should I increase the Elasticsearch JVM heap size value ?(https://www.veritas.com/support/en_US/article.100060258) I'm in EV 15.0 no fixes (yet) # Define the remote computer's name or IP address $remoteComputer = "evserver" # Define the script block to get the performance counter data $scriptBlock = { $JVMCounter = Get-Counter '\Enterprise Vault Indexing (Elasticsearch)(*)\JVM heap size % used' [pscustomobject]@{ Server = $env:COMPUTERNAME Name = $JVMCounter.CounterSamples.CookedValue } } Invoke-Command -ComputerName $remoteComputer -ScriptBlock $scriptBlock
Veritas Enterprise Vault performance issue
Dears i came Across Dtrace scripts and used performance scripts and what i saw in the logs seems not clear for me as per below logs my decompressed message size is smaller than my compressed message size. which is totally not logic for me, any ideas? CSavesetPersist::PackSavesetBytes Completed compression step. hr=Success (0)|Uncompressed size:79360 Compressed size:79401 Elapsed:0.00 (secs) CSavesetPersist::PackSavesetBytes Completed verification decompression step. hr=Success (0)|Compressed size:79401 Uncompressed size:79360 Elapsed:0.00 (secs)
