

I want to say Sonarr has a regex renaming feature, but I may just be making that up as I’m not looking at my instance right now. Doing whatever renaming based on a pattern would be preferable during the download phase in order to keep the metadata of each service clean.
Failing that, if you have a predictable list of release group strings you want removed from filenames, a one liner with sed or similar would take care of this. You’d then break the known locations of these files by any service tracking them of course, but they will eventually be reindexed.



First: there is no cheap way to back this amount of data up. AWS Glacier would be about $200/mo, PLUS bandwidth transfer charges, which would be something like $500. R2 would be about $750/mo, no transfer charges. So assume that most companies with some sort of whacky, competing product would be billed by either of these companies with you as a consumer, and you can figure out how this is the baseline of what you’ll be getting charged from them.
50TB of what? If it’s just readily available stuff you can download again, skip backing that up. Only keep personal effects, and see how much you can reduce this number by.