Video Screencast Help
Archiving and eDiscovery Community Blog
Showing posts tagged with Upgrade
Showing posts in English
AmolB | 02 Nov 2012 | 1 comment

This blog expalins how to upgrade Discovery Accelerator 9.0.4 to Discovery Accelerator 10.0.2 

Pre-Requisites:

OS: Win2008 R2 and above ( If DA9.0.4 is on Win2003 R2 than you need to migrate DA to a Win2008 R2 server)

IIS: IIS7.5 with IIS6.0 Management Compatibility and IIS Win Authentication.

MS .NET Framework 3.5SP1 and MS VC++ 2008 SP1 (x86) Redistributable Package

Enterprise Vault 9.0 or above (Just install binaries, do not configure)

 

Copy DA10.0.2 installables from the root of the installation media to the DA server.

Below image shows the version of DA9.0.4

 

Before proceeding with the  upgrade make sure there is no Search or Export operation in progress.

You may stop EV Accelerator Manager service on the DA server.

To begin Upgrade browse...

Wayne Humphrey | 06 Dec 2009 | 1 comment

Lots of times I refer back to the EV manuals to see whether something that I “discover” is actually documented.  I have a copy locally on my machine in the office of many of the manuals, from many of the different versions.  I had often wondered about an externalised version of them, and whether they were easy to find.

With the power of Google, I found :

http://seer.support.veritas.com/docs/277782.htm

That goes back as far as V6, which is the beginning of time (almost) as far as I am concerned

GertjanA | 26 Aug 2009 | 3 comments

Hello everyone,

As you are aware, upgrading a larger environment of EV-servers can be a little confusing.
I've done upgrades from 6 to 7, from 7 to 7.5 and now from 7.5 to 8.0

My environment is pretty large.
9 Journal Archiving servers
15 Mailbox Archving servers
4 Discovery Accelerator servers.

The attached sheet will only show updating EV, not DA.

The sheet consists of 2 pages.
Page 1 is the Pre-Upgrade steps.
Page 2 is the actual upgrade steps.

In the sheet, you will see a red line with the word Sync at the end at several steps.
This indicates that if you perform an upgrade with multiple people (each one doing a server (or 8 ;-)) that is the point where everyone has to wait for the others to reach that point before continuing.

I made the sheet having 3 servers.
1 EV-server being the first installed server, called Directory Server.
2 EV-servers, one being a Journal Archiving server,...

Glenn Martin | 30 Jul 2009 | 0 comments

We are pleased to announce that EV2007 SP6 has now been released, you can download it using the links shown below.

Core Service Pack download link
http://seer.entsupport.symantec.com/docs/329051.htm

For other components please refer to the following technote which has the full list of downloads.
http://seer.entsupport.symantec.com/docs/287162.htm


Key Fixes in this SP:

  • Client side PST migration caused an Outlook resource leak
  • Public folder shortcuts remained after users deleted them
  • OWA buttons did not work when an external Enterprise Vault URL was configured for OWA 2007 users
  • Archive Explorer copy and move operations failed when connected to Enterprise Vault 8.0 server
  • Corrupt messages caused Exchange Journaling task to stop
  • Domino...
Maverik | 20 Jul 2009 | 0 comments

Migrating from a third party vendor to Enterprise Vault, you may consider hard and too risky, but to be honest in a huge amount of cases it is not.

I have assisted with Projects such as these in the past so wanted to share my expereinces of these. Companies that I have dealt with have switched to Enterprise Vault because simply they have not received the flexibility, supportability,integration and most importantly end user expereince that other products provide. Enterprise Vault is the market leader in archiving quite simply.

Almost all third party archiving solutions have a mechanisim for restoring the data back to the users mailbox or file system and the only issue here can be storage. Planned properly this can easily be done in stages with groups of users or files. Planning and Project Management is of course the key here for a smooth transition, but this is not technically difficult just apply some common sense and a touch of expereince!! Technically this is...

jprknight | 17 Jul 2009 | 1 comment

Within our organisation we are solely concerned with email archiving. We have six Exchange 2000 active/passive clusters, with a dedicated EV server attached to each split equally across two data centres.

Before our virtualisation adventure took place we were running our EV email archiving servers on end of life hardware (End of life when the project implemented EV), which with ever increasing frequency of hardware failures took place. Typically mirrored disks would go down, raid card battery failures, RSA cards not functioning, the list goes on. It was just one big headache; and that was only the hardware.

For the software we were running on 2007 7.5 SP1, which seemed to give us no end of users complaining about their emails not completely archiving and their mailboxes not decreasing in size. We were also running on Windows 2003 SP1; which Symantec had advised us several times has serious shortcomings with MSMQs. Essentially the outgoing queues did not get processed...

Wayne Humphrey | 16 Jun 2009 | 0 comments

I always get asked about MSMQ, here is a short note on things to look at if you have MSMQ issue's, even if you don't have issues you can always benefit from tweaking MSMQ and enhance Enterprise Vault’s performance.

Microsoft Message Queuing (MSMQ)

The root cause I believe lies in the way MSMQ stores messages. In the Storage directory (normally under windows\system32\msmq) will be a number of 4MB files that will contain the messages. Each file can contain as many messages as will fit which works quite well to start with. If a message cannot fit into one storage file, though, because it is too big for the remaining free space then a fresh file is created. There can only be as many storage files as would fit within the storage quota and when this limit is reached then no more storage files can be created. For example from windows 2003 SP2, a 2GB quota could accommodate 500 4MB storage files. In older versions Microsoft used to have an 8GB quota...

GertjanA | 24 Mar 2009 | 0 comments

Designing a new EV environment is not an easy task to do.
I am in an environment that is currently
EV7.5SP2, Exchange2003SP2, Windows2003 SP2, SQL2000SP4

In (if all goes to plan) 7 to 8 months, I am in an environment that will be:
EV8.0SP2
Exchange2007SP2
Windows2008R2 (possibly)
SQL2008SP2

In addition to this, the amount of mailservers will decrease, there will be Exchange CCR (and how will that affect EV?)
Lot's of unknowns to me...

Microsoft is already in the house for designing (helping to), architecture etc for the AD/Exchange, but nothing for EV.

Might be worth to start fishing at the boss with the money...

GertjanA | 11 Mar 2009 | 3 comments

Hello fellow EV-admins, users, supporters,

My name is Gertjan. I am Dutch. (it ain't much if it ain't dutch!)

I am working for a contracting firm called T2. I've been placed at one of the largest EV implementations in the Netherlands. Due to the nature of the environment (as pointed out by someone..) I will not post too much about it.

It is big. Over 95000 mailboxes, over 75000 active archives

Besides managing Enterprise Vault, I also manage a little the Exchange environment.

Current version is EV2007SP2, planning to go to 8.0SP2 (august?)

I cannot promise to post regularly, but will try to do so.

I'm getting used to the new forum-layout, but this Blog is definitely an addition to it.

I'm an MCSE+Messaging2003, MCTS, Symantec Certified Specialist EV2007 for Exchange Administrator (yep, proud of it.)

 oh, forgot... Running the EV-servers as VM's... The index and storagedisks are SAN based. (EVA)

...

TonySterling | 06 Mar 2009 | 2 comments

Hopefully you are all aware of sp5 being released for EV 2007 (aka EV 7.5)  If you are not I highly encourage you to sign up for notifications.  See a blog posted by EV Guys linked here:

https://www-secure.symantec.com/connect/blogs/navi...

 

Whilst reading through the updates this feature caught my eye.  It is the ability for the user to easily send the log via email.  Now this might seem like a small thing but recalling my support days and having to walk folks through locating this file and then the EV Admin have to walk the end user through getting the email are little things that add delays to the support process.  Now all they have to do is click a button, how cool is that! 

Here are the details from the updates.htm

Option to create a mail message...