cancel
Showing results for 
Search instead for 
Did you mean: 

Error code 84 when duplication from Puredisk Diskpool a to b

demo4119
Level 6
Partner Accredited Certified

I receiving this error code after i have upgrade NBU master from 6.5.6 to NBU 7.5 with Puredisk 6.6.1 x 2 .

Before the upgrade of netbackup master , the duplication from diskpool a to b is working fine using SLP policy.

please advise.

 

5/15/2013 7:44:30 PM - Info Duplicate(pid=3053) Initiating optimized duplication from @aaaaf to @aaaah     

5/15/2013 7:44:32 PM - Info bpdm(pid=5853) started           

5/15/2013 7:44:32 PM - started process bpdm (5853)

5/15/2013 7:44:33 PM - Info bpdm(pid=5853) requesting nbjm for media        

5/15/2013 7:46:41 PM - Critical bpdm(pid=5853) sts_copy_extent failed: error 2060016 operation not supported     

5/15/2013 7:44:30 PM - Info Duplicate(pid=3053) Initiating optimized duplication from @aaaag to @aaaal     

5/15/2013 7:44:32 PM - Info bpdm(pid=5853) started           

5/15/2013 7:44:32 PM - started process bpdm (5853)

5/15/2013 7:44:33 PM - Info bpdm(pid=5853) requesting nbjm for media        

5/15/2013 7:46:41 PM - Critical bpdm(pid=5853) sts_copy_extent failed: error 2060016 operation not supported     

media write error(84)

1 ACCEPTED SOLUTION

Accepted Solutions

Nicolai
Moderator
Moderator
Partner    VIP   

Found this thread while searching for "error 2060016 operation not supported" error message:

https://www-secure.symantec.com/connect/forums/problem-optimized-duplication-between-two-5020-applia...

View solution in original post

2 REPLIES 2

Nicolai
Moderator
Moderator
Partner    VIP   

Found this thread while searching for "error 2060016 operation not supported" error message:

https://www-secure.symantec.com/connect/forums/problem-optimized-duplication-between-two-5020-applia...

Rusty_Major
Level 4
Partner

I don't work with classic PureDisk, but I do have PDDO appliances. We see this on occasion when the pools go down. Have you checked your pool status?

Did you patch PureDisk? Does the patch have to be committed like on the appliances to allow the pool to accept writes?

Is there something in your config that is now unsupported at this version?

If you've already tried the easy things, then you probably will need to increase logging and go from there.