Restore from tape fails with 'TAR Read Error' in Backup Exec 6.5
I am not able to restore from the tape. I was searching for solution and checked most of the settings and thats seems fine here are the failed log details. 15:28:26 10/1/2010: Restore Started 15:28:28 (62.xxx) Restore job id 62 will require 1 image. 15:28:28 (62.xxx) Media id B00500 is needed for the restore. 15:28:41 (62.001) Restoring from image created 7/2/2010 1:36:06 PM 15:28:43 (62.001) INF - If Media id B00500 is not in a robotic library administrative interaction may be required to satisfy this mount request. 15:28:46 (62.001) INF - Waiting for mount of media id B00500 on server miracle-main for reading. 15:28:47 (62.001) INF - TAR STARTED 15:28:48 (62.001) INF - Waiting for positioning of media id B00500 on server miracle-main for reading. 15:30:52 (62.001) INF - Beginning restore from server miracle-main to client miracle-main. 15:30:53 (62.001) FTL - tar file read error 15:30:53 (62.001) INF - TAR EXITING WITH STATUS = 13 15:30:53 (62.001) INF - TAR RESTORED 0 OF 1 FILES SUCCESSFULLY 15:30:53 (62.001) INF - TAR KEPT 0 EXISTING FILES 15:30:53 (62.001) INF - TAR PARTIALLY RESTORED 0 FILES 15:30:53 (62.001) Status of restore from image created 7/2/2010 1:36:06 PM = file read failed 15:30:54 (62.xxx) INF - Status = the restore failed to recover the requested files.2.1KViews0likes6CommentsBMR on Solaris Multipathing
“Until now, BMR supported EMC Powerpath solution. But the demand for native multipath is increasing, which is a platform-independent technique. To cater to this demand, support for native multipath is added in BMR 7.5 for the Linux platform.” BMR supports only EMC Powerpath solution. BMR does not Support for Native multipathing on Solaris. Question is: When will SYMANTEC Netbackup start support for Solaris Multipathing? A big deploymment was done, and the backup solution was the Netbackup 7.5 but now we came at the point that BMR does not support Solaris Multipathing. in such situation, Customer is surviving and big question mark on BMR Solaris Multipathing.839Views0likes3Commentsnetapp backup is failing with error 84 and showing message "FREEZING media id XXXXX, too many data blocks written, check tape/driver block size configuration"
One netapp volume(NDMP) backup is failng with error 84 and in details logs it is showing the message " FREEZING media id XXXXX, too many data blocks written, check tape/driver block size configuration" we are using netbackup 7.0.1.2 (OS-Solaris10).795Views0likes3Comments