#Backup exec 16 services failing to stop install#
#Backup exec 16 services failing to stop update#
#Backup exec 16 services failing to stop full#
#Backup exec 16 services failing to stop windows#

There will all ways be percentage of people who donРІР‚в„ўt type mistype product name. If we change search term from backup exec to backupexec we can see that interest in Backup Exec was indeed fading. Most of the companies gained trust in virtualisation, time when it was ok to virtualise Active directory. Interestingly Veeam picked up interest from the market and it began to rise.

Comparing Veeam vs Backup exec, we can see that in year 2006, time of Backup Exec 11d, interest from the market was huge, it kept somehow steady interested until 2009, the time when Veeam was launched. To understand this phenomenon, letРІР‚в„ўs take a look at Google trends. Why did this happen?Р’В How come that market leader lost a customer? And I guess we were not the only one. We found Veeam, did a test, liked what we saw and moved away from Backup exec. You were not able to group jobs and the way product worked was so different that was not humane. Job monitor was gone and multi-server job feature was non existing.

All the jobs that we had were gone and logic for tape backup was 360 degrees away from old РІР‚вЂњ correct way of doing backup to tape. User interface changed 1000%, it was basically a new product, not related to BackupExec at all. But 2012, sigh, it changed a perspective and respect I had for Symantec. Until version 2012, most of upgrades went fine. Symantec provided product videos and they were twitting several times a day success stories and how great is theirР’В latest productР’В . Twitter, Facebook, blogosphere, they were all praising latest and greatest. ForР’В the first time, I noticed enormous marketingР’В push and extent of online campaigns. I received mail to my inbox in the morning, that Symantec just released version 2012. We compared several solutions and said hey letРІР‚в„ўs do some testing and compare products available. BackupExec was not an option as it had horrible support for VMware backup. We migrated most of the infrastructure from Physical to Virtual. There had to be something better, affordable solution. How long canР’В you afford to be without backup? In my case it was a week. Or your backup works until it decides to stop. For the most part, solution was there.Р’В Imagine having a major incident, your infrastructure borked, you try to restore and nothing. Technician never got back to you and you had to browse for solution in their forums. When that didnРІР‚в„ўt happen you called Symantec support again, you had to wait, again, polite guyР’В would answer, get the sameР’В information from you and again promise you that technician will get in touch. If you had a problem and called in, you had to wait for a long time for a lady to tell you that technician will call you back.

#Backup exec 16 services failing to stop update#

It also happened thatР’В one patch failed to install, when that happened, Live Update failed to update Backup ExecР’В with remaining patches. SometimesР’В it was not possible to continue with patch installation. You could be updating for anР’В hour or even more, if you were lucky and got an update that borked something.

#Backup exec 16 services failing to stop install#

When you installed Backup Exec you had to spend a while to download and install all the patches / Service Packs. I donРІР‚в„ўt know why, but every time Symantec released a hefty service pack I was trembling if update will bork installation or not. What are your intended backup destinations? If you have anything 'optional' connected, you may want to disconnect it during troubleshooting to help isolate issues.But, itРІР‚в„ўs not all roses, you see, there were also problems. Using a domain account is certainly the best way to go when you want the BE server to interact with other servers, but it isn't needed to get services started locally.Р”В®ven if things (sources/targets) aren't configured in BE yet, the Device and Media Service does some exploring of your server to see what devices are out there. Since this is a fresh install, maybe it is just that something wonky happened during the install, so you may want to try and un-install, reboot and re-install of BEР”Р‡or the issue you see, I don't think that the servioce account matters.

#Backup exec 16 services failing to stop full#

You may need to open a tech support case for full log analysis.

Look for errors or issues in SGmon or tracer.

Use BE Service manager to start the BE services.

start SGmon.exe and enable logging for pvlsvr.

#Backup exec 16 services failing to stop windows#

check Windows Device Manager for any issues.

Once the server is booted and BE services are stell stopped: This allows you to torubleshoot BE separate from the server booting. I would use the BE Service manager (servicesmgr.exe, or another method) to set the BE services to manual. Larry, the backup exec is just now installed and I ve not been able to successfully log into the backup exec and hence no storage is created or added at this point