>there's no good and easy option to backup your phone other than iCloud.
Turn off iCloud and do local encrypted backups to your PC or Mac.
This works over your wifi network (if you prefer wireless charging at home) or via a cable connection.
Turn off iCloud and do local encrypted backups to your PC or Mac.
This works over your wifi network (if you prefer wireless charging at home) or via a cable connection.
(to clarify, my desktop PC is always turned on and connected to the network, so most of the other complaints in this thread about it not working with low battery laptops or whatever don’t apply in my scenario. Even in my ideal-case scenario it still barely works)
I've tried getting my family to use it (mainly because they didn't want to pay for iCloud storage), before giving up and just paying their storage for them.
I mean... yes? How else would they do it? Data transfer is power-intensive, and encryption is also power-intensive. Imagine having only 10% battery on your laptop while you're working at a coffee shop or something and suddenly it drops to 5% because it's started a backup.
Sure, the majority of the time it'd probably work out fine, but Apple's UX philosophy is to simply remove undesirable states from the equation by sufficiently limiting users' options. This is exactly the kind of behavior I would expect from this feature.
Or are you suggesting that an average Linux user who wants to back up their iPhone needs to buy and install Windows in a VM, and then is further expected to tinker with ingress/egress network rules to make sure no data is being sent over to Microsoft? I'd say that's a tall order.
If you only use that VM for backing up your iPhone, there are no useful telemetry signals for them to collect in the first place.
Haha, good one. Who cares?
It also does put a shelf life on the underlying software in a way that even crazy old computer software like for an IBM 700 series doesn't have.
It's a command line suite for Mac, Linux, and Windows that interfaces with your iPhone through it's native protocols, including for encrypted local backups.
I’ve also had instanced where the latest version of that library supposedly works, but it’s dependent on another library that hasn’t hit Debian mainline yet. So I’ve had to wait months just to get a version that works even though it was released much earlier.
It’s not a perfect solution by any means.
I'm saying that my phone becomes the synced copy. The cloud is the canonical version (backed up separately elsewhere) and my phone becomes a device I can lose or break and not worry about anything so I don't need to back it up. As soon as I create any content on my phone I upload it to the cloud.
Take my phone from my hand at any moment and as long as I've had signal in the last few minutes I've lost nothing.
What do you think is special about a phone backup compared to a backup of anything else?
I said don't have the primary store of your content to be on your phone and don't backup your phone.
The reason for this is that if you lose your phone, everything is lost since you last backed up.
Instead, store have the primary store of your content to be in the cloud and backup your cloud.
The reason for this is that if you lose your phone, it's irrelevant, just get a new phone and re-install your cloud apps. Now you don't need to worry about backing up your phone ever.
The only failure mode is if your phone has not had a signal to upload new content to the cloud in the last few minutes. Well guess what you probably also haven't backed up your phone in that time either if that's what you were doing.
See?
1: https://www.macworld.com/article/3269361/apple-discontinues-...
Of course then you have a local backup on a hard drive which is itself subject to seizure and I believe even encrypted backups can be cracked.
I suppose I could mount a network drive / nfs share at the location iTunes believes is local ...
https://reincubate.com/support/how-to/change-itunes-backup-l...
I fixed the problem for now. I have some older devices I don’t care about the backups for any longer.
>How to move your iPhone or iPad backups to an external hard drive
https://www.imore.com/how-move-your-iphone-or-ipad-backups-e...
If anything, they're more prone to being cracked, since an attacker can load the backup onto a very fast system and run custom software which can run many permutations of keys against the backup to try to unlock it. With actual hardware, they're limited by having to manually enter the key in most cases plus any hardware or OS features which would notice that the user has entered too many incorrect passwords and lock down the device further.
On the other hand, if the computer that your backup has been backed up to is itself reasonably locked down, that might be an acceptable trade-off; they can't try to crack a backup they can't access in the first place.