Backup failed: Invalid repository type.. Vizioncore.vRanger.Facade.Repositories.CIFSRepositoryDTO (4032510)

Backup failed: Invalid repository type.. Vizioncore.vRanger.Facade.Repositories.CIFSRepositoryDTO

This issue occurs after upgrade to Ranger 6.1.0. Only customers, that created restore from manifest (RFM) job in 4.2.3.1 (year 2010) or prior and gradually upgraded Ranger installation all the way to 6.1, are affected.

Every time restore from manifest (RFM) job is configured, a special hidden CIFS repo (type 4) is created in Ranger DB. Apparently Description column must match some defined pattern.

Expected: Manifest: \\<host_IP>\<share_name>\<relative_path>\<some_SP>.Manifest.metadata
In affected DBs column looks differently, e.g.: Manifest: \\<host_IP>\<share_name>\<relative_path>
Description column for some reason was truncated to 100 chars durig upgrade to 4.2.3.1. In 4.5.0.1 it is back to 'max' again. Thus customers that started using Ranger (and RFM jobs) from 4.5 should not see this issue.

Below is simple SELECT command to find repos not matching expected pattern.

USE vRangerPro
SELECT * FROM Repository
WHERE RepositoryTypeId = 4 AND
Description NOT LIKE  'Manifest: \\%.Manifest.metadata'

There are 2 workarounds at the moment:
1. Description column for RFM repos can be 'normalized' - filled with some fake data matching expected pattern. Definitely restore job, that created this repo, won't work. It is assumed this job is not actual anymore or has been removed (marked as deleted) already.
2. All references to restore jobs can be deleted. That involves 10+ tables. Restore template, restore job/task, RFM repo and corresponding SP will be purged. Side effect is that ALL restore jobs will be gone. Counters in My Job view may dicrease.

Instructions. Run either script using MS SQL Management Studio or sqlcmd (e.g. sqlcmd -S  host\vRangerPro -i  c:\restore_purge.sql)
There is no need to restart Ranger services.