This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Optim to make use of REST API / S3 protocol instead CIFS protocol
The problem statement is below:
OPTIM is unable the read any archive file from HCP device (cifs protocol used) and this has become more frequent for the past two weeks. The archive file written locally can be retrieved without any IO Error.
The Optim archiving process currently writes on HCP device (version 9.3 3.14) that makes use of the cifs protocol. The PROD environment being used is OPTIM 22.214.171.124 64-bit on VM Windows Data Center 2016.
OPTIM is severely under pressure in reading the archive data from HCP, returning an IO Error on all our written archive files.
Example as below:
IO error on \\cifs.hcp01-105w.africa.nedcor.net\Optim_OptimCentera\data\VOLANTE_17032022SEQ25096.AF.
OSIO Error in OSIO_ReadFile called from OSIO_ReadSegmentTrailer The operation
completed successfully. (00000000)DDName = [None] - Filename =
5096.AF - position = 412479
This impacts all the Business areas as well as our daily operations whereby we can only archive the data bit not delete them, because of the IO Error on the input archive file.
Also Business are currently experiencing a poor performance while executing the queries they used successfully the past week.
The work around at the moment is, while waiting for the issue to be resolved (replacing cifs protocol with Rest API / S3 protocol),
to archive data locally (on our F:\ drive size 400GB).
After a series of discussions with the SAN Storage Team for the use of HCP cifs protocol, they strongly recommend that we make use of Rest API / S3 Protocol since the cifs one is made for small volume of data. Hence, it cannot handle the flow. For your record, we've reported this issue in 2020 and below please find the feedback received from IBM Support L3 (Case TS002561160):
IBM do not have the REST API at this time to move data to and from the Hitachi
OPTIM is not going to be using the REST API to write archive files to HCP in the foreseeable future
For this to come to pass, The Request for Enhancement (RFE) has to be logged.
Do not place IBM confidential, company confidential, or personal information into any field.