How does the iOS backup work?
-
In Pythonista, I want to maintain a local .db file of 2 GB.
My iOS backup is on iCloud and the file is already saved in a previous backup.
The "next backup size" (settings/iCloud/iCloud storage/manage storage) is some MB, this is normal.
I only add one little record in the dB file and this "next backup size" just goes to 2 GB.
I hoped that only some bytes need to be backuped, thus I don't understand how this iOS backup works...It seems that if an app file is modified, the entire file would be in the next backup. Thus, I should abandon this way π’
-
@mikael I don't know dbm but I've read " A dbm database can only store strings, both as keys and values".
If it is still true, my keys are string but my values are images...
-
Could you keep files on disk, and just store file name? That would keep your DB to small text, and images themselves probably change rarely
-
@JonB yes but in this cases, the number of files will stay 30.000, isn't it?
Folders names are authors names
Files names are books names
Files are covers png
-
@JonB you are right, the images never change. The only modification in the dB or files tree is to add an author/book/cover. I'm not sure that this info could help to find the right way but so you have all infos
-
@cvp, yeah. I guess you could encode/decode the images, but would have to experiment what kind of control you have on the number of files.
-
If you place the 10000 folders underneath a folder called .DB or something, I wonder if that still causes slowness. I'm thinking I have git repos with hundreds of commits resulting in thousands of files stored in . git, and don't necessarily have massive slowdown in creating or moving files, but I'm not sure.
Could maybe have heirarchys to keep single folders small -- for instance git deals with tons of commits/blobs/trees, each which is its own folder based on the hash. But top level folders are first 2 letters of the hash, thus making it fast to lookup a particular hash -- top folder has < 256 subfolders, etc.
-
@JonB You are right (as usual π), all my 10.000 folders are under a folder that I prefixed with a dot, and creating or moving a file has retrieved its normal speed.
Thus, thanks a lot. I'll keep my 30.000 files without a dB...
I'll have to modify some scripts to access these sub-folders or files because the upper folder is not visible.Although, I still think that iOS backup should not be so designed, by file...But, ok, it is not vital.
A last time (for today), thanks for your time.
-
last edited by
-
Unforeseen consequence: uploads via SFTP to my backup server ADrive.com does not work anymore from sub_folder of hidden folder π’ (error 2 "no such file").
Exactly same process to my iMac (where standard SFTP server runs) works successfully.
Edit: ADrive server seems to have (temporary, I hope) problems. The same error occurs actually even for an upload from a visible folder.
Just when I test my modification...π’andπ
-
Folder rename (drop/add the leading dot) before and after sftp operations might be a workaround.
-
@ccc Yes sir but I still hope it is a temporary problem. Wait and see
-
Problem disappeared today, it was thus a server problem...occurred at a bad moment π