Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.
Backup and Recovery Community Blog
Showing posts tagged with 12.x
Showing posts in English
4L SpA | 28 Dec 2013 | 0 comments

Workaround to Event 57802 and 57804, catalog mistmatch (Following a successful upgrade, the Backup Exec Server Service fails to start and the event logs report an error "The Backup Exec Server Service detected a schema version mismatch)

 

1.- Upgrade existing BE 2010 R3 to 2012

2.- Using existing procedure, copy folders Catalog and Data to safe place or shared drive

3.- Install brand new Windows Server, with the EXACTLY same name as the old one, as on step 1.

4.- Copy the folders Catalog and Data from step 2.- using procedure accordingly

5.- Start services of the new BE 2012

6.- That's it!

@BackupMikko | 06 May 2013 | 0 comments

How far along are you on your virtualization journey? Most organizations already have more than half of their systems virtualized and are currently virtualizing their most business critical applications.

Now you are facing the challenge of keeping your ever-expanding virtual environment protected while providing the required service level for the business critical physical systems. Managing two separate isolated environments increases complexity and introduces potential for gaps in the data protection strategy if not carefully planned and implemented.

A poorly planned data protection strategy will not only increase risk to the data but will also consume more storage, restrict your recovery options and increase the time spent managing the environment. This is why it is important to understand the options and pitfalls when building a data protection strategy for virtual and mixed environments.

Host-level Integration and Virtual Machine optimized...

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

AmolB | 03 Oct 2012 | 7 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.

 

Overview:

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

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.

 

Background:

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

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

Kiran Bandi | 06 May 2012 | 3 comments

As i have seen some members asking for download links to earlier verisons of Backup Exec, i thought of posting those in a BLOG.

Backup Exec 11d for Windows Servers: https://www4.symantec.com/Vrt/offer?a_id=30140

Backup Exec 12.5 for Windows Server: https://www4.symantec.com/Vrt/offer?a_id=51792

Backup Exec 2010 R3 for Windows Server: http://trialware.norton.com/files/fc/Backup_Exec_2...

SeanRegan | 12 Jan 2012 | 0 comments

 

I’m excited to have a guest Blogger Rudy McNeese and the Heathrow, Florida office join the Countdown to Better Backup. Today we opened the launch countdown window for Instant Disaster Recovery with P2V and B2V. 

With this capability Backup Exec 2012 will expand add two new key capabilities, physical to virtual conversions, known as P2V, as well as the ability to backup to virtual format, known as B2V.

The P2V process utilizes parallel data streams to store backup data from a protected server to a Backup Exec 2012 server while simultaneously sending the same backup data, in the form of a virtual machine, to a virtual host in the environment for both VMware vSphere and Microsoft Hyper-V environments.

The result of a P2V operation is a fully recoverable backup set as well as a fully functional virtual machine that can be used for permanent virtual conversion operations as well as warm failover, disaster recovery scenarios.

The B2V...

SeanRegan | 09 Jan 2012 | 0 comments

 

Why Roseville?

We started the NetBackup and Backup Exec launch sequence this week with the release of the Countdown to Better Backup Calendar. This was modeled after the idea of an Advent Calendar. Every few days we will open a new window to reveal a new feature of the launch calendar leading up to the product launch. As part of the launch effort each square on the calendar will open in a different city worldwide. This helps us reach our customers and partners in cities around the world and it gives us a chance to bring together all the people who have worked on the release.

Often in marketing it is hard to deliver technical information to the end customers. Everyone is busy, and there is so much noise online it is hard for product announcements to reach customers. One just needs to post a question on LinkedIn asking...