- #USING SYMANTEC BACKUP EXEC 2010 R3 FOR SQL DATABASE SOFTWARE#
- #USING SYMANTEC BACKUP EXEC 2010 R3 FOR SQL DATABASE LICENSE#
- #USING SYMANTEC BACKUP EXEC 2010 R3 FOR SQL DATABASE FREE#
- #USING SYMANTEC BACKUP EXEC 2010 R3 FOR SQL DATABASE WINDOWS#
Instead, for me Veeam should be focusing on supporting encrypted replication of backups to any other removable media, especially USB for the SMB. And besides it's totally legacy technology superseded by everything Veeam stands for - shown I think nicely by the tapes on display at Bletchley Park and any other computing museum. I'd actually encourage Veeam not to put any kind of tape support in, since once that can has been opened very likely Veeam will gain something of the reputation for poor reliability that has plagued BackupExec and all the other tape backup product vendors.
#USING SYMANTEC BACKUP EXEC 2010 R3 FOR SQL DATABASE SOFTWARE#
I Believe there is going to be a senate inquiry in the parliament about software companies charging Aussies so much more. We couldn't afford this extra hit, so we went for Veeam Standard. In my calculations, it cost around $US320 extra per socket for the Enterprise edition, all up an extra $US2,500 for 8 sockets, just for being Australian! Very unfair IMHO. I have a feeling they charge Aussie customers more than US customers for the product. It would be nice if it could write to tape (not a complaint, just a wish)
#USING SYMANTEC BACKUP EXEC 2010 R3 FOR SQL DATABASE FREE#
Veeam doesn't get away scott free though. They have tried to fix it with BE2012, but some of the most basic things are still hard to find. It has a simple interface (yet has a lot of technology under the hood). BE would fail for us in this circumstance. I can even perform a live migration of a VM while it is being backed up, and Veeam will keep working. From day one of trialling it, it was been rock solid reliable without any failures. You had to run the Altaro front end on a Hyper-V host, and the product didn't support software compression (their answer to that seems to be "turn on NTFS compression on the backup drive"!!). I tried Altaro Hyper-V backup, and found it way too simplistic and limiting.
#USING SYMANTEC BACKUP EXEC 2010 R3 FOR SQL DATABASE LICENSE#
Very greedy IMHO, why not make it one license per server? You need to purchase a separate agent license per SQL database/instance. Read this thread for hundreds of complaints from current customers. BE 2012 is buggy, and they didn't listen to their customers. They never really placed many resources into improving Hyper-V CSV backups, often giving customers the promise of "we haven't forgotten about Hyper-V customers, improvements around the corner" - these promises were lip service.Ģ. We had BE from 2010 onwards, and this behaviour never improved. Tried all the fixes and patches, with only minor improvement. We would change nothing, and BE would randomly fail.
#USING SYMANTEC BACKUP EXEC 2010 R3 FOR SQL DATABASE WINDOWS#
Unreliable backups for a Windows 2000R2 Hyper-V Cluster. We have recently switched from BE2012 to Veeam 6.ġ. To me, this is false advertizement no matter how you look at it - punishable in most countries including US. For example, I can tell you that Symantec document you have linked has multiple false statements, and I will send this link with my comments to our lawyers for further action. not just by sending some skewed bullet list where half of the bullets are irrelevant to you, and other half is wrong. If you'd really like to make real comparison with Veeam, our sales representative will be glad to go over that with you, and explain why Veeam might be a better choice while keeping in mind specifics of your environment and your data protection needs. However, don't read the above as "you can never have this type of information from Veeam". Of course, we do have similar comparisons, but those are internal documents not intended for public distribution - just an internal resource to help our sales understand our strength against specific solutions. The law is in fact working, as we just tried on one other competitor for a start - they had to remove the comparison. Well, may be Symantec has bigger purse to pay their lawyers - we do not. To see which providers are installed, launch Windows Services on the guest machine and confirm one of services from the table above are listed.AdRemSoft wrote:So Symantec can do this and Veeam can't? Once the Backup Exec Remote Agent is installed, thus installing the BE VSS Provider, do NOT re-install the VMware Tools VSS Provider as this will re-create the conflict condition and cause quiesce and/or snapshot errors. The Backup Exec VSS Provider cannot exist in a guest alongside the VMware Snapshot Provider as having both installed on a guest will cause quiesced snapshots to hang the guest and timeout. "When installing the Backup Exec Remote Agent on a guest machine for GRT enabled virtual machine backups, the VMware Snapshot provider is automatically uninstalled and the BE VSS Provider installed (this is why a reboot is required).