Symptoms
CAS migration from Centera to ECSClip that has been migrated from Centera to ECS cannot be read and throws error: Maximum C-Clip size reached, code: -10026Example of the failed restore on ECS:
java -jar /home/filepool/bin/CenteraExerciser.jar -address xx.xx.xx.xx?casuser.pea -order ro -clipfile file
Starting restore of clips and blobs to cluster...
FPClip::CheckCDFSizeEstimate()<FPTag::BlobWrite(stream,2)<FPTag_BlobWrite(-,-,0)
com.filepool.fplibrary.FPLibraryException: Maximum C-Clip size reached
at com.filepool.fplibrary.FPTag.BlobWrite(Unknown Source)
at com.filepool.fplibrary.FPTag.BlobWrite(Unknown Source)
at com.emc.centera.apiengine.core.CenteraSDK.storeRAW(CenteraSDK.java:2150)
at com.emc.centera.centeraexerciser.utils.RawOpenThread.run(RawOpenThread.java:215)
ERROR: Writing blob (com.filepool.fplibrary.FPTag@1cd296b.BlobWrite(java.io.FileInputStream@5a7159)) - com.filepool.fplibrary.FPLibraryException: Maximum C-Clip size reached, code: -10026 [Thread-1] CenteraSDK.java:2169 at 2019-05-07 17:41:06,757
**** RawOpen(s) finished ****
Test has finished with 1 errors
Test failed
Cause
Centera cannot migrate clips over 100 MB to the ECS.This is by design, it is CAS SDK behavior which stops taking additional tags once CDF crosses 100 MB. Although a raw-read is successful on the Centera, the file read on ECS fails.
Resolution
The clip must be directly written from the application to the Centera and then migrated once more to ECS. This generates a new clip ID.The new clip must be updated on customer application database. It may have to be stored with previous clip ID which can cause read errors.
