Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Once the installation is complete, or whenever you select the installed app from the list going forward, you can reach the app configuration menu on the left, under BACKUP CENTER.

...

Backup Center Configuration

From the Apps menu, select Configuration to setup the connectivity and storage parameters.

Setting Atlassian credentials

In order to use the Backup for Jira Cloud app you need to enter an Atlassian API token - this token is required in order to enable the app access to backup functionality. To obtain a token, go to the Atlassian website page - HERE.

Click the button Create API token. In the popup that appears enter a name for your token.

...

When you click Create, you should have access to your token.

...

Click Copy to copy the token string to your clipboard. Then, paste it in the app configuration Atlassian API Token field. If at any point in the future you want to change the token, you can create a new one and use it. Always make sure you keep your key securely.

Essentially, you can now click the button Save and this is all that you need to you to get the app to start creating basic backup snapshots and keep the 10 most recent ones. The rest of the configuration steps allows you to tailor your backup in more details to your needs.

Atlassian credentials

...

In the Email address field, enter your Jira user email address.

Backup schedule

The Backup Center app supports two types of backup snapshots. The Basic type includes all the site projects and issue data, without images and attachments. The Extended type includes images and attachments. Naturally, the extended backup file size is significantly larger than the basic one. In addition Jira prevents creating an extended backup if any other backup was performed in the preceding 48 hours. The app supports saving basic, extended, or a combination of two, with a timing schema that supports the extended backup constraints.

If you choose the Basic backup, it will be triggered daily. Extended backup will be triggered three times a week. The Combined schema will create basic backups with a once a week extended one.

Backup time: You can choose the time of day in which the backup is running, with default value of midnight (the exact running times may vary slightly). The time zone of this field is taken as the setup in your Jira site.

Number of backup files to keep: this is the maximum number of files that will be saved in the storage. The default value is 10. Once this number is reached, files are being rotated, where the oldest file is removed whenever a new one is created.

Storage configuration

The default Managed storage space for the backup was created for you by the app. This cloud storage keeps your most recent backup snapshot files, up to the number of files that you configured, or up to the storage quota allocated for you. Currently the storage quota is 20GB. Note that this quota may be reached eventually if you specify a very large number of backup files to preserve. If you reached the quota you can reach Addon Experts Center for a paid increase of storage. Also note that you can download backup files from the storage and delete them as you wish.

Alternatively you can use your own, network connected, FTP storage server to store your backup files. We support the FTP, FTPS and SFTP protocols. To use such a configuration make sure you have a server ready, and get the following parameters that are necessary to define the secure access and communication method. Once you have the information about that storage, enter the information bellow.

  • Protocol Type: the backup can use FTP, FTPS or Secure FTP.

  • Storage target: the server to which the backup is delivered. You can use an IP address or a domain name.

  • Storage port: the network port that the backup is using. Default is the standard port 21 for FTP.

  • Storage username and password: your FTP server credentials.

Once you completed configuring your backup, snapshots should be created automatically and saved in storage.