Add Data Center / Server
- Gia Jgarkava
You can add Data Center or Server instance to backup schemas from from there and also restore schemas into the DC/Server instance.
To enable this feature, DC/Server app, Insight Assets Cloud Migration Assistant, should be installed on the source DC/Server instance with internet access. If you need to grant network access only to Insighit Assets Backup and Migration Cloud app, please contact us.
After the Insight Assets Cloud Migration Assistant is installed on the source DC/Server instance, you can add DC/Server instance for syncing the schemas by clicking “Add new“ button in the Cloud app:
Configuration of connection with DC/Server
After clicking the button, you will see a popup with the necessary fields:
Connection name
Choose a name for the connection
Base URL
DC/Server URL (the URL must be public so that it can be accessed from Cloud)
API Token
Atlassian API token secures account access to the API. You can create a token, through the following URL: Atlassian account - API Tokens. You can read more about Atlassian API Token on the documentation page: Manage API tokens for your Atlassian account | Atlassian Support.
After creating an API Token, just copy and paste it into the corresponding “API Token“ field on the configuration page.
All fields are mandatory.
After clicking the Add button, the instance will be added to the “Data Center / Server to migrate” section:
The ATTACHMENTS MIGRATION shows whether migration of attachments is enabled for the DC/Server instance and what is the current status. See Backup and Restore of object Attachments for more details.
You can also authorize DC/Server with username/password. To do so, click “For Jira Core version below 8.14, use username/password authentication“ toggle and enter username and password:
To use username/password, Basic authentication should be enabled on the DC/Server instance: Disabling basic authentication | Atlassian Support.
After clicking the Add button, the instance will be added to the “Data Center / Server to migrate” section.
Please use the public address, where your Jira DC instance can be reachable from the internet, for example “localhost” address will not work. In addition, if your Jira DC URL is redirected to another address, please use URL that is the final destination (i.e. address of Jira instance). e.g. if the URL (servicedesk.yourcompany.com) is redirected to yourcompany.com/jira, please use the latter (yourcompany.com/jira). If the DC/Server instance is not publicly accessible from the internet, please contact us to receive the required information for whitelisting the app IPs on your server/firewall.
For secure connection with DC/Server, HTTPS, SSL/TLS certificates are used to encrypt the communication. Make sure to have a valid public certificate on your DC/Server.
Due to the known issue with seevral versions of Jira Server and Data Center, you may receive “PLUGIN NOT INSTALLED“ error, after adding the source instance.
Affected Jira versions:
8.14.0
8.15.0
8.22.3
If you have one of these versions, follow the Workaround 2 instructions on the corresponding Jira bug page: JRASERVER-72209:
Workaround 2
Disable websudo (secure administrator sessions) following the steps here :
To edit the configuration, click “three dots“ and select Edit Configuration. You will see the same three fields, which you can modify. You can delete the instance by “three dots“ and selecting Delete. After clicking Delete on the confirmation backup, the instance will be deleted from the list.
Sync schemas
After the connection is added, click Sync schemas and you will see the DC/Server schemas in the Synched schemas list - Server/DC schemas will be indicated and DATA-CENTER under the “Location“ column:
With the trial license of Insight Assets Cloud Migration Assistant, only 50 objects and 10 Asset custom fields can be backed up!
To further migrate the DC/Server schemas into the Cloud or another DC/Server, please see Restore & Migration Guide.
If you are migrating from Server to Cloud, the “Text“ attributes may contain more than 255 characters. In such case, after the migration, the objects containing more than 255 characters in this attribute, will not be restored. If this happens, you need to change the affected attribute type “Text“ to “Text Area“ on the Cloud and Restore only affected specific object types in the existing schema: Restore & Migration Guide | Existing schema.