Video Screencast Help

Backup Exec 2012 single backup for Multiple Servers.

Created: 14 May 2012 • Updated: 26 Sep 2012 | 47 comments
This issue has been solved. See solution.


I have multiple windows server.  I am using backupexec version 2012.  I need to backup my all server in single backup job like my previous backup exec version 2010.

But In backup exec 2012 i am not able to create common backup job for my all servers.  I don't want to create seprate backup job for each my server.

Can anyone please tell me how to configure one single backup job who can take backup of my multiple servers????

Thanks ,

Santosh Pawar

[Symantec Veritas Operations]

Comments 47 CommentsJump to latest comment

pkh's picture

With BE 2012, you cannot backup more than 1 server with a single job.  There is no way around this.

GAD Tech's picture

I have the same problem as Santosh. Version 2010 did it all in one job. When I upgraded to 2012 that stopped working. I thought maybe by grouping the servers they could be backed up as one job, but apparently a job is still created for every server in the group.

In fact, with 2012 I'm even having trouble getting two jobs on the same media. Is there no way to tell it to backup one server first and then append the second server on the same media as soon as the first job ends?

GLWSchwarz's picture

The actual BE2012 is not designed that way, it's optimised for targetting multiple jobs to backup-to-disk, to shorten the backup window, but...

Symantec is working on capabilites you asked for, like linked backups targetting the same tape-media-set, but this will take some time.

SuperBrain's picture


It is true that you cannot create a job with multiple servers resources selected.

one server per backup job. thats how it work in Backup Exec 2012.

If you are worried about the time it may take for job creation (considering you have multiple servers in your environment), you can try using the "Groups" feature in Backup Exec. - Using Server Groups in Backup Exec 2012. - Backing up server groups.

*** Important ***

This option will allow you to:

  1. Create a Group of all servers which you want to backup using Backup Exec 2012.
  2. Using the Group, you can create individual jobs for all selected servers at once (hence saving time and efforts to create each job one by one)
  3. Once all the jobs are created (i.e. one job per server), you can then modify each job as required (i.e. Device/Settings/Schedules/etc).
Hopest's picture

Technically you can backup multiple servers by putting the servers you would like to backup into a group and then by right clicking on the group you point to Backup - backup to tape and then this will open a new job with the server's listed on the right.

The only thing with this is that you can not edit the selections for each individual server, you have to backup the everything.

If you need to edit the selection for each server than i'm afraid you are stuck with how 2012 is built and have to create a new job for each.


Ken Putnam's picture

That still creates multiple jobs and the tape will rewind and fast forward between them (extra wear and tear in the mechanism)

If this response answers your concern, please mark it as a "solution"

SuperBrain's picture

Like i mentioned above, it will create individual (seperate) jobs with same settings for each server in the Group. 

These jobs can later be modified to change the selections/settings/devices/schecdules/etc as required byt the backup admin.

See for more info on Server Groups.

Sush...'s picture

You may also try the solution provided in this technote: : How to back up multiple servers to a single series of tapes in Backup Exec 2012



Hope this piece of Information Helps you... and if it does then mark this response as Solution....!!!

Elizabeth Teffner's picture


I'm a usability engineer for Backup Exec and we have heard about this issue from many users through many avenues and we are listening.

Currently we are working on a new workflow to accomplish the 1 job with multiple servers issue. It's in the mock-up stage and we are looking for users to give us feedback.

If you are interested in participating in a usability session, please check out the sessions I have for next week. These are remote session via WebEx and about an hour long.

If you have any questions about this, feel free to leave a comment here - or send me an email directly.



ForemanNZ's picture

The Backup Exec 2010 job tree option was just what I needed - I have a combination of physical and virtual servers, and at the moment I have 21 backup jobs + 11 incrementals + duplications, whereas previously I had 2.  We paid maintenance on our existing licencing to give us GRT exchange backup ability, but at the moment I'm spending days at a time managing backups as every server has its own jobs (multiples!), and if there is a problem in the way I've setup a backup, I have to apply to fix to each job independently!

Mandar Sahasrabuddhe's picture


There appear to be two parts to the question,

  1. Multiple server selection - Kindly refer to Bhavik's post above for creating jobs for multiple servers in one go. That will create jobs per server and they can be further edited to change the selection lists. Just a point to note that jobs per server is the model in BE 2012.
  2. Editing multiple jobs - The multi-edit feature in BE 2012 is for editing multiple properties for jobs in one go, instead of applying fix to each job independently, which is the second part of your post. Following link is about the multi-edit feature


Elizabeth Teffner's picture

Hello everyone!

I just wanted to give you an update on my request for user feedback. 

I had 9 participants who looked at the mock-ups of the new workflow. Everyone gave me a lot of great feedback which I’m taking back to the developers.

I wanted to thank everyone who participated!  I really appreciate everyone’s input!

Regards… Elizabeth

jaikudo's picture

Hi Elizabeth,

I would very much like to be in the loop of this update.

I am downgrading back to Backup Exec 2010 today because of the multiple servers not being in the single job in 2012 sp1.

I have tried playing around with the grouping and all, but i don't want to overwrite any backup nor do i want to have few jobs for servers.

Please forward any links that would keep me updated as I have lost 2 days of backups because of this and now I have to install 2010 again.


Elizabeth Teffner's picture


Sorry I missed this earlier when you posted this.  I can't give out dates when this will be released. What I can tell you is that the team is diligently working on this.  There are several threads on SymConnect that touch on the backup jobs with multiple servers.  When I have updates I can release, I'll post those to all the various threads.

I ran one round of user testing with an earlier version. I do have plans on running another round to get more user feedback.  Keep an eye peeled for that post.  I'm "hoping" to get this in the works in less than a month.

Best Regards,


pguerrero's picture

This was a bad idea. There's no reason BE couldn't do simultaneous backup streams to any device that supports it. In this day of multitasking/multithreaded processors and applications it seems backwards to go to a server focused backup strategy. For me backups are managed as a set and all resources are interconnected.

crispyc4's picture

Hi Elizabeth

When will the new workflow be implemented?  

BE 2012 is useless to me in it's current implementation, I now have no choice but to revert to BE 2010, what a waste of money on new 2012 licencing.

Was this new server centric backup method requested by existing Symantec clients or was it just a bad decission made internally without consultation?

Please give me feedback as soon as possible.



charlesc_act's picture

i have to say, after using Backup Exec for over 10 years I am amazed that such a radical change was implemented without more user testing or at least maintaining an option to use the old way of working.

It was only when I found this thread I realised how unuseable this approach is for our scenario and I am now, after a full saturday of migration to a new server, going to be spending my sunday rolling the BE software back to 2010 - and that's if I can get 2012 to uninstall which proved difficult before.

We have just relicensed for this year, but if this is not fixed within the year I will seriously have to look at different software.

jaikudo's picture

Hi Elizabeth,

I would like to point out another change with the scheduling: In previous versions you could tick and choose which days you want the job to run, but on 2012 you can have weekdays and weekends. Problem with our environment is that our weekend (for backups) is Friday. So having just weekdays and weekends option is not going to do for us.

Again, I would like to have a link for any update news and also to report the bugs and problems (sounds more like a beta version to be honest)

Elizabeth Teffner's picture

Sorry for the delay in responding.  I actually got to take a few days of PTO.  Woo Hoo...

We have received a lot of feedback from our users and there were several regarding how we've made it a bit tricky to schedule some backup scenarios.  We are in the process of enhancing some of the schedule options. These new options are set to be released soon (sorry can't give an exact date). 

If you are interested in taking a look at this and give me some feedback on these new options, please send me a DM and I can set up a WebEx session.  I'm very curious to see if the new additions we are working on will allow you to schedule your backups.

BTW - anyone else who is reading this thread and is interested, please feel free to DM me!!

Regards... Elizabeth

Lesta G's picture

It's easy to get one job to backup all the servers......... answer.... virtualise them all to VMWare vsphere, use vcenter to control all the ESX hosts and then you can do it all in one go using the AVVI agent.... except the media server which will need to be in a separate job.... trivial really....

Go on you gotta laugh or you will cry.......

If this response answers your query, please mark it as a solution

ForemanNZ's picture

If you pick Monthly in the schedule, you get extra options like last day of the month, or first saturday, etc

In terms of the server centric, my job list is now corrupt and it won't save changes to my jobs, cannot delete them, cannot do anything ... nice.

In terms of using VMware, yes, I'm using that too, but you cannot select files at the folder level, so while its good for a disaster recovery, its no good for a selective incremental backup

Elizabeth Teffner's picture


See my comment above to jaikudo's post.  The same offer applys!  I'd love to have you take a look at the upcoming scheduler additions to see if these will help with your scheduling options.  Feel free to DM me!!

Regards... Elizabeth

espartan's picture

forgive me if im wrong. im planning and designing a backup and recovery strategy utilising symantec. I belive the requirement for the user is a caso license? this will allow the user to centrally manage all backups and most importantly assist the user from a recovery point of view?

BanksyMJ's picture

Hi Espartan

If you have a single Backup Exec Media Server then you can manage all your backups from that server. If you have multiple BE Media Servers then you can use CASO to 'promote' one of the Media Servers to a central management server. From this management server you can manage backups, restores, storage etc. on all your BE Media Servers.

In BE 2012 the CASO option is now part of the Enterprise Server Option (ESO). ESO also includes the Advanced Disk Backup Option (ADBO) and the SAN Share Storage Option (SSSO). If you have are still in maintenance and have either CASO, ADBO or SSSO. When you upgrade to BE 2012 you are automatically entitled to ESO.



Karl Wilhelm's picture


Are we any closer to fixing this issue?

This is a huge problem when backing up files and folders on clustered resources as each instance must be backed up separately and treated individually :(



dedupe-works's picture

How to back up multiple servers to a single series of tapes in Backup Exec 2012



GAD Tech's picture

Yeah, I kind of figured that out the first time I started using BE 2012. Excuse me for saying so, but when I was younger that was called a workaround, not a solution as TECH189306 calls it.

The problem that you still have is that you have to guess when the previous backup will be done and schedule the next one to start sometime after that. That I know of, there is no trigger in BE that says the previous backup is done and now you can switch servers and start the other one.

As I see it, the need for a solution still exists. But thanks for something to work with until that solution is implemented.

BTW, others have suggested this same article further up the thread. I'm hoping that what I read that Elizabeth is working on will be what we need.

GAD Tech

Karl Wilhelm's picture

I agree with you GAD Tech. While this work around is great for complete(all drives and states) server backups what about selectively only backing up say the X:\Backup folder on each server? Thats where the workaround falls short.

Elizabeth was kind enough to mail me back saying as soon as they have a solution it will be posted.



BobsBarlo's picture


After spending two days thinking I would look like a complete idiot for asking how to backup 2 servers at the same time I find .

Lets hear it for Backup Exec 2010!!

I can't believe how much time I waisted on this!! no

VincentStrijd's picture

I have been working with Backup Exec for a very long time, with various employers and have always been very satisfied with Symantec products.

Unfortunately, about three months ago, I decided to upgrade to BE 2012, since then I did not have a successfull backup, we are running a mixed environment with the majority of our servers virtualized on VMWare ESX 4 and a few physical servers.
Besides the one job per server nightmare and the try and tweak all jobs to go to one tape rather then all 30+ servers ending up on a seperate tape (You might think Symantec is a major stockholder in LTO-tape producing companies)
My biggest problem is that the VMWare backups can not be used to restore individual files (despite the fact that this is clearly advertised)

I have just re-installed my entire backup environment for a third (and final) time, if I still experience problems, I am done with Symantec and will start looking for other solutions on the market.

To end with some positive feedback... If you have only one physical server with one single tape drive, Backup Exec 2012 is a very nice and easy to configure product.
For our smaller (single server) branches it works perfectly.

espartan's picture

Thats interesting. Looking at rolling out a new backup and recovery strategy incorporating BE2012. Whole project is approx £36k. Not going to venture unless I know BE2012 will work.  

ForemanNZ's picture

I had Symantec send me a survey the other day, so I let rip!

The biggest problem with the product is they changed the very fabric of how it backs up your environment, instead of creating a parallel product with the server sentric style.  This is not Windows Backup, this is a product you use to backup your complex business system into a tried and tested backup infrastructure, and when you change how it talks to both its sources and targets without offering the setup everyone knows, you add substancial cost and risk to make it work.

Spyda1999's picture

* help please *

With the new changes for backup exec - you can't easily identify the backup tapes used for both full and incremental backups.

We previously had one or two backup jobs for our small sever environment – within the backup job it listed under ‘device and storage’ the backup tapes used for that job for all our servers.

Now under the server centric model, I have to click each server and locate or check the tape number for that job.

I’m not sure if its me or I don’t know how to drive the program, but is there a way to get the tape number for our weekly backup job like under the old version.

The new changes for backup exec don't seem to show you the tape number for a given backup jobs.

techdruid's picture

I just want to be notified if/when a new release comes out that allows multiple servers in a single backup.

I'm using the workaround right now, but would like the solution.

Not sure I'll be updated or not, since I don't recall being asked for my email address before posting this.  But hopefully Symantec finds it based on me being logged into mysupport.

gdevrye's picture

After reading the entire post, I gave 2012 a try. Took me 15 minutes to realise it's not going to work. From two jobs for daily and 3 for weekly backups, I ended up with 30+ jobs. That's just not possible. I immediately did a rollback from the server image I had previously taken.

The problem is: i was expecting to use Bexec 2012 to backup/recover a sharepoint farm running SQL 2012, and Bexec 2010 does not support it. I contacted Symantec support and got: 

"SQL 2012 is supported only with Backup Exec 2012, It is not supported with Backup Exec 2010 R3. We are sorry, there is no workaround for SQL 2012 with Backup Exec 2010 R3"

Unless someone can help here, I guess I will have to look somewhere else for another backup software doing Exchange, Sharepoint, SQL2012 and Linux...

So much time, money and effort wasted. Not too happy about it.

Karl Wilhelm's picture

Hey gdevrye

You could get your DBA's to schedule a full SQL backup to file and back that up as a workaround.

It is not ideal but would be a point in time backup of the DB for now.



pkh's picture

You would probably end up with a logicall inconsistent Sharepoint farm if you restore the individual databasess.  See my blog

RECH's picture


I have been trying to 'fiddle' with the 2012 backup for a month and I'm still having issues during my weekend jobs. (3 servers to one tape).

With 2010r3 I had no issues, all was working with no issues. Moved to 2013 and I found myself with 3 different jobs and schedules (not counting with the verify jobs).

I have removed the weekend jobs (as they were all going to the same tape) and just going for the week jobs to try to get reliable backups. (as I'm at the office)

I want multiple servers per job back (as 2010).

Do we have an ETA on this?


twp5253's picture

Wow, I really like this new product.   I really didn't need those jobs where I was backing up several servers with  a single job.  I am so happy Symantec got rid of that feature.   And the interface is so easy to learn.  Now, I just have to decide if searching for a new product from a different vendor would take less time than learning this one? 

santoshpawar's picture

Great someone is happy to backup this way...but for me it's frustrating to create single backup for single server when there is many server which i need to backup.

I hope as earliest as possible symantec will find solution for this which will make easier for everyone to manage their backups. 

let me notified if any new release comes out that allows multiple servers in a single backup in backupexec 2012.


Santosh Pawar

cem0211's picture

I too agree!  This has made my backup administration a complete nightmare to say the least, infact I feel now I wouldn't recommend this backupexec as a viable solution or recommendation to anyone.

I have been using backup exec version 2010 for two years without any issues and this backed up a lot of multiple servers onto as little as 2 x LTO tapes.  However, since having a problem with backup exec 2010 that seemed to get itself locked out and I could no longer run backup jobs, the backup exec knowledge base answer was to fix the issue by upgrading to 2012.

Since I have upgraded to 2012, I now find that my single backup job I had in 2010 has now become multiple backup jobs in 2012 and it is now using 1 tape for each job.  Therefore if I continue using this product, I will have to resort in taking 27 tapes for offsite storage as opposed to 2 tapes.  This is just ridiculous and I think a bad flaw.

When you have organisations that rely on on a small backup window opportunity and is also business critical, you do not want to be spreading a simple backup strategy over a wide number of very expensive tapes when a previous version could condense into 2 tapes.

If i wanted to go disk space storage backup, we would have invested in a large capacity SAN to do this but unfortunately I cannot store a SAN offsite or rotate a SAN on a backup regime.

I also notice that 2012 does not support SUN Solaris UNIX anymore either, it supports LINUX - why not Solaris like 2010 did?

Bad Bad flaw Symantec, Very bad indeed !

santoshpawar's picture

The Beta program is starting soon and will allow you to test new features and customer-recommended improvements in Backup Exec 2012. Some of the updates include:

  • Protection of Microsoft Windows Server 2012:
    • New ReFS (Resilient File System) support
    • New Hyper-V version support
    • Updated Failover Clustering support
  • Protection of Microsoft Windows 8
  • Microsoft SQL 2012 support:
    • Smart incremental/differential backups to prevent errors due to SQL mode (simple vs. full recovery model)
  • Customer-recommended Improvements:
    • Ability to sequence the order of multiple jobs and target those jobs to a specific tape device
    • Ability to customize selections for backups in multiple servers at once
    • Ability to set the order of resources within a backup job
    • Ability to see all jobs including backups and utility jobs in 1 place
    • Ability to initiate restore from Storage view and from a specific job
    • More flexible scheduling options

Tim g's picture

This is without a shadow of a doubt the most RUBBISH "upgrade????" to a piece of software I have EVER had the misfortune to deal with.

This morning I came into messages about my storage tape being full, so , understandably I had to cancel the job, however, YOU CANT CANCEL ONE JOB!!!!

Oh no, know you have to cancel every single job across all my servers.

Coupled with the AGE OLD STILL UNSOLVED application inactivity when trying to cancel a job, apparently associated with the amount of time the job has been on hold for....baaaah.

Service re-starts, Database corruption when trying to SCROLL through jobs sets in order to delete them to free up disk space.

It is now 15.40 & I started to clear up the job cancellations at 8.30am this morning, I AM STILL STRUGGLING TO CANCEL THEM!!!!!!!

What a load of old TRASH this is.

Administrators Guide - UNINSTALL, make do with version 2010, at least you could use the damn thing.

Better still get a refund, or change vendor.

twp5253's picture

Liz, have you ever worked in IT were you were responsible for doing backups?    The more I use this software, the more I don't want to use it.    Thankfully, I get the software from my parent corporation so it does not cost me $$ out of my budget.   Had I spent real $$ for this software, I would be one very unhappy customer.   I am not surprised that I belong to a large and growing group of IT professionals who actually know what they are doing.

Jimmy Mac's picture

With the original thread being locked as of 7/12, I have not been recieving any updates as to when this is going to be resolved.

Symantec, what is the time frame for the updated version that will permit these core requirement features that were removed in 2012?