NDMP Notify Mover halted: Internal Error. NDMP Log Message: Mover encountered internal read error BEWSNdmpMover: Switching state ACTIVE => HALTED ndmpError = 7, internal_error = 258, mover_halt_reason = INTERNAL_ERROR BEWSNdmpMover: ProcessReadRequest returned error 258 If I look at the log created by the BE Debug Monitor I find: NDMP Log Message: Mover encountered internal read error. NDMP Log Message: RESTORE: Mon Dec 5 16:22:35 2011 : We have read 747313 KB from the backup. When I look at the NDMP log that is within the BE Job log I see: Network is via an HP Procurve Gigabit switch. Ran the job and it got as far as 786GB before failing. So for example i put 8 tapes into the Autoloader, did a quick erase on all the tapes. Tape Drive: HP StorageWorks 1/8 Ultrium 960 Autoloader. Our filers are NetApp devices running OnTap v7.3.5.1 and we are using NDMP to backup. Backup Software: Symantec Backup Exec 2010 R3. Our media server is running Win2008 64bit Standard. To work around the issue, we can need to use T-SQL from Management Studio.Whenever I try to restore a file from tape I get following error:įinal error: 0xe000130a - The NDMP server returned a restore error. If you run the "RESTORE HEADERONLY" command from T-SQL, you can see that it takes several minutes to complete which is much longer than the 20-second timeout for GUI. This timeout is to prevent these dialog boxes from hanging forever when there is no tape present in the drive. The timeout will happen on the "Specify Backup" dialog. Right click on a database > Tasks > Restore > Database > From Device > Click on button > Backup Media = TAPE > Add > Select Backup tape > OK > OK. In GUI this fails for large databases due to the fact that certain operations like the below sequence have a built-in timeout of 20 seconds. #Backup exec 2010 restore from tape software#Jump to page: Results 1 to 15 of 20 Enterprise Software Thread, Some Backup Exec 2010 R2 questions in Technical This was all installed and setup when I took over the network, annual renewals are fairly cheap so Im happy. Step 5: Perform the actual restore operation. Some Backup Exec 2010 R2 questions Latest Threads. Step 4: Obtain the list of files present in the backup set/media. Step 3: Fetch the backup header (This can take time depending on the size of the backup and backup media/device). Step 2: Fetch details about the backup that we are trying to restore. These are the steps that take place in the background when the restore is performed in GUI, RESTORE HEADERONLY is terminating abnormally. Disk storage is a location on a locally attached internal hard drive, a USB device, a FireWire device, or a network-attached storage device to which you can back up data. LAN backup and recovery: A centralized backup server (Backup Exec server) runs the backup software and backs up other servers (backup clients) by using software agents.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |