Skip to main content
Solved

Please confirm that the 11.28 version contains all of the fixes found in 11.26.


Forum|alt.badge.img+7

Below is the analysis from commvault:

 

- StoreOnce Aux copy failing due to "Unexpected copy parameters. SFileNum [1] != [1] || CcId [2] != [2] || Offset [0] + [71680] != [73728]."
- FR25 MR23 contains the fix for the issue you are seeing.
https://documentation.commvault.com/11.25/assets/service_pack/updates/11_25_23.htm
3395 -- AuxCopy jobs from HPE StoreOnce catalyst libraries as source and destination may fail with Error "Unexpected copy parameters. SFileNum [1] != [1] || CcId [2] != [2] || Offset [610712232] + [378000] != [611279232].
- Customer to install MR23 on source MA.

  • So we decided to upgrade to 11.26 as it is the latest and has all fixes as 11.25.32.
  • But can we wait for 11.28 and upgrade to 11.28.
  • Will it have same bug fixes as that of 11.26.

 

Best answer by Jos Meijer

11.28 is planned for production environments on the 15th of August. Until then it is advised only for technical preview as fixes can still be implemented in an upcoming maintenance release

View original
Did this answer your question?

2 replies

Jos Meijer
Commvault Certified Expert
Forum|alt.badge.img+17
  • Commvault Certified Expert
  • 638 replies
  • Answer
  • July 19, 2022

11.28 is planned for production environments on the 15th of August. Until then it is advised only for technical preview as fixes can still be implemented in an upcoming maintenance release


Damian Andre
Vaulter
Forum|alt.badge.img+23

To expand on this answer, if an issue is discovered and fixed on 11.26 and 11.28 is not yet released, then generally it should be fixed in 11.28 upon release as well.

If the issue is discovered on 11.26 after the release of 11.28, then the fixes will be created on 11.26 and also forward-ported to 11.28 - as a general rule, both should be simultaneously available in the next maintenance release.

There is a small window when 11.28 is ‘locked’ for testing an no further updates are made until testing is complete. This is where updates created before release for another feature release may not be included, but should be available in the first maintenance release.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings