Re:macOS extensions are moving away from the kernel
by CharlesW on Wednesday July 07, 2021 @04:12PM
(#27765267)
> Apple can. I can’t. Making APFS snapshots requires special entitlements, which they’re not going to give me.
What makes you think that? Carbon Copy Cloner does this, and is made by a small independent developer.
https://bombich.com/kb/ccc6/leveraging-snapshots-on-apfs-vol...
Re:macOS extensions are moving away from the kernel
by Hackbraten on Wednesday July 07, 2021 @05:13PM
(#27765789)
They have managed to obtain the special entitlement.
Source: https://bombich.com/blog/2018/03/30/building-better-backups-...
They’re one of two apps in the world who have been granted the entitlement as far as I know. The other one is Time Machine.
Re:macOS extensions are moving away from the kernel
by yehaaa on Wednesday July 07, 2021 @01:20PM
(#27763524)
You can use tmutil to create a snapshot.
Or do you want to create an app that performs a snapshot via some API.
Re:macOS extensions are moving away from the kernel
by Hackbraten on Wednesday July 07, 2021 @02:51PM
(#27764514)
One does not simply create an APFS snapshot using tmutil.
Using tmutil means Time Machine creates a snapshot for me. It also conveniently earmarks the snapshot for later removal at Time Machine’s own discretion.
That’s not what I want. I want to have a say in snapshot retention, not have some tool make the decision for me.
Specifically, I need precise control over snapshot retention so I can maintain several off-site replicas of my backup.
Apple can. I can’t. Making APFS snapshots requires special entitlements, which they’re not going to give me.
> It also use checksums for filesystem integrity.
It doesn’t check integrity of the actual data though. But I care about my data.