Thanks for your reply.

To the best of my knowledge, none of the files (mainly media) have suffered bit rot, but I have a new NAS since the prior one was old and one drive failed - thank you Raid 1! However, if you visit forums (e.g. Reddit), pretty much everyone will tell you to use BTRFS. But, based upon your explanation, CloudBerry would save me because I would notice that a new version was backed up, which would alert me to a problem (since I almost never modify these files).

Thanks for the reply. I am using v. 6.2.5.91 and update frequently, so I was using 6.1+ before I had this problem. Should I submit a ticket or try something else?

Thanks for your post, but when you say "You can even do that right now by renaming CBB_Prefix folder...", I am not sure how to do that because the actual prefix name is not shown in the Backup Storage tab of CBB. Do I need to use CloudBerry Explorer to rename it?

As I indicated before, my backups are running fine. I have no problems with CBB on the new PC and the backups picked up exactly where they left off. I don't have any issues with CBB. I am just trying to figure out if the names of the existing backup prefixes can be changed (as a matter of convenience) without running entirely new backups.

Thanks.

Thanks for the reply, although I am a little confused. I already continued the backup on my new PC, which is what the first part of the article is about. The second part is about changing the drive letter, if necessary, on the new PC, although it wasn't necessary for me.

Are you saying that I can rename the backup prefixes by using CloudBerry Explorer?

Have you enabled ransomware protection? It comes nack if you disable this option. — ds2

You're right. I disabled ransomware protection and the delete files option returned, but when I tested it by enabling ransomware protection again, adding a file locally, running the backup, deleting the file, and then running the backup again, the file was still in my cloud storage. It seems like you now either have ransomware protection enabled or have the ability to remove files which were deleted locally. Am I missing something or is this a bug?

It sounds like the default Lifecycle Policy setting (if enabled/applied) is in fact confusing. I have one backup set to transition to Glacier in 0 days (so straight to Glacier) and my other backup set to transition to S3-IA after 30 days (which is the minimum), so I think I am fine, but the changes in the upcoming release will be appreciated.

Thanks!

"Resolved" status means that the records in your local database have been corrected according to the info that consistency check was able to acquire from storage. — Matt

Thanks for your reply, but could you please clarify what you mean. My local database (the actual files on my NAS) have not been changed - they're still there. So, are you really saying that if the Backup History shows that the files were successfully uploaded, the files are there and just ignore Consistency Check for Glacier?

I knew going in that Glacier had limitations, but I just want to confirm that my files are in fact there... Would it make sense to try to view them with Cloudberry Explorer or is that going to basically work the same as Cloudberry Backup's Backup Storage tab?