f you manage a Jira Data Centre instance, you\u2019ve likely encountered system health warnings in the Atlassian Troubleshooting & Support Tools. One critical notification that often gets ignored or deferred is the “Health Check: Local Backup Security” <\/b>warning.\nAt first glance, having automated backups saved locally inside your Jira directories feels convenient. After all, if something goes wrong, the backup is right there, ready to restore… right?\n<\/p>\n
In reality, storing unencrypted backup files inside your application storage creates a massive security vulnerability.<\/b><\/p>\n
As an Official Atlassian Solution Partner,<\/b> we regularly see growing enterprise teams trip over this exact issue during routine maintenance. Let\u2019s break down why this health check fails, what risks it exposes, and how you can resolve it permanently.<\/p>\n\n\n\n\n\n\nWhat Triggers the “Local Backup Security” Warning?<\/h2>\n\n\n
Jira automatically runs background health checks to ensure server security and stability. This specific check scans your Jira directories\u2014specifically: If Jira finds any .zip backup files residing in these folders on single-node or clustered Data Center nodes, it immediately flags a warning:\n<\/p>\n Found Ignoring this warning leaves your organization exposed to two primary security vector risks:<\/p>\n\n\n Local XML export backups contained in .zip files store unencrypted instance data\u2014including project details, internal user comments, personal identifiable information (PII), and intellectual property. If a rogue user or malicious actor gains access to the underlying web server filesystem, they can exfiltrate your entire Jira database in a single download. If an attacker compromises your application server, local backups are sitting ducks. Attackers can delete or encrypt these backup files alongside your live data. When disaster strikes, you lose both your live production instance and your recovery point\u2014leaving you with zero fallback options. Atlassian recommends replacing local filesystem backups with enterprise-grade backup strategies. Here are four steps you can take:<\/p>\n\n\n Move all existing .zip files out of If Jira’s built-in Scheduled Backup <\/b>feature is enabled, it will continuously generate new local .zip files and trigger the health check warning repeatedly.<\/p>\n\n\nDiscontinue relying on built-in XML exports as your primary disaster recovery method for large production environments.\n\n\nIf you must keep them running, set up an automated script to immediately transfer generated backups off the Jira filesystem to a secure repository as soon as they are created.\n\n\n\n\n\n\n\n For production environments, best practices dictate using database-native backup tools (e.g., PostgreSQL, Oracle, or MySQL native utilities) combined with regular snapshotting of shared and local home directories. This provides faster recovery point objectives (RPO) and recovery time objectives (RTO) without leaving exposed XML dumps on the web application tier. If you are running Jira 9.16 or newer, Jira natively supports storing XML backups directly in Amazon S3 buckets. This ensures backups bypass local application disks altogether while taking advantage of AWS encryption and access policies. Fixing local backup security is just one piece of keeping Jira fast, compliant, and secure. Over time, Jira environments accumulate orphan schemes, unindexed custom fields, permission leaks, and performance bottlenecks that slow down your teams and increase security risks.\nAs an Official Atlassian Solution Partner in India,<\/b> we help engineering and IT leaders optimize, secure, and scale their Atlassian footprint.\n<\/p>\n We are currently offering Free Comprehensive Jira Health Checks for businesses in India. Our certified Atlassian experts will run a full audit of your environment, covering:<\/p>\n\nSecurity & Compliance:<\/b> Directory permissions, user access hygiene, and backup security risks.\nPerformance Optimization:<\/b> Index health, database query efficiency, and custom field bloat.\nLicense & App Audits:<\/b> Uncover unused licenses and optimize Marketplace app spending.\nData Center & Cloud Readiness:<\/b> Migration assessment and best-practice checks.\n\n\n\n","protected":false},"excerpt":{"rendered":" Issue Risk Level Best Action Local .zip files in Jira directories High Move files to secure off-server storage immediately. Active XML scheduled backups Medium Transition to database-native backups or automated offloading. Unmonitored Jira System Health High Conduct periodic health checks to catch security risks early.<\/p>\n","protected":false},"author":1,"featured_media":744,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"pagelayer_contact_templates":[],"_pagelayer_content":"","footnotes":""},"categories":[12],"tags":[],"class_list":["post-741","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-project-management-tools"],"jetpack_featured_media_url":"https:\/\/preflexsol.com\/blog\/wp-content\/uploads\/2026\/07\/Jira-health-check-Blog-600x-450px.png","_links":{"self":[{"href":"https:\/\/preflexsol.com\/blog\/wp-json\/wp\/v2\/posts\/741","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/preflexsol.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/preflexsol.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/preflexsol.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/preflexsol.com\/blog\/wp-json\/wp\/v2\/comments?post=741"}],"version-history":[{"count":5,"href":"https:\/\/preflexsol.com\/blog\/wp-json\/wp\/v2\/posts\/741\/revisions"}],"predecessor-version":[{"id":752,"href":"https:\/\/preflexsol.com\/blog\/wp-json\/wp\/v2\/posts\/741\/revisions\/752"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/preflexsol.com\/blog\/wp-json\/wp\/v2\/media\/744"}],"wp:attachment":[{"href":"https:\/\/preflexsol.com\/blog\/wp-json\/wp\/v2\/media?parent=741"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/preflexsol.com\/blog\/wp-json\/wp\/v2\/categories?post=741"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/preflexsol.com\/blog\/wp-json\/wp\/v2\/tags?post=741"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/p>\n\n\n\nWhy Is Storing Backups on the Jira Server Dangerous?<\/h2>\n\n\n
1. Unencrypted Data Exposure<\/h3>\n\n\n
<\/p>\n\n\n2. Ransomware & Cyber Attack Vulnerability<\/h3>\n\n\n
<\/p>\n\n\n\n\n\n\n4 Ways to Resolve the Local Backup Security Warning<\/h2>\n\n\n
1. Immediately Relocate Existing Backups<\/h3>\n\n\n
2. Review and Adjust Scheduled XML Backups<\/h3>\n\n
3. Implement Database-Native Backup Policies (Recommended)<\/h3>\n\n\n
<\/p>\n\n\n4. Offload XML Backups to Amazon S3 (Jira 9.16+)<\/h3>\n\n\n
<\/p>\n\n\n\n\n\n\nKey Takeaways for Jira Admins<\/h2>\n\n\n\n\n
Issue<\/th> Risk Level<\/th> Best Action <\/th><\/tr><\/thead> Local .zip files in Jira directories<\/strong><\/td> High<\/td> Move files to secure off-server storage immediately.<\/td><\/tr> Active XML scheduled backups<\/strong><\/td> Medium<\/td> Transition to database-native backups or automated offloading.<\/td><\/tr> Unmonitored Jira System Health<\/strong><\/td> High<\/td> Conduct periodic health checks to catch security risks early.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n How Healthy Is Your Jira Instance? Find Out for Free.<\/h2>\n
Get a Free Jira Health Check!\n<\/h3>\n