Video Screencast Help

PureDisk cause to netbackup`s 48 error

Created: 28 Nov 2012 • Updated: 28 Nov 2012 | 1 comment

 

Hello,

Optimized duplications from Production Storage server to DR storage server via SLP fail with status 84, but backups to both Storage Pools complete successfully. 

 

Job Details:

21/11/2011 14:22:51 - Critical bpdm(pid=5672) sts_copy_extent failed: error 2060029 authorization failure 
21/11/2011 14:22:51 - Critical bpdm(pid=5672) image copy failed: error 2060029: authorization failure 
21/11/2011 14:22:51 - Error bpdm(pid=5672) cannot copy image from disk, bytesCopied = 18446744073709551615 
21/11/2011 14:22:51 - Critical bpdm(pid=5672) sts_close_handle failed: 2060022 software error 
21/11/2011 14:23:00 - Info pdmedia01(pid=5672) StorageServer=PureDisk:pdrnbpd0a; Report=PDDO Stats for (pdpd0a): scanned: 2 KB, stream rate: 0.00 MB/sec, CR sent: 0 KB, dedup: 100.0%, cache hits: 0 (0.0%)

 

At the same time i saw that in one of Puredisk`s nodes (SPC)  the Q-Process faild and after rerun he dont starting.

 By this site i followed to this page:

http://www.symantec.com/business/support/index?page=content&id=TECH175441

and I saw that in pdwfe.log this error:  Cannot create PDDO Task (id: 51000) job, Storagepool FULL

so by the site that i worte here, i clear the /var/log (was 70%) and restart the pd.

the duplicate run ok, but the q-process still doesnt work on SPC node. (on SPA and SPB work fine).

after 12 hours the problem happend again and the duplicate again faild with 48 error, the /var/log is ok by the way (40% each node).

anyone can help?  out pd ver is 6.6.3

 

Comments 1 CommentJump to latest comment

f25's picture

Hi,

1. 6.6.3 in general has some issues with self-cleanup and 6.6.3 was even "rolled-back". 6.6.3a version was released few moments later. So it would be best if you had in your /opt/pdinstall/applied the following:
apply-NB_PDE_6.6.3a.sh (*if you started with 6.6.3a it may not be here)
apply-NB_PDE_6.6.3_ET2657689-bundle_v6.sh
The ET2657689-bundle_v6 has some cumulative fixes to 6.6.3.

2. Try this semi-script to asses proper size utilisation:
# /opt/pdcr/bin/crcontrol --dsstat | head -n 4 | tail -n 3
# df -h | grep S

It may happen that your Content Router report 40% storage usage but has a lot of empty containers, still using the storage space. If that's the case run this when not much is happening (not during CR Queue Proccessing or backup window):
# /opt/pdcr/bin/crcontrol --compactstart 0 0 1
When it completes the CR and volume utilisation should not be differing more than 1%.
 

3. What is your storage layout? Do you use one "/Storage" volume for all or have separate CR sotrage? Please share output of those two if you still need help:
# df -h
# /opt/pdcr/bin/crcontrol --dsstat

4. Manual cleanup of any directories is like asking for troubles...

5. NetBackup 7.1.0.4 is the minimal NetBackup version that will properly expire PDDO images on the PureDisk storage pool. You can also try limiting the I/O streams per disk pool.

Have a nice weekend!