Catalogue jobs failed - data inconsistent on each tape?? V-79-57344-33994
Hello, i haveto restore an old backup (created with backup exec 10 i guess). For this restore i use Backup Exec 2010 R3 on Server 2008 R2. There are no entries for this backup in the catalog. So i loaded all tapes for this backup (20x LTO4 containing one backup) in my 24-Slot loader and inventorized them. After that i created catalogue jobs for each tape, starting with the first one. After 2 hours and about 800gb data the job on tape 1 failed with the error (translated): V-79-57344-33994 - Data read from media is not consistent. All other tapes failed with the same error. I can browse the data of the first tape and restore some of the items (others have a red cross). All other tapes are not in the catalogue, so i cant browse them. What i tried: * cleaning drive * checking statistic data for all tapes (0 errors) * Under BE Options > catalogue > disabled request all media in a row (translated) * enabled debugging May the first tape be broken? Is there a possibility to check the contents of all other tapes? I'm doing something wrong? Thanks for your help Andreas Debugging log for a catalogue job: [...] skipped loading tape [0984] 11/19/13 12:22:37 [tpfmt] - Current media tape header was written by "NetVault Domain". [0984] 11/19/13 12:22:37 [tpfmt] - OSF: Got tape one during slow cat. Continuing = false. [0984] 11/19/13 12:22:37 [tpfmt] - TpRead( ): [0984] 11/19/13 12:22:37 [tpfmt] - Error = 0 Req = 65536 Got = 65536 [0984] 11/19/13 12:22:37 [tpfmt] - ReadThisSet( cur_fmt=0 ) [0984] 11/19/13 12:22:37 [tpfmt] - Set 1 was written by version 1.0. [0984] 11/19/13 12:22:37 [tpfmt] - F40_MoveNextDBLK: Proceed -- Assuming this is a DBLK header, but we were expecting a stream. [0984] 11/19/13 12:22:37 [tpfmt] - Recalculation of LBAs disabled for slow catalog of set. [0984] 11/19/13 12:22:37 [tpfmt] - OSF: Found first or lowest known set. runningBSnum = 1. bset num = 1. Continuing = false. [0984] 11/19/13 12:22:37 [tpfmt] - ReadThisSet() return=0x00000000 [0984] 11/19/13 12:22:37 [tpfmt] - Current VCB: ID = 4cdbeb8b Seq = 1 Set = 1 [0984] 11/19/13 12:22:37 [tpfmt] - PositionAtSet( ): TF Msg = b [0984] 11/19/13 12:22:37 [tpfmt] - UI Msg = 8002 [0984] 11/19/13 12:22:37 [tpfmt] - HARDWARE COMPRESSION ===> Compression is configurable. [0984] 11/19/13 12:22:37 [tpfmt] - HARDWARE ENCRYPTION ===> Encryption is supported. [0984] 11/19/13 12:22:37 [tpfmt] - GET_DRV_INF: bsize = 32768 [0984] 11/19/13 12:22:37 [tpfmt] - GET_DRV_INF: preferredBlockSize = 65536 [0984] 11/19/13 12:22:37 [tpfmt] - End of TF_OpenSet: Ret_val = 0x00000000 Buffs = 10 HiWater = 0 [0984] 11/19/13 12:22:37 [tpfmt] - TF read xfer time = 0 seconds. [0984] 11/19/13 12:22:37 [tpfmt] - AbortRead( ) [0984] 11/19/13 12:22:37 [tpfmt] - TF_CloseSet [0984] 11/19/13 12:22:37 [tpfmt] - TF_OpenSet( ) [0984] 11/19/13 12:22:37 [tpfmt] - Requested Set: ID = 4cdbeb8b Seq = 1 Set = 2 [0984] 11/19/13 12:22:37 [tpfmt] - Current VCB: ID = 4cdbeb8b Seq = 1 Set = 1 [0984] 11/19/13 12:22:37 [tpfmt] - GotoBckUpSet( desired=2, this=1 ) [0984] 11/19/13 12:22:37 [tpfmt] - state 0, 1 sets to go [0984] 11/19/13 12:22:37 [tpfmt] - state 1, 1 sets to go [0984] 11/19/13 12:22:37 [tpfmt] - MoveNextSet( cur_fmt=0 ) [0984] 11/19/13 12:22:37 [tpfmt] - MoveFileMarks( 1 ) [0984] 11/19/13 12:22:37 [tpfmt] - TpReadEndSet( ): [0744] 11/19/13 12:22:38 [server] - Updating status for: 'Katalogisieren 00031' (0x8 0x0) [0744] 11/19/13 12:22:38 [server] - Status for: 'Katalogisieren 00031' updated [0984] 11/19/13 12:23:16 [tpfmt] - MoveFileMarks( ) return=0x00000000 [0984] 11/19/13 12:23:16 [tpfmt] - MoveNextSet() return=0xE00084CA [0984] 11/19/13 12:23:16 [tpfmt] - GotoBckUpSet( ) return=0xE00084CA [0984] 11/19/13 12:23:16 [tpfmt] - FreeFormatEnv( cur_fmt=0 ) [0984] 11/19/13 12:23:16 [tpfmt] - End of TF_OpenSet: Ret_val = 0xE00084CA Buffs = 10 HiWater = 0 [0984] 11/19/13 12:23:16 [tpfmt] - TF_CloseSet [0984] 11/19/13 12:23:16 [tpfmt] - Error detected [0984] 11/19/13 12:23:16 [tpfmt] - FreeFormatEnv( cur_fmt=65535 ) [0984] 11/19/13 12:23:16 [tpfmt] - Setting rewind flag to true for older device. This will likely degrade the performance of the current job. [...] skipped unloading tapeSolved2.4KViews0likes4CommentsReady; No idle devices are available
I'm new to Symantec Backup Exec as I've taken over the duties of someone else that left the company. The problem that I'm having is I can't get Backup Exec to backup anything, not to tape, not to a shared drive, etc.. Logically I would have thought the issue was that the previous employee had used his account for all Symantec functions, I was able to change his account information for all the services and the connection to the server. Everything appears to be fine, I'm able to do a Test Run without any problems but when I go to do a backup I don't receive any alerts I just get a message that says "Ready; No Idle devices are available". Same result no matter where I try to backup to. Anyone seen this before, have any suggestions of how I can fix it? We're using Backup Exec 2012 S1a. Thanks28KViews1like11CommentsBE 2012 - After migration, storage pools but no storage devices
Migrated our BE 2012 server using the steps in the article below. We moved from a Win2K8 R2 Enterprise OS to Win2K8 R2Standard OS for licensing reasons. Everything seemed to migrate successfully except for the storage devices which are simply network drives/shares. In the BE console on the new BE server, the storage pools, that were on the old BE server, are there and the properties of the storage pools show the related storage devices. The problem is that the storage devices do not show up as individual devices on the storage tab of the BE console, so I cannot edit the properties or even use them with the migrated backup jobs. I tried renaming the old BE server and taking it offline, then renaming the new BE server to the old BE server name, but I could not log into BE using the old or new name after that. I put the new name back into place so now I'm back at square one again. I thought about just configuring new storage devices with new names but I'm concerned about how that will affect my ability to restore existing backed up data that is on these drives. Ideally, I would like to get some help on how I can get this migrated BE server to recognize the storage devices again. https://support.symantec.com/en_US/article.TECH129826.html Thank You, RA907Views0likes3CommentsThe 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.4KViews3likes3Commentsback up failed
I encountered this problem after the backup was done Completed status: Failed Final error: 0xe0000354 - Consistency check on Exchange objects cannot be performed because Backup Exec cannot find the required component CheckSGFiles.dll. Ensure that the Exchange Management Tools for Exchange Server is installed on the Backup Exec server. Final error category: Resource Errors For additional information regarding this error refer to linkV-79-57344-852I encountered this problem after the backup was done I couldn't find the solution online notethat the backup was done without any problems thanks1.2KViews0likes3CommentsBackup 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.8KViews1like4CommentsUnable to delete managed backup exec server from caso
Hi, I'm unable to delete managed backup exec server from caso server. I think I started to do this in wrong way because I first uninstalled the backup exec server from managed server. Now in caso server I try to delete managed server but I get error. How I can delete managed server from caso in situation where managed backup exec server is allready uninstalled? Br.MattiSolved1.7KViews0likes5CommentsBackup Exec 2012 - LiveUpdate Stuck on SP 1a
Greetings, Every time I start the update using LiveUpdate to SP 1a, within a few seconds for starting the download, it fails with error LU1825 - Update might of gotten corrupted. I have since manually downloaded and installed the update. The issue is I still have the error on Liveupdate for SP 1a. How can I clear out this possible corruption so I can get updates using LiveUpdate again? Thanks, RobbSolved829Views0likes2Comments"the query for ResourceContainer failed" BE2012 - Clean Install
Hi All, just want to share the problem i have with BE 2012. It is a clean fresh installation on clean newly installed Win2008 R2 SP1 (all pre-checks passed fine). After remote push of 2 agents and creation oddedupe folder, the console reports error in lower left corner of the screen saying : "The query for ResourceContainer failed". The result is that nothing is visible inside GUI anyomore (groups, agents, jobs...). Debugging shows : MANAGEME: [03.27.12 15:00:28] [0000] ERROR: Reason: DataAccess DataAccessBEServer QueryResourceContainer: caught an exception:Invalid column name 'finaljobstatus'.. MANAGEME: [03.27.12 15:00:28] [0000] ERROR: Stack: at BackupExec.Management.Components.DataAccess.DataAccessBEServer.QueryResourceContainer(ItemCriteria& queryInfo) I have tried reinstall, removal of installation, deletition of profile, registry keys, deletition of all associated folders and tried a clean install, also i have trye dusing another SQL server as opposed to using SQL express, but always the same error appears (will have to rebuild the server form scratch it seems). Any ideas? Ayone seen this before? Thanks. All the best, KresimirSolved5.8KViews1like13CommentsAvoid 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