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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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.