Optimized duplications failing with status 84, "Critical bpdm(pid=5672) image copy failed: error 2060029: authorization failure"
|Article:TECH175441|||||Created: 2011-11-25|||||Updated: 2012-07-28|||||Article URL http://www.symantec.com/docs/TECH175441|
Optimized duplications from Production Storage server to DR storage server via SLP fail with status 84, but backups to both Storage Pools complete successfully.
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%)
2 PDDO pools with Puredisk 18.104.22.168 EEB20 installed
The Source PureDisk Storage Pool was flagged as full due to /var/log being 100% full as a result no PDDO tasks could be created to execute the duplication. This could be seen in the /Storage/log/pdwfe.log:
Mon Nov 21 2011 00:22:39.601769 CRIT (1074796864): Cannot create PDDO Task (id: 51000) job, Storagepool FULL
Mon Nov 21 2011 00:22:39.634757 ERROR (1074796864): Return error event: Cannot create PDDO Task (id: 51000) job, Storagepool FULL
Resolved the issue with /var/log being 100% full (partition was only 4gb) by removing a large logfile and then restarted PureDisk Server Agent (/etc/init.d/puredisk restart pdagent) to re-run the monitor process which would then reset the StoragePool full flag.
Article URL http://www.symantec.com/docs/TECH175441