Bound TrueNAS Google Photos sync to app-created albums

Bottom line: Treat the Google Photos API integration as an app-created album workflow. Do not approve it as a full-library backup or accept a successful dry run as proof of transferred recovery data.

Source fact: what the authority says

The TrueNAS 25.10 Google Photos guide states that the March 31, 2025 API change limits external applications to media and albums they create, and that a complete library backup through the API is not possible. The guide says pull tasks can access albums created by the TrueNAS sync client, not the full library or shared albums. Its SYNC mode deletes destination files absent from the source and affects only albums created by the sync client. A dry run simulates transfer without sending or receiving data and can report success even when a misconfigured task would fail to transfer it.

What the source does not establish

This article covers the documented API and task boundaries rather than certifying preservation of a whole account. It does not approve a destructive transfer mode or establish the completeness of a separate archive-export workflow.

Applicability questions

• Which albums were created by this TrueNAS sync client?
• Is the required recovery population larger than that accessible album set?
• What direction and transfer mode have the data owner approved?
• Which harmless test files can demonstrate actual transfer without risking originals?

DSE recommendation: controlled next steps

The following steps are DSE recommendations based on the cited source.

DSE recommends listing the required photo population before creating the task. Mark app-created albums, shared albums and other library content separately. Ask the data owner to identify any required item outside the accessible set; leave the full-library recovery requirement unresolved until another documented approach has been reviewed.

Write the approved direction and transfer mode next to the album list. For a proposed SYNC case, require an explicit decision about destination-only files before the task runs. Avoid interpreting an attractive task name or a valid credential as proof that deletion behavior matches the retention requirement.

Use disposable albums and harmless copies for the first transfer trial. Include one item in the app-created scope and a separately identified control item outside it. Keep the control observation read-only and do not move valuable originals into a new layout simply to make a pilot appear complete.

Keep the dry-run result as a configuration checkpoint, with an actual transfer and recovery observation as separate tasks. Retain the approved album mapping and protected credential reference. Do not include OAuth tokens or private photographs in a broadly accessible change record.

Verification and evidence

Proposed verification: inspect the saved direction, mode and target album against the approved mapping, then perform the permitted dry run. Record its result without closing the transfer task. Run the separately authorized small-data trial and inspect the intended destination for the exact harmless files.

Compare the observed accessible population with the original requirement list. If permitted by the owner, rehearse retrieval of the transferred test item into a separate location and compare its identity with the source copy. Record absent or inaccessible content as an explicit recovery gap rather than reporting a complete account backup.

Official references

• TrueNAS — Adding a Google Photos Cloud Sync Task — official product documentation; confirm the installed release and configuration.

Source review completed October 29, 2026. Recheck the official documentation and deployment-specific applicability before a production change.