Back Up Jira Properly Database Plus Home Directory
Your Jira now holds the real work of your whole team. Losing the server should be an inconvenience, not a catastrophe — and that difference is decided entirely by what you back up this week.
✍️ Technical Anshu🪟 Windows⏱️ 6 minute read
🎥 The install video built the Jira — this guide makes sure you can rebuild it
Ask admins what their Jira backup contains and most will say "the database". Half right — and the missing half is where attachments live. This guide covers both halves, the schedule, and the one test that makes a backup real.
A complete Jira backup — both halves, every time (illustration)
Half 1 — the databaseNative database backup or dump
Half 2 — the home directoryAttachments, avatars, indexes, config
Where copies liveAnother machine or disk — never only this server
Restore testDone at least once — a backup untested is a hope
👆 Backing up only the database loses every attachment. Backing up only the folders loses every issue. Jira is two halves — schedule both, together.
1
What a Jira Backup Must Contain
The database. Issues, comments, workflows, users, permissions — the substance of Jira. Back it up with the database's own tools (a scheduled dump or your database server's backup job), not by copying live database files.
The home directory. Attachments live here under the data folder, along with avatars, search indexes and configuration. Copy the whole home directory while Jira is stopped, or use a backup tool that handles open files honestly.
Your licence and configuration notes. Keep the licence key, database password location and any custom settings documented with the backup — a restore performed by a colleague at 2 a.m. should not need you awake.
Jira also has a built-in XML backup under Administration → System. It is handy for migrations and small instances, but for a growing production instance Atlassian recommends native database backups — XML exports get slow and are not a full disaster-recovery answer on their own.
2
Schedule It Like You Mean It
Nightly database backup, and home-directory backup on the same rhythm — a day apart means a day of attachments pointing at nothing.
Keep several generations (for example the last 7 days plus one weekly copy). Ransomware and silent corruption both punish single-copy backups.
Store copies off the server — another machine, a NAS, or cloud storage. A backup on the same disk dies in the same fire.
3
The Restore Test Nobody Does
Once — just once — restore your backup onto a spare machine or virtual machine and log in. Time it. Write down the steps. Most teams discover their backup gap (missing attachments, wrong database password, forgotten licence) during a real disaster; the test moves that discovery to a calm afternoon. After the test, your restore is a procedure, not a prayer.
🎥 Watch the Complete Install in the Video
The full installation, screen by screen, is in the video — this page is your written companion for every step and warning.
For a small instance or a migration, it is useful. For production disaster recovery it is not the whole answer: Atlassian recommends native database backups, and you still need the home directory for attachments and configuration.
How often should Jira be backed up?
Nightly is the sensible default for both the database and the home directory, with several generations kept and at least one copy stored off the server. Match the rhythm to how much work a day of lost issues would cost you.
Where do attachments actually live?
In the Jira home directory, under its data and attachments folders — not in the database. That is why a database-only backup restores issues whose attachments are permanently gone.
This guide is based on the Technical Anshu Jira Server installation video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏