Symptom
The following errors will be displayed in the SIDBprune and CVMA logs when updating a file on Hitachi Content Platform storage during pruning.
SIDBprune.log
CIndexFile::Close:2429 Unable to close the index file, error=0xEC02AC4C:{CCloudFile::Close(995)} + {CVBaseRemoteFile::GetLastMMErrorCode(392)/MM.44108-Error = 44108}
Cannot close the index file, error [0xEC02AC4C:{CIndexFile<struct SSfileContainerIndexEntry,&char const * const g_szSFileIndexHdrMagic>::Close(2430)} + {CCloudFile::Close(995)} + {CVBaseRemoteFile::GetLastMMErrorCode(392)/MM.44108-Error = 44108}]
CVMA.log
### [DEVICE_IO] 0000: PUT /cvbackup/6FKAHP_12.11.2017_04.19/CV_MAGNETIC/V_XXXX/CHUNK_XXXXX/SFILE_CONTAINER.idx.FOLDER/0 HTTP/1.1
### [DEVICE_IO] 006e: Host: service_host.address
### [DEVICE_IO] 00a7: User-Agent: APN/1.0 CVLT/1.1 CVRF/2.0
### [DEVICE_IO] 00ce: Accept: */*
### [DEVICE_IO] 00db: Cookie:
### [DEVICE_IO] 0126: Content-Length: 296
### [DEVICE_IO] 013b: Content-Type: binary/octet-stream
### [DEVICE_IO] 015e: Content-MD5:
### [DEVICE_IO] 0185: Expect: 100-continue
### [DEVICE_IO] 019b:
### [DEVICE_IO] <= Recv header, 23 bytes (0x17)
### [DEVICE_IO] 0000: HTTP/1.1 409 Conflict
Resolution:
Versioning must be turned on in the cloud storage and retention must be set to 0 days for pruning. By default, the Hitachi Content Platform cloud server will act like a WORM device and without versioning the content files cannot be updated.