Journal / topic tag
A focused reading collection for backups.
A backup plan should describe the project you expect to recover, not only the job that creates a copy. The articles tagged here examine source snapshots, repository history, retained states, and the supporting data outside Git. Use them to connect preservation choices with a restoration someone can actually perform. Assign someone to resolve each gap revealed by the rehearsal and update the recovery process.
Begin with the Git backup, archive, and recovery guide, then compare its inventory with your own assets, uploads, settings, and access requirements. The backup and security hub provides the wider overview. Record the result of a recovery rehearsal, including any missing dependency, so the next attempt starts with better instructions.
A ZIP, a clone, and a working backup preserve different things. Learn how to protect repository history, recover large-file objects, retain application state, and rehearse restoration without depending on the original host.
Large files need a storage decision before they need a Git command. Learn which assets belong in ordinary Git, which fit Git LFS, and which should stay in artifact storage or application backups.
A CMS combines versioned code with changing content. Build a practical WordPress Git workflow that keeps themes and plugins reviewable while protecting uploads, database changes, configuration, and reliable releases.