DI integration with EV
I’m doing DI-EV workflow tests. I’ve set up everything between the 2 tools, but despite numerous attempts to archive a file or the folder, I’m receiving the same error on DI side (version 6.5.0). “[Exception in method Archive:System.ServiceModel.FaultException`1[www.symantec.com.EnterpriseVault.API.FileSystemArchiving.Data.TimeoutFault]: The File System Archiving task service failed to start. Check that the File System Archiving task service is enabled in the configuration file, <Enterprise_Vault_installation_folder>\EvFSAArchivingTask.exe.config. (Fault Detail is equal to www.symantec.com.EnterpriseVault.API.FileSystemArchiving.Data.TimeoutFault).]” There is not much on this error on the VERITAS site:https://sort.veritas.com/public/documents/SDI/4.5/windows/productguides/html/sdi_admin/apas06.htm The site states that the error occurs at random and suggest re-submission. I’d done that many times, but the error is not random but consistent. Is there any solution to it? Thank you Tomasz534Views0likes0Comments(CEP-19028) Multi-Tenancy Survey
Interaction Date: February 5 - February 19, 2024 Interaction Type: Online Survey This survey aims to gather your preferences and requirements regarding various aspects of the solution, including multi-tenancy configuration, resource consumption, reporting and billing, and disaster recovery capabilities. We are particularly interested in understanding your organization's unique needs and priorities. Your feedback will guide us in customizing our multi-tenant solution to ensure it aligns seamlessly with your business goals. Whether you are focused on chargeback and billing, disaster recovery preparedness, or resource optimization, your input will contribute to the development of a solution that meets your expectations. If you are interested in getting more details about this opportunity or in participating in other exciting interactions and are not currently a member of our CPEP program, you can register here:https://cpep.veritas.comthencontact us atcustomer.engagement@veritas.com.215Views0likes0Commentsmigrate the enterprise vault from microsoft failover cluster to veritas VCS cluster
Hi All, iam planning to migrate the enterprise vault from Microsoft failover cluster to veritas VCS cluster. i already built the VCS cluster identical to the MFOC but need to no is it possible or not.652Views0likes0CommentsRestore all items
We are moving to Exchange online in a few months. We currently archive from Exch2016 without shortcuts, on EV 12.5.1. The plan was to disable the users for archiving, and export a users archive back to their orginal mailbox, then migrate to the cloud. Any concerns with that approach? A user had a question, if they move items from their mailbox in to Virtual Vault, would it restore the item back to the original folder? I assume if it's named the same, say Inbox to Inbox then it would work, but if they moved from Inbox to Inbox\reports it would create the folder structure Inbox\reports if it didn't already exist? Thanks.1.9KViews0likes6CommentsDA client error - Access to the temp directory
Hi All, I have recently upgraded a DA Client from 11.0.0 to 11.0.1. The customer is in the process of upgrading to EV 12 eventually. The upgrade of DA Server went fine. The only issue is that whenever DA client is opened or closed an error message appears as below but it can be dismissed to proceed. Does anyone know what could be reason for this error? I have aready set registry key to skip checking TEMP folder. Also I have checked and found that EV Service account has permissions to the TEMP folders (system TEMP and user profile TEMP). Access to the temp directory is denied. Identity 'DOMAIN\evservice' under which XmlSerializer is running does not have sufficient permission to access the temp directory. CodeDom will use the user account the process is using to do the compilation, so if the user doesnt have access to system temp directory, you will not be able to compile. Use Path.GetTempPath() API to find out the temp directory location. Regards, VJSolved1.1KViews0likes1Commentspace needed to perform index upgrade
Hi All, I am in the process of upgrading 32 bit index for a customer. I would like to know if the size of the converted index (64 bit) will be same as the original 32 bit index. This is to get an idea of the amount of free space needed at the open index locations. Environment details: EV 11 Index Server Groups present Thanks & Regards, VJSolved1.3KViews0likes3Commentsindex upgrade from 32bit to 64bit
Hi All, I have a customer running EV 11 and currently in the process of planning upgrade to EV 12. There are still some 32bit indexes that are yet to complete conversion to 64bit due to large number of 32bit indexes. Can the index upgrade (32 to 64) be resumed after performing the upgrade to EV 12? Is it mandatory to upgrade 32bit index to 64 prior to upgrade to EV 12? Thanks! Regards, VJSolved936Views0likes1Comment