![move symantec backup exec 2014 to another server move symantec backup exec 2014 to another server](https://www.doitfixit.com/wp-content/uploads/2014/11/Unable%20to%20establish%20trust_www.doitfixit.com%20(4).jpg)
Of course by new set of features, Tan is probably referring to 2010 features that got stripped out of 2012. “With a set of new product features built from this feedback, Backup Exec 2014 will help our customers and partners overcome key backup and recovery challenges such as reducing costs, complexity, and improving the backup and recovery of virtual server environments.” “To ensure that Backup Exec 2014 would be a backup and recovery solution that would meet the increasingly demanding needs of Singapore enterprises, Symantec sourced the collective feedback of approximately 3,700 customers and partners worldwide who participated in a beta program,” said Tan Yuh Woei, Country Director, Singapore, Symantec. Featuring improved performance, increased visibility, simplified management, and support for the latest operating systems and applications* Backup Exec 2014 is a faster, stronger** backup solution than previous versions. Symantec (NASDAQ:SYMC) today announced the availability of Backup Exec 2014 which delivers powerful, flexible, and easy-to-use backup and recovery to protect virtual, physical and hybrid infrastructures. I usually have fun with these press releases when spin masters use every conceivable adjective to flower an announcement without backing up claims (most times). After all, it took the company no more than two years, the ouster of two CEOs Enrique Salem and Steve Bennett, and a 19 percent dip in the company’s stock price, to finally roll out Backup Exec 2014 – purportedly bringing back with it features that users lamented were unwittingly removed by the vendor with the 2012 version. To see most of the 228 comments against BE 2012, you only need to Ĭertainly Symantec learned its lesson. The grouping of servers prior to creating new jobs really doesn't help much, as you cannot fine-tune the selection lists until you back out and edit each job separately! Job history is a nightmare!" PCTEamAdmin: "Instead of having 3 jobs run, I now have 36 to seperately manage. Mark McFarlane: "I would go from 2-3 backup jobs currently to more than 30 backup jobs.no way Im upgrading.I mentioned this during beta testing and was politely told – it's much better in the new server-centric model.not in my environment it isn't!"
![move symantec backup exec 2014 to another server move symantec backup exec 2014 to another server](http://www.testlabs.se/blog/wp-content/uploads/2011/07/062111_0851_Installandc2.png)
I spent weekends and nights trying to make it all working again and i'm still unable to have all my backup working." Josefino: "It's a complete nightmare at my company. James Avery: "I have entirely enough to do during my week's work without having to climb a nonsensical learning curve for a product that I've used for years, which the designers thereof have decided to 'improve'."
#Move symantec backup exec 2014 to another server update
Advice to others who thinking of an update to BE2012, DON'T do it it suckZZZ! Here is one lost customer!!" Guten: "The new BE 2012 totally destroyed my jobs and now I have been working four days to get everything back to normal but no luck installing BE 2010 again, now i have to clean the registry and see if it works. The transition from 2010 R3 to 2012 has been nothing short of nightmarish." Complaints ranged from:īulbous: "Menus are now hidden behind other menus, and everything has a completely counter-intuitive feel."Ĭhristopher Joles: "It really feels like I am clicking more times than I have ever clicked in my life.
![move symantec backup exec 2014 to another server move symantec backup exec 2014 to another server](https://images.sftcdn.net/images/t_app-cover-l,f_auto/p/d2db3f28-96d9-11e6-93c9-00163ed833e7/1055919086/vmware-converter-screenshot.gif)
are there some ndmp logs somewhere on the filer? I am not sure if this is an issue with Backup Exec, ndmp (or something else on the filer) or a problem with the tape library.Don’t fix what ain’t broken! That was the message Symantec learned when it released Symantec Backup Exec 2012 back in February 2012. Once this has happened to all of the drives connected to the filer the only way I have found to unload the tapes from the drives is to reboot the tape library which resets the prevent tape removal flag from the drive so that I can either manually move the tape out using the Remote Management Interface of the tape library or let Backup Exec unload the tape when it tries to load a different one.Īnyone have any suggestions as to why these jobs are failing or some hints on where I can look to investigate the issue, e.g. Sometimes it will leave the tape in the drive and sets the drive to prevent removal of the tape from the drive. I can see that a tape is loaded into the drive but then the job fails.
![move symantec backup exec 2014 to another server move symantec backup exec 2014 to another server](https://content.spiceworksstatic.com/service.community/p/post_attachments/0000156301/52b494dd/attached_file/Untitled.png)
I have always managed to get the job to work but it can take up to about half a dozen tries to get it to work. Most evenings the backup jobs fail with an error of 0xe0008f4 - An unknown error has occurred. I am doing NDMP backups using Symantec Backup Exec to a HP MSL4048 Tape Library connected to my NetApp Filers directly via FC.