Webcast on Wed Mar 25, 10 AM PDT: Enterprise Vault / Office 365 Deep Dive
In our Office 365 webcast last fall, we shared several reasons why Office 365 alone is not enough to meet the archiving and discovery needs of most organizations. This follow-up webcast will provide additional details, including demos, head-to-head performance comparisons and ROI projections. These details will illustrate how Enterprise Vault goes beyond Office 365 by providing superior information governance, ensuring regulatory compliance and avoiding vendor lock-in—all while delivering a superior ROI for organizations in any industry. Wednesday, March 25, 2020 | 10:00 a.m. PDT Register here: https://www.veritas.com/form/webinar/enterprise-vault-goes-beyond-office-365-deep-dive.html
MSMQ Outgoing Queues referencing failed EV server - using Building Blocks for High Availability
Hi Everyone We make use of Building Blocks to build High Availability in our EV environment. We have come across a peculiar problem and wanted to know if anyone here has noted a similar issue. Scenario: We are in the archiving schedule and there are (say) 5 EV Mailbox Archiving Servers archiving 5 Exchange Servers. There are cross-references across EV and Exchange Servers i.e. the Storage Service for an archive is on an EV server other than the one which is running the Archival Task. Problem: If an EV Mailbox Archiving Servers fails, we use Building Blocks to quickly bring up services on a standby server by running Update Service Locations. However, we notice that items are still in archive pending state in user mailboxes being archived by other EV Servers. New items are also going into archive pending state across all user mailboxes. Analysis: We have already run a flushdns (or Clear-DNSClientCache in Powershell) across all EV servers. In the MSMQ Outgoing Queues, we noticed that there are queues which still resolve to the old failed servers and are in Failed to Connect or Waiting to Connect state, since MSMQ does not resolve to the EV aliases but the EV server hostnames. Solution: To resolve the issue, we need to add a host file entry resolving thehostname of the failed server to the IP address of the now active server and restart the storage/taskcontroller service. Has anyone of you come across a similar situation? We wish to avoid making host file entries and make thefailover process seamless.
Enterprise Vault Expired Mail Items Curiosity
Our site properties base expiry on Modified Date. Our site retention policy is 7 years If i view a users archive through archive explorer, the oldest item in the vault is from march 2009 (we archive after 15 days), so all seems well. However in the archive the oldest item date is shown as 2006 (see below): I also ran the sql query USE EnterpriseVaultDirectory SELECT ArchiveName, OldestItemDateUTC, YoungestItemDateUTC, HighestItemSequenceNumber, IndexedItems FROM EnterpriseVaultDirectory.dbo.IndexView ORDER BY OldestItemDateUTC Which brought back a vast number of pre 2009 items, and a lot of NULL (which i think can be explained by them being the 32bit archive - Is that right ?) Anway, can anyone explain the variance to me ? Is it as simple as the index retains all information, even after expiring and purging items ? or is there more to it ? ThanksArchiving status = Warning:failed to process mailbox
Hi, I have problems with 4 users mailboxes for other hunders there isn't any problem. In Enterprise Vault their archived mailboxes are empty. There are warnings in Archiving reports that users mailboxes' couldn't be archived and the warning is : Archiving status = "Warning:failed to process mailbox". - There isn't any problem in Deployment Scanner. - Operating System Name Windows 2008 R2 Server Standard (full installation) Service Pack 1 64-bit - SQL 2014 version:12.0.4213.0 - Enterprise Vault Version : 11.0.1.3474 - CHF Version 11.0.1.3683 In Dtrace there are some erors it can be related or not: 2479 10:22:23.628 [5376] (StorageArchive) <5736> EV:H Error MAPI_E_NOT_ENOUGH_MEMORY (0x8007000E): Attempting to read the property into a stream... 2480 10:22:23.628 [5376] (StorageArchive) <5728> EV:L The correct propTag value [0x10100003] is different from the dwAlignPad value [0x00000000] 2481 10:22:23.628 [5376] (StorageArchive) <5720> EV:L The correct propTag value [0x10100003] is different from the dwAlignPad value [0x00000000] 2482 10:22:23.628 [5376] (StorageArchive) <5724> EV:H Error MAPI_E_NOT_ENOUGH_MEMORY (0x8007000E): Attempting to read the property into a stream... 4452 10:22:23.691 [5376] (StorageArchive) <5728> EV:H {WriteSavesetCommand::Execute:#98} _com_error exception: [The system cannot find the path specified. (0x80070003)] 4453 10:22:23.691 [5376] (StorageArchive) <5740> EV:L {CSavesetSISData::GetSavesetIdentifier} (Exit) Status: [Success] 4454 10:22:23.691 [5376] (StorageArchive) <5728> EV:L {WriteSavesetCommand::Execute} (Exit) Status: [The system cannot find the path specified. (0x80070003) (anticipated err may not indicate an issue)] 4455 10:22:23.691 [5376] (StorageArchive) <5740> EV:L {CSaveset2::get_VaultId} (Entry) 4456 10:22:23.691 [5376] (StorageArchive) <5728> EV:L {EVCommandExecutor::ExecuteRecoverWithRetry} (Entry) 4457 10:22:23.691 [5376] (StorageArchive) <5740> EV:L {CSavesetOnIStg::get_VaultId} (Entry) 7040 10:22:29.619 [35632] (ArchiveTask) <6464> EV:H :AgentMessageDispenser::ProcessMessages() |Exiting routine |For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3683&error=V-437-2429 7041 10:22:29.619 [35632] (ArchiveTask) <18324> EV:H :CAgentSchedule::ProcessSchedule() |The scheduler is shutting down. |For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3683&error=V-437-2399 7042 10:22:29.619 [35632] (ArchiveTask) <10092> EV:L {AgentMessageDispenser::ThreadDeInitialise} (Entry) 7589 10:22:29.743 [35632] (ArchiveTask) <30792> EV:L MSMQ Nack Message Handler for Archive Agent Admin Queue stopped |For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3683&error=V-437-6423 7590 10:22:29.743 [35632] (ArchiveTask) <30792> EV:L {CQueue::~CQueue} (Entry) Here is another Dtrace log: 4769667 10:23:39.803 [24624] (ArchiveTask) <23076> EV:H 23076:ServiceMain() |Creating entries for all this agents queues |For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3683&error=V-437-2321 4769668 10:23:39.803 [24624] (ArchiveTask) <23076> EV:H 23076:ServiceMain() |Ensure that all required queues are available and usable |For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3683&error=V-437-2322 Thank you,
