Searching for a file undiff tool
-
Hi, don't know what I mean by the subject? Me neither :). I'm searching for infos, a phrase, a tool or a component which can do the following (I'm not even sure if this is technically possible): - Monitor a file for changes - Whenever portions of the file are changed it stores the original data (only the changed) somewhere - Restores the original state from the saved data (if needed) The purpose is the following: I'm using a third party component to access and change some (very) large files. So far I'm copying those files before anything gets changed. Thus the user has the possibility to commit all changes or rollback (then I'm switching to the copies). The problem is that those files can have sizes of several hundred megabytes but normally only some kilobytes are changed. Before anyone asks: I'm not able to alter the behaviour of this third party component nor is it possible for me to keep changes in memory and flushing them when commiting. I'm not even sure if this can be done and I don't know what phrase I could type into Google to find it. Any hints are greatly welcome.
-
Hi, don't know what I mean by the subject? Me neither :). I'm searching for infos, a phrase, a tool or a component which can do the following (I'm not even sure if this is technically possible): - Monitor a file for changes - Whenever portions of the file are changed it stores the original data (only the changed) somewhere - Restores the original state from the saved data (if needed) The purpose is the following: I'm using a third party component to access and change some (very) large files. So far I'm copying those files before anything gets changed. Thus the user has the possibility to commit all changes or rollback (then I'm switching to the copies). The problem is that those files can have sizes of several hundred megabytes but normally only some kilobytes are changed. Before anyone asks: I'm not able to alter the behaviour of this third party component nor is it possible for me to keep changes in memory and flushing them when commiting. I'm not even sure if this can be done and I don't know what phrase I could type into Google to find it. Any hints are greatly welcome.
automatic incremental backup (methinks) Advanced backup tools (a) do incremental backups, and (b) run in the background, monitoring file changes. They very much differ in their friendliness of restore, though.
We say "get a life" to each other, disappointed or jokingly. What we forget, though, is that this is possibly the most destructive advice you can give to a geek.
boost your code || Fold With Us! || sighist -
Hi, don't know what I mean by the subject? Me neither :). I'm searching for infos, a phrase, a tool or a component which can do the following (I'm not even sure if this is technically possible): - Monitor a file for changes - Whenever portions of the file are changed it stores the original data (only the changed) somewhere - Restores the original state from the saved data (if needed) The purpose is the following: I'm using a third party component to access and change some (very) large files. So far I'm copying those files before anything gets changed. Thus the user has the possibility to commit all changes or rollback (then I'm switching to the copies). The problem is that those files can have sizes of several hundred megabytes but normally only some kilobytes are changed. Before anyone asks: I'm not able to alter the behaviour of this third party component nor is it possible for me to keep changes in memory and flushing them when commiting. I'm not even sure if this can be done and I don't know what phrase I could type into Google to find it. Any hints are greatly welcome.
Isn't this what source control does? Let you check out a previous version, effectively undoing your changes and returning you to a previous state? Marc Pensieve
-
Hi, don't know what I mean by the subject? Me neither :). I'm searching for infos, a phrase, a tool or a component which can do the following (I'm not even sure if this is technically possible): - Monitor a file for changes - Whenever portions of the file are changed it stores the original data (only the changed) somewhere - Restores the original state from the saved data (if needed) The purpose is the following: I'm using a third party component to access and change some (very) large files. So far I'm copying those files before anything gets changed. Thus the user has the possibility to commit all changes or rollback (then I'm switching to the copies). The problem is that those files can have sizes of several hundred megabytes but normally only some kilobytes are changed. Before anyone asks: I'm not able to alter the behaviour of this third party component nor is it possible for me to keep changes in memory and flushing them when commiting. I'm not even sure if this can be done and I don't know what phrase I could type into Google to find it. Any hints are greatly welcome.
Well, as a backup solution: http://www.storactive.com/[^] And I believe KeepSafe might work: http://www.stardock.com/products/keepsafe/[^]
-
Isn't this what source control does? Let you check out a previous version, effectively undoing your changes and returning you to a previous state? Marc Pensieve
Marc Clifton wrote:
Isn't this what source control does? Let you check out a previous version, effectively undoing your changes and returning you to a previous state?
It'd depend on the implementation. Because of file sizes and the small ammounts changed, Robert wants a SC program that only stores the changed portions and not the entire file and then use the saved diff data to recreate a specific version on demand. I haven't looked at implementation details, but I'd assume a normal SC tool would do the oposite, storing a snapshot of each version and generating the differences on demand.
-
Hi, don't know what I mean by the subject? Me neither :). I'm searching for infos, a phrase, a tool or a component which can do the following (I'm not even sure if this is technically possible): - Monitor a file for changes - Whenever portions of the file are changed it stores the original data (only the changed) somewhere - Restores the original state from the saved data (if needed) The purpose is the following: I'm using a third party component to access and change some (very) large files. So far I'm copying those files before anything gets changed. Thus the user has the possibility to commit all changes or rollback (then I'm switching to the copies). The problem is that those files can have sizes of several hundred megabytes but normally only some kilobytes are changed. Before anyone asks: I'm not able to alter the behaviour of this third party component nor is it possible for me to keep changes in memory and flushing them when commiting. I'm not even sure if this can be done and I don't know what phrase I could type into Google to find it. Any hints are greatly welcome.
IIRC, this is a versioning file system. NTFS doesn't support it directly, but I think WinFS, next generation file system does. Too bad it's not released yet. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
IIRC, this is a versioning file system. NTFS doesn't support it directly, but I think WinFS, next generation file system does. Too bad it's not released yet. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
Exactly. I've search a bit and it can be found on MSDN under Transaction Management (TxF)[^]. Transactions on the file system! Now that's pretty cool. This is what I need. But I don't have the time to wait till Microsoft releases it.
-
Marc Clifton wrote:
Isn't this what source control does? Let you check out a previous version, effectively undoing your changes and returning you to a previous state?
It'd depend on the implementation. Because of file sizes and the small ammounts changed, Robert wants a SC program that only stores the changed portions and not the entire file and then use the saved diff data to recreate a specific version on demand. I haven't looked at implementation details, but I'd assume a normal SC tool would do the oposite, storing a snapshot of each version and generating the differences on demand.
No, source control systems only store one full file and a bunch of diffs. IIRC, SCCS store the original and diffs to generate newer versions, whereas RCS stores the latest version and diffs to generate previous versions. ...cmk Save the whales - collect the whole set
-
Marc Clifton wrote:
Isn't this what source control does? Let you check out a previous version, effectively undoing your changes and returning you to a previous state?
It'd depend on the implementation. Because of file sizes and the small ammounts changed, Robert wants a SC program that only stores the changed portions and not the entire file and then use the saved diff data to recreate a specific version on demand. I haven't looked at implementation details, but I'd assume a normal SC tool would do the oposite, storing a snapshot of each version and generating the differences on demand.
dan neely wrote:
It'd depend on the implementation.
True. You'd have to find one that saves diffs. I think those are getting pretty rare, since the performance hit is then on getting the latest version. Marc Pensieve