MongoDB migration clarification

This commit is contained in:
alnoam 2022-02-13 19:40:04 +02:00
parent 584ca23fda
commit ed92d5d250
4 changed files with 8 additions and 8 deletions

View File

@ -57,8 +57,8 @@ This section contains the steps to upgrade **ClearML Server** on the new AWS ins
1. On the old AWS instance, [backup your data](clearml_server_aws_ec2_ami.md#backing-up-and-restoring-data-and-configuration)
and, if your configuration folder is not empty, backup your configuration.
1. If upgrading from **Trains Server** version 0.15 or older, a data migration is required before upgrading. First follow
these [data migration instructions](clearml_server_es7_migration.md), and then continue this upgrade.
1. If upgrading from ClearML Server version older than 1.2, you need to migrate your data before upgrading your server. See instructions [here](clearml_server_mongo44_migration.md).
If upgrading from Trains Server version 0.15 or older, a data migration is required before continuing this upgrade. See instructions [here](clearml_server_es7_migration.md).
1. On the new AWS instance, [restore your data](clearml_server_aws_ec2_ami.md#backing-up-and-restoring-data-and-configuration) and, if the configuration folder is not empty, restore the
configuration.

View File

@ -8,7 +8,6 @@ title: Google Cloud Platform
docker-compose -f docker-compose.yml down
1. If upgrading from ClearML Server version older than 1.2, you need to migrate your data before upgrading your server. See instructions [here](clearml_server_mongo44_migration.md).
1. If upgrading from **Trains Server** version 0.15 or older to **ClearML Server**, do the following:
1. Follow these [data migration instructions](clearml_server_es7_migration.md),
@ -18,6 +17,7 @@ title: Google Cloud Platform
sudo mv /opt/trains /opt/clearml
1. If upgrading from ClearML Server version older than 1.2, you need to migrate your data before upgrading your server. See instructions [here](clearml_server_mongo44_migration.md).
1. We recommend [backing up data](clearml_server_gcp.md#backing-up-and-restoring-data-and-configuration) and, if the configuration folder is
not empty, backing up the configuration.

View File

@ -33,10 +33,10 @@ For backwards compatibility, the environment variables ``TRAINS_HOST_IP``, ``TRA
docker-compose -f docker-compose.yml down
1. If upgrading from ClearML Server version older than 1.2, you need to migrate your data before upgrading your server. See instructions [here](clearml_server_mongo44_migration.md).
1. If upgrading from **Trains Server** version 0.15 or older, a data migration is required before continuing this upgrade. See instructions [here](clearml_server_es7_migration.md).
1. If upgrading from ClearML Server version older than 1.2, you need to migrate your data before upgrading your server. See instructions [here](clearml_server_mongo44_migration.md).
1. We recommend [backing up data](clearml_server_linux_mac.md#backing-up-and-restoring-data-and-configuration) and, if the configuration folder is
not empty, backing up the configuration.

View File

@ -16,10 +16,10 @@ title: Windows
docker-compose -f c:\opt\trains\docker-compose-win10.yml down
1. If upgrading from ClearML Server version older than 1.2, you need to migrate your data before upgrading your server. See instructions [here](clearml_server_mongo44_migration.md).
1. If upgrading from **Trains Server** version 0.15 or older, a data migration is required before continuing this upgrade. See instructions [here](clearml_server_es7_migration.md).
1. If upgrading from ClearML Server version older than 1.2, you need to migrate your data before upgrading your server. See instructions [here](clearml_server_mongo44_migration.md).
1. We recommend backing up data and, if the configuration folder is not empty, backing up the configuration.
:::note