BUG REPORT: NetBackup 6.5 Storage Lifecycle Policy optimized duplications to PDDO (PureDisk Deduplication Option) to PureDisk Remote Office Edition 6.5 fail after 6 hours of running with status 50 'client process aborted'.

Article:TECH64465  |  Created: 2008-01-24  |  Updated: 2009-01-27  |  Article URL http://www.symantec.com/docs/TECH64465
Article Type
Technical Solution

Product(s)

Environment

Issue



BUG REPORT: NetBackup 6.5 Storage Lifecycle Policy optimized duplications to PDDO (PureDisk Deduplication Option) to PureDisk Remote Office Edition 6.5 fail after 6 hours of running with status 50 'client process aborted'.

Error



operation aborted

status 50 client process aborted

Solution



The issue:
NetBackup 6.5 SLP (Storage Lifecycle Policy) optimized duplications to PDDO fail after 6 hours of running.


Troubleshooting:
NetBackup administration console Activity Monitor 'Detailed Status' for a failed SLP duplication from one will display a 6 hour difference between 'begin writing' and 'operation aborted', ending in status 50 'client process aborted':

 
8/7/2008 5:20:31 PM - Info Duplicate(pid=3588) Initiating optimized duplication
from @aaaad to @aaaas      
8/7/2008 5:20:32 PM - started process bpdm (3916)
8/7/2008 5:21:01 PM - begin writing
8/7/2008 11:23:43 PM - Critical bpdm(pid=3916) sts_copy_extent failed: error
2060014 operation aborted        
8/7/2008 11:23:43 PM - Critical bpdm(pid=3916) image copy failed: error 2060014:
operation aborted      
8/7/2008 11:23:43 PM - Error bpdm(pid=3916) cannot copy image from disk,
bytesCopied = -1      
8/7/2008 11:24:05 PM - Error bpduplicate(pid=3588) host hostname backup id
hostname_1216710249 optimized duplication failed, media write
error (84).  
8/7/2008 11:24:05 PM - Info hostname(pid=3916)
StorageServer=PureDisk:192.168.1.32; Report=PDDO Stats for (192.168.1.32):
scanned: 0 KB, stream rate: 0.00 MB/sec, CR sent: 0 KB, dedup: 0.0%, cache hits:
0 (0.0%)
8/7/2008 11:24:05 PM - Error bpduplicate(pid=3588) Duplicate of backupid
hostname_1216710249 failed, media write error (84).    
8/7/2008 11:24:05 PM - Error bpduplicate(pid=3588) Status = no images were
successfully processed.      
8/7/2008 11:24:05 PM - Error bpduplicate(pid=3588) Continuing with normal
duplication.          
8/7/2008 11:24:05 PM - requesting resource pd_disk_pool2
8/7/2008 11:24:05 PM - requesting resource @aaaad
8/7/2008 11:24:05 PM - reserving resource @aaaad
8/7/2008 11:24:07 PM - awaiting resource pd_disk_pool2
Reason: Drives are in use., Media Server: not_selected,  
Robot Number: 0, Robot Type: NONE, Media ID: N/A, Drive Name: N/A,  
Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A
8/7/2008 11:25:10 PM - reserved resource @aaaad
8/7/2008 11:25:10 PM - granted resource
MediaID=@aaaas;DiskVolume=PureDiskVolume;DiskPool=pd_disk_pool2;Path=PureDiskVolume;StorageServer=hostname;MediaServer=hostname2
8/7/2008 11:25:10 PM - granted resource pd_disk_pool2
8/7/2008 11:25:10 PM - granted resource
MediaID=@aaaad;DiskVolume=PureDiskVolume;DiskPool=pd_disk_pool1;Path=PureDiskVolume;StorageServer=192.168.1.32;MediaServer=hostname
8/7/2008 11:25:11 PM - started process bptm (4944)
8/7/2008 11:26:45 PM - started process bpdm (1656)
8/7/2008 11:26:57 PM - begin reading
client process aborted(50)


Workaround:
Limit the possible size of the Storage Lifecycle Policy duplication via the MAX_KB_SIZE_PER_DUPLICATION_JOB parameter within the <install_path>/netbackup/db/config/LIFECYCLE_PARAMETERS file so that each individual duplication will complete writing in under 6 hours. Please refer to the the Veritas NetBackup (tm) 6.5 Release Notes for UNIX, Linux, and Windows, pages 92-93 in the Related Documents section below for details about this configuration file.


Resolution:
Symantec Corporation is committed to product quality and satisfied customers. Symantec has acknowledged that the above-mentioned issue (ETrack 1383410) is present in the current version(s) of the product(s) mentioned at the end of this article. This issue is currently being considered by Symantec to be addressed in NetBackup 6.5 Release Update 6.5.4. That release will add an OPTDUP_TIMEOUT option to the NetBackup pd.conf PDDO configuration file to allow a timeout to be set to any number of minutes desired.

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.  As future maintenance packs are released, please visit the following link for download and readme information:
http://www.symantec.com/business/support/downloads.jsp?pid=15143


Supplemental Materials

SourceETrack
Value1383410
DescriptionNBU optimized SLP duplications from one PureDisk disk pool to another timeout at 6 hours and revert to 'normal' dup.

SourceError Code
ValueStatus 50
DescriptionClient process aborted.


Legacy ID



312335


Article URL http://www.symantec.com/docs/TECH64465


Terms of use for this information are found in Legal Notices