Take the time to understand what your needs are before you make a decision on what software you want.ĭemo each product if you can and call support during the demo.
If your house gets destroyed by fire or flood and you don't have insurance and take the time to understand the insurance you're going to be in a world of hurt. At the end of the day think of it like being a homeowner. Whining about them here won't make Symantec rethink it's licensing (though they should). I cannot reiterate what Bryce said about agents enough. I've had backups that were useless with BE only because I or the person prior to me thought we had the right agent but alas we did not. What has failed in BE is the overly complicated and at times confusing and/or redundant set of configurations needed to make it work. I will say that BE has never, ever failed me (though neither has Veeam in the short time I've used it). What Bryce mentions about agents is very, very critical to implementing a successful BE environment. Without going on a long rant about what I don't like about BE and what I like about Veeam I'll just say if I was 100% Virtual it wouldn't be an issue. I need backup virtual machine (backup exec vray edition) and phisical machine. Since you're new, it's important to learn the difference. Im a new to Symantec BackupExec user and I wounder if some one could. NOTE: "business need" does not necessarily mean "IT preference". Your setup may necessitate a different solution.ĭon't be afraid to use a hybrid solution if it does what your business requires, and don't be afraid to jettison one package in favor of another if you find that also best serves your business need. Storage devices attached to the Backup Exec server contain the media on which backup data is written. The Administration Console can be run directly on a Backup Exec server or from a remote system (using a Backup Exec Remote Administration Console). Pay close attention to the level of backup/restore granularity you require, as not all of BE's agents do the same things and it's not always clear what the best route is in terms of cost vs benefit.įerinstance, I found that installing an individual server agent on each VM was more cost-effective and gave me more granular restore options than using a VMware agent. The Backup Exec Administration Console is the interface to control a Backup Exec server. though the whole "need to run BE on 圆4 to backup Exchange 2010" rather took me by surprise.īE requires various special "agents" to backup various servers. I'm presently using BE 2012 at a client site with a mixed physical/virtual environment. Thank you for your opinions and greetings from Spain. I don´t see any mayor advantage on using both softwares.īut I would greatly appreciate your opinions and experience, because as I said, I'm pretty newbie. I had to learn to use both programs from scratch and now I'm thinking about making all backups with Veeam, as I think it´s more reliable and more easy to use, and it also let me recover individual files from the file servers. Veeam Backup for SQL Server (we don’t have BackupExec SQL agent) and other servers (Terminal Server, VirtualCenter, web server…).Īll backups are going to two NAS, one at the headquarters and another remote, and we have no tape system. BackupExec to backup the file servers and Active Directory database on the domain controllers. I’ve been recently hired as syadmin in a company which has all his servers virtualized with VMware and uses Veeam Backup and Symantec BackupExec as backup software as follows: Although I have little experience I expect to contribute to the community when possible. Thanks.Hi, this is my first post on Spiceworks. Thanks if you guys can help me on this issue. Writer Class Id: ĭoes this issue related to the VSS or Symantec Backup Exec V-Ray unable to backup Hyper-V Cluster CSV volume? I had tried used window backup and restore to do a test backup, it was working fine to backup vm that in csv.Īnyone know what's wrong for my setting? I had log call to Symantec backup and they troubleshoot for my problem over 2 weeks but still no solution for me. This is often caused by incorrect security settings in either the writer or requestor process. Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. Select another snapshot technology, and then run the job again. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology that you selected does not support snap technology for this volume. Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). Snapshot Technology: Initialization failure on :"VRTSRV::\\cluster_name\HYPER-V?HA?VM\vm_name".
Below is the backup exec error code and event viewer error code: When I try to use the backup exec 2012 v-ray (win server 2008) to backup these vm inside csv. I have newly configure a hyper-v failover cluster that build up with two host (win server 2012) and 5 vm (win server 2012).