Mbx Archiving State / Mbx Exchange State
Often the question of what is the different states of MbxArchivingState and MbxExchangeState in the ExchangeMailboxEntry table. The Archiving State translates as follows: 0 = Not Enabled 1 = Enabled 2 = Disabled 3 = Re-Link To view the Archiving State you can use the following:EMC Documentum backup procedure
I was really shocked when I learned that EMCDocumentum (Content Management solution) does not allow you to put itself into "online backup mode". As we used Documentum with anOracle database, and your content storage and DB should be backed up at the same time to ensure theconsistency.
EV Clearing up temporary files
Several people ask about how Enterprise Vault clears up temporary files, and why it might or might not be working on their system.Here is how to trace it and see what it is doing : Create a Dtrace Filter as follows : Dtrace Set adminservice v Filter Clear includes Include CCleanUptempFiles Exit Log to a file, and then MON Once an hour you will get the following : 2465 10:00:44.968 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::ThreadRoutine - GetTempPath 2466 10:00:45.390 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::ThreadRoutine - TempPath = C:\DOCUME~1\vsa\LOCALS~1\Temp\ 2467 10:00:46.437 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::ThreadRoutine - GetRegistrySettings 2468 10:00:46.671 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::GetRegistrySettings - Try toopen [SOFTWARE\KVS\Enterprise Vault\AdminService] 2469 10:00:46.671 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::GetRegistrySettings - Read [DelFilesOlderThanHours] 2470 10:00:46.671 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::GetRegistrySettings - DelFilesOlderThanHours = [24] 2471 10:00:46.671 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::GetRegistrySettings - Read [DelFileTypes] 2472 10:00:46.671 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::GetRegistrySettings - DelFileTypes = [] 2473 10:00:46.671 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::GetRegistrySettings - CloseKey 2474 10:00:47.218 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::ThreadRoutine CleanupFiles loop 2475 10:00:47.843 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::CleanupFiles - Find Files (C:\DOCUME~1\vsa\LOCALS~1\Temp\EV$*.*) 2476 10:00:47.843 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::CleanupFiles - Skipped – Not due for deletion (ev$1.1) 2477 10:00:47.843 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::CleanupFiles - Exit 2478 10:00:49.031 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::CleanupFiles - Find Files (C:\DOCUME~1\vsa\LOCALS~1\Temp\~DF*.TMP) 2479 10:00:49.031 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::CleanupFiles - Exit 2480 10:00:52.749 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::ThreadRoutine - wait for 1 hour or until service exits. There are a couple of things to note : • It runs once per hour • It will remove non-read-only files which aren’t in use • By default it will use the file pattern : $*.* and ~DF*.TMP. • It won’t delete files newer than 24 hours old Control of the last two options is through the registry keys : HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\AdminService\ DelFileTypes = “~DF*.tmp;EV$*.*;*.tmp” DelFilesOlderThanHours These are read dynamically (at the next run interval)
Who is the owner of this shortcut?
Occassionally my users end up with someone else's shortcut in thier mailbox. They get there any number of ways: sent as attachements, cross mailbox copying, copying in and out of shared public folders, etc. And often the user does not have access to the originating archive, so when they open the shortcut, they get the typical access denied error. After much research, I finally ca
Enterprise Vault and Backup Exec
Backup Exec 12.5 released an Agent for Enterprise Vault, which is designed to offer complete protection for Enterprise Vault 7.5 implementations. When Enterprise Vault 8.0 was released, architectural changes in EV 8.0 made the Backup Exec 12.5 Agent for Enterprise Vault unable to automatically protect all aspects of Enterprise Vault. An integrated solution will be in the next version of BE.
