1 post • joined Friday 13th July 2012 12:15 GMT
Enrique Salem, President and CEO
Read this article:
And this thread:
And this post:
Sorry, no matter how much you pay google to hype your product, we still can find out the truth.
What an unmitigated disaster your product has become.
Really, this is not that complicated. Backing up data is simply stated, a copy of the data in another location that can be used to recover the data if the original is corrupted, deleted, or destroyed. Backup should automate this process, with some ability to report that the backup completed. BEXEC 2012 can barely run a straight forward backup job of a windows server, it can’t run more than one consecutive full backup of my exchange environments without failing on the next job, it has in-comprehensible error messages that vary from job to job, if I were to follow the conflicting resolutions I would disable my exchange server but have great backup jobs!
Here is what I would suggest as a possible solution:
Run every job as a “test-scan”, surely you can design something that will at least pretend to back up my network and exhibit a fancy progress bar along with generating “success” messages? At least I won’t feel as bad and I will be able to show my boss that my hours of working on fixing these errors was time well spent? Would bribery help? Maybe I could buy you and your engineers a round?
Backup Exec 2012 is possibly the worst upgrade that has ever come out of Symantec.
We no longer use Symantec AV / Endpoint protection, we have started to hate on Symantec Ghost, and we never were able to get the knack of using NAC in an enterprise environment. Symantec should get an award for products from hell. It seem like you have a personal vendetta for IT administrators.
The only reason we still use brightmail is because it actually started working after years of bizarre internal bugs.
Please don’t change brightmail, please, please, please.