LTO5 tape is showing incorrect capacity
Hi There, I'm new to this forum, I use Backup Exec 2010 with an IBM LTO5 tape drive and we have three tapes that are showing a capacity of 35.4gb. If I try to use them it does indeed become full after 35.4gb. I've tried a full erase and everything I can think of and they're stuck at this capacity. I know it's only 3 tapes, not the end of the world... But I'm really curious as to what has happened to them. They weren't new, I think they came with the drive and had been opened. Any insight greatly appreciated!971Views0likes6Comments
The job failed with the following error
We have updated BackupExec from 2012 to 2014 and all job are running fine but on a few backup jobs i am receiving following error. In one job i am receiving following error.. Completed status: Failed Final error: 0xe000942a - Backup Exec did not find any resources to include in the backup. Check the backup selections for this job to make sure it includes resources that are available for backup. Final error category: System Errors For additional information regarding this error refer to link V-79-57344-37930 and another job is failing with following error: Completed status: Failed Final error: 0x2000fe07 - FS_NO_MORE Final error category: For additional information regarding this error refer to link V-79-8192-65031 Please help me out in this...Solved5.4KViews3likes3Comments
Backup Exec 2010 Error "There is not enough disk space"
Hello I am running Backup Exec 2010 R3 on Windows Server 2003 R2. For the past 2 weeks, I've hadthe followingrepeated failure message on some backup jobs: Storage device "Windows Full" reported an error on a request to write data to media. Error reported: There is not enough space on the disk. V-79-57344-34034 - An attempt to write data past the end of the media has failed. This and a few other backup jobs are backing up to a 1 TB local disk on the same server on which Backup Exec is running. These backup jobs have been running successfully for the last few years but now lately the backup disk is becoming full and some jobs are failing. No configuration changes have been made. I do see that backups from a 3 or 4 days ago are still present. By deleting them, the jobs continue. I must add that all of these backup jobs were created about 4 years ago by my predecessor and I have newly taken over these responsibilities.Backup Exec is very new to me and I have a few questions: 1. I would assume that the backup jobs where the data is written to harddiskare configured such that older backed files are purged automatically: is this correct? How do I determine this in the backup job's setup? 2. I have checked the Job Setup for each of the different backup jobs and I cannot see anything which indicates that a particular backup job is backing up to a hard disk instead of to a tape. How do I determine whether data is being backed up to hard disk or to tape? 3. I think that Catalogs are part of the backup process to hard disk process. I see that there are files in the ...\Program Files\Symantec\Backup Exec\Catalogs\BackUpServer folder dating back to 2009. Are these old files necessary? I would think that Backup Exec would automatically purge old unnecessary catalog files: is this correct, or do they need tobe purged manually? Or should theynot be purged at all? Thank you for your help. Yes, I know I need to read the user guide but it's over 1200 pages long and I need to get this issue resolved before I focus on training. Best regards, SuzanSolved1.8KViews1like4Comments
Backup SQL Server with SQL Agent
Hi, i want to backup my MS SQL Server 2005 with my BE 11d. The BE SQL Agent is installed an the BE RemoteAgent too. When the BE Job runs to the SQL Server, the RemoteAgent stops and the SQL Debugger popup to the Screen. When i close this popup the BE Job runs to the end, but the SQL Databases are not backuped!! What can i do, to backup my databases?? Thanks JBR728Views0likes2Comments
A snapshot operation required by this job was unsuccessful
Hi folks Got a minor issue that's a little confusing. We're running Backup Exec v12 and have a daily backup that includes flat files, SQL databases and Exchange w/ GRT and AOFO enabled. Each day the backup completes successfully with exceptions. The email notification is as follows: (Server: "<servername>") (Job: "Daily Backup") The job completed successfully. However, the following conditions were encountered: <#> files were skipped. A snapshot operation required by this job was unsuccessful. Check the job log and the Windows Event Viewer for additional information. Note: The backup job was configured to use the Advanced Open File Option. However, files were skipped during backup processing. Please ensure that the Media Server <servername> is properly licensed with the Advanced Open File Option, or that the job is properly targeted for media servers that are licensed with the Advanced Open File Option. If I double click on the Job History entry, a Job History tab opens - there's no Job Log tab - and therefore there's no details on the skipped files, snapshot issue, or AOFO licensing problem. Furthermore, there's nothing in the Windows Event Viewer that's relevant; the only entry has what is already detailed in the email notification. Correct me if I'm wrong, but there really shouldn't be having any AOFO licensing prompts, as it's included in Backup 12, and shouldn't there be a Job Log tab in the Job History dialog? Any help anyone can offer would be appreciated. Cheers, Georgia Message Edited by Georgia on 05-09-2008 08:48 PM3.3KViews0likes5Comments
Avoid Exception Error "Remote Agent not detected" when using NAS as clients
Hi, Server: Backup Exec 2012 Client: NAS Box Issue: Successful completion with Exceptions "Remote Agent Not Detected" In our environment, we are taking backups successfully from NAS boxes. But after the sucessfull completion of the Backup job, there are errors thrown with Exceptions as "Remote Agent not detected". Knowing that the NAS boxes added as a client of File Server Type, which does not have remote agent, why is it checking for a remote Agent, and how to avoid this Exception.Solved2.6KViews0likes4Comments
How can I hide the Backup Exec Remote Agent from the System Tray?
Hi, I'm running v11 and amlooking to hide the Remote Agent from the System Tray. Preferably I'd like to do this fornon-administrators but I'll take whatever I can get. We run a large Terminal Server environment and I would rather my users not have any interaction with the backup processes, agent, agent's tools or anything else. Thanks, JPC0706582Views0likes1CommentBackup Exec 2014 duplicate backup sets without encryption?
Hi, As above really! We are backing up our servers using BE definedpassphrase (256 bit AES encryption) on our LTO5/6 drives. We are going to start supporting an external company and rather than dedicate separate media sets (And tapes)to this company what we want to do is the following: Setup their jobs to append to our tapes using our current encryption key In the extremely unlikely scenario that they want a copy of their backups I do not want to give them our tapes (Just incase they get into our data). So what I want to do is duplicate their backup sets onto an unencrypted tape. When I select a backup set and select the Duplicate option there is an option about encryption which Symantec mentions can be used to encrypt unencrypted backup sets. It also mentions that if a different encryption key is specified only unencrypted data will be encrypted with this key. So I am wondering if I select no encryption will it simply make an encrypted copy, or will it make an unencrypted copy?Solved1.5KViews0likes4Comments
LTO5 tape is showing incorrect capacity
Hi There, I'm new to this forum, I use Backup Exec 2010 with an IBM LTO5 tape drive and we have three tapes that are showing a capacity of 35.4gb. If I try to use them it does indeed become full after 35.4gb. I've tried a full erase and everything I can think of and they're stuck at this capacity. I know it's only 3 tapes, not the end of the world... But I'm really curious as to what has happened to them. They weren't new, I think they came with the drive and had been opened. Any insight greatly appreciated!
