Showing results for 
Search instead for 
Did you mean: 
The Backup Exec Install Blog

My name is Nick Elmer and I’m a developer on the Backup Exec Install Team. I started with the company over 13 years ago in support(during the Seagate Software days), then I spent a few years after that in our quality assurance team(during the VERITAS Software days), and finally, I transitioned into a developer role. I spend time these days working on the DVD Browser, DVD media, Cluster Wizard, Install Dialogs, Push Install, and various other install related items. My best strengths are security, networking and writing secure code. I enjoy what I do immensely! 

In the upcoming weeks, I will be posting occasional blogs on install related topics for Backup Exec. If you have items you would like me to cover, feel free to contact me with those topics, and I’ll address them the best I can. Some of the topics I hope to cover would be: 

How Backup Exec 2010 R2 improves the upgrade experience.
How your participation in the user experience program is helping make the install more reliable.
How we improved the DVD Browser in 2010 to provide a best practices approach.

I look forward to sharing this information with you, and the discussions that will follow.

Thanks for your time,


Would you help us understand the offsite backup option in Symantec System Recovery ?


First, the only offsite option available is FTP, which is laughable at best.  Even if you choose the AES encryption of your backup files, the username and password for your offsite location are transmitted in cleartext.  While I support including FTP as an option for legacy integrations, it cannot be the only choice.  

SFTP (over SSH) or FTPS (SSL encrypted FTP) or even WebDAV over SSL would be good candidates for options there ... SFTP probably being the best.

Second, why are offsite backups not available for folder backups ?  I am able to do offsite backups when I create a job that backs up my entire computer, but when I create a job that simply backs up one or more folders, the option is not present at all.  This makes no sense.

Why is user interaction required to run the offsite backup (in the form of a pop-up notification from the systray) - am I really going to sit in front of the system for X hours waiting for the local backup to finish so that I can quickly (before it disappears) click "yes" or "no" to run the offsite backup ?  (although it should be noted that it appears to run by default if you "miss" the pop up window)


When defining the offsite job, the wizard explicitly asks you if you want to break up the backup into multiple chunks in case the offsite filesystem can't handle large files - if you say yes to this, and then later in the wizard, under advanced, choose chunking for the local backup, the setting is lost.  So your local backup is chunked into, say, 100 MB files, but the offsite backup is back to the default file sizing.


The same seems to be true of AES encryption - if you specify it early in the wizard, that setting is lost if you go into an advanced dialog box later in the wizard (unless you re-specify it there).

Also ....

The "Progress and Performance" window states that "no operations are currently running", but the systray status shows "Offsite Copy 4%", and I can see that the offsite copy is indeed transferring data.


Why doesn't the "Progress and Performance" (or ANY of the job status indicators) know anything about the offsite backup ?

Hi rsync,

Thank you for taking the time to post your questions. Unfortunately, I'm not familiar with the Symantec System Recovery product enough to address your comments. Your may be able to find some answers in the SSR forums.


Hi Nick

I have been searching for a Backup Exec 2010 Remote Agent for Macintosh Servers, but can't seem to find it.
I already have the Backup Exec 2010 V 13.0 but now I need some kind of backup for a Mac.

Can you point me in the right direction or is it just the same agent as I use already.


As Nick mentioned below, this blog post (and Nick's expertise) is focused on Backup Exec, not Symantec System Recovery (formerly known as Backup Exec System Recovery). Hopefully the name change for SSR will help prevent this kind of confusion in the future Smiley Happy.

For checking to see if something is a known issue (posted by our backline team) you can go here:
For asking the community if there's a workaround/suggestion I'd suggest the forums:
For giving your suggestion/Idea check here to vote for an existing similar Idea or add your own:

Hi Tha,
This is a common question. We do have an agent for Linux, Unix and MAC systems. That agent is located on our DVD. If you browse the DVD you will find a directory that is called "LinuxUnixMac". In that directory you will find a file called RALUS_RMALS_RAMS-1416.0.tar.gz. This is obviously a gzip file, and as such, it implies that it should be extracted on a Unix/Mac system. This is because it contains Perl directories, and when those are extracted on a Windows system, it cannot handle files with the same name, yet with different case(which perl has).

So, you should extract this file on your Linux/Unix/Mac system, and then you will find the installers for those platforms. There are step by step instructions in our admin guide for installing on these platforms.

If you need to see if the MAC OS version you are running is supported, you can find that here:

I hope this helps!



I have downloaded BE 2010 and installed the trial, the issue is with our tape Lib. it sees the 7 slots and the IBM tape drive unit but when i try to inventory, erase i get errors. this unit works well with Retrospect but i want to move to BE2010 for exchange any ideas?


Error under job failed is.....

Inventory Device 00002 -- The job failed with the following error: Physical Volume Library Robot not found.



Thank you.

Hello Nick,

One question I had related to install enhancements is when you migrate the Backup Exec database from one server to another, but then it leaves in the devices tab the older server. Have any enhancements been made with BE 2010 R2 or R3 to address this? I don't recall having this issue as much in previous versions of Backup Exec like 12.0 or 11d.

Also per it mentions that you shouldn't follow this process if the new Backup Exec server is on a different operating system. Do you know why the operating system would affect the ability to migrate the Backup Exec database to a new server?


Hey, my problem is to use the Agent with Vmware ESX 4.1 and any VM machine with independent disk!

in my situation, we have any machine with "c" and "d" partition. The "d" partition are over 1TB for use MS SQL e.g. - So this "d" are installed as separate LUN device and marked es independent disk.So there are not possible to use the Snapshot function on a running system. (with memory)

My question is: I need only the "c" partition to backup for restore the system. But there are no option to separate the "c" from the "d" partition in Backup Exec selective list.

Is it possible to use the function "exclude/include" to describe an exclude for "d" ? Or use the snapshot without memory ? or or or ?

thx for replay

Is there an easy way to move the sql database in BE 12.0 without destroying it or the installation?  I need to free ups some space on my C: partition and this looks like a prime candidate.  OS is Windows 2003 r2.


I am getting an Installation failed with error 1619. GetLastError=:216 immediately upon attemp to install.  Just downloaded lastnight.


The line above this says:  The .Net Installer returned 1619.  Exiting install.


I manually downloaded and installed .net 2.0 x64 and get the same results.



My small network has a Dell Server running Windows 2011 Small Busines Server 64 bit with three desktops. Two of the three desktops run Windows XP Professional 32 bit and the third desktop runs Windows 7 Ultimate 64 bit.

When I install Backup Exec 2010 R2 remote backup agents on the client desktops Backup Exec thinks the Windows 7 Ultimate 64 bit machine is a server. It gives an error message and says I must purchase a license for this client. 

I downloaded the latest version of Remote Agent (I think) and reinstalled them on all of the client machines but still got the same message. 

What steps do I need to take to get this problem resolved?

Hi Michael,

Excellent questions! I am working on answering them in my next blog. Your questions are good ones which are probably being asked by others as well. I will try to have a follow-up post this week.

Hi Ted,

Yes you can, you can move the database by using a program in the Backup Exec install directory called BEUTILITY.EXE. This link should help you.


Hi Gisdir,

The error 1619 is reporting that the .NET installer had a problem accessing files it required to install .NET. The second error 216 indicates that there is an error with the platform.

Together these errors imply that there is a problem with the redistributable package we supply on the DVD image for .NET installs. I would venture a guess that there is a problem with the download and you may need to re-download it. Give that a try and let me know your results.


Hi Vollgut,

I'm sorry, but your questions are outside my realm of expertise. I would suggest posting something in the forums on this issue.


Hi Port_447

This question is a hardware question, and also outside my realm of expertise. I would suggest posting something in the Backup Exec forums.


Hi Harry,

Yes, WIndows 7 and Windows Vista workstations do require a license. Here is a link in our technote database that describes this requirement.


I currently have 2 Exchange servers (1 CAS/HUB and 1 MBX).

I only want to backup the databases.

I installed successfully the agent on my MBX server.

I have no issue to get a full backup using GRT but when I try to restore a single email to a mailbox I got the following error message:

e0000f04 - The media server could not connect to the remote computer. The remote computer may not be running the Backup Exec Remote Agent for Windows/Linux. Make sure that the correct version of the Remote Agent is installed and running on the target computer.
For additional information regarding this error refer to link V-79-57344-3844

The remote computer which is trying to be reached is the CAS/HUB server!!!?

Should I buy and install an agent on my CAS/HUB server ?

Hello Nick!

there are any special instruction before we upgrade backup exec 2010 R2 to Backup exec 2010 R3. for example backup catalog folder/ data folder.

please advise.



Hi Muhammad,

I found this topic which can perhaps help you:


Hi Muhammad,

Its always a good idea to stop your Backup Exec services prior to performing an upgrade and make a redundant copy of the "Data" and "Catalogs" folders prior to upgrade. This way, should anything fail, you have your original data to fall back to. Once that is completed, go ahead and run the upgrade.

Hope this helps,

Hi Nick,

I have just read all of this topic:

If I well understand, we need only one license key Exchange agent for the whole Exchange organization.

But we have to install the remote agent on all Mailbox Servers to be backuped and on all CAS servers if we want to use GRT.

Can you confirm it ?

Thanks in advance.

Hello Nick,

We have upgraded one of our servers to BE 2010 and deployed the 2010 remote agent to the servers it is backing up.  We still have BE 12.5 installed on another server and it is backing up various servers using BE 12.5 remote agent.  My question is: Can I use BE 2010 Remote Agent with BE 12.5?  I have some servers being backed up by both versions of BE. Hope this question makes sense.



Hi Linda,

You can go backwards, but not forwards. What that means is that you can use Backup Exec 2010 to backup your 12.5 agent, but not the other way around. When your 2010 server runs a backup of an old agent, you will get a message that it needs to be upgraded. Our support for older agents is designed to give our customers time to upgrade their agents after upgrading their media servers. Its not designed to be a permanent solution. If you need to use the same agent from multiple backup servers, you should get them up to the same media server version.

Hope this helps,

Thanks, Nick.

Don't you think there should be some sort of notice that the five client licenses that you buy are for Windows XP professional clients only.  I also purchased Symantec Endpoint at the same time and it doesn't seem to have the same problem with considering my Windows 7 x64 client as a special case.  Frankly, I think Symantec should develop a Backup Remote agent for Windows 7 x64 clients just like Windows XP clients.  Is there a reason for this distinction?

Who can I contact to get Symantec to give me the license for this Windows 7 x64 client?  I know there is a certain amount of "buyer beware" but this software was purchased as a package from the server manufacturer and their salesman assured me that five client licenses would be sufficient for the three client computers on my network.

Thanks for the link to the forum conversation on the upgrade from 2010r2 to 2010r3.  Has Symantec published a more formal tech-note on this process?  I see there's this:

which addresses the process to go from [various previous versions] to 2010 R2, but haven't managed to track down anything for 2010r2 > 2010r3, other than the forum conversation linked above.

Or is it a "no-brainer" hence no article?




Hi GrNathan,

The process is the same for 2010 R3. We need to have someone update the document to specify R3 (instead of R2), since that is what we are currently shipping. I will ask the appropriate team to revise the document.


I was told BE2010R3 would do backup of my Windows 7 machines in addition to my XP machines - just like you Harry.  So I shelled out $800+ for the upgrade & it didn't do it.  Just like you.  So what happened?  Did you shell out more for the additional keys?

Hi Nick,

We have 2 Backup Exec servers. 1 with BEWS 12.0 rev 1364 running on Windows 2003 R2 SE SP2 and the other with BEWS 12.5 rev 2213 running on Windows 2008 Standard SP1.

We want to consolidate both servers into 1 using Backup Exec 2010.


1. Is this possible?

2. Where can I find the documentation on how to migrate/move the catalog and DBs into the new server?

If  #1 is not possible what are the other options. The most important is for us to be able to move/migrate the catalog and DBs onto to the new server.

Hi Joji,

I'll answer the best I can. Though its not simple, here is what I would do in your situation.

  • I would recommend that you get both servers to the same version and build. Based on what you provided above, that would be 12.5.2213. Having the data in databases on different OS platforms should not be an issue.
  • Second, there is an option within Backup Exec called "Copy Jobs". You can read more about the option in the Administrator Guide. It basically says this "To copy jobs, selection lists, or polices to other media servers, the Copy Server Configurations feature must be installed." Once that is installed, you can right click on your jobs and specify "Copy to other media servers". That will get the jobs to the other server. (I believe they need to be trusted so we can connect and transfer the information. Either that or pass-through authentication may suffice).
  • Now that you have jobs, you need to merge the catalogs. Catalogs are flat files in the Backup Exec installation folder, in a directory aptly named "Catalogs" (Unless you retargeted the folder in Tools-Options). Hopefully you know where these are! There are various files with different extensions. To merge the catalogs, you will need to stop all of the Backup Exec services on both servers, and copy the files from the second server to the first. I would recommend making a backup copy of the destination servers catalog folder before trying this merge. If there are any conflicts, they will have to be manually reviewed and resolved. I would not overwrite any files that are duplicated(If there are any). Since they are all unique GUIDs for names, there is a small chance they will be duplicated. I'm not aware of any documentation on doing this step! It may not even be supported! We support moving from one server to another, and re-cataloging tapes. But manually merging two sets of catalogs from different servers is probably not on the short list of supported migration paths (though this should work). When services start, Backup Exec will begin indexing any new catalogs it finds. When it is finished, you should see all of your catalogs when clicking restore. It may take awhile to complete the indexing rebuild.
  • If memory serves me well, the job history from the second server may be lost with the move. I cannot remember if the copy job will migrate it or not. I do not believe that it does. In which case, I would make a copy of the "Data" folder under the Backup Exec install directory, and move it over to the consolidated server. Just in case you ever need to reference a job log for restore, or something related which required having it available.

The Administrators Guide is a good reference, as well as technotes on the copy job steps above. Like I already said, merging catalogs is probably not supported, though it should work. Let me know if reports, job history and such are on the list of required data and I'll ask my colleagues for more details.

Hope this helps!

Hello Nick

I've a backup Exec 2010 R3 intalled over w2008 server, I've two FS server w2003 coneected to SAN storage by fibre. And I've a hp storage works 1/8 G2 tape Autoloader (scsi) connected to a one FS.

I can't connect de library to backup exec server because I dont have fibre or scsi in this server. The backup exec server can't discover the autoloader, I don't know why. I need know how I should connect all element (server,san, autoloader...)


Thanks in advance



I have a very simple problem I think:

I try to install Symantec BESR 2010, but it doen't work. An error appears:

BESR 2010 is not supported by Windows XP/Vista ! Windows 2008 Server R2 is my operating system, not WXP or WVista !

I have searched in many Symantec help sites, but I didn't find a good answer !

Thanks in advance and regards

Frank Klyk

Hi Frank -

If you are running Windows 2008 R2, you will want to upgrade to Symantec System Recovery 2013, which supports this operating system. BESR 2010 supports 2008, but not 2008 R2. (BESR was renamed to Symantec System Recovery).


If you have further questions about BESR\SSR, please click here: