i need some info regarding the disk staging

[anishC5]

Hi All,

I am new to disk staging and storage life cycle policy. In our environment, we have implemented the same only a week back.

While the disk staging is happening smoothly, we are having frequent errors with status code 191. Upon checking the inside log, we find that there is a different error say 82 or 85 and a image name like server-a.abc.com_1342345711. going forward I see another stream which has failed for the same image name with same error. But after that the server name is there but the last ID is changing.

Should I consider that the failing image is lost or has it got converted to some other image name please?

Any ideas?

[Marianne]

Please give us all relevant info about your environment:

Where is backup going to? What kind of disk STU? Advanced? OST? 
Dedicated media server for STU or shared with other media servers?

Duplication destination? Tape? Another disk or OST?

Actual NBU version and patch level on master and media servers?

Please copy all text in Details tab for failed job and post here.

[Nicolai]

 server-a.abc.com_1342345711 - the number is the backup time of the server. You can convert the number  to human time by using the bpdbm command on both Windows & UNIX.

bpdbm -ctime 1342345711

There is a good change that the image that causes 82 and 85 is damaged, but is hard to tell right now. 

Please provide the information Marianne ask for - especially the detailed tab for the failing job.

[anishC5]

07/16/2012 06:03:43 - requesting resource LCM_LAN-BKP_LTO5
07/16/2012 06:03:44 - Info nbrb (pid=603) Limit has been reached for the logical resource LCM_LAN-BKP_LTO5
07/16/2012 09:03:33 - granted resource  LCM_LAN-BKP_LTO5
07/16/2012 09:03:33 - started process RUNCMD (pid=21460)
07/16/2012 09:03:34 - begin Duplicate
07/16/2012 09:03:34 - requesting resource LAN-BKP_LTO5
07/16/2012 09:03:34 - requesting resource @aaaaf
07/16/2012 09:03:34 - reserving resource @aaaaf
07/16/2012 09:03:34 - ended process 0 (pid=21460)
07/16/2012 09:03:36 - awaiting resource LAN-BKP_LTO5. No drives are available.
07/16/2012 09:21:36 - awaiting resource @aaaaf. Waiting for resources.
          Reason: Disk pool is unavailable, Media server: N/A,
          Robot Type(Number): NONE(0), Media ID: @aaaaf, Drive Name: N/A,
          Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A,
          Disk Pool: MED_SVR_A_DISKPOOL01, Disk Volume: H:\
07/16/2012 09:21:45 - awaiting resource LAN-BKP_LTO5. No drives are available.
07/16/2012 09:54:28 - awaiting resource @aaaaf. Waiting for resources.
          Reason: Maximum I/O stream count has been reached for the disk volume., Media server: N/A,
          Robot Type(Number): NONE(0), Media ID: @aaaaf, Drive Name: N/A,
          Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A,
          Disk Pool: MED_SVR_A_DISKPOOL01, Disk Volume: H:\
07/16/2012 09:55:21 - awaiting resource LAN-BKP_LTO5. No drives are available.
07/16/2012 09:56:24 - awaiting resource @aaaaf. Waiting for resources.
          Reason: Maximum I/O stream count has been reached for the disk volume., Media server: N/A,
          Robot Type(Number): NONE(0), Media ID: @aaaaf, Drive Name: N/A,
          Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A,
          Disk Pool: MED_SVR_A_DISKPOOL01, Disk Volume: H:\
07/16/2012 09:57:17 - awaiting resource LAN-BKP_LTO5. No drives are available.
07/16/2012 10:03:15 - awaiting resource LAN-BKP_LTO5. Waiting for resources.
          Reason: Robotic library is down on server, Media server: nbu-not-med1.backup.local,
          Robot Type(Number): TLD(0), Media ID: N/A, Drive Name: N/A,
          Volume Pool: NetBackup, Storage Unit: med1_TLD0_DLT, Drive Scan Host: N/A,
          Disk Pool: N/A, Disk Volume: N/A
07/16/2012 10:03:38 - awaiting resource LAN-BKP_LTO5. No drives are available.
07/16/2012 10:38:26 - awaiting resource @aaaaf. Waiting for resources.
          Reason: Maximum I/O stream count has been reached for the disk volume., Media server: N/A,
          Robot Type(Number): NONE(0), Media ID: @aaaaf, Drive Name: N/A,
          Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A,
          Disk Pool: MED_SVR_A_DISKPOOL01, Disk Volume: H:\
07/16/2012 10:38:51 - awaiting resource LAN-BKP_LTO5. No drives are available.
07/16/2012 10:46:00 - resource @aaaaf reserved
07/16/2012 10:46:00 - granted resource  C00023
07/16/2012 10:46:00 - granted resource  TS3500-F09-R01
07/16/2012 10:46:00 - granted resource  med1_TLD0_DLT
07/16/2012 10:46:00 - granted resource  MediaID=@aaaaf;DiskVolume=H:\;DiskPool=MED_SVR_A_DISKPOOL01;Path=H:\;StorageServer=med-svr-A.backup....
07/16/2012 10:46:01 - Info bptm (pid=13805) start
07/16/2012 10:46:01 - started process bptm (pid=13805)
07/16/2012 10:46:01 - Info bptm (pid=13805) using 262144 data buffer size
07/16/2012 10:46:01 - Info bptm (pid=13805) setting receive network buffer to 262144 bytes
07/16/2012 10:46:01 - Info bptm (pid=13805) using 64 data buffers
07/16/2012 10:46:01 - Info bptm (pid=13805) start backup
07/16/2012 10:46:07 - Info bpdm (pid=9448) started
07/16/2012 10:46:08 - started process bpdm (pid=9448)
07/16/2012 10:46:09 - Info bptm (pid=13805) setting receive network buffer to 262144 bytes
07/16/2012 10:46:09 - Info bptm (pid=13805) backup child process is pid 13818
07/16/2012 10:46:09 - Info bptm (pid=13805) media id C00023 mounted on drive index 30, drivepath /dev/nst28, drivename TH-TS3500-F09-R01, copy 2
07/16/2012 10:46:09 - Info bptm (pid=13805) INF - Waiting for positioning of media id C00023 on server nbu-not-med1.backup.local for writing.
07/16/2012 10:46:12 - Info bpdm (pid=9448) reading backup image
07/16/2012 10:46:12 - Info bpdm (pid=9448) using 30 data buffers
07/16/2012 10:46:12 - Info bpdm (pid=9448) spawning a child process
07/16/2012 10:46:12 - Info bpbrm (pid=9448) child pid: 8676
07/16/2012 10:46:13 - Info bpdm (pid=9448) requesting nbjm for media
07/16/2012 10:46:13 - Info bpdm (pid=8676) started
07/16/2012 10:46:13 - started process bpdm (pid=8676)
07/16/2012 10:46:20 - begin reading
07/16/2012 12:14:33 - Critical bpdm (pid=9448) sts_read_image failed: error 2060017 system call failed
07/16/2012 12:14:33 - Critical bpdm (pid=9448) image read failed: error 2060017: system call failed
07/16/2012 12:14:33 - Error bpdm (pid=9448) cannot read image from disk, Invalid argument
07/16/2012 12:14:34 - Error bptm (pid=13805) media manager terminated by parent process
07/16/2012 12:14:58 - Error bpduplicate (pid=21460) host med-svr-A.backup.com backup id client-server-a.backup.com_1342397121 read failed, media read error (85).
07/16/2012 12:14:58 - Error bpduplicate (pid=21460) Duplicate of backupid client-server-a.backup.com_1342397121 failed, media manager killed by signal (82).
07/16/2012 12:14:58 - Error bpduplicate (pid=21460) Status = no images were successfully processed.
07/16/2012 12:14:58 - end Duplicate; elapsed time 3:11:24
no images were successfully processed  (191)

[anishC5]

The duplication backup is going ot tape. not sure about the kind but looksl ike advanced(not open storage)
NBu version: 7.1.0.2, same on both master andm edia servers

[Nicolai]

What OS are you using ?

This T/N is for Wind2003

http://www.symantec.com/docs/TECH56632

Another T/N

http://www.symantec.com/docs/TECH56511

[anishC5]

HI

Our master server is on redhat linux 5.1

The server which is failing is windows server 2003. Ill refer to the TNs..thanks

[Marianne]

If  "host med-svr-A.backup.com" is W2003, the TNs that Nicolai posted seem very relevant.

Please ensure that the following log folders exist on this media server under <install-path>\veritas\netbackup\logs:
bpbrm bptm bpdm