Design the routine before leaving
A useful travel backup is a sequence you can repeat when tired, not a collection of drives you hope to organize later. Before departure, photograph a small test set, copy it with the reader and computer you will carry, and confirm that your software opens the originals. Include a video clip if you intend to film. Estimate storage from your own sample files and expected shooting days, leaving space for more than the average day. Label the cards and destinations in plain language. The goal is to know where a photograph exists at each stage without having to infer its status from a cable, an application icon or a half-remembered transfer.
Keep the card as the first safety copy
Our recommended field procedure is to copy, not move, the day’s files into a clearly named destination. Preserve the card’s folder structure when a video workflow depends on it, and place each card inside a unique parent folder such as 2026-09-13_CameraA_Card03. This avoids collisions between cameras that generate the same filenames. Do not mix a fresh card with a partly imported one in an unmarked pocket. Keep used cards in a separate section of the case until the copying and checking stages are finished. Retaining the original card buys time to discover an interrupted transfer before the only complete version is overwritten by tomorrow’s photographs.
Make copies independent of one another
The Canadian Centre for Cyber Security recommends the 3-2-1 principle: three copies, two media types and one copy off-site. For a traveler, the practical lesson is independence. A card plus a laptop plus a second storage destination is more resilient than three folders on the same laptop, but it still does not protect against theft if everything stays in one bag. Separate the destinations where reasonably possible and complete an off-site copy when connectivity permits. A temporary travel arrangement may fall short of a full archive strategy; describe that gap honestly and close it after returning. Counting copies is useful only when considering what could destroy them together.
Verify more than the progress bar
A finished copy dialog confirms that a process ended; it is not a complete review of the photographs. Compare the expected file count and total size, and investigate discrepancies before deleting anything. Where the transfer software supports checksum verification, use it to compare the copied data with its source. Then open representative full-resolution RAW files and play video from several points, including near the end of long clips. These are complementary checks: a thumbnail can look normal even when the full file is damaged, and a spot check does not validate every byte. Keep the source unchanged until the verification step is complete.
Back up the edit as well as the originals
Adobe explicitly notes that a Lightroom Classic catalog backup does not contain the photographs or exported files. Preserve the original image folders independently and include the catalog and other edit information required by your chosen workflow. A folder full of JPEG exports cannot necessarily recreate the original RAW processing decisions. For a simple travel arrangement, keep separate areas for untouched captures, editing data and delivery files so their roles remain clear. Close applications or use their supported backup method before copying active project databases. At home, open the restored project against a copied set of originals to confirm that the archive preserves both the pictures and the work done to them.
Be specific about what reached the cloud
Do not assume that a cloud icon means every original has arrived. Check which folder or library is being uploaded, whether the service retains full-resolution originals and whether any items are paused or waiting for connectivity. Download a sample from the destination and inspect it separately. On a slow connection, prioritizing irreplaceable files can be a useful temporary measure, but record which files remain unprotected. The Canadian guidance also recommends strong account protection and separating backups from the computer. For travel, that means thinking about both access and recovery: a remote copy is helpful only if you can securely regain access when the laptop or phone is lost.
When a card behaves strangely, stop writing to it
If a card suddenly produces errors or missing files, do not format it simply because a prompt offers that option. Stop shooting on it, label it and set it aside. Check the copies you already have before attempting recovery. For irreplaceable work, seek a qualified recovery service and explain what happened, including any attempted repairs. Avoid testing a series of unfamiliar tools against the only source. A cautious response preserves choices; additional writes can make a recoverable problem worse. This is also why the backup routine should be calm and predictable: a clearly identified last verified copy is far more useful in a failure than an uncertain collection of duplicates.
End each day with a short record
A small transfer log can contain the date, card identifier, destination folders, verification result and whether an off-site copy is complete. It need not become an administrative project. Five clear lines can answer the important question the following morning: which cards are safe to reuse? Keep the log with the project and do not mark a stage complete merely because it was started. Before formatting a card in its camera, confirm that the required copies exist and are readable. Once home, integrate the trip into the main archive, test a restore and retain the travel copies until the archive has passed its own checks.
