Backups 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.Solved14KViews0likes10CommentsHow to update Backup Exec Remote Agent For Windows System_
Hi all! I'm excperiencing connecting problems during night becakup to random clients - V-79-57344-65072 "the connection to target system has been lost". I've checked Backup Exec RAWS version at media server as well as on all remote systems - it's 13.0.5204.109. The Backup Exec RAWS version on the media serverin newer than enywhere else - it's 13.0.5204.114. In order to try to resolve this issue I want to update agents first. Is it possible to do it automaticly? The uninstallation process and push install doesn't help - the older version is installed.14KViews1like18CommentsNo easy way of removing backup sets in BE2014
Hello Upgraded from Be2012 to Be2014, and absolutely hate there is no way of manually deleting backup sets. The backup strategy is backup to disk (1 week retention) and immedietly duplicate to tape (4 week retention). The problem I seem to have, is that the expired disk based backup chain thinks the duplicated non expired tape chain is a dependancy, and will not remove itself during the storage grooming process. So the HDD storage is filling up with expired backup chains, that can't be deleted. I would easily remove them manually if I could, but the that functionality has been removed. I will try recreating all the jobs, but its a huge nuisance. Has anyone had the same problem?7.4KViews2likes49CommentsBackup Exec version history
Backup Exec versioning changed from number-based (7,8,9,..) to years-based (2010,2012,..). However, the numbers-based versioning is still there, for example in the database (bedb.dbo.Version). Could you help me fill in the gaps? (marked with question marks below) Seagate Backup Exec 7.2 1998 VERITAS Backup Exec 7.31999 VERITAS Backup Exec 8.0 2000 VERITAS Backup Exec 8.6 2001 VERITAS Backup Exec 9.0 2003 VERITAS Backup Exec 9.12003 VERITAS Backup Exec 10.0 2005 Symantec Backup Exec 10d 2005 Symantec Backup Exec 11d 2006 Symantec Backup Exec 12 2008[4] Symantec Backup Exec 12.5 2008 Symantec Backup Exec 2010 13.0 Symantec Backup Exec 2010 R2 ????? Symantec Backup Exec 2010 R3 ????? Symantec Backup Exec 2012 14.0 Symantec Backup Exec 2014 ????? There should be a version 13.5 somewhere.Solved7.1KViews2likes3CommentsExport and Import Backup Exec Jobs (from 2014 to 15)
Hello. I find this way to export jobs and settings: Get-BEBackupDefinition | Export-BEBackupDefinition > script.ps1 And in this script Powershell ISE marked string 333 as error syntax: [CmdletBinding(DefaultParameterSetName = 'NoSelectionsParameterSet')]- unexpected tocken '[CmdletBinding in expression or statement. Why did this happen? This is first question. And second:to Import i do this: & '<full_path_and_name_of_exported_settings>.ps1' -AgentServer (Get-BEAgentServer "<server_name>") | save-BEBackupdefinition What "server_name" should I insert?Solved6.2KViews0likes10CommentsBE2015 Capacity Edition - BE CAREFUL over license model
Hi, I don't ofter post, but i wanted to share my concerns over the limitations on the licensing model the Capacity Editions versions. Having previously been on BE 2014 SBS, Upon renewing my support , the distributer decided to Cross Grade my license to the new 2015 Capacity Edition Lite License. ( As SBS is not available) After a lot of phone calls, a Poor Licensing Document from Symantec ( Tech229205 ), and finally a tech support case, I can now share the following. Lets assumeyou have a 1TB License Day Backup Job Uncompressed Data Cumulative amount of data backed up 0 - Install BE 2015 0TB 1 Full Backup 750GB 750GB 2 Partial Backup 100GB 850GB 3 Partial Backup 100GB 950GB 4 Partial Backup 100GB 1050GB - JOB FAILS 5 Partial Backup 100GB 1050GB - JOB FAILS 6 Partial Backup 100GB 1050GB - JOB FAILS So the 1TB Capacity limit applies to the Cumulative amount of data that bas been backed-up, and NOT as I thought to the JOB Size ---------- My Question to Technical support---------------------- Please confirm the situation in the following example ( the table above) is correct --------------- official response from technical support-------- Yes you are correct as per the abovescenario which you have mention is correct Note: Backup exec Capacity edition will work based on the uncompressed front-end data of the server , once it crosses 1TB data the backup wouldn't get through The calculation is made on 30 days calculation on successful full backups Full backup are considered on capacity calculation. ---------------------------------------------------------------------- I Hope this helps someone else. Capacity Edition is not for me ! If of course the official technical response is incorrect, then please advise Regards ChrisSolved6.2KViews1like11CommentsUpgrade Bacup Exec 2010 R3 to BE 15
We have license for BE 15 and I need to go from BE 2010 R3 to BE 15 on the same server. Can anyone advise if it possible to do an upgrade between the 2 versions or will I have to build a new server for BE 15 and re-create the jobs etc?Solved6KViews0likes7Commentsinstall failed with error code 1603
Hi, When taking image backups i am getting the particular error. Even the Full Image backups doesnt work. Image Backups-Incremental Image Backups-Daily -- The job failed with the following error: Incremental\\Differential backup methods are not supported for this VM. The backup job failed, since the option 'to fall back to a full backup' was not selected. I logged a case with Symantec support and they said each VM should have an agent installed whether you need to take a GRT backup or just an image backup. Secondly they said all VMs must have hardware version7 inorder to do an incremental backup inorder to allow change block tracking feature within VMware. As a first step I am trying to push the RAWS agent to each VM. While installing agents on some VMs i am getting the following error 'install failed with error code 1603' I checked firewall settings and they are disabled. Thanks!Solved5.5KViews1like4CommentsUnable to connect to vCenter. A communication error occurred.
Hi, I recently upgraded to Backup Exec 2012 from Backup Exec 2010. vCenter version 5. All licensed. WhenI add a servervCenter toBackup Execget the following message: "Unable to connect to "VMVCM::\vCenter\Virtual Center". A communication error occurred." System account is configured to connect to vCenter, under this account I am connected to a vCenterin vSphere Client. But with this account can not add a server vCenter toBackup Exec2012. The account is set up in accordance with Article: http://www.symantec.com/business/support/index?page=content&id=TECH129645 What am I doing wrong? I would like to receive official information about configuring permissions account for vCenter+Backup Exec 2012 Sorry for my English.Solved5.2KViews1like15CommentsSymantec Device Drivers for IBM Tape Drives
Hi I'm running Backup Exec 2010 R3 SP2 w/ hotfix 176937 & 180429 on Windows Server 2008 R2 SP1 x64. The tape drives are IBM Ultrium 4 and 5 drives in a Spectra Logic library, both running Symantec drivers dated 2/12/2008, version 5.1.37.0. When I click on "Update Driver" in Device Manager, it upgraded both to a newer IBM driver dated 2011 but upon library + BE reboot, I notice that both drives have the black "X" mark and are not associated to the tape library list; basically non-functioning. I had to rollback in order get it working again. My gut feeling is BE requires Symantec drivers to work with these drives so... I been searching high and low but cannot find drivers on the Symantec site. Trying to troubleshoot issues and using 3.5 year old drivers does not help my cause... Thanks for the help.Solved4.9KViews1like4Comments