Video Screencast Help
Enterprise Vault
Showing posts tagged with Tip/How to
Showing posts in English
Darren Locke | 16 Sep 2009 | 6 comments

Over the last couple of years, we have seen a high uptake of Enterprise Vault File System Archiving (FSA) amongst our install base. However, we have not been able to offer support for customers where Apple Mac systems need to access the archived files. That is, until now. I’m excited to detail our support for FSA and Mac systems through our partnership with Group Logic.

First of all some background to why we have not been able to support Mac systems as clients for FSA. When we create placeholders we set the CIFS ‘O’ Offline attribute. A Windows client knows to treat this file differently to non-archived files. Indeed, on seeing the ‘O’ attribute set, Windows will change the icon of the file so that you have a visual indicator that this is a pointer to the file which is now “somewhere else”. (On Windows  XP you will see a black clock symbol in the bottom left of the file icon. With Vista and Windows 7 you will see an ‘X...

Glenn Martin | 01 Jun 2009 | 3 comments

If you use Discovery Accelerator at your site then a must read guide has just been published.

The Discovery Accelerator 8.0 Best practice guide for implementation is now available from this link http://seer.entsupport.symantec.com/docs/326055.htm

The purpose of this guide is to discuss the different aspects that you need to consider during sizing and recommend best practices for implementation. With V8 there are some new issues for you to consider when rolling out DA so make sure you download this document and start discovering more about DA V8.0.

Steve C Blair | 08 Apr 2009 | 1 comment
Over the past 10 years, a now accepted technology called “Archiving” or “Active Archiving” has come into play in almost all IT groups operations. When we look back over the past 15-20 years of IT history, we traditionally spent our time as SysAdmin’s doing weekly backups, nightly incremental backups, and quarterly/yearly save sets. The backups we took, provided we had time in our diary for all the other demands in our day, were periodically checked to make sure we could read them, and left alone. Then came a visit from a Legal firm, Government regulator, or HR staffer “We need information contained in files and emails” for John Doe, please restore the backups and give us access to search them. This was typically met with a real groan, sigh, and you knew when this happened that you were going to be sitting with tape catalogues, restoring files, running scripts on the directories/folders/files/emails restored, hoping to give whatever...
Michael Bilsborough | 04 Mar 2009 | 1 comment

Hi,

To allow support to work effectively on your support case we automatically send an email to you when you log a case.  Please do read this as it includes information which may well allow you to resolve the most common issues.  

If the suggestions cannot resolve it, we do ask you to run the deployment scanner and send us that information.  From time to time, I do work with support engineers to review the cases we get and many of them don't have this information in so adding a great deal to delays. 

 I cannot stress enough the importance of this and information from you describing in your own words the problem and when it began to occur etc.  The sooner the tech support engineer has this data, the sooner they can get to resolving your case and less time going back and forth trying to contact each other trying to get data. 

 

Mike

 

Wayne Humphrey | 04 Mar 2009 | 7 comments

So a while ago I wrote a simple vbs to query MSMQ as the PerfMon counters are not reliable.  There is an updated script I did some ware just need to dig it out.

Option Explicit
Dim MSMQApp ' As MsmqApplication
Set MSMQApp = CreateObject("MSMQ.MSMQApplication")

Dim strComputer

If Wscript.Arguments.Count = 0 Then
                WScript.Echo "usage: msmq.vbs server_name queue "
                WScript.Echo " "
                WScript.Echo "e.g. cscript msmq.vbs tus1ev1idxpin01 queue"
Else
                strComputer = Wscript.Arguments(0)
END If

On Error Resume Next...