File SYNCing error during file retention attempt.

[Froggie]

Greetings all! While still playing with Rollback, I decided to try using the "Program Settings/Advanced Settings" feature that lets you "keep these files or folders unchanged when Rollback system to another snapshot."

Following the first attempt, I received a file syncing error when the snapshot I rolled back to booted up. I thought it might be due to the fact that I wasn't saving the current configuration prior to the Rollback. So, next time I checked that feature and tried to Rollback once again... same File SYNC error. It happens all the time now following a Rollback unless I turn off the above feature I was testing.

Any hints, ideas, solutions... any help, greatly appreciated.

[Froggie]

Just a follow-up here...

I was able to "sync" a static not-in-use TEXT file using this method but it appears that any file that may be "in use" (OPENed?) by either an application or Windoze, when the sync file transfer is attempted following a Rollback, will fail this process with the appropriate error.

If that's the case, the function has very limited application. Still looking for anyone who may no more...

[nexstar]

I've just tested this out again and it successfully synchronised my NOD32 antivirus folder and NOD32 was already running when it did it. I would imagine that Windows files would be a problem and I suspect that the real purpose of the facility is to sync data files rather than system files.

Can you give an example of files it is failing on for you?

Graham

[Froggie]

Hi Graham! Thanks much for the input. I s'pect that the problem is with files that are currently OPENed for writing. I can't give you a direct example that you can play with but in my case, the 3-file set I was trying to retain (from my personal REMINDER system) failed due to the fact that one of the files is always open for purposes of writing.

I'm guessing that if Rollback used a similar feature like Phylock in Image For Windows, that it may be able to restore that kind of file... don't know for sure.

This is not a feature killer for me as long as I understand the limitations involved. In the case of my REMINDER system, I'm gonna test the file retention with a delayed startup for the REMINDER application. If my guess is correct, Rollback's retention should work just fine.

I'll keep you posted...


Indeed, when I ran the test above, all worked just fine. It appears to be the usual "file being locked" kinda problem that many apps see when trying to access certain files. I guess I'll just have to work with that type of limitation...