Incremental backups? Any opportunity to optimize speed?

[eigenphase]

I got pymobiledevice3+netmuxd working ... YAAAAY! Thanks for this project, I was about to throw the towel with libimobiledevice ...

This one takes many, many hours:

pymobiledevice3 backup2 backup --full /scratch/miPhone_backup

1. I love the "incremental backup" feature which iMazing for example provides. It only stores/transfers(?) data that was modified since last run. Is something like this possible with pymobiledevice3 ? Or does it always re-transfer and re-store the full thing? And overwrite the previous backup?
2. It's extremely slow but Wifi should be quite a bit faster. What is the limiting factor of this? Is there any opportunity to optimize/speed up the process?

[doronz88]

The backup feature is incremental by default. Simply dismiss the --full option

[eigenphase]

👍

seems —no-full has to be specified explicitly (just leaving out —full doesn’t work)

[doronz88]

Oh its a CLI bug caused when migrating to typer. Will fix that. The --full should be specified explicitly

[doronz88]

#1576