Duplication issue

[raffl]

Need some exprt help!

Using Master/media all on 2008 with NBU7.5.0.4

I had my duplication runig fine using SLP but now we have connected one more library with one more media server. This is new media server and was not part of initiat dupliactions using SLP.

I am trying to do tape to tape duplication but it is going to pending request. It still look for the other media server from where it got duplicated initially. If I do the movedb of tape to new media server it works but i have to do tape to tape duplication for 100 tapes and movedb for 100 tapes will take time and I don't want to use it. Alos if I am duplication from tape to tape why it looking for that emdia server.Please help  duplicate this data.

[raffl]

even after movedb the duplication runs for couple of bytes and fails.Shows below msg

12/20/2012 11:13:07 AM - Error bptm(pid=557) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_sun_D7, No media in drive. (1112)  
12/20/2012 11:16:57 AM - Error bptm(pid=557) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_sun_D7, No media in drive. (1112)  

pls help

[RamNagalla]

hi,

when you say you have configured the new media server, did you change the existing SLP to make use of the new meida server and Storage unit?

if that is the case did you check the vertions of SLP and make the modifications?

please run nbstl -L -all_versions

and check the desired SLP versions, and make sure your change in SLP is reflecting in all versions of particular SLP.

you can provide the command output and old and new media server and stoarge unit info to verifiy by us.

[raffl]

No i didn't, actualy i just want to run tape to tpae dupltion from that media server.Cant i do it

[RamNagalla]

so how you are trying to to taht tape to tape duplication? 

could you expline it?

[raffl]

from teh catalog section, i kee getting the error while duplication plse suggest

12/20/2012 11:13:07 AM - Error bptm(pid=557) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_sun_D7, No media in drive. (1112)  
12/20/2012 11:16:57 AM - Error bptm(pid=557) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_sun_D7, No media in drive. (1112)

[Marianne]

You need to post full bptm log on the media server as File attachment.

.... why it looking for that media server ....

because tape is assigned to that media server who wrote the backup.
Duplications in SLP as well as cmd can be configured with 'altreadhost'.
Another option is to do movedb with '-allvolumes'.

[raffl]

Thanks Marianne, your answer is promising. I am haveing 100 tapes  should i do movedb or altreadhost. Also how to do altreadhost?

Tried couple of tapes wioth movddb but the duplication writes a samall amount and fails

08:22:17.165 [3880.3868] <16> really_tpunmount: error unloading media, TpErrno = Robot operation failed
08:22:17.165 [3880.3868] <2> openNTDevice: config_path: {2,0,1,0}, serial_num: HU184642Z2
08:22:17.165 [3880.3868] <2> get_drive_path: SCSI coordinates {2,0,1,0}, dos_path \\.\Tape1, pnp_path \\?\scsi#sequential&ven_hp&prod_ultrium_4-scsi&rev_h58s#5&37adb7ad&0&000100#{53f5630b-b6bf-11d0-94f2...}
08:22:17.165 [3880.3868] <2> check_serial_num: serial number match for drive with SCSI coordinates {2,0,1,0}, dos_path \\.\Tape1, drive serial number HU184642Z2, expected serial number HU184642Z2
08:22:17.180 [3880.3868] <2> process_tapealert: TapeAlert returned 0x20000000 0x00000100 (from tapealert_and_release)
08:22:17.180 [3880.3868] <2> send_MDS_msg: DEVICE_STATUS 1 30857287 media50.usa.xl *NULL* 0 SUN_D9 2000479 TAPE_ALERT 536870912 256
08:22:17.180 [3880.3868] <2> log_media_error: successfully wrote to error file - 12/22/12 08:22:17  -1 TAPE_ALERT SUN_D9 0x20000000 0x00000100
08:22:17.196 [3880.3868] <2> ConnectionCache::connectAndCache: Acquiring new connection for host master20.usa.xl, query type 1
08:22:17.196 [3880.3868] <2> vnet_pbxConnect: pbxConnectEx Succeeded
08:22:17.196 [3880.3868] <2> logconnections: BPDBM CONNECT FROM 20.54.16.23.24217 TO 20.54.16.30.1556 fd = 1200
08:22:17.196 [3880.3868] <8> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2
08:22:17.243 [3880.3868] <2> db_end: Need to collect reply
08:22:17.243 [3880.3868] <8> process_tapealert: TapeAlert Code: 0x03, Type: Warning, Flag: HARD ERROR, from drive  (index -1), Media Id
08:22:17.243 [3880.3868] <2> ConnectionCache::connectAndCache: Acquiring new connection for host master20.usa.xl, query type 1
08:22:17.243 [3880.3868] <2> vnet_pbxConnect: pbxConnectEx Succeeded
08:22:17.243 [3880.3868] <2> logconnections: BPDBM CONNECT FROM 20.54.16.23.24218 TO 20.54.16.30.1556 fd = 1204
08:22:17.243 [3880.3868] <8> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2
08:22:17.290 [3880.3868] <2> db_end: Need to collect reply
08:22:17.290 [3880.3868] <16> process_tapealert: TapeAlert Code: 0x38, Type: Critical, Flag: UNREC. UNLOAD FAILURE, from drive  (index -1), Media Id
08:22:17.305 [3880.3868] <2> tapealert_and_release: report_attr, fl1 0x00000001, fl2 0x00000000
08:22:17.305 [3880.3868] <2> tapealert_and_release: SCSI RELEASE
08:22:17.305 [3880.3868] <2> drivename_unlock: unlocked
08:22:17.305 [3880.3868] <2> drivename_close: Called for file SUN_D9
08:22:17.321 [3880.3868] <2> main: Sending [EXIT STATUS 174] to NBJM
08:22:17.321 [3880.3868] <2> bptm: EXITING with status 174 <----------
08:23:06.791 [5816.6076] <2> write_data: write of 262144 bytes indicated only 0 bytes were written, err = 1112
08:23:06.791 [5816.6076] <2> ConnectionCache::connectAndCache: Acquiring new connection for host master20.usa.xl, query type 1
08:23:06.791 [5816.6076] <2> vnet_pbxConnect: pbxConnectEx Succeeded
08:23:06.791 [5816.6076] <2> logconnections: BPDBM CONNECT FROM 20.54.16.23.24226 TO 20.54.16.30.1556 fd = 1240
08:23:06.791 [5816.6076] <8> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2
08:23:06.838 [5816.6076] <2> db_end: Need to collect reply
08:23:06.853 [5816.6076] <4> write_data: WriteFile failed with: No media in drive. (1112); bytes written = 262144; size = 0
08:23:06.853 [5816.6076] <2> is_possible_recoverable_error: not attempting error recovery, errno = 1112
08:23:06.853 [5816.6076] <2> ConnectionCache::connectAndCache: Acquiring new connection for host master20.usa.xl, query type 1
08:23:06.853 [5816.6076] <2> vnet_pbxConnect: pbxConnectEx Succeeded
08:23:06.853 [5816.6076] <2> logconnections: BPDBM CONNECT FROM 20.54.16.23.24227 TO 20.54.16.30.1556 fd = 1252
08:23:06.853 [5816.6076] <8> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2
08:23:06.900 [5816.6076] <2> db_end: Need to collect reply
08:23:06.900 [5816.6076] <16> write_data: cannot write image to media id B20932, drive index 11, No media in drive.
08:23:06.900 [5816.6076] <2> send_MDS_msg: DEVICE_STATUS 1 30854321 media50.usa.xl B20932 4000881 SUN_D4 2000492 WRITE_ERROR 0 0
08:23:06.916 [5816.6076] <2> log_media_error: successfully wrote to error file - 12/22/12 08:23:06 B20932 11 WRITE_ERROR SUN_D4
08:23:06.931 [5816.6076] <4> write_backup: Calling close_all_ft_pipes
08:23:06.931 [5816.6076] <2> check_error_history: just tpunmount: called from bptm line 19386, EXIT_Status = 84
08:23:06.931 [5816.6076] <2> io_close: closing Y:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_SUN_D4, from bptm.c.16437
08:23:06.931 [5816.6076] <2> drivename_write: Called with mode 1

Also Veritas\NetBackup\db\media\error has got lot of OPEN_ERROR,POSITION_ERROR and WRITE_ERROR.

The robtest works fine. Please help .

[raffl]

my reply is gone to administrator for moderation? Why I can't post

[raffl]

please help!

[RamNagalla]

hi,

could you expline us, how your starting the duplication jobs, source and destination tape drive info..

robots info.. ?

[Yasuhisa_Ishika]

Please check log if your tape library and your OS if any error occured. There are some errors suggesting HW error or mis-configuration like below.

---
08:22:17.165 [3880.3868] <16> really_tpunmount: error unloading media, TpErrno = Robot operation failed
---
08:22:17.180 [3880.3868] <2> process_tapealert: TapeAlert returned 0x20000000 0x00000100 (from tapealert_and_release)
08:22:17.243 [3880.3868] <8> process_tapealert: TapeAlert Code: 0x03, Type: Warning, Flag: HARD ERROR, from drive  (index -1), Media Id
08:22:17.290 [3880.3868] <16> process_tapealert: TapeAlert Code: 0x38, Type: Critical, Flag: UNREC. UNLOAD FAILURE, from drive  (index -1), Media Id
---
08:23:06.791 [5816.6076] <2> write_data: write of 262144 bytes indicated only 0 bytes were written, err = 1112
08:23:06.853 [5816.6076] <4> write_data: WriteFile failed with: No media in drive. (1112); bytes written = 262144; size = 0

Also check if you can use this library with normal backups.

[Marianne]

Have you tried to do a couple of test backups to new robot?
Perhaps robtests was left open while NBU tried to mount tapes?

The snippets in your post points to something wrong at hardware level.

Please do the following before doing test backups:

Add VERBOSE entry to vm.conf on Media Server.
(In <install-path>\veritas\volmgr)
Restart NBU Device Manager service.

Ensure bptm log folder exists (<install-path>\veritas\netbackup\logs\bptm).

Perform test backups and let us know the result.

Device errors will be logged in Event Viewer System and Application log.
Please save both theses logs as TEXT files and upload them as File attachments along with bptm log (rename to bptm.txt).