Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Archiving and eDiscovery Community Blog
Showing posts tagged with Enterprise Vault
Showing posts in English
EC at TW | 14 Feb 2014 | 3 comments

I had trouble archiving 2 large (133 and 149 MB) messages from an Exchange mailbox, no errors in the Event Logs and all other messages archived without issue, dtrace snippet (further log attached) showed errors as below:

CArchivingAgent::MakeItemPendingAndProcessMsg - Com Result [0x80004005]

CArchivingAgent::WriteWorkItemsToQueue - At Default Handler with Error code [0x80004005]

After investigation the cause of the issue was the the MaxReceiveSize and MaxSendSize configured on the Exchange 2010 transport servers. The transport settings are change controlled but setting a higher value at the mailbox level allowed the messages to be archived.

Check the MaxMessageSizeToArchiveMB value in the VAC first.

Rob.Wilcox | 09 Feb 2014 | 0 comments
Do you store your Enterprise Vault data on locally attached disks to your server (DAS)? Do you use a Storage Area Network (SAN)? Do you use Network Attached Storage (SAN)?
 
Whatever you use, the storage has to be fast, and reliable.
 
On top of that the storage has to be flexible and cope with the increasing footprint of Enterprise Vault over time. Not just more email being archived, but think of all the different content sources and how they might be added on to Enterprise Vault at some point in the life time. Things like SharePoint, File Server Archive, Domino, Public Folders, and more.
 
Think also of how long that 'life time' might be. Many people launch in to using Enterprise Vault without a clear strategy when it comes to storage expiry. Of course that's really a mistake, but it is a very common one!  Without any kind of storage expiry not only does the footprint of Enterprise Vault grow...
Rob.Wilcox | 06 Feb 2014 | 1 comment
Yesterday I encountered a rather odd issue at a customers site, whereby the storage service seemed to have gone a little bit, well, how shall we say ... mad?
 
After a little bit of troubleshooting I happened across this particular article on Symantec's knowledge base:
 
 
We were indeed seeing lots of the 6656 and 6654 error-pairs throughout the event log.  In the end the only thing that fixed it for us was a system wide reboot across 4 different EV servers.
 
Very odd, but so far (touch wood) we've not had the same issue again.
Rob.Wilcox | 03 Feb 2014 | 0 comments

One of hats that I wear at QUADROtech is testing one of our top products, Archive Shuttle.  In order to test it, and really in order to test many aspects of Enterprise Vault I often have the need to have repeatable testing.

Repeatable in terms of:

- Being able to export the same archived data to PST from a mailbox archive

- Being able to ingest the same data over and over to multiple archives in multiple vault stores, across multiple test systems

I've found so far that the easiest way to achieve this is to build up a mailbox how I want it to be in terms of:

- The folder structure (number of folders, and depth)

- The names of folders (simple folder names, long folder names, foreign character folder names)

- The items within each folder (lots of small items, a few very large items)

Once you've got the mailbox set up like that you can then archive it. In fact what I often do when setting up a particular mailbox archive and...

NaturesRevenge | 30 Jan 2014 | 0 comments

Just sharing some information.

Following this forum post - https://www-secure.symantec.com/connect/forums/dfs... - I've been able to successfully migrate PSTs using the client-driven migration method. There are a couple of requirements:

At the client-side computer, the OS cannot be Windows XP. I've only been able to get this to function when the OS is Win7 / Win8.

On our primary EV server - where the PST migrator task runs - a HOSTS file entry must be created that resolves the IP address of your primary DFS server with the short name and the FQDN of your domain name.

10.1.1.1     domain       domain.com

Once you enable the mailbox for client-side migration, and the user has a PST opened in Outlook that's on - for example - their home directory...

Rob.Wilcox | 28 Jan 2014 | 0 comments
In the past I have used my hackintosh to connect to corporate email servers, and I've used the Enterprise Vault OSX Add-in.  It's something though that sometimes lags behind from a Symantec point of view.
 
When new versions or rather Service Packs of Office for Mac are released, and, when new versions of OSX are released there isn't the general 'rush' to support the changes. I suppose it's down to the amount of effort versus the number of users; there are just far fewer OSX users who need Enterprise Vault connectivity than Windows users. There are also far fewer testing resources (hardware and people) when it comes to OSX.
 
That being said it is good news!  I spotted a note on the Connect Forums which says that OSX 10.9 *is* supported.
 
...
Rob.Wilcox | 24 Jan 2014 | 0 comments

For a long time moving SQL servers underneath Enterprise Vault took a bit of time and a bit of planning.  Actually plenty of time and plenty of planning!

I spotted something rather interesting on the Enterprise Vault RSS Feed the other day:

EV SQL Move Tool

http://www.symantec.com/business/support//index?page=content&id=TECH214373

I haven't personally tested it (yet) but well, yeah.. wickedly good, right?

Rob.Wilcox | 22 Jan 2014 | 1 comment
Setting up the content of Exchange shortcuts that Enterprise Vault should create is something that should be given due time and consideration.  There are many factors to consider, so let's describe some of them here.
 
How will users access items
 
Possibly the first thing to think about is how users will access the archived items. Will they just be using Outlook on Windows? Will they be using mobile devices, or search pages, Outlook Web App and so on? If people are likely to be using mobile devices then having a very small amount of content in a shortcut is going to hinder those users, especially when you take in to account the next point ...
 
What age will items be archived
 
If you're running just an age based policy and archiving 'old' items say more than 6 months old, then really, how often will people access the archived content...
Rob.Wilcox | 13 Jan 2014 | 0 comments
 
When some people start using Enterprise Vault they don't always put a lot of thought in to the types of messages that the system should archive. Many people figure email is email and Enterprise Vault just archive it all, right?  Well the answer to that is no.  By default only a small number of message classes are archived by Enterprise Vault by default.  The message class itself gives different MAPI properties which programs like Outlook can interpret and display differently.  For example an IPM.Task 'message' has additional properties on it which relate to tasks.  The same holds for things like IPM.StickyNote. And so on.
 
The basic list of message classes can be seen here:
 
message class list.png
 
Some organisation will go above and beyond this and might...
Rob.Wilcox | 10 Jan 2014 | 0 comments
The PST Holding Area is used by PST Migrations into Enterprise Vault, but how big should you make it? Of course there are a few schools of thought on this topic, so let's discuss:
 
As Big As You Can
 
The first sort of flippant answer that you might often hear is that you should make the holding area as big as you can. Multi-terabyte even, if possible.  But that's not particular good, I don't think.. it just shows lack of thought and allows lax management of the area.
 
A Manageable Size
 
It is far better to do some investigation work and try to figure out how big the holding area needs to be, and discuss with the backup team how big it can be so that they can comfortably backup the area each evening.  If you use the Locate, Collect, Migrate for PST Migration then you can do the 'Locate' stage and get a good idea of the sizes of...