Code
#!/usr/bin/env bash BACKUP_DIR=”\(HOME/Library/Application Support/MobileSync/Backup" OUTROOT="\)HOME/backup_reports” LOGFILE=”\(OUTROOT/run.log" mkdir -p "\)OUTROOT”for b in \((mobilesync-inspect list --json | jq -r '.[].backup_id'); do OUT="\)OUTROOT/\(b-\)(date +%Y%m%d%H%M%S)” mkdir -p “\(OUT" mobilesync-inspect metadata --backup "\)b” > “\(OUT/metadata.json" mobilesync-inspect extract --backup "\)b” –domain HomeDomain –path ‘Library/Contacts/Contacts.sqlite’ –out “\(OUT/contacts.sqlite" || true # parse contacts.sqlite with sqlite3 and export CSV sqlite3 "\)OUT/contacts.sqlite” -header -csv “SELECT displayName,value FROM ABPerson JOIN ABMultiValue ON ABPerson.ROWID=ABMultiValue.recordid;” > “\(OUT/contacts.csv" || true echo "\)(date -Iseconds) processed \(b" >> "\)LOGFILE” done
Notes:
- Use the tool’s JSON output (if available) to drive decisions programmatically.
- Handle failures with fallbacks (|| true) and robust logging.
- Limit parallelism to avoid I/O overload when working with many or large backups.
Parsing outputs: examples
- JSON outputs: consume with jq in shell scripts:
Code
mobilesync-inspect list –json | jq -r ‘.[].backupid’ - SQLite artifacts: run targeted queries via sqlite3:
Code
sqlite3 contacts.sqlite -header -csv “SELECT displayName, value FROM ABPerson JOIN ABMultiValue ON ABPerson.ROWID = ABMultiValue.recordid;” > contacts.csv - Binary/plist files: use plutil or Python’s plistlib:
Code
plutil -convert json -o - AddressBook.sqlitedb > ab.json
Scheduling and scaling
- Cron (simple scheduling):
- Add a cron entry to run nightly and rotate outputs.
- systemd timers (Linux) for more control over concurrency and
Leave a Reply