NMM 19.9.0.5.Build.227 SQL VDI restore fails with error 'No stripe objects could be located for '/dbname'

NMM 19.9.0.5.Build.227 SQL VDI restore fails with error:
'No stripe objects could be located for '/dbname' (pid=9308,11-07-2025 15:31:14) D:/views/nw/19.9/nsr/db_apps/bsmsql/rplan.c(1555): Stripe /C1-db02~1 from Stripe Map Missing, Exiting. 151535 11-07-2025 15:31:15 No stripe objects could be located for '/dbname'

- Browse and Retention for the SQL VDI backups is set to 4 weeks
- Full, Cumulative incr and Log only backups are configured
- A full backup is performed on a day followed by Cumulative inc for next few days
- Restore from a cumulative incr backup is attempted for which the dependent Full backup has passed its browse and retention period.
- Save sets for Full backup are still browsable due to dependency on Cumulative incr backups
- Some of the cumulative incr backups in between have crossed their browse and retention periods

mminfo output for the partially expired cumulative incr backup looks like:
Backup1107.001        Data Domain    win19-sql19-c1 4218476226       1 MSSQL:C1-db02~2          11-07-2025 14:47:52     1752225472 cr      11-07-2025 14:57:51      11-08-2025 23:59:59
Backup1107.001        Data Domain    win19-sql19-c1 4201699010       1 MSSQL:C1-db02~1          11-07-2025 14:47:53     1752225473 cr      11-07-2025 14:57:51      11-08-2025 23:59:59
Backup1107.001        Data Domain    win19-sql19-c1 4184921798       1 MSSQL:C1-db02            11-07-2025 14:47:58     1752225478 cb      11-07-2025 14:57:45      11-08-2025 23:59:59
Backup1107.001        Data Domain    win19-sql19-c1 4168144583       1 MSSQL:                   11-07-2025 14:47:59     1752225479 cb      11-07-2025 14:57:45      11-08-2025 23:59:59

Two parent save sets have cb flag while the two child save sets have cr (index entries for these save sets have been purged.

As per NMM SQL design, cumulative incremental backup (with/without strips) was selected to be restored.  NMM iterated through the indexes reading objects information up to last full backup.  
There is no separate linkage maintained between cumulative incremental backup to last full backup. 

Once the full backup is found, then NMM  will ignore cumulative incremental/Log backups in between and restore only selected cumulative incremental backup and last full backup. 
In this particular case, it was not able to found the indexes for cumulative incremental backup (child save sets), hence causing the restore to fail.

Workaround: for similar scenario is to remove the mminfo entries for the partially expired cumulative incr backup using command:

nsrmm -d -P -S 1933473985

Then in  SQL Server client node, Windows start Menu-> EMC Networker -> NMM SQL plug-in -> Database Restore Tab -> Restore windows -> Verify that DB entry (3rd June) is not present. Select the unexpired Cumulative incremental and perform DB restore.