Video Screencast Help
Backup and Recovery Community Blog
Showing posts tagged with 2012
Showing posts in English
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.

lmosla | 12 Nov 2012 | 0 comments

Do I have to verify?    Here is a short summary of what’s up with that verify portion of the job that everyone says is so important, but seems to take too long. 

To ensure your backups are healthy it is strongly recommended to run a Verify.  The Verify job checks that data can be read or restored from the media. Backup Exec includes this as a default in backup jobs but you can schedule the verify operation to run at a different time or you can disable it. Scheduling Verify to run at a separate time enables the backup jobs to complete in a shorter time window.

Options  are:

At the end of the job.  This is automatically set in the job

After job finishes, as a  separate job  You can check the checkbox to  Verify the data on the client if the device supports it;  This allows the verify job to run remotely therefore freeing up...

Donald Eady | 29 Oct 2012 | 3 comments

 

-          Browse to www.backupexec.com on the right hand side of this page click on  Traialware as highlighted below

-          On the Trialware page choose Backup exec and then Download Now

-          Review and agree to the terms and conditions and you will be taken to a software download page

-          You may be prompted to enter/create your SymAccount login crendentials

-    ...

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 | 1 comment

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

Jason Wiese | 21 Sep 2012 | 4 comments

There seems to be a problem in Backup Exec 2012 in how it detects virtual windows servers (Hyper-V) as being virtual rather than being physical boxes.

When you backup new virtual servers on the host machine, Backup Exec normally adds the newly discovered virtual servers to the selection list as virtual servers with the blue virtual server icon.

However, if you have already installed the Backup Exec Remote Agent for Windows Servers inside of the virtual server prior to backing up the virtual server for the first time, Backup Exec sees the server as a physical box and adds the virtual server to the selection list as a physical server. Backup Exec then says this server has never been backed up and you can not do any granular restores of the virtual server.

The workaround for me was to delete the mis-identified virtual server from the selection list. Uninstall the Backup Exec Agent from inside the virtual server. Then do a backup of the host again. Backup Exec then...

Kyle Drake | 11 Sep 2012 | 0 comments

So I just finished up VMworld in San Francisco week before last, and I was amazed at how many different products were out there to enhance customers’ virtual infrastructures, whether their data centers were on premise or “in the cloud”.  There were many monitoring and reporting products, partner companies looking to relieve the burden for customers to manage their virtual projects, and of course many products that provide backup and recovery capabilities for critical virtual machines.  I think there were 4 or 5 that claimed they were “#1 in VM backups”.   I haven’t seen so much confusion on who’s number 1 since college football introduced the BCS!

What was clear was that the companies touting “#1” were all point product solutions specifically for VM backup and recovery.  These solutions solely focus on the virtual machines themselves, with a little integration to VMware’s management...

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

Jim Harrison | 10 Aug 2012 | 0 comments

These are my experiences with the BE 2012 upgrade:

- Lost all jobs in upgrade from 2010, had to create new sets

- Compounding on above - interface appeared easy but frustration ensued when configuring media, day 5 no backups is scary!

- DAG was recognized in server set but cannot select in edit settings - confusing. (update 8.14) It's not backing up the DAG. I had not installed the Agent for Applications and Databases. Once installed I was able to see the DAG. Also the licenses did not transfer correctly from 2010 to 2012 but I eventually got that worked out as well. Now my DAG is backing up from the wrong site. I am installing Exchange Management Tools for Microsoft Exchange Server 2010 on the BE Server. This was not installed with 2010 and am not certain it was required but Symantec says it will help.

- Tapes were not immediately recognized and had to inventory before backups began to work....

Joins05 | 18 Jul 2012 | 1 comment

 

After upgrading to BE 2012, I wanted to set up backups for all of our workstations.  I had previously only backed up our servers and workstations needed for our daily production at our sign shop.  The decision to backup all workstations was due to a new need for better safetyguards for our workstations going down due to me moving too far away to be onsite on a daily basis for any hardware/software failure.  Our domain controller is SBS 2003 running exchange, it also runs the backup exec.  We also have Server 2008 acting as a fileserver.  The servers that already had remote agent on them from BE 2010 had no problem ungrading.

However, when I tried to push install Agent for Windows to our other workstations (XP or 7), I recieved the status "Error connecting to the remote computer.  Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. 1603".  I checked the workstations and their...