Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Backup & Archiving Community Blog

Showing posts tagged with Installing remove filter
Rob Wilcox | 25 Jan 2010 | 1 comment

By default the OWA extensions timeout a request to restore an item after 30 seconds.  This was previously not configurable.  In some environments this has posed a problem in the past, where some internal Windows API calls were taking a little bit of time to come back, with, for example, user->group membership details.

A fix for this was introduced and can be used with version EV 8 and  onwards

The fix is slightly dependent on whether you are using Exchange 2003, or Exchange 2007.  If it is Exchange 2003, edit your EVBackend.ini file to include a line like this :

 

exch1.1.exchange.restorerequesttimeout=45

(where exch1 is the name of the Exchange Server)

If it is Exchange 2007, edit the web.config file so that it has the following line added :

 

You will see a line in the EV OWA Diagnostic log file similiar to this when you've...

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

DominikG | 25 Nov 2009 | 0 comments
The available knowledge base article to move a Backup Exec server to another machine does not help you, if the new machine runs on a different OS, e.g. 64-bit operating system.
I noticed that many users do not know of a useful option in Backup Exec, named “copy server configurations”. With this free option and my following guide, you will be able to copy your existing Backup Exec server onto a new machine with different operating system.
 
If both servers are present, you could use the following steps to copy your data:

please note:

Go to "Tools" -> "Install options and license keys on this media server" and check if the free option to copy server configuration, named "copy server configurations", is installed on the media server. If not, please install it.

copy the data:

...
DominikG | 19 Nov 2009 | 2 comments

Many users of Backup Exec are annoyed by the recommendation to apply all hotfixes made to the server also to the remote agent. I think this is quite understandable, because in daily business it is in most cases simply not easy to do it because of other, higher priority topics.

With this short piece of text I would like to change your point of view.
Please consider the following facts:

1. Many problems of backups with BE result out of a mismatch of server and RAWS.
2. Hotfixes are hotfixes, because they fix important issues.
3. If you have to call tech support, they will definitely check the version of server and RAWS and in case they do not match advise you to update.
4. This is really important: If you are waiting too long, the number of updates that have to be applied increase that much that a push update will no longer be possible.

The last point is really important. My investigations showed that somewhere between 8 (result of tech...

GFK | 04 Sep 2009 | 0 comments

The right resource, at the right time, for the right cost

Most of us never really have the time (or inclination for that matter) to design and deploy a really great solution backup strategy based on BE and/or BESR. There are a whole raft of really good partners of Symantec’s who do this and can help customers get the best out of their BE deployment as well as keep the environment up to date. In order to compliment services offered by partners there are a number of fixed priced service offerings from Symantec to help support both customers and partners accelerate the successful implementation and upgrade of Backup Exec and Backup Exec System Recovery when resources can be limited.

The services are suitable for Small Business customers whose environments range in size from 1 to 10 servers. The fixed price gives the customer the comfort of knowing that the project will never exceed their allocated budgets providing a number of key benefits:

  • Minimise...
Mark Garringer | 03 Sep 2009 | 1 comment

Our second meeting went very well. It was great to see returning faces as well as new faces at Adesa in Carmel!

19 people attended from 14 different orginizations around the Indianapolis area!

Phil Weingart gave a quick overview of the backup environment at Adesa, touching on design challenges and future projects. We also had two very successful breakout sessions discussing Disaster Recovery and VCB Implementation.

Our next meeting is scheduled for December 8th. Stay tuned for details on time and location!

Attached are the meeting minutes, a copy of Phil's presentation, a write up on Sallie Mae's VCB Implementation, and a VCB Proxy Installation slide show.

RahulG | 04 Aug 2009 | 3 comments

Hello All,

  There have been cases when you have to update the remote agents on the remote clients. Most of us either push install the remote agent or perform the local install of the remote agent . Some time its difficult to use the push install utility or perform the local install when you have to update the remote agent on many servers . So here is the solution for it ,there is a new utility in 12.5 called the Remote Agent for Windows Systems Bulk Upgrade and Update Utility. Its documented in the Administrators guide on page 904. You can run the utility from the install directory of Backup Exec. The utility name is "RAWSBulkUpdate.exe.
Here is an excerpt from the admin guide:

The Remote Agent for Windows Systems Bulk Upgrade and Update Utility lets you install Remote Agent upgrades and updates to multiple servers simultaneously. The utility helps you to better manage environments with multiple servers. You can use the Bulk Upgrade and Update...

jprknight | 29 Jul 2009 | 0 comments

Enterprise Vault Server Installation

After installing all pre-requisites and running the deployment scanner ASP.NET 2.0 is highlighted as not installed or not configured correctly (Critical). This can occur when .NetFramework 2.0 is installed before IIS. ASP.NET 2.0 has not been correctly registered with IIS.

Although I did not take a screenshot at the time ASP.NET 2.0 was missing from the below. So I was unable to give ASP.NET 2.0 Allow permissions.

imagebrowser image

I then needed to use the aspnet_regiis.exe utility to correct the problem as below:

imagebrowser image

so:

c:
cd\
cd windows
cd Microsoft.Net
cd Framework
cd v2.0.50727
aspnet_regiis.exe -i

It took me a...

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...

Masti24by7 | 07 Jul 2009 | 1 comment

Solution

you can switch to install mode while lusers are on the server. However I would recommend that you disable log on for new users till you installed the stuff:

Please use the following command before you start with the remote agent installation.

change logon /disable
change user /install

Install software

change user /execute
change logon /enable

Please let me know if you have any other resolutions for the same.