Forum Discussion
Symantec has been talking about a fix for this mess for the past 2 months. Where is it?
So far BE 2012 is the worst piece of software I have every had the displeasure of using. What I would like to know is what software engineer thought it would be a good idea to totally trash the old backup model that has worked for the past decade or more? Splitting the jobs into individual servers makes absolutely no sense if you are backing up to tape. I have 11 servers to backup. So now, with this brilliant new paradigm, my tape gets to be moved into and out of the drive 11 times per day by the robotic library. I'm sure that's good for the longevity of the device and the tapes.
Here's another major problem. How to I string all my backups together on my tapes unless I erase them first? You can't. If you don't erase the tapes first, it will append the jobs until it hits the end of the tape, then it starts overwriting. You have no control of what gets overwritten. You can't set the jobs to overwrite the tape either because each successive job will simply overwrite the one you just completed. In the old model I simple set the job to overwrite every day and it wasn't a problem because all the servers were contained in that one job. It's supposed to span multiple tapes too but I haven't been able to make that work either. It used to work in 2010 but 2012 seems to be fixated on putting everything on the first tape in my partition. It's probably some minor setting I've missed that is buried 15 layers deep in the new interface.
Oh yeah. The performance of this new model sucks too. It takes at least 3 hours longer to back up all my servers than it did in 2010.
Here is some free advice. Stop trying to change things. Backup Exec is the premier backup product because IT people like me know how to use it and like the way it works. The only thing you need to do to improve it is make it faster and more reliable. We don't need any new paradigms we need a piece of software that gets the job done without causing undue irritation. You have failed to provide that with BE 2012. Fix it please and fix it fast because the frustration this is causing me is making think about a real paradigm shift in my backup model. I might just switch to VEEAM and give up on BE altogether.
Related Content
- 2 months ago
- 5 years ago
- 10 years ago
- 14 years ago