Test retrieval, not your luck
A backup routine ends with an observation: the copied material can be retrieved and used. This drill is designed to produce that observation without wiping a device, emptying a trash folder or disconnecting an account. It is a planning method developed for this site, not a claim that KYD has tested your hardware or cloud subscription.
Set aside a short, uninterrupted session. Use a small sample first, retain the originals, and create a new destination folder that is not part of your photo synchronization. Do not change live retention settings to perform the exercise.
Choose a sample that can reveal different failures
| Sample | Reason to include it | Observation to record |
|---|---|---|
| Recent photo | Exposes a stalled or incomplete recent upload. | Correct image, expected dimensions and usable export. |
| Older imported photo | Challenges the assumption that every folder was included. | Found by date or known context, not only by a thumbnail. |
| Video | Adds a playback and sound check. | Beginning, middle and end play; expected audio is present. |
| Special format you use | A still JPEG may omit motion, RAW data or an edited version. | The components and behavior you actually need survive the export. |
This is a targeted sample, not a statistical certificate. Add personally important material that would be costly or impossible to replace. Keep that list private; no one needs to know the contents for you to use the worksheet.
Run the drill without deleting the source
- State the route. For example: “Retrieve an exported copy from the external drive into a new test folder.” Do not just write “backup works.”
- Retrieve. Copy the sample out of the backup location. Use the provider’s documented export route for cloud material. Note the account or device dependency privately without recording credentials.
- Open locally. After retrieval completes, open the downloaded files from the test folder, not from a link in the cloud app. If testing offline access, disconnect only after downloads finish and only if doing so will not interrupt other work.
- Inspect. Check content, dimensions, video playback and special-format components. For a plain, unmodified file copy within the 32 MiB limit, also use the local byte comparison.
- Record and retain. Keep a short result, date and next action. Leave the originals and the backup unchanged.
The export route matters. Apple documents separate ways to copy originals and notes limitations for Shared Albums. Google’s folder and item backup checks help identify what entered a cloud library. Neither substitutes for opening your own retrieved sample.
Use a record that separates facts from assumptions
Recovery observation sheet
Date: ____________________ Device / app version: ____________________
Retrieval route (no passwords): __________________________________________
Sample scope and formats: ______________________________________________
Observed result: ☐ Retrieved ☐ Opened ☐ Video checked ☐ Components checked
Still untested: ________________________________________________________
Next action and next check date: ________________________________________
Print this page or use your own private note. A filename can reveal a person, event or location; store the sheet where you would store other private backup records. Do not attach it unredacted to a public issue.
Example record: “October 7: three synthetic test files copied into a separate folder; contents compared. No cloud export, photo decoding or full-library recovery tested.” This is the kind of limited statement a software test can support. It would be misleading to rewrite it as “all photos are safe.”
Stop when a result is ambiguous
- A sample is missing: identify the missing folder or date range before any cleanup.
- A file opens only online: establish whether you saved a placeholder, a link or the complete file.
- A hash differs: check for conversion or editing; do not label the original corrupt from that result alone.
- A copy needs the same unavailable account: your recovery dependency remains unresolved.
- The drive disconnects, reports errors or is physically failing: stop repeated experiments and seek appropriate recovery help.
Schedule your own next check after a major library move, export-setting change or new storage device. There is no universal interval that proves safety. The value comes from noticing when your assumptions no longer match the actual retrieval path.
Return to the backup self-check to identify unfinished checks, or to the copy map if the independence of your copies is unclear.
Sources & scope
Source pages checked October 7, 2026. Provider behavior is source-based; examples and the planning method are KYD’s own synthesis, not a hands-on cloud-service test.