BackupExec 2010 dropping tape drive offline
Hi, This is a new topic to re-open the issue discussed here: https://www-secure.symantec.com/connect/forums/tape-drive-goes-offline-second-backup Just to recap on the issue itself: Running BE2010 Trial on Windows Server 2008 R2 x64. Hardware is Dell R710 rack server, connected to a HP Ultrium 1760 LTO4 SAS drive via a Dell PERC 6/E SAS Adaptor card. This is what’s happening: Setup and run a backup job with full verify. I’ve tested up to a 250GB job and it completes fine the first time around. After completion of first job, rerun the same backup job (after tweaking the media overwrite/append etc settings) The job immediately fails, reporting the drive as offline – cannot bring drive back online using BackupExec administrator Close BackupExec administrator, restart BackupExec Device/Media service (which also restarts associated service dependencies). Re-open BackupExec administrator - drive appears to be online again, ready for another job to be kicked off. I’ve completely replaced: Numerous LTO tapes The Dell SAS adaptor that connects the Dell server to the HP rack chassis The HP Rack chassis that houses the 1U internal HP LTO4 Ultrium 1760 SAS drive, SAS adaptor board and all The internal HP LTO Ultrium 1760 drive itself We’ve verified that all above component drivers and firmware are fully up to date. This problem occurs with both Symantec Tape Drive drivers and HP's official LTO4 tape drivers, To me, the following facts suggest that the problem lies with BackupExec itself: After the drive goes offline, a simple restart of the BackupExec services seems to bring it back online again If the drive goes offline, and I stop the BackupExec Device/Media service, I can still access the drive using HP LTT utility, and HP Data Protector Express – only BackupExec detects the drive as offline. We’ve replaced all possible hardware components and the problem still remains This problem only ever occurs with BE, I'm testing with HP Data Proctector Express and MS's Data Protection Manager - all work fine. Luckily, I haven't bought a license for BackupExec yet, however this means I doubt Symantec Support will be willing to spend too much time on it, so I might be forced to go with MS's Data Protection Manager instead if I can't get a resolution soon. Has anyone seen/resolved this issue before? AlistairSolved8.8KViews1like40CommentsRD1000 Unable to Eject after backups complete
Hello all, We're having troubles with Dell RD1000 cartridges using Backup Exec 12 for Windows Servers (Small Business Server). In all 4 cases, this is on systems that had previously been running nightly backups using v11d successfully for months (or even a year) without a hitch. We can back up properly, but we can never eject the cartridges once a backup has been completed. We press the "eject" button on the drive, but the cartridge will not eject. It's totally "locked". This has been tested and confirmed on four unrelated and relatively dissimilar servers at four different locations. We have tried this with both the Internal (SATA) RD1000 drive chassis and have also reproduced the issue on one of our servers using the external USB drive chassis. In all cases, the Dell RD1000 "RDXMon" service (which supposedly aides in ejection) is installed and running fine. In all 4 cases, these drives had been previously successfully used with Backup Exec 11d, and we had done an upgrade installation to v12. The only change to the system was an upgrade to BE 12, along with all available LiveUpdates (3 at the time). One of the servers is a clone (running an Asus server motherboard, external USB RD1000 drive). The remaining 3 servers are Dell PowerEdge 2900 systems using the Internal SATA chassis. At this point, as best I can tell, we have a serious regression in the product and the product is completely unusable on RD1000-equipped systems (again across 4 locations, we have not had a successful backup, through the point of cartridge ejection yet). This is holding off a rollout toourremaining 25 servers (there are about 30 total). I understand that BE cannot "automatically" eject the cartridge as it can with "true" tapes. But I'm not talking about that. I'm referring to being totally unable to manually eject the cartridge (using the eject button on the drive) unless I PHYSICALLY POWER OFF the server and power it back on. Help anyone? I've got a string of clients we're waiting to upgrade here and I cannot in good conscience bring them forward until this issue is resolved. -Dan6.7KViews1like84CommentsMedia mount failed.
Backup Exec 11d Get the following error: Backup- System?State System?State Media mount failed. User canceled a Physical Volume Library operation. V-79-57344-33861 - The media operation was terminated by the user. As far as I can see the whole backup runs and think al data is saved to tape, but assume something goes wrong in verifying data when job is completed. I have reinstalled the drivers of HP C7438A (Internal SCSI) Rebooted the system but no luck. Have updated to the latest patch Version 11.0 Rev. 6235 Have cleaned and tested new tapes. Nothing helps so far, below find the job log. Hope somebody can help me out. André Job Log: BEX_MALKA_03046.xmlJob Log for Backup 070327 Completed status: Canceled, timed out Expand AllCollapse All Job Information Job server: MALKA Job name: Backup 070327 Job started: zaterdag 18 oktober 2008 at 02:34:40 Job type: Backup Job Log: BEX_MALKA_03046.xml Drive and media mount requested: 18-10-08 02:34:41 The media is being retensioned. Device and Media Information Drive and media information from media mount: 18-10-08 02:34:42 Drive Name: HP 1 Media Label: 07082006 Media GUID: {4c28332a-cf19-43dc-8375-662d3ea62bb5} Overwrite Protected Until: 31-12-99 01:00:00 Appendable Until: 31-12-99 01:00:00 Targeted Media Set Name: Media Set 1 All Media Used 07082006 Job Operation - Backup Backup Options Media operation - overwrite. Compression Type: Hardware [if available, otherwise software] Server - MALKA AOFO: Started for resource: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). The following volumes are dependent on resource: "C:" . The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). AOFO: Started for resource: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). The following volumes are dependent on resource: "C:" . The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). Set Information - C: SYSTEM Backup Set Information Family Name: "Media created 18-10-08 02:34:41" Backup of "C: SYSTEM" Backup set #1 on storage media #1 Backup set description: "Backup 070327" Backup Method: Full - Back Up Files - Reset Archive Bit Backup started on 18-10-08 at 02:36:09. Backup completed on 18-10-08 at 02:57:56. Backup Set Summary Backed up 23523 files in 4089 directories. Processed 5.244.724.541 bytes in 21 minutes and 47 seconds. Throughput rate: 230 MB/min Set Information - D: Backup Set Information Family Name: "Media created 18-10-08 02:34:41" Backup of "D: " Backup set #2 on storage media #1 Backup set description: "Backup 070327" Backup Method: Full - Back Up Files - Reset Archive Bit Backup started on 18-10-08 at 02:58:07. Backup completed on 18-10-08 at 03:48:07. Backup Set Summary Backed up 21939 files in 3772 directories. Processed 11.780.626.142 bytes in 50 minutes and 0 seconds. Throughput rate: 225 MB/min Set Information - F: IDE_Local Backup Set Information Family Name: "Media created 18-10-08 02:34:41" Backup of "F: IDE_Local" Backup set #3 on storage media #1 Backup set description: "Backup 070327" Backup Method: Full - Back Up Files - Reset Archive Bit Backup started on 18-10-08 at 03:48:17. Backup completed on 18-10-08 at 03:56:45. Backup Set Summary Backed up 56 files in 48 directories. Processed 985595989 bytes in 8 minutes and 28 seconds. Throughput rate: 111 MB/min Network control connection is established between 127.0.0.1:5379 <--> 127.0.0.1:10000 Network data connection is established between 127.0.0.1:5969 <--> 127.0.0.1:5968 Set Information - \\MALKA\Microsoft Information Store\First Storage Group Backup Set Information Family Name: "Media created 18-10-08 02:34:41" Backup of "\\MALKA\Microsoft Information Store\First Storage Group " Backup set #4 on storage media #1 Backup set description: "Backup 070327" Backup Method: Full - Database & Logs (flush committed logs) Microsoft Exchange Server Agent: Started The option to enable the restore of individual items from the database backup was selected for this backup. Backup started on 18-10-08 at 03:56:58. Backup completed on 18-10-08 at 04:39:37. Backup Set Summary Backed up 2 Exchange Server stores Backed up 2 Exchange Server logs Processed 7.415.878.082 bytes in 42 minutes and 39 seconds. Throughput rate: 166 MB/min Network control connection is established between 127.0.0.1:5379 <--> 127.0.0.1:10000 Network data connection is established between 127.0.0.1:6317 <--> 127.0.0.1:6316 Database Consistency Checks Consistency checking master Consistency Check including Indexes. Consistency check was completed. Consistency checking model Consistency Check including Indexes. Consistency check was completed. Consistency checking msdb Consistency Check including Indexes. Consistency check was completed. Consistency checking STS_Config Consistency Check including Indexes. Consistency check was completed. Consistency checking STS_MALKA_1 Consistency Check including Indexes. Consistency check was completed. Set Information - MALKA\SHAREPOINT Backup Set Information Family Name: "Media created 18-10-08 02:34:41" Backup of "MALKA\SHAREPOINT " Backup set #5 on storage media #1 Backup set description: "Backup 070327" Backup Method: Full - Back up entire database or filegroup Microsoft SQL Server Agent: Started Microsoft SQL Server Agent: On-disk Copy Enabled On Disk Copy Path: MALKA F:\Disaster\SQL_BUP Backup started on 18-10-08 at 04:39:53. Backup Set Detail Information Database Consistency Checks Consistency checking master Consistency Check including Indexes. Consistency check was completed. Consistency checking model Consistency Check including Indexes. Consistency check was completed. Consistency checking msdb Consistency Check including Indexes. Consistency check was completed. Consistency checking STS_Config Consistency Check including Indexes. Consistency check was completed. Consistency checking STS_MALKA_1 Consistency Check including Indexes. Consistency check was completed. Backup completed on 18-10-08 at 04:40:35. Backup Set Summary Backed up 5 databases Processed 45.201.841 bytes in 42 seconds. Throughput rate: 61.6 MB/min Network control connection is established between 127.0.0.1:5379 <--> 127.0.0.1:10000 Network data connection is established between 127.0.0.1:6357 <--> 127.0.0.1:6356 Set Information - \\MALKA\Utility Partition Backup Set Information Family Name: "Media created 18-10-08 02:34:41" Backup of "\\MALKA\Utility Partition " Backup set #6 on storage media #1 Backup set description: "Backup 070327" Backup Method: Full - Back Up Files - Reset Archive Bit Backup started on 18-10-08 at 04:40:47. Backup Set Detail Information The .DR file required for Intelligent Disaster Recovery is created/updated. Backup completed on 18-10-08 at 04:41:29. Backup Set Summary Backed up 1 Utility Partitions Processed 156286213 bytes in 42 seconds. Throughput rate: 213 MB/min Network control connection is established between 127.0.0.1:5379 <--> 127.0.0.1:10000 Network data connection is established between 127.0.0.1:6374 <--> 127.0.0.1:6373 Set Information - Shadow?Copy?Components - VSS Writer File System Backup Set Information Family Name: "Media created 18-10-08 02:34:41" Backup of "Shadow?Copy?Components - VSS Writer File System" Backup set #7 on storage media #1 Backup set description: "Backup 070327" Backup Method: Full - Back Up Files - Reset Archive Bit Backup started on 18-10-08 at 04:41:41. Backup Set Detail Information The .DR file required for Intelligent Disaster Recovery is created/updated. Backup completed on 18-10-08 at 04:42:04. Backup Set Summary Backed up 4 Shadow Copy Writers Backed up 4 Shadow Copy Components Processed 107908432 bytes in 23 seconds. Throughput rate: 268 MB/min Server - MALKA AOFO: Started for resource: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). The following volumes are dependent on resource: "C:" . The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). Set Information - System?State System?State Backup Set Information Family Name: "Media created 18-10-08 02:34:41" Backup of "System?State System?State" Backup set #8 on storage media #1 Backup set description: "Backup 070327" Backup Method: Full - Back Up Files - Reset Archive Bit Backup started on 18-10-08 at 04:42:36. Backup Set Detail Information Drive and media mount requested: 18-10-08 04:47:57 Media mount failed. User canceled a Physical Volume Library operation. V-79-57344-33861 - The media operation was terminated by the user. Backup completed on 18-10-08 at 08:34:44. Backup Set Summary Backed up 7 System State components Processed 827556074 bytes in 3 minutes and 34 seconds. Throughput rate: 221 MB/min Job Completion Status Job ended: zaterdag 18 oktober 2008 at 08:34:44 Completed status: Canceled, timed out The job was automatically canceled because it exceeded the job's maximum configured run time. Errors Click an error below to locate it in the job log Backup- System?State System?StateMedia mount failed. User canceled a Physical Volume Library operation. V-79-57344-33861 - The media operation was terminated by the user.6.5KViews0likes1CommentBlue Screen Caused by virtfile.sys
This post is FYI as this weekend after our LiveUpdate installed a couple of hitfixes onto our Backup Exec server it started to Blue Screen while executing our Backup-To-Disk Jobs for File System, Exchange, Active Directory and VMware, with the following Crash Dump Information. ----- Start Crash Analysis BugCheck 3B, {c0000005, fffffade381a651c, fffffade30fa1a10, 0} Unable to load image \SystemRoot\system32\DRIVERS\VirtFile.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for VirtFile.sys *** ERROR: Module load completed but symbols could not be loaded for VirtFile.sys Probably caused by : VirtFile.sys ( VirtFile+b51c ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffffade381a651c, Address of the exception record for the exception that caused the bugcheck Arg3: fffffade30fa1a10, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: VirtFile+b51c fffffade`381a651c ?? ??? CONTEXT: fffffade30fa1a10 -- (.cxr 0xfffffade30fa1a10) rax=000000006e66744e rbx=fffffade6d5e3c08 rcx=0000000008000000 rdx=fffffade377b3c20 rsi=fffffade6d5e3ac0 rdi=fffffade6dcb6ea8 rip=fffffade381a651c rsp=fffffade30fa2220 rbp=fffffade6dcb6c30 r8=fffffa80001e5800 r9=fffffade30fa2200 r10=fffffa80001e0007 r11=fffffade6d070000 r12=000000001000000c r13=fffffade6d5e3b68 r14=0000000000000000 r15=fffffade6d657010 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 VirtFile+0xb51c: fffffade`381a651c ?? ??? Resetting default scope CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0x3B PROCESS_NAME: REMNTD~1.EXE CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffffa80001e5800 to fffffade381a651c STACK_TEXT: fffffade`30fa2220 fffffa80`001e5800 : fffffade`30fa2270 fffffa80`001e5800 fffffade`30fa2200 fffffade`6dff7100 : VirtFile+0xb51c fffffade`30fa2228 fffffade`30fa2270 : fffffa80`001e5800 fffffade`30fa2200 fffffade`6dff7100 00000000`00000000 : 0xfffffa80`001e5800 fffffade`30fa2230 fffffa80`001e5800 : fffffade`30fa2200 fffffade`6dff7100 00000000`00000000 fffffade`6ce7b010 : 0xfffffade`30fa2270 fffffade`30fa2238 fffffade`30fa2200 : fffffade`6dff7100 00000000`00000000 fffffade`6ce7b010 00000000`00000000 : 0xfffffa80`001e5800 fffffade`30fa2240 fffffade`6dff7100 : 00000000`00000000 fffffade`6ce7b010 00000000`00000000 fffffade`00000000 : 0xfffffade`30fa2200 fffffade`30fa2248 00000000`00000000 : fffffade`6ce7b010 00000000`00000000 fffffade`00000000 00000000`00000000 : 0xfffffade`6dff7100 fffffade`30fa2250 fffffade`6ce7b010 : 00000000`00000000 fffffade`00000000 00000000`00000000 fffffade`6d832350 : 0x0 fffffade`30fa2258 00000000`00000000 : fffffade`00000000 00000000`00000000 fffffade`6d832350 fffff800`c00000bb : 0xfffffade`6ce7b010 fffffade`30fa2260 fffffade`00000000 : 00000000`00000000 fffffade`6d832350 fffff800`c00000bb 00000000`00000000 : 0x0 fffffade`30fa2268 00000000`00000000 : fffffade`6d832350 fffff800`c00000bb 00000000`00000000 fffffa80`001e5800 : 0xfffffade`00000000 fffffade`30fa2270 fffffade`6d832350 : fffff800`c00000bb 00000000`00000000 fffffa80`001e5800 fffffade`6d832380 : 0x0 fffffade`30fa2278 fffff800`c00000bb : 00000000`00000000 fffffa80`001e5800 fffffade`6d832380 00000000`00000000 : 0xfffffade`6d832350 fffffade`30fa2280 00000000`00000000 : fffffa80`001e5800 fffffade`6d832380 00000000`00000000 00000000`00000000 : 0xfffff800`c00000bb fffffade`30fa2288 fffffa80`001e5800 : fffffade`6d832380 00000000`00000000 00000000`00000000 fffffade`37783ee2 : 0x0 fffffade`30fa2290 fffffade`6d832380 : 00000000`00000000 00000000`00000000 fffffade`37783ee2 fffffade`6d5e3b68 : 0xfffffa80`001e5800 fffffade`30fa2298 00000000`00000000 : 00000000`00000000 fffffade`37783ee2 fffffade`6d5e3b68 fffffade`30fa2340 : 0xfffffade`6d832380 fffffade`30fa22a0 00000000`00000000 : fffffade`37783ee2 fffffade`6d5e3b68 fffffade`30fa2340 fffffade`30fa2308 : 0x0 fffffade`30fa22a8 fffffade`37783ee2 : fffffade`6d5e3b68 fffffade`30fa2340 fffffade`30fa2308 00000000`00000000 : 0x0 fffffade`30fa22b0 fffffade`37787160 : fffffade`30fa2408 fffffade`6d657010 fffffade`6d658720 00000000`00000000 : fltmgr!FltpPerformPreCallbacks+0x3e2 fffffade`30fa23a0 fffffade`377a3e07 : fffffade`6d658720 fffffade`6ce7b010 fffffade`6ce7b010 00000000`00000000 : fltmgr!FltpPassThroughInternal+0x40 fffffade`30fa23d0 fffff800`012827c9 : fffffade`6fbcba60 fffff800`01282170 fffffade`30fa2950 fffffade`6d74fcb0 : fltmgr!FltpCreate+0x3a7 fffffade`30fa2460 fffff800`01280164 : fffffade`6fbcba60 fffffade`6fbcba10 fffffade`30fa2790 00000000`00000001 : nt!IopParseDevice+0x1088 fffffade`30fa2610 fffff800`01284887 : 00000000`00000000 fffffade`30fa2780 00000000`00000040 00000000`00000000 : nt!ObpLookupObjectName+0x931 fffffade`30fa2720 fffff800`01291e4d : 00000000`00000000 00000000`00000000 00000000`00000b81 00000000`00000000 : nt!ObOpenObjectByName+0x180 fffffade`30fa2910 fffff800`01298ef7 : fffff700`00081080 fffff700`00081000 fffff680`0000e510 fffffade`41d11c40 : nt!IopCreateFile+0x630 fffffade`30fa2aa0 fffff800`01298d39 : fffff6fb`7da00000 fffffade`30fa2c70 fffffade`6d14d040 fffff800`01052c0f : nt!IoCreateFile+0x12f fffffade`30fa2b80 fffff800`0102e33d : fffff6fb`7dbed000 00000000`00000000 fffffade`6d14d3b0 00000000`00000000 : nt!NtCreateFile+0x69 fffffade`30fa2c00 00000000`77ef0f3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3 00000000`0012e448 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ef0f3a FOLLOWUP_IP: VirtFile+b51c fffffade`381a651c ?? ??? SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: VirtFile+b51c FOLLOWUP_NAME: MachineOwner MODULE_NAME: VirtFile IMAGE_NAME: VirtFile.sys DEBUG_FLR_IMAGE_TIMESTAMP: 48a30145 STACK_COMMAND: .cxr 0xfffffade30fa1a10 ; kb FAILURE_BUCKET_ID: X64_0x3B_VirtFile+b51c BUCKET_ID: X64_0x3B_VirtFile+b51c Followup: MachineOwner --------- 0: kd> lmvm VirtFile start end module name fffffade`3819b000 fffffade`381ab000 VirtFile T (no symbols) Loaded symbol image file: VirtFile.sys Image path: \SystemRoot\system32\DRIVERS\VirtFile.sys Image name: VirtFile.sys Timestamp: Thu Aug 14 01:44:05 2008 (48A30145) CheckSum: 0001673B ImageSize: 00010000 Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0 ----End Crash Analysis We Run Backup Exec 12.5 with SP1 on an IBM x3550 with 16GB RAM, with Windows Server 2003 SP2 x64 as the OS. The version of the virfile.sys that was causingus an issue is "1.0.114.0" and was updated as part of one of the hotfixes, but unfortunately we have been unable to ascertain which hotfix at this stage. The blue screens were prevented by rolling back to the version of virtfile.sys that is available in "C:\Program Files\Symantec\Backup Exec". The version of this file is "1.0.114.125". Once this version of the virtfile.sys was replaced in safe mode all jobs proceeded successfully. Hopefully this information will be of assistance to someone... :) Cya..4.6KViews0likes19CommentsBackup Exec cannot find Tape Drive
Hi I have installed Backup Exec 2010 R3. I have Tandberg SLR7 (scsi). I have attached it to server. In installation procedure it finds that i have i have Tandberg SLR7 and gives the message that "found a driver Tandberg SLR7 and it is not digitally signed by microsoft ,do yoo want to continue ? Continue anyway? and i click yes after backup exec installation , Backup Exec cannot discover device, and it remains in Discovering device in Devices Tab I have restarted Server but again it remains at Discovering device is there any settings that i should do after Backup Exec installation ?Solved3.9KViews0likes4CommentsBackup Exec mark as bad some LTO that are good
Hello, I've a strange problem with my installation of backup exec. I have a new IBMTS3100 (LTO4)libraryconnected (via SAS) with an IBMx3400 (using a dedicated HBASAS - 25R8060). On the x3400 I have a fresh W2k3 64bit installation with Symantec Backup Exec 12.5. Both O.S. and Backup Exec are upgraded to the last version, service pack and patch. I have also installed the symantec driver for the tape and upgrade the firmware of library, tape and HBA to the last release. Everything work correctly, but about once a day the library mark a tape as bad and the Backup Exec stop to write on the tape. If I remove the bad LTO Backup Exec it works again. Today I have removed the fifth "bad" LTO. It seems strange to me that in 10 LTO cartridges (all IBM original) purchased there are already 5 defective. Thinking on an hardware problem I've open a ticket to IBM support.They've analyzed my log andtold me that writing is blocked but can't understand if it's a physical problem on the tape or whether a software issue (BackupExec detects any error in writing and mark cartridges as bad). IBMsend me a tool(ITDT) that write directly on the tape.With this software there isn't any problem.I've tried to write for about 20 hours without any block. Moreover if I try to write on an LTOthatBackupExec has marked as bad ITDT can write on them and after the write process the cartdrige "rises" and work again. Everything makes me think of a question of dialogue between BackupExec and my library. Any idea about? Thank you very much, Fabio GrassoSolved3.5KViews2likes10CommentsDell PowerVault TL4000 - Import/Export/Eject of Tape Media/Magazine will not work!
We have a Dell PowerVault TL4000 with dual LTO-4 Tape Drives--Fibre Channel According to Symantec's latest Hardware Compatibility List for Backup Exec 11/12, Dell's PowerVault TL4000 is on there as supported device. Each library is assigned to a tape drive. Our Host computer: -Quad Core with 2 GB of RAM -QLogic HBA with dual Fibre Channeladapter -500 GB HD -Windows 2003 Standard R2 with SP2 and all latest Windows Update I've tested this without using Backup Exec and the unit is operational just fine (using the Dell Web Utility): -moving tapes from one slot to another slot -tape drive cleaning -library/magazine ejects fine -and all the works After installing Backup Exec 11D and liveupdated with SP2, import/export/eject of tape media and magazine do not work. Period. With Backup Exec, Dell Web Utility cannot eject the magazine. I have to unlock the tape drives in Backup Exec and then shut down all of Backup Exec services so that I can eject the magazine from Dell Web Utility. On the PowerVault TL 4000 console, I cannot eject the I/O station either. I have to unlock the tape drives in Backup Exec, then shut down all of Backup Exec services so that I can eject just the I/O station from the Unit's console. In other words, the only way I can get medias in / out is to: -unlock the tape drives and shut down Backup Exec completely -go to Dell Web Util and unlock the magazines -manually import / export the tapes from the magazine -reinsert the magazine -startup Backup Exec and do Inventory I've called up Dell to troubleshoot this and it was obvious that WITHOUT Backup Exec, the unit works just fine as it should. Dell technician even stated that the problem is in Backup Exec 11 and not the unit. Called up Symantec Tech Support to troubleshoot and after hours of several tests and trials, I can plainly see that the problem is with Backup Exec and not the unit. The issu is being escalated to level 2. Case #: 290-958-414. If anyone else have a Dell PowerVault TL2000 or TL4000 and have Backup Exec v11 or v12 and have the same issue or have found another work around, please let us know in this forum. PS I will be doing another test with BE v12 later on. My gut feeling is going to be the SAME problem as with BE v11 SP2. Message Edited by Kingsley Mok on 03-20-2008 03:39 PM3.1KViews0likes4CommentsAdamm Mover Error: Read Failure! Backup Exec 12
I am running Backup Exec 12 (Rev. 1364) and using an HP LTO 4 Ultrium 1840 tape drive.The server running the backup is running Windows Server 2003 SP2. We keep getting device errors in the application Log when we run backup jobs using harware encryption. I have checked with Symantec and HP documentation and hardware encryption is supported with this tape drive in this version of Backup Exec. The backup job rus completes sucessfully, and test restores from the backup jobs have confirmed that the backup runs sucessfully. I have not been able t find a resolution for the device error in the Symantec Knowledge Base. Anyone have any suggestions? Below is a copy of the error from the application event log n the server running Backup Exec: Event Type:Error Event Source:Backup Exec Event Category:Devices Event ID:33152 Date:4/30/2008 Time:6:31:16 AM User:N/A Computer:SRVMAIN1 Description: Adamm Mover Error: Read Failure! Error = 0xE0008121 Drive = "HP-1840" {93F0C990-7E8E-4E01-ADDD-B06AA513461B} Media = "104" {C931D92F-FDDC-4B11-8CCA-8E5CE4E578EE} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1)2.9KViews0likes6CommentsDevice Manager Sees Superloader 3, Backup Exec 12.5 Does not
I've recently moved my Backup Exec from one server to another. The new server is an HPDL380 G3, running Windows 2003 R2 x32. I installed Backup Exec and successfully moved the data and catalog information from the old server to the new server. The final step was to get the device online and start my backup. Under device manager, it installed the most recent driver from Quantum for my device. However it never shows up in Backup Exec 12.5 as it did for my old server. How can I diagnose this?It is urgent of course as no backup is running now :( The Superloader 3 is an LTO2 drive, a few years old. The BIOSon startup on the new server also regognizes the Superloader to be on the SCSIIDthat Iset it to be on. I can't blame the hardware or the operating system at this point, I hope there is something I'm missing in BE! Please help, KurtSolved2.8KViews0likes21Comments