Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Backup and Recovery Community Blog
Showing posts tagged with Backup Exec
Showing posts in English
OneManITShop | 19 Aug 2009 | 0 comments

I had to restore a file this morning using my B2D job. While I had no problems and everyone is happy I found it to be the perfect opportunity to go over my backup plan. It can’t hurt.

I backup 3 data types:
Email (Domino Server)
User data (aka files)
Active Directory

I’m using Backup Exec for all my backup jobs and most of the time I’m happy with the performance.

Domino backup is done using the Domino agent. Using this article as a reference I backup the Lotus\Domino\Data folder. Weekly cycle to tape with daily full backup to disk provide a strong backup. One important note that helps me keeping the backup in reasonable size is old users nsf files. When a user leave the company we still need to keep the mailbox (compliance, compliance, compliance) but it is not changing and there is no point in backing the same file every day. I have...

Monica Girolami | 19 Aug 2009 | 0 comments
Efficiency. That seems to be on the minds of many business leaders. Lately I have been thinking about how organizations can improve efficiency. So many businesses are brainstorming how to keep their business operating at its best without breaking the bank.
Simple steps can often have a big impact. One thing that is often pushed aside during economic downtimes is upgrading backup software.  But in the meantime, new technologies, such as server virtualization and the latest versions of Windows, have been implemented within the environment and need to be supported by the backup software. 
It surprises me how often we find that organizations are operating on outdated backup software by three years or more. When you consider the significant technology improvements made with each new version, organizations are missing out on a number of key benefits that can ultimately save time and money through...
CraigV | 06 Aug 2009 | 0 comments

I've already written an article on how we moved from ARCserve 11.5 on about 34 sites to Backup Exec 11D, detaling all the issues we had and how we got around them, so this blog deals with moving to Backup Exec 12.5 and why we did so!

I am a storage engineer for an outsource team, looking after a very large production company with sites across Africa and Asia.

Over the course of around 18 months, we were running Backup Exec 11D (first rev. 6235 which was problematic from the start), and then on to rev. 7170 (which brought more stability, but only just). With our initial financial considerations for moving over to BE moving out the way (ARCserve licensing would have worked out more expensive to relicense than to buy a new application with licenses!), the focus turned to getting stability in the backup environment. Backup Exec had been chosen as it was cheaper to license, support seemed better, and with the problems using ARCserve being an almost constant...

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

Geoff_Vane | 29 Jul 2009 | 0 comments

This is a message about appending problems, you may have.

I am mis-using BackupExec and a LTO dirve as an archive, not as a backup.
So, I write once and store the tapes.

Appending goes very well, when you are writing lots of data for the first time.
When the tape is full, you are asked to put in a new one, and the writing continues.

You may have noticed, your second tape is not completely full.
So, next time you may decide you want to use it again, to append data to it. Fill it up, so to speak.

Now very often a problem occurs.
You start the backup job, put in the half filled tape.
Backup Exec keeps kicking the tape out, over and over again.
It will not accept this used tape to write on.

There is a solution to this problem!
You must group your media in backup exec.
This is called a media set.

1. On the navigation bar, click Media.
2. Under Media Set Tasks in the task pane, click New...

GFK | 24 Jul 2009 | 0 comments

1. BE SP2 Release

There are a number of fixes around GRT including up to a 90% decrease in the time taken to run an incremental GRT backup. Please see the following technote which provides links to and details around the changes and fixes in SP2

Release notes are here:

2. You know I keep banging on about AD … well it’s not just me:

Optimizing Exchange and Active Directory Backup and Recovery – Thursday, 28 May 2009, Written by Pat Hanavan


RahulG | 20 Jul 2009 | 1 comment

The Backup Exec Command Line Applet is a convenient way to access some of the most useful features of Backup Exec from a command prompt.

The Command Line Applet allows management of only one media server at a time, but allows for remote management of media servers within an enterprise. However, if the Central Admin Server Option (CASO) is installed, you can administer all servers managed by the central administration server.

Backup Exec must be installed and running on a media server in order for the Command Line Applet to target it, but the Command Line Applet does not have to be run from a media server. The Command Line Applet uses functional command switches typed in a command prompt window to perform most Backup Exec functions and utilities.

Note: Backup Exec Command Line Applet is only backwards compatible for a previous release and dot releases of the same version of Backup Exec.

The Command Line Applet displays job statuses as numeric values....

GFK | 17 Jul 2009 | 0 comments

You might have had a really (really) good backup strategy 2 or 3 years ago, but does it stack up today? Every vendor you’ve ever heard about is always banging on about backup and recovery being even more tricky than it was yesterday; and how it is now ever more challenging than it ever was, and, frankly it was pretty trick then … what with data growth going crazy, sprawling physical and virtualised environments, shrinking, nay, shrunk backup windows (what’s backup window?), and escalating storage management costs.

Gosh, haven’t we heard it all before? But, it is certainly true that the age old conventional backup solutions have not kept up with the data protection requirements, as well as the growth in data itself forcing substantial investments in hardware and dramatically increased administrator workload.

You might already have a good data backup strategy in place. But if your server hardware were lost or your building suddenly off limits,...

| 09 Jul 2009 | 4 comments

When using the Backup Exec MSVS agent  to backup the Hyper-V virtual images it will backup the complete hard drive and not the actual data on the drive. I mean if you have created a VHD of 100 GB and have only 30 GB used, when we backup it the VHD it will backup complete 100GB and not 30 GB this is because Unlike VMware, MS doesnot provide any utilty like VCB which inturn compress the data and lets the Backup Exec backup the only data and not the free space.

hence when backing up Hyper-V images it will backup the complete VHD though you donnot have that much data on the drive.....

Let me know if some has any other answer to this question.

| 09 Jul 2009 | 1 comment


VCB is Vmware consolidated backup a utility from which allows backup applications to take online snapshots of running Linux and Windows Guest virtual machines hosted on VMware ESX or ESXi servers. VCB then allows those snapshots to be moved to a separate system known as a “VCB Proxy Server” to be backed up “off-host” from the ESX host server by a backup application, such as Backup Exec 12.5, without impacting the ESX host server and all of its Guest virtual machines during a backup

AVVI agent doesnot include the VCB, you cannot use the AVVI agent without VCB as that is utility which will all the backup software to take the snapshot of the VM's

If u have a VM ware server that should not cost u . u can download it using the link