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

Krishna Pratap Singh | 16 Sep 2012 | 0 comments

So far we have covered the steps on how to download the plugin, configure the pre-requisites and finally Install the plugin. All this is fine but we still need to do some configurations on the plugin so that we are all set for monitoring the Back Exec environments, which is afterall our primary requirement isn't it. So without taking too much of your time, lets just jump straight into it.

Configuring the plug-in to start monitoring Backup Exec environments

To monitor Backup Exec servers, several agent procedures have been provided under Agent Procedures > Manage Procedures > Schedule /Create > Shared > Backup Exec Procedure. All the agent procedures MUST be run from this default...

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

Krishna Pratap Singh | 21 Aug 2012 | 0 comments

In my last post I showed you how you can configure the pre-requisites required for installing the Plug-in. This post will take you through installing the plug-in. To begin with you need to have administrator privileges on the system where you are trying to install the plug-in. Please note that there are some software prerequisites that must be installed on your computer as a part of the installation process. The installation program checks if the required software exists on your computer. If they are not found, the installation program automatically installs them on your computer. So let's begin.....

Run the setup

Run the downloaded setup file “Symantec Backup Exec Management Plug-in 1.1 for Kaseya.exe”, Click “Continue”. This will extract the package and proceed to welcome screen.

...

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

Krishna Pratap Singh | 06 Aug 2012 | 0 comments

What is it?

Symantec Backup Exec Management Plug-in 1.1 for Kaseya is a plug-in for the Kaseya RMM platform. It is designed for Managed Service Providers (MSP). It enables the MSPs to remotely monitor the Backup Exec media servers in the customer environments.

All right, but how does this help me?

Well for starters it helps you by collecting the following information:

  • Status of the backup tasks that ran on the Backup Exec servers. For e.g. Successful backup jobs, failed backup jobs, and so on.
  • Active alerts generated on the Backup Exec servers. For e.g. jobs completed with exceptions, Database maintenance information, etc.
  • State of the storage devices and amount of space available on the disk-based storage devices that are configured with the Backup Exec servers. For e.g. disk-based storage device has gone offline or the storage space has reached a critical limit based on the configured...
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...

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