on 05-24-2012 04:24 AM
This is a great article because it helps explain how to quickly deploy backup jobs using the new backup paradigm.
Keep the information coming and help the customers get their head around the new backup model.
Good work!
WOW nice information
This acticle confirmed my suspision, that BE2012 is not for me.
The nolonger existing possibillity to use individual selection lists on many servers to create one tape job starting at one time, was not even printed in small types anywhere.
I had to try, while fighting the "randomly dissapearing server bug", to create a singel backup to tape job for multiple servers just like i have on my BE 11d.
Finally i found an answer here, that will save me some hours, so i can give up earlyer rather than later.
I could have saved my department some money by sticking to BE 11d, or simply by pushing data to backup server, and then schedule a tape dump. But now that the software is paid for, ill have to enjoy the expensive bling bling menus.
Backup Exec 2012 R2 will release soon (not sure abt the exact date though), but its coming up with lots of improvements... and yes, coming back with the ability to add multiple servers in one selection list (or multiple server to same job)
Check this official blog entry for more details --> https://www-secure.symantec.com/connect/blogs/new-beta-program-backup-exec-2012-r2
You can also sign up for the Backup Exec 2012 R2 beta program.
First, I need to rant.
As other users have stated, BE2012 does not work for my enterprise as did previous versions. The inability to create one job encompassing multiple servers is a severe impediment to my job functionality. I'm not sure what Symantec was smoking when they made this decision, but infuriating a huge chunk of your core clientele is probably not the best thing to do.
So after spending tens of thousands of dollars to expand BE to serve as my enterprise backup system I find that 2012 is nowhere near 2010 in relation to function. It simply will not work in my situation, and I'm wondering what other, larger organizations have to say about this. It can't be good.
OK, end of rant.
So does anyone have an idea of a timeline for these supposed changes? If it's gonna be a year then I have no choice but to uninstall 2012 and return to 2010, where I can manage one job rather than >100 jobs!
Hi ristst.
Had the same experience. But i have found out a way that might work for me.
I create a "One-Time-Backup", and this job definition will then stay as a job definition on BE2012.
Then from the commandline (BEMCLI) run the job by the command:
get-bejob -name "[name of the backup job]" | start-be-job -confirm:$false
This can be done for each server, and if you add all the backup jobs you need to one powershell script and run it by scheduler, you might get the result you want.
/J
Hi SuperBrain,
It has been sometime since this thread was added to, but as it was the only one that relates to my delema and I am hoping you can assist me!
We are currently running Backup Exec 2012 V14.0 Rev. 1798, and my question relates to Server Groups.
Backup Exec 2012 seems to poll our network and source every server on the network and place them in All Servers Group. When I remove the unwanted servers they reappear after a period. After some investigation it appears Backup Exec is continually polling our network and re-establishing them in the list.
Therefore how do I:
Thank you.
I believe the following may work for you.
In B.Exec 2012, go to the B.Exec button (I am not sure what else to call it). It is at top left of the GUI. Choose Configuration and Settings > Backup Exec Settings > Discover Data to Backup. Deselect "Discover Data to Back Up".
Just make sure that if another admin puts a new server online that they know to notify you as to the specific backup requirements.
Hope this helps.