cancel
Showing results for 
Search instead for 
Did you mean: 

Import of BE tapes in NBU failing

lovee
Level 5

Hello,

Import of BE tapes in NBU failing with below error:

Error bptm (pid=20585) error requesting media, TpErrno = Robot operation failed

and it made drive dowm.

NBU - OS, Linux 6.8 - NBU version 7.6.1.2

NBU - drive configuration HCART3

BE - drive type LTO4

 

Thanks

 

8 REPLIES 8

Thiago_Ribeiro
Moderator
Moderator
Partner    VIP    Accredited

Hi,

Take a look this TN..

DOCUMENTATION: Statement of support for the importing of Backup Exec images in NetBackup 7.x using the Backup Exec Tape Reader - https://www.veritas.com/support/en_US/article.TECH125836

Error bptm (pid=20585) error requesting media, TpErrno = Robot operation failed

 About this error above, I seems a problem with your tape or library..Did you try use the Robtest command?

 

Regards,

 

Thiago

Marianne
Level 6
Partner    VIP    Accredited Certified
I agree with Thiago.
First thing to check is compatibility. Any recent BE version won't work.

If you by any chance want to import a very old BE version that is supported, you need to verify media and tape drive compatibility.
What exactly are your hcart3 drives?
It could be LTO3 or LTO6.

Thanks for the reply.

I checked to import one of LTO5 tape and phase 1 completed but phase 2 partially successful and failed with blow error.

 

07/05/2017 08:59:33 - begin reading

07/05/2017 08:59:33 - Error bpbrm (pid=26278) from client <abc>: read invalid database name. database name size = 0x0, database name offset = 0x0

07/05/2017 08:59:33 - Error bpbrm (pid=26278) from client <abc>: block type = dirb, common block attributes = 0x20080, file system type = 0x0, file system version = 0x0, logical block address (low) = 0x237, logical block address (high) = 0x0, control block identifier = 0x2, string type = 0x2

07/05/2017 08:59:33 - Error bpimport (pid=26023) from host <abc>, read invalid database name. database name size = 0x0, database name offset = 0x0

07/05/2017 08:59:33 - Info mtfrd (pid=26282) done. status: 182

07/05/2017 08:59:33 - Error bpimport (pid=26023) Import of policy engine_yearly, schedule win_full (<backup_id>) failed, tar had an unexpected error.

07/05/2017 08:59:33 - Error bpimport (pid=26023) Status = no images were successfully processed.

07/05/2017 08:59:33 - end Import; elapsed time 0:02:33

07/05/2017 08:59:35 - Error bptm (pid=26290) cannot write data to socket, Connection reset by peer

07/05/2017 08:59:35 - Info bptm (pid=26283) EXITING with status 24 <----------

07/05/2017 08:59:35 - Error bpbrm (pid=26278) could not write EXIT STATUS to OUTSOCK

07/05/2017 08:59:35 - Info mtfrd (pid=26282) done. status: 24: socket write failed

no images were successfully processed (191)

 

Thanks

Genericus
Moderator
Moderator
   VIP   

Also, if the BE tape is encrypted, it flat will not work.

 

NetBackup 10.2.0.1 on Flex 5360, duplicating via SLP to Access 3350, duplicating via SLP to LTO8 in SL8500 via ACSLS

Thiago_Ribeiro
Moderator
Moderator
Partner    VIP    Accredited

Hi,

Did you check the compatibility ? What @Genericus said its true.

DOCUMENTATION: Statement of support for the importing of Backup Exec images in NetBackup 7.x using the Backup Exec Tape Reader - https://www.veritas.com/support/en_US/article.TECH125836

If yes, take a look this article. There is a similar problem to your.

https://vox.veritas.com/t5/NetBackup/Phase-2-import-not-finding-images-from-BackupExec-import/td-p/5...

 

Regards,

 

Thiago

Marianne
Level 6
Partner    VIP    Accredited Certified

@lovee

Please tell us which version of BE you are trying to import and what kind of backup (e.g. File-level, Exchange, SQL, etc.)

BE version is 2010 and backup type is file level.

Marianne
Level 6
Partner    VIP    Accredited Certified

BE2010 is not supported.

As per documentation shared previously, nothing after BE 12 is supported. 
Extract:
There is no support for Backup Exec 12.5 images or later image versions.

If you are unsure about succession of BE versions, have a look at this TN: 
http://www.veritas.com/docs/000116356

Here you will see that BE2010 is newer than BE12.x.