The Database Instances page provides an overview of the current source types that have been scanned and uploaded into mConsole, the OpEx and rCapEx of retaining or retiring the existing sources, and the total OpEx (Current and Future) and rCapEx (Current and Future) costs for all sources that have been selected to be migrated, retained or retired within the project.
The page displays the sections:
The Database Instances section allows defining which sources will be migrated, modernized, retained or retired. This designation determines the OpEx and rCapEx costs displayed on this page as well as on the Project Details page and the TCO Projects page. Any changes made in the Migrating tab also impact the Cloud Instances section. Any changes made in the Migrating, Retained and Retiring tabs are reflected on this page as well as on the Project Details page and the TCO Projects page.
Choose Projected Pathway for Source
Each source on the TCO dashboard is assigned a Projected Pathway based on the future plans for this source. Sources can go down a path of Migration (Modernization), Retention, or Retirement.
During the migration project, the sources in this pathway will be migrated from their current environment.
The pathway selected for the available sources influences the data shown on the relevant sections of the Database Instances page:
Sources selected for migration, retention, or retirement, sorted by the engine type.
Duration of the migration.
Projected future costs due to migration, retention, or retirement.
To configure a source to follow the Migration pathway:
Select the Migrating tab and click Add. The instance settings window opens.
Select sources from the Choose databases to migrate list. Optionally, apply filtering to find sources by their names and other parameters. The filter is applied to values from any of the columns.
Fill in the Additional info section fields:
Select Instance from the dropdown list of created instances or create a new instance. Mind the instance limits.
If selecting the instance from the dropdown list, click Confirm.
If creating a new instance, fill the form, specifying:
Instance Name (shall be unique)
Depending on the target platform, fill in other required fields. For more details about creating target instances, see Cloud Instances.
4. Click Confirm.
Target Instance Limits
The values of cloud instance resources are not editable by design. They are calculated automatically based on the sources selected for migration to the cloud instance.
The ranges below the values show basic requirements and limitations that the target platform and engine impose. These ranges are considered while adding sources to the same cloud instance. In case a source is added that exceeds the resource limits of the selected target cloud instance capability, the Instance Group and Target Engine fields of the New Instance form are cleared, the Confirm button becomes disabled, and the following message appears:
The total resources required to host your selection are higher than the available resources on the target. Please remove sources from your selection to meet the limit set by the cloud platform.
The values exceeding the range are highlighted in red.
If an attempt is made to add an extra source which would exceed the resource limits of an existing instance, both the instance name in the Instance list and the Confirm button become disabled, and the following message appears:
The instance has reached its resources limit.
To enable adding of the sources to the instance, uncheck some of the selected sources from the Choose databases to migrate list and fill the cleared fields of the New Instance form.
Retained sources are planned to remain in their current location both during and after the migration project.
To configure a source for retention:
Select the Retained tab and click Add. The retention settings window opens.
In the window, select sources from the Choose databases to retain list. Optionally, apply filtering to find sources by their names and other parameters.
In the Additional info section, select the Instance Group.
Retiring sources are planned to retire after a known period of time, set as the retirement time. The retirement date can be during or after the migration project ends.
To configure a source for retirement:
Select the Retiring tab and click Add. The retirement settings window opens.
In the window, select sources from the Choose databases to retire list. Optionally, apply filtering to find sources by their names and other parameters.
In the Additional info section:
Select the Instance Group.
Set the retirement term (3-24 months) from the Retire In dropdown list.
To remove sources:
Select the Migrating, Retained, or Retiring tab.
From the list, select sources to remove
If a source is removed from the Migrating, Retained, or Retiring tabs, all selected sources are removed from the project and return back to Database Inventory as Unassigned.
To confirm the removal, click Confirm in the popup window.