Backup exec management services could not be started
I am facing issue in Backup exec 2014. When i started backup exec console then it first ask for credentials and then gave an error "Backup exec management services could not be started. Backup exec database is offline, turn it online then restart backup exec services" i re install the backup exec 2014 but still have the same issue. Platform consist of Windows server 2008 R2 standard and also it consist of SQL 2008 which is running by client but Backup exec database use its built in database.Solved22KViews1like14Comments
Medium changer not showing up in device manager
Hello We have a Windows2012 R2 serve with a HP StoreEver MSL2024 autoloaderattached. It was all working ok until it randomly started going offline in Backup Exec 2014. In device manager the Tape drive was showing up as HP Ultrium 5-SCSI SCSI sequential device and the medium change was showing up as "Unknown medium changer". I thought that changing to the HP Ultrium 5 drivers from HP for the autoloader might fix this issue (I should have read more before I did this as I know this is wrong now) but now the tape drive is showing up as Hewlett Packard LTO Ultrium-5 drive and no medium changer shows up at all. I haven't removed the autoloader from BE yet, but it's still showing as offline. How can I first get the right drivers back on to the tape drive (the generic Microsoft ones) and then secondly how can I get the medium changer showing up again? Then how can I get BE detecting the autoloader properly? Thank you!Solved18KViews1like11Comments
Backup Jobs are getting failed with V-79-57344-41488 - Due to one or more errors in \\server\E:, this backup cannot be used for conversion to virtual machines, Simplified Disaster Recovery (SDR), or a complete online restore.
Hello All, We are using Backup Exec 2014 SP2 In a Windows 2012 R2 server as a media server and taking backups of the Clients through Remote agent. Few are windows 2008 server and one of them is Windows 2012 R2 server. The issue started with the Win2012 R2 remote agent while backing up the backup is getting failed for the drives with the above mentioned error.The files are normal flat files. Media Server : Windows 2012 R2 64 bit Remote Agent : Windows 2012 R2 64 bit I have tried to take backup of those problematic folder through WIndows server backup however it got successful in that case. The account which we are using for taking backup is domain user however its been added to remote agents local admin too.But no luck. Would appreciate if any wrokariound or solution can be provided except asking for upgrade it to BE 15 ;) .Solved17KViews0likes10Comments
Backup Exec 2014 - Stuck on 'Discovering Resources'
Small Business Server 2011 - fully patched and freshly rebooted Backup Exec 2014 Small Business Edition - fresh install Set up a Friday full job and a Monday-Thursday differential jobs to a set of USB drives that are rotated. The Friday full job sits on 'Discovering Resources' for HOURS. I started the job almost 7 hours ago and it has not backed up a single byte. There is no one on the server, no open files, nothing going on. Resource monitor is very quiet. Thoughts as to what is going on?Solved17KViews1like7Comments
Backup Exec 2014_TCP error code 10061: no connection could be made because the target machine actively refused
Hi everyone I need some help. I have installed Symantec Backup Exec 2014 on a Windows Server 2012 R2 Std. I have use the local administrator account for the installation and the login. The installation have been quite easy. However, when I start Backup Exec 2014 it always give me an error msg: "Could not connect to net.tcp//[server_name]:50104/BEMService/ServerData. The connection attempt lasted for a time span of 00:00:02.0002511. TCP error code 10061: No connection could be made because the target machine actively refused it [server_ip]:50104." I have found that some users have posted this problem on the forum. I have try to have a look about the solution proposed in the forum. Like creating a new rule in the Firewall setting, I have also disable the firewall. The problem is still there. I have noticed that some services is not started. Unfortunately, I cannot start them. They always give error message like: "Error 1068: The dependancy service or group failed to start". The services are: Backup Exec Remote Agent for Windows Backup Exec Agent for Browser Backup Exec Device & Media Service Backup Exec Job Engine Backup Exec Management Service Backup Exec Server I have try tochange the services execute path using administrative command in windows environment,the problem is still the same. Can someone help me please ... Thanks.Solved15KViews1like6CommentsBackups don't complete - hangs on Active: Running - Backup
Just upgraded from a working install of Backup Exec 2012 to BE2014 14.1 with all update installed. Since upgrading, I have not had a single successful backup. I have deployed the 2014 backup agent to my servers and rebooted them after the install. They now validate as having the latest version of theagentinstalled. The backups will run and appear to backup all of the selections as expected. The issue is the backup job never ends. It just hangs up on "Backing up". Job status indicates "Active: Running - Backup". If I view the job activity, it doesn't seem to be working on any current file or directory. Judging by bytes and file count, I'm pretty sure everything has been backed up, but the job doesn't stop. The job log xml file shows the following: Job server: BACKUPSRV Job name: SRV23.DOMAIN.LOCAL Backup 00014-Full - End of Week Job started: Monday, March 30, 2015 at 4:40:37 PM Job type: Backup Job Log: BEX_BACKUPSRV_04279.xml Job Backup Method: Full Drive and media mount requested: 3/30/2015 4:40:39 PM Drive and media information from media mount: 3/30/2015 4:40:42 PM Drive Name: Synology DS512+ Media Label: B2D014498 Media GUID: {6326d716-216c-493b-a5d8-4eeac38bbb6f} Job Operation - Backup Backup Set Retention Period: 3 Weeks. Compression Type: None Encryption Type: None SRV23.DOMAIN.LOCAL Backup Exec server is running Backup Exec version 14.1.1786.1103 with SP-2,HF-227745. Agent for Windows(SRV23.DOMAIN.LOCAL) is running Backup Exec version 14.1.1786.1103 with SP-2,HF-227745. Snapshot Technology: Started for resource: "\\SRV23.DOMAIN.LOCAL\C:". Snapshot technology used: Symantec Volume Snapshot Provider (VSP) for Windows Server 2000 only. Snapshot Technology: Symantec Volume Snapshot Provider (VSP) snapshot cache file settings for volume "C:" : Initial: 12376 MB. Maximum: 12376 MB. File: "\\?\Volume{dd143455-36c9-11dc-a162-806d6172696f}\Backup Exec AOFO Store\_BEVspCacheFile_1.VSP". Snapshot Technology: Symantec Volume Snapshot Provider (VSP) snapshot settings used: Quiet Time: 5 seconds. Time Out: 2000 seconds. Network control connection is established between 172.22.1.62:62236 <--> 172.22.1.53:10000 Network data connection is established between 172.22.1.62:62331 <--> 172.22.1.53:3450 \\SRV23.DOMAIN.LOCAL\C: Family Name: "Media created 3/30/2015 4:40:39 PM" Backup of "\\SRV23.DOMAIN.LOCAL\C:" Backup set #1 on storage media #1 Backup set description: "" Backup Method: Full - Back up files (using modified time) Backup started on 3/30/2015 at 5:06:53 PM. Backup completed on 3/30/2015 at 5:11:08 PM. Backed up 11495 files in 1321 directories. Processed 1,137,817,834 bytes in 4 minutes and 15 seconds. Throughput rate: 255 MB/min Additionally, cancelling the backup manually (which requires killing the job engine process) results in the Job Status being "Cancelled". It also means the filesfrom the backupdo not show up in the restore list when attempting to restore. I can provide additional logs as needed.Solved14KViews0likes10Comments
Solution for VSS exceptions with VMware guests / VM tools
Hi everyone, We have been experiencing VSS issues with VMware guests in regards to the installed Backup Exec Agent and a previously installed VMware Tools VSS option. Uninstalling the VMware Tools VSS option in various ways including restarts did not fix our issues. If you search the internet for solutions, you find many attempts but no real solution or explanation. One of our admins spend several hours with the Veritas support without a solution, he was about to escalate the issue with them, when we found the root cause and could actually fix our issues. First the steps to solve this: Uninstall the VMware Tools VSS option (no restart will be requiered) Make sure VMware VSS service was deleted If this is not the case, you might need to do so manually and remove additional DLL's etc. as well as restart the system, but this is independent from this solution You might have already done steps 1 and 2 but you still get VSS exceptions from the backup that says you have more than one VSS agent installed: V-79-8192-38331 - The backup has detected that both the VMware VSS Provider and the Symantec VSS Provider have been installed on the virtual machine 'hostname'. However, only one VSS Provider can be used on a virutal machine. You must uninstall the VMware VSS Provider. Now you wonder what causes this and you get stuck You could uninstall the Veritas/Symantec Backup Exec Agent and only back the system up per VMDK You would lose the GRT / granular backup / restore capabilities Check your registry for the following reg key HKLM\System\CurrentControlSet\Services\BeVssProviderConflict If this key exists, but your VMware VSS provider is uninstalled, you need to follow up with step 5 Open a notepad as administrator Open this file in the notepad C:\ProgramData\VMware\VMware Tools\manifest.txt Search for the following two entries: Vcbprovider_2003.installed vcbprovider.installed Make sure both of them are set to FALSE, most likely one of them is TRUE Run a test backup This test backup now should not show the exception anymore The registry key should vanish (refresh/press F5) without you taking action So what happened? You uninstalled the VMware Tools VSS provider, but this manifest file did not get updated. We actually could see that it sometimes does get updated and sometimes does not. This seems to be some kind of issue with the VMware Tools uninstalled/installer. But why this manifest.txt file? As we found out, there scripts that get executed by Symantec/Veritas Backup Exec before the backup. You might find them in two locations, and it seems to depend a bit on the Windows version which script is executed (at which location). You could edit them both and just undo the checks in the scripts, but this wouldn't be correct. It is more correct to update the manifest.txt file. If you want to, you can check the date/time of the manifest.txt file before you change it - you might see it was not updated while you uninstalled the VMware Tools VSS provider (assuming you did only do this and not do additional installs/uninstalls within the VMware Tools / please note as well that this only is true when you still experienced those issues). Now, back to those scripts, you find them here: C:\Windows C:\Program Files\Symantec\Backup Exec\RAWS\VSS Provider The name of the script that matters: pre-freeze-script.bat This script checks several DLLs, registry entries, paths and on Windows 2008 and newer the ProgramData-Path for this specific manifest.txt file and the two entries mentioned. Once you uninstall the VMware VSS provider, and the file did not get updated, you might see this issue and wonder how to solve it. The solution is to simply update it to mirror the uninstallation of the VMware VSS provider (vcbprovider). We double checked this with several installations and could see if the file actually gets updated, those two values are set to FALSE, if it doesn't, at least one of the values remains true, what causes the pre-freeze-script.bat to write the registry key mentioned earlier and therefor causing the issue in the backup - exceptions. If you still have the same issues after updating the manifest.txt, simply check all the DLL's that are mentioned in the script and make sure they don't exist. You might also consider to manually delete the registry-key (it seems to be just a dumy-key) to make sure there is no issue that prevents the script from deleting it. Make sure it does not re-appear after a backup! Otherwise you might still have some DLLs left on your system that cause the script to re-create the registry key. Hope this helps a few of you out there. This was an ongoing issue for a while and I came accross those issues many times ever since Windows 2008. This applies to Windows 2008 R2, Windows 2012, Windows 2012 R2 and pretty sure to Windows 2016 as well. It helped us getting rid of those issues completely and actually not even needing a single restart of the guest VM to solve the issues (removing the VMware VSS provide did not need a restart). Regards Florian RossmarkSolved14KViews2likes10Comments
Exchange 2013 backup fails with Backup Exec 2014
For the past week I've been having failures with my backup of Exchange. I get the errors: V-79-57344-34070 - Snapshot Technology: Initialization failure on: "Microsoft Information Store". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). Snapshot technology error (0xE0008516): The database specified for the snapshot was not backed up because the database was not mounted. All databases are mounted. The VSS list writes are all stable. Not sure what to do again. Any suggestions?Solved13KViews1like10CommentsBE2014 DLM not delete already expired backup sets
Hello, I have upgraded a BE2012 SP4 installation to BE2014. The backups go to a DataDomain DD160 using as a OpenStorage device. There a lot of backup sets which are already have been expired. The DLM of BE2014 seems not deleting already expired backup sets (e.g. from BE2012). For new expired backup sets the deletion works. How can I delete the >1000 expired backup sets?11KViews3likes44CommentsCannot push or otherwise communicate with Backup Exec 2014 Remote Agent for Windows. Receive error: 0xe00086ce - Backup exec cannot connect to the remote computer.
http://www.symantec.com/business/support/index?page=content&id=tech224348 hi people am having this exact problem from the link above i have disabled firewall network connection is now ok i can re-add the server but when i try to push the agent. i get those errors whats the actuall cause of this.Solved11KViews1like16Comments
BE2014 DLM not delete already expired backup sets
Hello, I have upgraded a BE2012 SP4 installation to BE2014. The backups go to a DataDomain DD160 using as a OpenStorage device. There a lot of backup sets which are already have been expired. The DLM of BE2014 seems not deleting already expired backup sets (e.g. from BE2012). For new expired backup sets the deletion works. How can I delete the >1000 expired backup sets?