Folks,
If the NTFS permissions and/or the owner of a file are changed, but the user data in the file is NOT changed, how does that affect an incremental backup? Will the entire file be backed up, or will the backup job only write the NTFS/owner changes to the .vib file? Thus, is the NTFS/owner information handled by the Changed Block Tracking just as the user data in the file?
PJ
-
- Veteran
- Posts: 463
- Liked: 47 times
- Joined: Jun 06, 2018 5:41 am
- Full Name: Per Jonsson
- Location: Sweden
- Contact:
-
- Veteran
- Posts: 3077
- Liked: 453 times
- Joined: Aug 07, 2018 3:11 pm
- Full Name: Fedor Maslov
- Contact:
Re: Changes to NTFS permissions and/or owner
Hi Per,
It's up to CBT to decide what blocks have changed and thus must be processed by the backup job, which, in turn, depends on how the file system handles such changes. I.e. if the file system writes the data to new blocks, they will be processed by CBT and then backed up. This also applies to MFT files that store ACL data and may take quite a bit of space on the volume potentially resulting in numerous changed blocks to be processed by the backup job.
Thanks
It's up to CBT to decide what blocks have changed and thus must be processed by the backup job, which, in turn, depends on how the file system handles such changes. I.e. if the file system writes the data to new blocks, they will be processed by CBT and then backed up. This also applies to MFT files that store ACL data and may take quite a bit of space on the volume potentially resulting in numerous changed blocks to be processed by the backup job.
Thanks
-
- Veteran
- Posts: 463
- Liked: 47 times
- Joined: Jun 06, 2018 5:41 am
- Full Name: Per Jonsson
- Location: Sweden
- Contact:
Who is online
Users browsing this forum: Semrush [Bot] and 111 guests