Disk Staging Duplications.

[Philip_Brown_2]

Have configured Disk Staging to duplicate data from disk to final destination of tape, however some images from the disk do not duplicate and return error below:

11/14/2008 12:02:14 AM - begin Duplicate
11/14/2008 12:02:25 AM - requesting resource dcnetbackup-hcart2-robot-tld-0
11/14/2008 12:02:26 AM - awaiting resource dcnetbackup-hcart2-robot-tld-0 - No drives are available
11/14/2008 12:38:11 AM - awaiting resource dcnetbackup-hcart2-robot-tld-0 - Maximum job count has been reached for the storage unit
11/14/2008 12:38:16 AM - awaiting resource dcnetbackup-hcart2-robot-tld-0 - No drives are available
11/14/2008 12:17:09 PM - awaiting resource dcnetbackup-hcart2-robot-tld-0
     Reason: Drives are in use., Media Server: dcnetbackup,
     Robot Number: 0, Robot Type: TLD, Media ID: N/A, Drive Name: N/A,
     Volume Pool: NetBackup, Storage Unit: dcnetbackup-hcart2-robot-tld-0, Drive Scan Host: N/A
11/14/2008 12:33:36 PM - awaiting resource dcnetbackup-hcart2-robot-tld-0 - No drives are available
11/14/2008 12:43:30 PM - started process bptm (9476)
11/14/2008 12:43:27 PM - granted resource H143L1
11/14/2008 12:43:27 PM - granted resource HP.ULTRIUM2-SCSI.001
11/14/2008 12:43:27 PM - granted resource dcnetbackup-hcart2-robot-tld-0
11/14/2008 12:43:35 PM - started process bpdm (9688)
11/14/2008 12:43:36 PM - begin reading
11/14/2008 12:43:38 PM - started process bptm (9476)
11/14/2008 12:43:38 PM - mounting H143L1
11/14/2008 1:21:58 PM - Critical bpdm(pid=9688) sts_read_image failed: error 2060017 system call failed     
11/14/2008 1:21:58 PM - Critical bpdm(pid=9688) image read failed: error 2060017: system call failed    
11/14/2008 1:21:58 PM - Error bpdm(pid=9688) cannot read image from disk, Invalid argument     
11/14/2008 1:21:59 PM - Error bpduplicate(pid=7928) host dcnetbackup backup id wps1_1226352110 read failed, media read error (85). 
11/14/2008 1:21:59 PM - Error bpduplicate(pid=7928) host dcnetbackup backupid wps1_1226352110 write failed, media manager killed by signal (82).
11/14/2008 1:22:00 PM - Error bpduplicate(pid=7928) Duplicate of backup id wps1_1226352110 failed, media manager killed by signal (82).
11/14/2008 1:22:00 PM - Error bpduplicate(pid=7928) Status = no images were successfully processed.     
11/14/2008 1:22:01 PM - end Duplicate; elapsed time: 13:19:47
no images were successfully processed(191)컒

Netbackup 6.5 on Windows Server 2003 Enterprise SP2

Apple XServe Raid

Overland Neo 4000 LTO 2 Drives.

Any help would be appreciated.  Thanks.

[Rakesh_Khandelw · Accepted solution]

This technote should help you resolve the issue -

http://support.veritas.com/docs/295563

GENERAL ERROR: Duplication jobs fail with Status Code 191 (no images were successfully processed)" and "image read failed; error 2060017: system call failed" errors

Exact Error Message
Critical bpdm (pid=10992) sts_read_image_failed: error 2060017 system call failed

Critical bpdm (pid=10992) image read failed; error 2060017: system call failed

Error bpdm (pid=10322) cannot read image from disk. Invalid argment.

Details:
Overview:
Duplication jobs fail with Status Code 191 (no images were successfully processed)" and "image read failed; error 2060017: system call failed" errors


Cause:
• More files are open than the memory cache manager can handle. As a result, the cache manager has exhausted the available paged pool memory.

• The backup program has tried to back up a file whose size is larger than the backup API can access on that version of the operating system. This has the same result (that is, the paged pool is exhausted).


Solution:
On the Windows 2003 server in question, 2 Registry Keys (PoolUsageMaximum, PagedPoolSize) may be created to fine-tune how the operating system manages Paged Pool Memory.  For complete details on creating and configuring these registry keys, review Microsoft Knowledge Base Article below:
 http://support.microsoft.com/kb/304101/en-us

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.