Now, i recently discovered, while rerunning failed jobs, that all of our Diff duplicates were just vanishing into thin air. If the job doesnt run during its scheduled time frame, it will throw a "missed" error. If we manually intervene with a job and cancel it, it will show up as canceled. This will show up in the reports we run and will kick off an alert and a ticket in our setup (ssooo many tickets :( ). In backup exec, if a job fails to complete while running, it causes a "failure". We duplicate all of our production backup jobs to tape (fulls and diffs), keeping them for 1 month and keeping our month end fulls forever. An untraceable and unauditable issue (thank God): i could go on and on and on.īut here is the most recent issue i have found. Its file quiescing is second to none in the crappy department. It will write data at an astonishingly low rate. Its extremely sensitive and will throw random failures all day long. We have been trying to move our clients off of BE and onto commvault for some period of time now, but there are still x2 BE 2010 environments that i have to manage daily. The more and more time you spend managing that software, the more and more bugs and BS you will find, and the more and more you will hate it. Regardless if it's owned by Veritas or Symantec it's a garbage product and at the end of the day I don't trust it. Not as if they read from a flow chart for troubleshooting methods. Since at this point with all the phone tag and them not answering e-mails for weeks on end my backups had expired.īut hey, this is why we outsource our support to other countries because they are extremely reliable and know the product. In the end I was "moved up" to their DataDomain specialist, who told me flat out "I am not very familiar with DataDomain." At that point I simply told him I'll make a new DDBoost interface and write all my backups over there. This was after I had already dealt with EMC ensuring it wasn't something from their end. I worked with them for a month and a half on why I couldn't write data to my DataDomain unless I did an inventory before hand (which would only make it writable for about 3-6 hours). So far on a Disaster Recovery on a 2019 server I hit a brick wall.The fun part of Backup Exec is that when you call their support they suck just as much as the product. I tried to duplicate the backup to a USB drive, boot the server with the SDR disc, connect the USB drive to the server and tried to restore from local drive but, unable to find a *.DR file to restore. An in-place restore (server up and restoring), will start but, 20-25 min later it fails with TONS of permissions issues. I have booted the server with the SDR disc, and it lists the server but, shows no backup time, so I am unable to restore. I can restore single files/folders with no issues but, a SDR restore is not possible from what I have found in my testing.
I have a Windows 2019 server I just built for testing this (well it will be something else later), I have done a 1 time backup to test, Backup Exec 2014 does successfully backup the server with no errors. We have not had an issue backing up/restoring any servers till now. I KNOW 2019 is not on the compatibility lists but, for now, I need a solution for this, if possible. As you can see upgrading to the newest version would cost a small fortune. The server has the library expansion, Deduplication, Windows, VMware, Applications, Unix licenses. We are backing up to disc, then duplicating to Tape for longer storage.
I have Backup Exec 2014 SP2 (newest build, 14.1 Rev.
As we have 2014, it does not qualify for upgrade pricing according to Veritas, so this limits my options even more. In my company, I am an admin who deals with the backups, with this being said, budget is not there for a upgrade at this time.