You are viewing documentation for Structure Server and Data Center version 5.6 and patch releases. For other versions, see Version Index or [Structure Cloud].
Automatic Structure maintenance runs daily and performs Structure backup and database optimization. The optimization removes stale data from the database and may improve general Jira responsiveness.
Automatic maintenance can be run only with a valid Structure license.
To configure automatic Structure maintenance:
Select the maintenance schedule
By default, scheduled maintenance is enabled and set to run daily at 3 AM.
You have several options to specify a maintenance schedule:
Run every day at a specified time
The time is specified in the server's time zone, displayed near the time fields.
Question mark ( ? ) is used instead of '*' for leaving either day-of-month or day-of-week blank.
0 * * * * = the top of every hour of every day.
*/10 * * * * = every ten minutes.
0 8-10 * * * = 8, 9 and 10 o'clock of every day.
0 6,19 * * * = 6:00 AM and 7:00 PM every day.
0/30 8-10 * * * = 8:00, 8:30, 9:00, 9:30, 10:00 and 10:30 every day.
0 9-17 * * MON-FRI = on the hour nine-to-five weekdays.
0 0 25 12 ? = every Christmas Day at midnight.
Backup Structure data | Creates a backup of the Structure database in the
It is recommended that you maintain separate Structure backups, even though Structure data is backed up with Jira's normal backup, because this will allow you to restore from that data without rolling back changes in Jira. |
---|---|
Delete old backups | A backup is considered old if it is not among X latest backups (X is specified by the first parameter of this task) and it was made earlier than Y days ago (Y is specified by the second parameter). This task removes all such backups made by the Backup task.
|
Optimize favorites | If a user marks a structure as their favorite, Structure will keep this mark, even if the user is later deleted from Jira, and the popularity number of the structure will still accounts for that user. This task removes marks made by users no longer in Jira and recounts the structure popularity. |
Optimize structures | If an issue is added to a structure and then deleted from Jira, the structure will still contain a reference to this issue (although it will not display it). This task removes references to deleted issues and other items that have become permanently unavailable. |
Optimize view settings | If a view is deleted, some structure view settings may still reference it, and a blank view named ? (Unknown View) will be shown in its place. This task removes references to deleted views. |
Optimize synchronizers | This removes an data related to synchronizers of a deleted structure. |
Delete old synchronizer audit log records | This removes old records from the Synchronizer Audit Log, clearing up space in the database. Parameters:
If you set X to 0, the maintenance procedure will remove all records. |
Reindex change history | Currently does nothing. This task has remained as an option since Structure 2. Its purpose may be restored in a later version of Structure. |
Optimize structure perspectives | Removes old perspectives that haven't been used by anyone for a certain amount of time. Parameters:
|
Reindex structures | Clears and recalculates issue-to-structure index, used to define which structures contain a specific issue. (Issues added with Automation are not counted.) |
Delete old change history | The task removes old records from the change history. A history record is considered old if the change was made earlier than X days ago (X is specified by the first parameter) and it is not among the Y latest history records for the structure where the change was made (Y is specified by the second parameter). Parameters:
|
You can run specific maintenance tasks at any time.
To run maintenance manually:
Running maintenance manually does not affect the automatic maintenance settings or schedule.