Sticky

Trending 11.28 (CPR2022E) issues and fixes


Userlevel 7
Badge +18

Hey folks,

As we see a steady stream of adoption for version 11.28 (also known as Commvault Platform Release 2022E), there are a few trending issues we have detected along the way for that we have fixes for. I wanted to summarize those here to make folks aware in case they encounter them post upgrade and to help get your CommCell performing as it should as fast as possible.

 

Update 4/08 - Maintenance Release 11.28.14 resolves all the issues below. You can obtain the latest Maintenance Release here.

 

Issue #1 - “The case of the Unresponsive Commcell Console”

  

CommCell Console UI unresponsive after upgrading to Platform Release 2022E (11.28) or higher

 

This one is caused by having custom shortcuts to the CommCell console. In 11.28 we are leveraging a new release of Java which requires extra parameters to be added to the shortcut. As customer shortcuts can be created outside of the default deployment, Commvault does not update those during upgrade which leads to the condition. Thankfully, the solution is simple - details in the KB above.

In a future update, we will be able to detect this condition and warn the user upon login, avoiding a lot of head scratching.

 

Issue #2 - “The case of the erroneous pruning performance alert”

 

After installing or upgrading to 11.28, you may receive an erroneous alert stating "The system detected an unusual drop in the pruning performance for the following databases in commcell".

 

This anomaly alert gets a bit too excited after installing 11.28 and may send out false alerts that say the pruning performance has degraded. A couple of quick updates from the KB link above should make this one vanish.

 

Issue #3 - “The case of the overprotective ransomware protection”

  

With versions 11.26 or 11.28, if ransomware protection is enabled backups may fail and disk libraries hosted on a UNC path may go offline

 

Okay, well not strictly related to 11.28 (this one is a nuisance on 11.26 too). The ransomware protection feature may prevent access to UNC/SMB mount paths in a storage pool (disk library) or thwart the indexing database from access its files. How rude. Per the KB, this one is also fixed with recent maintenance releases. If symptoms persist, see your doct… err, support specialist!

 


23 replies

Badge +3

Can I delete the contents of the DBUpgrade folder post upgrade? It is still holding the dump files even after 7 days post upgrade. 

Userlevel 7
Badge +16

It might be the case for a temporary period of time. In my case it doesn't contain any data, but we have not performed a feature upgrade recently. So in case this folder by now is still holding a lot of data than I would recommend to up a TR. 

Badge +3

@Onno van den Berg is it normal for DBUpgrade folder to occupy around 56 GB space.

Userlevel 7
Badge +16

My system drive is getting full post upgrade, I have commvault installed there. The DBUpgrade folder under jobresults directory has taken up lot of space. 

@Shahzeb Yes, the jobresults folder is used during the upgrade of the database and will be cleaned automatically. 

Badge +3

My system drive is getting full post upgrade, I have commvault installed there. The DBUpgrade folder under jobresults directory has taken up lot of space. 

Userlevel 7
Badge +23

@Onno van den Berg , do you know if that syslog issue was limited to Linux commserves?  I found CMR 362396 regarding the issue, but not much more.

Curious if @MFasulo has anything further.

@Mike Struening  I have the issue on a windows based commerve

Then that’s not the one 😣  I’ll defer to @MFasulo 

Userlevel 6
Badge +16

@Onno van den Berg , do you know if that syslog issue was limited to Linux commserves?  I found CMR 362396 regarding the issue, but not much more.

Curious if @MFasulo has anything further.

@Mike Struening  I have the issue on a windows based commerve

Userlevel 7
Badge +18

Also, I’m on 28.15

To confirm - in the alert, is it stating the reason as “CommServe Job Records to be Deleted” or some other message? For you this may not be a false positive but may have actually caught something. Is the DDB referenced being used actively?

Well, they started after the initial upgrade to 11.28, so I dont think its a coincidence.  But yes, pretty much all of our dedupe DB pools are reporting “increase in (CommServe Job Records to be Deleted)”

Got it - I’d open a case in this instance as the fix does not appear to be working in your case. I do see another fix in the works where this could be triggered by sealed, corrupt or DDBs with micro-pruning turned off - but that does not sound like your issue.

Userlevel 6
Badge +12

you just beat me @MFasulo! thanks for the update. took some time before the coding started while multiple customers reported it already so I assume non of them openend an official ticket for it.

I cant say for sure on customers reporting.  The form was created over 2 weeks ago.  

Userlevel 7
Badge +16

you just beat me @MFasulo! thanks for the update. took some time before the coding started while multiple customers reported it already so I assume non of them openend an official ticket for it.

Userlevel 6
Badge +12

fix is getting coded right now… once its backported to 11.28 ill provide the MR details

Userlevel 7
Badge +23

@Onno van den Berg , do you know if that syslog issue was limited to Linux commserves?  I found CMR 362396 regarding the issue, but not much more.

Curious if @MFasulo has anything further.

Userlevel 7
Badge +16

@Damian Andre what about that syslog issue that was reported by several users? can't locate a fix in the recent maintenance releases.

Badge +1

Also, I’m on 28.15

To confirm - in the alert, is it stating the reason as “CommServe Job Records to be Deleted” or some other message? For you this may not be a false positive but may have actually caught something. Is the DDB referenced being used actively?

Well, they started after the initial upgrade to 11.28, so I dont think its a coincidence.  But yes, pretty much all of our dedupe DB pools are reporting “increase in (CommServe Job Records to be Deleted)”

Userlevel 7
Badge +18

Also, I’m on 28.15

To confirm - in the alert, is it stating the reason as “CommServe Job Records to be Deleted” or some other message? For you this may not be a false positive but may have actually caught something. Is the DDB referenced being used actively?

Badge +1

Also, I’m on 28.15

Badge +1

Unfortunately, the update to 28.10 for issue #2 didn't work for me.  Still getting the alerts.

 

@joe.f did you also apply the v11SP28_Available_HotFix2107_2108_WinX64\Windowsx64 hotfix?

Ah, reading is fundamental, thought it was one or the other, thank you.

Just checking in, I still get the alerts even after applying both 28.10 and the Hotfix.

Userlevel 7
Badge +16

@Jos Meijer I saw this one coming by a couple of days ago where it was reported as well. 
 

@MFasulo can you share an update on your findings? 

Userlevel 6
Badge +16

Issue #4 Syslog not receiving data

We have noticed that since 2022E there are issues with usage of Syslog, some platforms receive partial data, some receive none.

Have not found a solution yet.

Badge +1

Unfortunately, the update to 28.10 for issue #2 didn't work for me.  Still getting the alerts.

 

@joe.f did you also apply the v11SP28_Available_HotFix2107_2108_WinX64\Windowsx64 hotfix?

Ah, reading is fundamental, thought it was one or the other, thank you.

Userlevel 7
Badge +16

Unfortunately, the update to 28.10 for issue #2 didn't work for me.  Still getting the alerts.

 

@joe.f did you also apply the v11SP28_Available_HotFix2107_2108_WinX64\Windowsx64 hotfix?

Badge +1

Unfortunately, the update to 28.10 for issue #2 didn't work for me.  Still getting the alerts.

Userlevel 7
Badge +16

Thanks for sharing @Damian Andre! Really appreciate this approach to pro-activity reach out to inform customers before upgrading. Speaking of it, customers should preferably still wait until the state of the latest and greatest version changes from Technology Preview to General Availability which is due on August 15. 

Hope we can expect this form of pro-activity towards the future!!

Reply