What Did the Android Backup Question Ask?
The July 2026 community post describes a practical goal: replace cloud backup with a ZimaOS server while transferring only new or modified files, keeping server-side copies safe after accidental deletion on the phone, and finding a reliable way to preserve Android and WhatsApp data over time.
The post also compared ZimaClient with alternatives such as Syncthing, FolderSync, SMB, and SFTP. The original thread had no replies, so it did not establish community-tested answers to the five detailed ZimaClient questions.
What Does Current ZimaClient Phone Backup Confirm?
Current ZimaOS phone-backup documentation confirms that ZimaClient is available on Android and iOS. The phone first connects to the ZimaOS device on the local network, and remote backups can continue when ZimaOS Remote Access is enabled.
The current documentation also states that the first backup transfers the selected content and later backups transfer only what changed. That directly answers the original concern about copying the entire selection again on every run.
See the current ZimaOS Phone Backup guide for the supported setup flow.
What Is Still Not Documented for Android Phone Backup?
The current phone-backup guide does not clearly document several behaviors raised in the community post. It does not specify whether deleting a source file from an Android phone also deletes the backed-up server copy, whether mobile backup keeps previous versions of modified files, or whether ZimaClient can select Android's restricted WhatsApp database path such as Android/media/com.whatsapp/WhatsApp/Databases.
Those gaps should remain explicit rather than being filled with assumptions. Android storage permissions also change across OS versions, so access to application-managed folders must be verified on the actual Android and ZimaClient versions in use.
Do Not Confuse Phone Backup with the ZimaOS Backup App
ZimaOS also has a separate server-side Backup App with its own scheduling, retention, and versioning behavior. Current documentation for that app describes version retention and resume behavior, but those features should not automatically be assumed to apply to ZimaClient's mobile backup workflow.
If version history and protection from accidental deletion are mandatory, verify the behavior of the phone backup first and then consider a second server-side backup task so the ZimaOS copy is protected independently.
How Can You Build a Safer Android-to-ZimaOS Workflow?
- Install the current ZimaClient for Android and connect it to ZimaOS on the same local network for the initial setup.
- Choose the supported phone content and a destination on a data disk or RAID rather than filling the ZimaOS system drive.
- Run the initial backup on a stable Wi-Fi connection.
- Verify that a later run transfers only changed content, as described by current ZimaOS documentation.
- Test deletion behavior with a disposable file before trusting the workflow for irreplaceable data.
- Test whether the exact WhatsApp folder is visible to ZimaClient on your Android version instead of assuming Android grants access.
- For important archives, create a separate server-side backup of the destination so one phone or application action is not your only protection.
Frequently Asked Questions
Does ZimaClient upload every Android file again during each backup?
Current ZimaOS documentation says the first backup transfers the full selection and later backups transfer only what changed.
If I delete a file from my Android phone, is the ZimaOS copy deleted too?
The current phone-backup documentation reviewed for this page does not clearly specify that behavior. Test with a nonessential file before relying on deletion protection.
Does ZimaClient keep previous versions of modified Android files?
That behavior is not clearly documented for the mobile backup workflow. Version retention documented for the separate ZimaOS Backup App should not be assumed to apply to ZimaClient phone backup.
Can ZimaClient back up the WhatsApp Databases folder?
The current public phone-backup guide does not document support for the restricted WhatsApp database path. Folder visibility can depend on Android storage permissions and the app version, so this needs direct verification.
Can phone backups continue away from home?
Current ZimaOS documentation says remote phone backups can continue when Remote Access is enabled on the ZimaOS device.
