Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Backup and Recovery Community Blog
Showing posts tagged with 2010
Showing posts in English
Jason_Dowzell | 23 Jan 2013 | 0 comments

With the ever increasing usage of disk based backup solutions, one of the questions I get asked most often is around the future of tape. There is no doubt that disk offers many benefits over tape, not least restore performance and reliability, combined with some great technical advances like deduplication. That said, does tape still have a place in modern data protection?

Rarely a week passes when I don’t talk to a customer who wants to reduce their reliance on tape. The main challenges customers experience with tape are performance, especially when backing up lots of small files, restore speed, and also reliability issues caused by media volatility and drive failures. Add to that the cost of taking tapes off-site and cycling them back on site each day and it is little wonder many want to try and reduce their reliance on the technology.
Disk as a backup technology has been around for many years but, in recent years, has become almost a...
lmosla | 15 Jan 2013 | 0 comments

Some issues that may occur if BESA does not have the required rights:
• Backups or Restores are failing
• Log on Account Errors
• In the backup selections “Enable Trust relation" keeps displaying
• During an install of Backup Exec for Windows Servers when entering the service account information the error "Unable to authenticate with the user and password information given for \User name " appears .
• On system boot, the Backup Exec Device and Media Service fails to start automatically and generates Event ID 7041

All of the Backup Exec services (except the Backup Exec Remote Agent) run under a user account which the Backup Exec system services use. When a user account is configured for the Backup Exec services to use it is known as the BESA (Backup Exec Service Account).

During the Backup Exec install the Backup Exec service Account (BESA) and the Backup Exec system logon...

Donald Eady | 15 Jan 2013 | 1 comment

Alright… So just got that brand new or not so brand new Robotic Library (Autoloader/Changer) and or Tape Drive(s). Still bubble wrap / ship safe fresh, just unpacked and attached to the server and bam.. here comes the brick wall. The storage device is not displaying or perhaps the tape drives or libraries show up offline or worse yet they are not found, recognized or detected at all. What do you do? Well you have a couple of options you can spin once counter clockwise, blink your left eye, wiggle the mouse frantically, right click and see if its working now. Or you can take the suggested approach and follow this informative right down the golden paved road to the promise land of problem resolution.

From time to time hardware that despite being officially tested and supported by Symantec might show as offline, display incorrectly within the console, function outside of the way it was intended and or throw errors within the B.E. job log or windows event viewer. ...

Walid | 09 Jan 2013 | 0 comments

Banking, education, services, insurance, retail in addition to other industries in Lebanon are using Backup Exec 2012 to protect their data and consequently their business. It is widely used to backup databases, mailbox stores, files, virtual images, active directory and others platforms. It can be used to protect servers, personal computers and laptops.  Backup Exec 2012 offers an easy to use, user friendly interface with a step by step wizard to configure multiple options.  

Initially when I installed Backup Exec 2012, I was really disappointed to find out that some configurations did not work the same way that they did in 2010.  There were major changes to the interface and menus as well as the backup scheme switched from multiple selections/servers in one job to resource centric backup jobs.

On the other side, I was extremely happy to see simplified wizards to configure full and incremental jobs by using the easy add stage while configuring backup...

Drew Meyer | 20 Nov 2012 | 0 comments

Hey readers - new post about Symantec's official VMware support on the official Backup Exec and NetBackup blogs. Be careful who you trust with your data.

AmolB | 03 Oct 2012 | 8 comments

Very often there are queries on the connect site related to BE Quick Start Edition.

This blogs explains what all and what not is included in the QSE.


BE Quick Start Edition is a cut down version of Backup Exec. QSE is shipped by Tape Drive manufaturers

along with the hardware.This edition is useful only for a small setup like a single server with a tape drive.

For larger setup full version of BE will be required. For media server OS compatibility refer to Backup Exec

Software compatibility list.

 Features Included in QSE:

  • Can be used to backup only standalone server (server on which QSE is installed)
  • QSE can backup to a disk as well as to a tape
  • Supports DLO ( 5 Desktop & Laptops only)
  • With LEO multiple tape drives can be added to the library.

 Limitation of QSE:

  • Cannot backup remote servers...
AmolB | 28 Sep 2012 | 2 comments

Frequently there are posts on the connect site about protecting or recovering Backup Exec itself from a Disaster.

Below procedure explains what to backup and how to recover Backup Exec.


Everyday Backup Exec runs a database maintenance and creates a healthy copy of BE database.

This copy of database is saved in the form of BEDB.bak in the DATA folder, located in the installation

directory of BE. The option of database maintenance is enabled by default and it runs at 04:00 hours.

This option can be disabled (not recommended) and the schedule time of maintenance can be changed too.

In BE2010 and older versions, Database Maintenance option is avialable in the BE console -> Tools ->

Options -> Database Maintenance. In BE 2012 this option is avialable in BE console -> Backpu Exec

button (Top left hand corner) -> Configuration & Settings -> Backup Exec Settings ->Database...

CraigV | 10 Sep 2012 | 4 comments

Backup Exec 2012 was released a couple of months ago, and almost immediately people started complaining. Check the forums for some very long posts. To many it missed the mark, while to Symantec, it addressed a number of new features it introduced that people might have asked for.

People had gone from a working environment with BE 2010 for instance, to something they no longer understood using BE 2012 where the focus was now no longer on resources, but on a server-centric basis.

Fast-forward a couple of months, and the long complaint queries have died off a bit. EIther people are no longer upgrading, and waiting for Backup Exec 2012 R2, or they're learning to deal with how BE 2012 now does things. In doing so, they're essentially working through the issues and changing their mindsets.

This is where my topic is early adoption of new software worth it?

You're only as good as your last backup...or your last restore is the old adage...

ByronHPull | 18 Jul 2012 | 1 comment

Since October 2011, (9 months) I have had recurring issues which has now resulted in BEWS completely failing to backup.

I have a relatively simple system, primarily a file server, (no Exchange) with a backup set of 400GB, on a 1000GB HP RDX.

Initially (since Symantec withdrew cascading tape drives) and I had to change the system, it worked perfectly, then October last year the problems started.

The correction process has been appalling, with it me putting in more time in providing data and running WebEx's than the engineers.

After a number of first line engineers "played," with no success only to create more issues, I managed to get it escalated, in the hope of some intelligence being applied.

After an initial success which took about 5 months, BEWS is now down (9 hours to do 120GB, when previously that would have done the full backup)

Tech response has been reactive rather than proactive, and I get the distinct impression no-...

SaurabhK_BE | 28 Jun 2012 | 1 comment

Enterprise Vault (EV) stores data as many small files within various directories called EV partitions. These files might be millions in number. Backing up a large number of small files results in lesser performance than backing up a single file of the size equivalent to the cumulative size of all files.

To circumvent this problem, there is a setting in Enterprise Vault that makes EV collect the stored data into a CAB files. If this collection process is executed before the backup, the backup will run faster as the data is now in some larger files rather than hundreds of small files.  Refer the following TechNote:

Vault store Partition Collection can be enabled using the below mentioned steps:

  • In the EV Admin Console, select the Vault Store which contains the partition in...