Orphaned backup files in Dedup Storage folder
Hello Community, I've read through some topics regarding to orphaned .bkf files and how to handle them, but I think my situation is a little bit different and I'd like to ask for some help or guidance where to look further. So we are using a Dedup Storage in order to have more storage space for backups. However we are about to run out of free space so the situation is quite bad. First of all, I started to look up backup sets with old data, but I could not find any relavant information, it seemed OK and I did not understand what is occupying so much space. I went further and started digging in the files. I've found almost 8 TB of data (.BHD and .BIN files) from July 2017 (D:\BackupExecDeduplicationStorageFolder\data) as well as some PostgreSQL log files (D:\BackupExecDeduplicationStorageFolder\log\pddb). Okay, that's a huge amount of data. So I've headed back to Backup Exec admin console and started to look for backups from 2017. I've checked the Job History and I found a very few backups from November 2017 but still no backup which might contain old backup sets from July. I also checked Backup Calendar, maybe that helps me. Nope. Same as Job History. What I would like to know: Am I missing something and looking for old data at the wrong place? How do I know which backup set created those old files? If I have more information about those files, can I safely remove them manually? If have no more information, what could be the worst case if I remove those files manually? Hopefully I've provided enough useful information. If not, I'm happy to help further in order to resolve this case. Thanks, CsabaSolved2.4KViews0likes3Comments