<link>https://www.edugeek.net/blogs/blog/1521-virtualization-backup-storage-cloud-startups-vbscs/</link><description/><language>en</language><item><title>Veeam reclassified critical VBR7 bugs into non-criticalhttps://www.edugeek.net/blogs/entry/915-veeam-reclassified-critical-vbr7-bugs-into-non-critical/A week ago I posted a list of Veeam Backup & Replication 7 bugs that I found critical: Veeam Backup & Replication 7 – total disaster | VBSCS (do read my post to become familiar with mypoint of view).

Anton Gostev, The guy behind Veeam Backup & Replication, Director ofProduct Management at Veeam Software (http://goo.gl/VwQZQy) answered me: Veeam Backup & Replication 7 – total disaster | VBSCS (do read his answer in full):

Regarding critical bugs: in our definition, any bug that results in unrecoverable backup produced, or production data corruption. Only one such bug is reported on v7 so far (in 1 month), and it has a very small scope. Nevertheless, the hotfix is already available. We document critical bugs in our support KB, and there is a dedicated Veeam forum sticky too.

Any other bugs, we don’t normally differentiate between them. ALL issues our customers come to support are hotfixed (unless there is an easy workaround, or extremely minor). The hotfix is provided to a customer, and included in the patch release that we do once every few months (kind of
service pack
). At this time, we have about 60-70 change sets included in the upcoming patch, however not all of those are
bug fixes
– part of those are enhancements in the new functionality based on the first feedback.

 

Read the full post in my blog:

Veeam reclassified critical VBR7 bugs into non-critical | VBSCS

]]>915Sun, 27 Oct 2013 17:46:38 +0000Symantec Backup Exec 2012 bug report: ‘BE2012 was the horror’https://www.edugeek.net/blogs/entry/914-symantec-backup-exec-2012-bug-report-%E2%80%98be2012-was-the-horror%E2%80%99/I will not go as far as calling Symantec names like other bloggers do, for example‘The Great Yellow Peril’, none of the name-calling in this post is by me, it all is from various blogs and forum posts and is indicated as such.

I use lots of software and all solutions have bugs. Before I try something new, especially in a critical area like backup, I’d like to read what people say about it. In my previous posts you can see the problems that I and many other people found with new VBR7 (Veeam Backup & Replication 7). One of the alternatives to this product is Symantec Backup Exec 2012. I made a research of what people say about it, trying to determine if it is a stable product. My findings prove that this product has major flaws and many problems. Here are some examples:

Backup Exec 2012 SQL agent brings SQL server 2005 to a crawl

- this is new version, but it crashes and support doesn’t help

https://www-secure.symantec.com/connect/forums/backup-exec-2012-crashes-system-bug

- system slows down when BE is working (not good)

There is a huge post on SpiceWorks that sums up user experience with BE2012:

Has anyone looked at Backup Exec 2012 yet? - Spiceworks

You can read it yourself, I’ll just say that BE2012 was not the best release for Symantec...

 

 

Read the full post in my blog:

Symantec Backup Exec 2012 bug report: ‘BE2012 was the horror’ | VBSCS

]]>914Sun, 27 Oct 2013 17:40:04 +0000