<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Symantec Backup Exec vs Veeam	</title>
	<atom:link href="https://www.itsmdaily.com/symantec-backup-exec-vs-veeam/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.itsmdaily.com/symantec-backup-exec-vs-veeam/</link>
	<description>Product news, reviews and know how for IT Professionals</description>
	<lastBuildDate>Tue, 02 Jul 2019 16:25:59 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Ted Mittelstaedt		</title>
		<link>https://www.itsmdaily.com/symantec-backup-exec-vs-veeam/#comment-3854</link>

		<dc:creator><![CDATA[Ted Mittelstaedt]]></dc:creator>
		<pubDate>Tue, 02 Jul 2019 16:25:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.itsmdaily.com/?p=2627#comment-3854</guid>

					<description><![CDATA[BE 2014 got enough service packs released so it finally stabilized but it still will glitch every once in a while.  Once very few weeks an agent will stop reading files in the middle of a backup and to fix that the server being backed up has to be restarted.   The rule of thumb with BE is to always run a version behind since they follow the model of release a version with a lot of bugs then release service packs that fix them.

The real reason it was so buggy was because Veritas decided to write most of it in .NET and .NET was very very very buggy for many many many years.  That&#039;s why Microsoft kept releasing new versions.

The big problem with veem is it won&#039;t backup the free ESXi you must pay for the commercial version of ESXi.  So the true cost of veem is sky high.  And veem has refused to support the free Vmware probably because there is an under-the-table agreement with them and vmware.

The reality though in windows backup is that ALL windows backup products are based on the VSS api&#039;s that are built into windows and those are almost undocumented, and that system has very few tools from Microsoft that can be used to troubleshoot it.  If that system gets screwed up then your backup program will fail no matter who it comes from including Microsoft.

The main difference between the cheap backup solutions like BE is support.  The super expensive enterprise systems that cost $100k a year have guys on staff with a lot of secret tools and such who can go in and completely clean out problems in your servers.  Their software isn&#039;t structurally any better but their support is top notch.   BE&#039;s support is all in India and it is all geared to being so slow that you give up and uninstall and reinstall their product by the time they get around to getting back to you and doing that fixes 90% of the problems when it goes off the rails.]]></description>
			<content:encoded><![CDATA[<p>BE 2014 got enough service packs released so it finally stabilized but it still will glitch every once in a while.  Once very few weeks an agent will stop reading files in the middle of a backup and to fix that the server being backed up has to be restarted.   The rule of thumb with BE is to always run a version behind since they follow the model of release a version with a lot of bugs then release service packs that fix them.</p>
<p>The real reason it was so buggy was because Veritas decided to write most of it in .NET and .NET was very very very buggy for many many many years.  That&#8217;s why Microsoft kept releasing new versions.</p>
<p>The big problem with veem is it won&#8217;t backup the free ESXi you must pay for the commercial version of ESXi.  So the true cost of veem is sky high.  And veem has refused to support the free Vmware probably because there is an under-the-table agreement with them and vmware.</p>
<p>The reality though in windows backup is that ALL windows backup products are based on the VSS api&#8217;s that are built into windows and those are almost undocumented, and that system has very few tools from Microsoft that can be used to troubleshoot it.  If that system gets screwed up then your backup program will fail no matter who it comes from including Microsoft.</p>
<p>The main difference between the cheap backup solutions like BE is support.  The super expensive enterprise systems that cost $100k a year have guys on staff with a lot of secret tools and such who can go in and completely clean out problems in your servers.  Their software isn&#8217;t structurally any better but their support is top notch.   BE&#8217;s support is all in India and it is all geared to being so slow that you give up and uninstall and reinstall their product by the time they get around to getting back to you and doing that fixes 90% of the problems when it goes off the rails.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: BackupExecGuy		</title>
		<link>https://www.itsmdaily.com/symantec-backup-exec-vs-veeam/#comment-122</link>

		<dc:creator><![CDATA[BackupExecGuy]]></dc:creator>
		<pubDate>Tue, 07 Mar 2017 05:48:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.itsmdaily.com/?p=2627#comment-122</guid>

					<description><![CDATA[Backup Exec Version 15 and 16 does have new OS Support and Virtualization platforms supports from the first day they released and can be proved on paper.

Moreover Veritas Backup Exec is a Unified solution for Physical and Virtual both and both workloads can be managed using a Single Glass of Pane. So the complexity automatically increases as Veeam has different products for Physical and Virtual (Major on Virtual only).

Their technology for Virtual is pretty straight forward only snapshots that’s it and that is the one of the biggest reason why Tape Backup is not supported easily.

Strong Points of BE: 
•	Unified Solution
•	Single glass of Pane for all the operations irrespective of physical, virtual or cloud
•	Global De-duplication across platforms either virtual or physical
•	Instant Recovery for VM&#039;s from Point of Time
•	Licensing approach is also simpler
•	Optimized de-duplication and that’s why we do not need WAN Acceleration as we replicate/duplicate only changed data

Etc etc depends on scenario to scenario and according to requirement…… 


Strong Points of Veeam: 
 Veeam has a feature called Sure backup / Sure replica which in combination with Virtual lab, starts all the servers and makes sure that they are able to run and that services work after the backup. it’s smart as it knows that for Exchange recovery you need working AD. First it starts AD server, once up and running it starts Exchange and it makes sure that both work and can be recovered so you can sleep.

This is the feature now which is really great but again only for Virtual and Too much CPU Intensive which even Veeam states clearly in there guides….

•	SureReplica
•	SureBackup
•	Application Group
•	Virtual Labs]]></description>
			<content:encoded><![CDATA[<p>Backup Exec Version 15 and 16 does have new OS Support and Virtualization platforms supports from the first day they released and can be proved on paper.</p>
<p>Moreover Veritas Backup Exec is a Unified solution for Physical and Virtual both and both workloads can be managed using a Single Glass of Pane. So the complexity automatically increases as Veeam has different products for Physical and Virtual (Major on Virtual only).</p>
<p>Their technology for Virtual is pretty straight forward only snapshots that’s it and that is the one of the biggest reason why Tape Backup is not supported easily.</p>
<p>Strong Points of BE:<br />
•	Unified Solution<br />
•	Single glass of Pane for all the operations irrespective of physical, virtual or cloud<br />
•	Global De-duplication across platforms either virtual or physical<br />
•	Instant Recovery for VM&#8217;s from Point of Time<br />
•	Licensing approach is also simpler<br />
•	Optimized de-duplication and that’s why we do not need WAN Acceleration as we replicate/duplicate only changed data</p>
<p>Etc etc depends on scenario to scenario and according to requirement…… </p>
<p>Strong Points of Veeam:<br />
 Veeam has a feature called Sure backup / Sure replica which in combination with Virtual lab, starts all the servers and makes sure that they are able to run and that services work after the backup. it’s smart as it knows that for Exchange recovery you need working AD. First it starts AD server, once up and running it starts Exchange and it makes sure that both work and can be recovered so you can sleep.</p>
<p>This is the feature now which is really great but again only for Virtual and Too much CPU Intensive which even Veeam states clearly in there guides….</p>
<p>•	SureReplica<br />
•	SureBackup<br />
•	Application Group<br />
•	Virtual Labs</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: ShadowMV		</title>
		<link>https://www.itsmdaily.com/symantec-backup-exec-vs-veeam/#comment-69</link>

		<dc:creator><![CDATA[ShadowMV]]></dc:creator>
		<pubDate>Thu, 23 Oct 2014 13:56:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.itsmdaily.com/?p=2627#comment-69</guid>

					<description><![CDATA[Thanks Eric for the detailed analysis. I am currently doing my own backup analysis and sifting through dozens of reviews trying to pick the best candidate for our customers. This helped a lot!]]></description>
			<content:encoded><![CDATA[<p>Thanks Eric for the detailed analysis. I am currently doing my own backup analysis and sifting through dozens of reviews trying to pick the best candidate for our customers. This helped a lot!</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
