Skip to main content

Backup Setting Save Button Never Available... Deleting an Old Backup

Thread needs solution

Hello! I have 3 backups on an external USB3 drive, using Windows 7 Prof, Acronis TI 2014 Premium, Build 6673. The first two backups are disk backups. If I click the "Settings" button in the lower right side of each of those backups, I get a dialog that allows scheduling to be changed, along with other settings. The "Save" button on those is available. On the 3rd backup, a file backup, the "Save" button is never available. By mistake, when I created this backup, I must have set it to scheduled. Since my backup external drive is not generally connected, TI generates an error message every time I boot my machine that it cannot find the backup to be scheduled (the first two are correctly "Do Not Schedule"). Therefore, I simply cannot change the 3rd backup to be not scheduled, as I can never save its settings. The backup validates; however, I've deleted the original material from the source, this is only an archive (that's one reason not to schedule it). Why can I not save this backups' settings?

I also have an old backup, which shows up in TI's UI. I can't delete it via TI's delete command; it's present on the backup drive, but TI reports that it cannot delete all the files. I can't remove the backup file from the backup drive using the Windows explorer, which reports unhelpfully that "the folder is open in COM Surrogate". I guessed that this refers to the various Acronis services, but stopping those services did not allow the file to be deleted. Presumably, a lock is being held which cannot be released. How do I delete an old backup? It seems like every path is blocked.

Thanks! - Roderick Llewellyn

0 Users found this helpful

I have solved the latter problem - the undeletable backup. I just used a command-line window. I suspect the problem is that Acronis links a component of itself into the Windows file explorer, and it's trying to "preview" the file, which prevents it from being opened because the file is corrupt. I've seen this with a corrupt video file - it couldn't be deleted within the Explorer for that same reason, but could be deleted via command line.