JIRA Disaster Recovery file replication process
プラットフォームについて: サーバーと Data Center のみ。この記事は、サーバーおよび Data Center プラットフォームのアトラシアン製品にのみ適用されます。
This article provides additional information on how the replication process functions when JIRA Data Center is configured to use a secondary folder for file replication as per the Disaster Recovery Guide for Jira.
When file replication is enabled, files are not simultaneously written to both the primary and secondary locations. Instead, JIRA monitors the primary home for changes to the selected file types (attachments, avatars, index snapshots, and/or user-installed add-ons) and then queues these changes for asynchronous replay to the secondary location. New files are copied from the primary home to the secondary location, and move/delete operations are mirrored to the secondary location.
For attachments, avatars, and index snapshots these operations are instantaneous. For add-ons, however, the copy/move/delete operation is performed once the replication queue has been idle for 60 seconds.
Configuration files on Jira Installation Directory are not synchronized automatically. The system administrator needs to ensure the application configuration customizations are properly applied on the Disaster Recovery instance.