Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[CoreyEMTP]

So, before I describe the problem, I'm fully aware that it's something I shouldn't do, and I had never done it before.

I had a batch running of new Redump DATs, and when it got to the Xbox DAT I realized it was unwantedly (but correctly) backing up all the magazines from my NAS to my local slow backup disc. I was in the backup folder at the time, when instead of correctly canceling the run I instead deleted the remaining files from the ROM directory directly. I expected an error, which I got. However, it then deleted all the files in the backup directory as I watched. Like I hinted, it's an unwanted consequence of a stupid maneuver, but I thought worth reporting because of the data loss.

Thanks!

[Roman]

Nothing is removed from the backup folder unless you somehow use a backup folder for one profile as rompath for another but even then you would have a different path as backup defined so your deleted unneeded files would be there. Same for a rebuild operation from backup with remove rebuilt source files.

Can you give a concrete example of what you did with specifying what was rom and what was backuo path at that point in time?

[CoreyEMTP]

Nope on the first, the backup is not in the rompath. The rompath in this case was "E:\Microsoft\XBox\Redump (Discs)" which is a SMB share on a TrueNAS NAS. The backup is locate at "D:\Emu\Tools\clrmamepro\backup" which is an internal hard drive on my local computer and is the same for all DATs. I do have remove source files selected, as well as use backup.

So, I had a window open (XYplorer instead of explorer) in the Xbox subdirectory of the backup directory, and I'm 95% sure inside the _unknown folder. I had a batch running of 200 no-intro DATs. It was on the Xbox DAT when I noticed it was backing up a lot of files that I didn't need, specifically in that set. I used another open XYplorer window to delete the unwanted files from the ROM directory that were left, except for the one it was currently processing. After it finished copying that one file to backup, it presented an error (sorry, didn't capture it) that said something to the effect of no files will be changed (?). It then wrote the remaining files to the output log indicating it was not processing them. At that point it moved on to the next DAT, while at the same time I saw all the files disappear from the Xbox backup directory in the window I had open. There were at least a dozen files, probably more, that it had backed up before my foolish deletion.

That's essentially it. Hopefully that's a little more clear.

[Roman]

Hmm….so you cancelled a backup job by forcing an error (manually removing files during processing) and that ended in a removal of the already created backups. Did I get this right?
I can double check that next week earliest due to vacation.

[CoreyEMTP]

That is it exactly, and no rush, I'm not planning on doing it again and I'm sure there aren't many others out there who would.   

[Roman]

ok..found it and fixed it (for a future release). It indeed killed the _unknown folder if something failed but only if it was just created before in this profile, in all other cases it survived.
Anyhow...fixed now...thanks for finding such a weird case.

[CoreyEMTP]

Glad to help, thanks for the fix