Recent Discussions
Moving EV Journal archive within site ignoring MaxFailedItemCount threshold?
Hello, We have a situation in which a VS database is corrupted and there is no backup of it available. In addition, huge amount of partition data was deleted the hard way - files were just deleted from the file system. I´m trying to work around this, so I created a new VS, and my intention is moving as much as possible data to a new VS / partition from the old VS whose database is corrupted, but the process fails when the maxfailedItemcount threshold is reached, which is expected in this case. Question: Is there a way to override any failed items count?
EV mailbox license challenges
Hi I am looking for a guidance to know appropriate number of licensed users of EV for mailbox archive. I am fine using usage summary report OR anything from logs (e.g. IIS) / SQL/PowerShell. Please apologies however I am not confident enough if Veritas tool (EVLA..ETC) gives correct picture of licensing. For any legal OR licensing perspective, this is very difficult to find out who is the actual user for EV. Here is my thought. • Mailbox archive by EV when it used to exist in exchange servers. Now if mailbox moved to EXO however, he may OR may not access the archive depending upon usage. For e.g. he may access EV for 1-2 month or maximum a year. Now since one-year emails are being archived by EXO then it’s rare user will look into EV archive. This situation AD a/c still exist. This may not reflect actual EV licensed user. Additionally, organisation pay double archiving fees as one is EXO second for legacy EV archived emails . • User left organisation and his EV archive still exist. For any reason say for example, retrieving important email, permission is assigned to his manager then again this will be eligible for license. • A shared mailbox archive either inactive or active, permission is granted to team members then the all-group member will be eligible for license. In my opinion, the license should be there only for a mailbox that is active in on-premises and archived by EV. All AD user account of shouldn’t be eligible for license. There could be best practice such as below. Mark in-active archives. E.g. User is migrated to EXO or left OR where there is no need to access to old, archived emails. • Remove permission from archive those are marked as in-active. This is good options instead of deleting archive. • Remove unnecessary permission archives from shared mailbox OR user left from mailbox. Please help me if anyone have similar challenges and have better high-level plan. Regards Pradeep Papnai
How to Migrate MBOX Emails to Network Solutions Account?
You can use the SysConverter for MBOX to effortlessly import MBXO to Network Solutions mailbox. With its advanced features, it is easy to complete the MBXO to Network Solutions import process in a few simple clicks. Using this tool you can also import multiple MBOX files into Network Solutions email account at once without any data loss. Steps to Import MBOX to Network Solutions Run the SysConverter for MBOX on your system. 2. Add the MBOX file to the software interface. 3. Click on Export >> IMAP. 4. Enter your Network Solutions login details and hit teh Save button. Done! here complete the importing process.
Error Recalling from Secondary Storage
Hi, I'm getting an error recalling some files from secondary storage. The error is event id 6882 Unable to complete retrieval request Failed to access file 'J:\Enterprise Vault Stores\EVstore01 Ptn5\2017\12-18\2\059\2059DB30C999293B54DA0D133FB8AC81~2D~6E9D4CD1~00~1.DVSSP'. Reason: The system cannot find the file specified. (0x80070002) Operation: READ Reference: CNTFSStorageDeviceReader::LoadFile The files exists in the CAB file in secondary storage. I can successfully recall the file if I manually copy the DVSSP file from the CAB into the location in the error. So the CAB and DVSSP file isn't corrupt. Error is occurring with multiple files in different CAB files and partitionsCan not delete 64bit Index Location after upgrade all index to Elasticsearch
Hi all, I have just finished upgrading all my indexes to Elasticsearch (after upgrading to Enterprise Vault 15.0). When I attempted to remove all old index locations from the Enterprise Vault Administration Console (VAC) in order to delete the old volume from the server, I received the following message: --------------------------- Enterprise Vault --------------------------- This folder is being used by the Indexing Service to maintain active indexes. You cannot remove this folder until all the archives have been deleted from it. --------------------------- OK --------------------------- After investigating I realised that I are still index register in the SQL database ( EnterpriseVaultDirectory - IndexVolumeView). The archive these indexes report they only have elasticsearch locations and all of them are still empty. Is there a way to correct this issue? I need to return the empty volume.
