IFW differentials and sectors
Posted: Sat Jul 19, 2014 8:21 pm
I was reading the backup strategies section of the manual and wanted to see if I could clarify something about sector-based backups.
Are there any situations where a file is "touched" by an app in such a way that only a couple sectors consumed by the file have changed, thereby making the differential process a snap, or is it a rule of the file system that anytime you see a new date on a file (as a result of its related program)--no matter how insignificant the changes are from the user's perspective--that all sectors comprised by the file were rewritten and a differential needs to sweep up all of those sectors?
I started thinking about this when it comes to PST (Outlook) archive files, which are often huge. Just opening one--not even changing anything in it--changes the date on the file.
Does whether a few or all file sectors change come down to how the app does things (efficiently or not) or is it driven by the the file system (NTFS)?
Are there any situations where a file is "touched" by an app in such a way that only a couple sectors consumed by the file have changed, thereby making the differential process a snap, or is it a rule of the file system that anytime you see a new date on a file (as a result of its related program)--no matter how insignificant the changes are from the user's perspective--that all sectors comprised by the file were rewritten and a differential needs to sweep up all of those sectors?
I started thinking about this when it comes to PST (Outlook) archive files, which are often huge. Just opening one--not even changing anything in it--changes the date on the file.
Does whether a few or all file sectors change come down to how the app does things (efficiently or not) or is it driven by the the file system (NTFS)?