What type of connection do you use? WLAN only or WLAN/Data? Can you give more information about your NextCloud instance? Is it a local one? Or you pay for it? Which one do you use?
Can you please update your bug report to include these informations?
Can you provide logs file stored at $HOME/.local/share/sailfish-backup/logs
You’ll find more information here.
Auto backup (daily, wifi only) has never worked normally on my previous XA2 or the current X10III.
Manually starting the backup always works.
Very rarely, and very random, it starts to backup when I get on a Wifi network after being only on mobile network.
Same here on XA2 and C2. Set to run daily at 21:00, wifi only, but it runs randomly at unxpexted time (it can be weeks between 2 runs). Manual backup works fine.
Yesterday I switched to weekly updates for trial, scheduled Sunday 03:00.
It definitely did not happen today early morning, so it’s doesn’t look like only a daily backup issue.
Maybe a reboot is required for you or your device is in deepsleep at 03:00 missing triggering mechanism. On Jolla C2 once weekly backup always works at 17:00. In this time the Device is beeing used and WLAN or Mobile Data is on.
Did anyone know now periodic backups are scheduled exactly? Backup settings is done thru D-Bus service org.sailfishos.backup provided by the /usr/libexec/sailfish-backup binary from the jolla-vault package. Scheduling is not done by systemd timer or by the timed daemon, but when I analyzed D-Bus communication captured by dbus-monitor with LLM model, it said that backup is triggered by the msyncd process (from buteo-syncfw-qt5-msyncd package)… If it is true, we are lucky, it is open-source: GitHub - sailfishos/buteo-syncfw · GitHub .
The March 8 backup also didn’t happen, but the 6 weekly Sunday backups were successful since then. I’m setting it now back to daily backup to see what happens.
But honestly I doubt that there’s any correlation between the settings and the success or failure.
