You can also backup schemas from other cloud instances for further restore and migration.
| Info |
|---|
To enable this feature, DC/Server app, Insight Assets Cloud Migration Assistant, should the app should also be installed on the source DC/Server cloud 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:
...
. |
Click “Add new“ button to add a source cloud instance:
...
After clicking the button, you will see a the popup with the necessary fields needed to be filled:
...
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
...
To easily identify the instance while migrating the schemas
Email
Fill in the email related to the Atlassian account that will be used to access the data in Assets (Insight) for a source instance (the user should have a valid admin role!)
Source WorkspadeID
Fill in the ID of the Assets (Insight) workspace you want to backup to. The Workspace ID can be found on the following link: https://[yourcloud].atlassian.net/rest/servicedeskapi/assets/workspace. The Jira Service Management REST API uses the workspace ID to identify your individual instance of Assets (Insight), it is an alphanumeric string with the following sample appearance:
3b3b70g5-66f8-3c01-a2d7-e5bbf2584dc3.
Source Instance URL
URL of source instance: https://[yourcloud].atlassian.net
Make sure to include “https://“ in the URL, otherwise you will not be able to save the instance.
You also won't be able to save the URL if you indicate https:// but in reality the URL does not support https://
Keep in mind, that you cannot use bypass like
localhostorlocaltest.me
Source Token
Token for the source instance: you can create a token through the following URL: Atlassian account - API Tokens. You can read more about Atlassian
...
tokens on the documentation page: Manage API tokens for your Atlassian account | Atlassian Support.
After creating
...
a token, just copy and paste it into the corresponding
...
“Source Token“ field
...
.
After clicking the Add button, the instance will be added to the “Data Center / Server to migrate” section:
...
| Info |
|---|
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:
...
After clicking the Add button, the instance will be added to the “Data Center / Server to migrate” section.
| Info |
|---|
Please use the public address, where your Jira DC instance can be reachable from internet, for example “localhost” address will not work. In addition, if your Jira DC URL redirected to another address, please use URL which 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). |
| Note |
|---|
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:
If you have one of these versions, follow the Workaround 2 instructions on the corresponding Jira bug page: JRASERVER-72209: Workaround 2Disable 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.
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:
...
| Info |
|---|
With the trial license of Insight Assets Cloud Migration Assistant, only 50 objects can ba backed up! |
To further migrate the DC/Server schemas into the Cloud, please see Restore & Migration Guide.
...
filling in the necessary information, click the Save source instance button to add the instance to the list.
After the instance is added, you can see and modify it from the Cloud instances to migrate.
...
When the cloud instance is added, you can click “Sync schemas“ button and all the schemas from the selected source instance will be synced and displayed in the Synced Schemas grid. The schemas from the source cloud instances will have ANOTHER CLOUD under Location and Instance name under Instance. You can also filter the schemas by the instance or location:
...
When the schemas are synced, you can back up and restore the schemas like the schemas from the current instance. Please see the detailed instructions on the following pages
You can edit the configuration of the source cloud, or delete the instance from the list, by clicking “. . .“ icon along the source instance:
...
| Info |
|---|
When the source instance is removed from the list, all the schemas and the corresponding backups will be also deleted. |