From 94af090f774ad3839ec0ebaf0bc730497c09c04c Mon Sep 17 00:00:00 2001 From: MicJ <92740932+micjohnson777@users.noreply.github.com> Date: Tue, 29 Oct 2024 11:10:59 -0400 Subject: [PATCH] 1430 24.10 migration article updates (#3145) * PD-1403 Remove 24.10 Migration Articles and Add MigrateCOREtoSCALE24_04.md Snippet to 24.10 Index This PR deletes the migration articles from the 24.10 branch, adds a new snippet with instructions on the only migration path and replaces the text in the /gettingStarted/Migrate/_index.md file with the new snippet. This snippet also goes into the Master branch file. * PD-1430 Fix broken links to deleted files * PD-1430 Add Aliases in 24.10 This commit adds the aliases for the deleted migration files. * PD-1430 Change Migration information in 24.10 This commit changes the content in the migration section of the 2410 getting started guide by adding back the deleted files, adds the new snippets MigrateCOREtoSCALE24_04.md and WhatDoesNotMigrate.md, and updates the content in the MigratePrep.md and MigrateCOREtoSCALE.md article. * PD-1430 Fix snippets in 24.10 * Update MigrateCOREtoSCALE24_04.md fix spelling * Update FirstTimeLogin.md revert to old links in to migration articles in the 24.10 branch * Update FirstTimeLogin.md revert line 97 to 24.10 migration links * Update FirstTimeLogin.md Revert changes in line 88 back to 24.10 article links instead of 24.04 * Update _index.md Revert link in like 39 back to 24.10 article instead of 24.04 * Update AFPMigration.md Revert reference in line 31 back to 24.10 instead of 24.04 * Update UpdateHASCALE.md Revert line 17 removing reference to 24.04 * PD-1430 Fix Link to MigratePrep.md. * Update MigratePrep.md - copy editing * Update MigratingFromCORE.md Copy edit and clean up the Migration Methods text. * Update MigrateCOREtoSCALE24_04.md update copy for 24.04 cutoff on update trains. * Update WhatDoesNotMigrate.md * Update MigratingFromCORE.md * Update MigratePrep.md --------- Co-authored-by: Tim Moore --- .../GettingStarted/Migrate/ComponentNaming.md | 4 +- .../Migrate/MigrateCOREHAtoSCALEHA.md | 2 +- content/GettingStarted/Migrate/MigratePrep.md | 138 +++--------------- .../Migrate/MigratingFromCORE.md | 93 +++--------- .../Migrate/SCALEZFSFlagRemoval.md | 10 -- content/GettingStarted/Migrate/_index.md | 4 +- static/includes/MigrateCOREtoSCALE24_04.md | 6 + static/includes/WhatDoesNotMigrate.md | 24 +++ 8 files changed, 75 insertions(+), 206 deletions(-) delete mode 100644 content/GettingStarted/Migrate/SCALEZFSFlagRemoval.md create mode 100644 static/includes/MigrateCOREtoSCALE24_04.md create mode 100644 static/includes/WhatDoesNotMigrate.md diff --git a/content/GettingStarted/Migrate/ComponentNaming.md b/content/GettingStarted/Migrate/ComponentNaming.md index 664a7baa20..0a6358470d 100644 --- a/content/GettingStarted/Migrate/ComponentNaming.md +++ b/content/GettingStarted/Migrate/ComponentNaming.md @@ -37,6 +37,4 @@ TrueNAS SCALE uses **bond** followed by a number (bond1). {{}} -See the [TrueNAS Systems](https://www.truenas.com/docs/hardware/) section for lists of the default port names for each platform. - - +See the [TrueNAS Systems](https://www.truenas.com/docs/hardware/) section for lists of the default port names for each platform. \ No newline at end of file diff --git a/content/GettingStarted/Migrate/MigrateCOREHAtoSCALEHA.md b/content/GettingStarted/Migrate/MigrateCOREHAtoSCALEHA.md index b72574e75e..6fd63c54bc 100644 --- a/content/GettingStarted/Migrate/MigrateCOREHAtoSCALEHA.md +++ b/content/GettingStarted/Migrate/MigrateCOREHAtoSCALEHA.md @@ -22,4 +22,4 @@ The process requires: Review the [Migration Preparation article]({{< relref "MigratePrep.md" >}}) to see detailed notes and caveats about the migration process. -{{< include file="/static/includes/iXsystemsSupportContact.md" >}} +{{< include file="/static/includes/iXsystemsSupportContact.md" >}} \ No newline at end of file diff --git a/content/GettingStarted/Migrate/MigratePrep.md b/content/GettingStarted/Migrate/MigratePrep.md index 35105c9aa0..fffa50d25e 100644 --- a/content/GettingStarted/Migrate/MigratePrep.md +++ b/content/GettingStarted/Migrate/MigratePrep.md @@ -2,40 +2,39 @@ title: "Preparing to Migrate" description: "Guides CORE users through preparation elements and steps before beginning the one-way CORE to SCALE migration process." weight: 10 +aliases: tags: - migrate -keywords: -- nas storage software -- data migration -- enterprise data storage solution -- backup strategies --- +{{< enterprise >}} +CORE Enterprise customers should contact iXsystems Support for assistance with the process of moving from CORE to SCALE, especially customers with HA systems. + +{{< expand "Contacting Support" "v" >}} +{{< include file="/static/includes/iXsystemsSupportContact.md" >}} +{{< /expand >}} +{{< /enterprise >}} {{< include file="/static/includes/MigrateCOREtoSCALEWarning.md" >}} ## What can or cannot migrate? -{{< include file="/static/includes/COREMigratesList.md" >}} +{{< include file="/static/includes/WhatDoesNotMigrate.md" >}} ## Preparing for Migration -Read this article before you attempt to migrate your CORE system to a SCALE major version. + +Read this article before you attempt to migrate your 13.0-U6.x system to TrueNAS 24.10. + {{< hint type="warning" title="Using USB Devices for Backups" >}} We strongly recommend not using USB flash drives or USB-attached drives for backups as these can have issues, including with recovering backed up files. For more information on using USB drives and devices in general, read the [CORE Hardware Guide](https://www.truenas.com/docs/core/gettingstarted/corehardwareguide/). If you must use a USB type device, verify you can access files on the device before you upgrade/migrate to SCALE. {{< /hint >}} -{{< enterprise >}} -Enterprise customers are encouraged to contact Support for assistance with the process of moving from 13.0 to 24.04, especially customers with HA systems. -{{< /enterprise >}} -1. Upgrade your CORE system to either the latest 13.0 or 13.3 release. - TrueNAS Enterprise-licensed (or community systems that haven't switched to 13.3) systems on 12.0x or earlier should upgrade to the latest 13.0 release (e.g 13.0-U6.2 or newer) prior to migration. - Community users with 13.3 installed should update to the latest maintenance release of that version prior to migration. - Either major version can use the [iso upgrade](#migrating-using-an-iso-file-to-upgrade) method for migration. +1. Upgrade your CORE system to the most recent publicly-available CORE major maintenance release version. + CORE systems at the latest 13.0 release can use the [iso upgrade](#migrating-using-an-iso-file-to-upgrade) method to migrate to SCALE. 2. Migrate [GELI-encrypted pools](https://www.truenas.com/docs/core/coretutorials/storage/pools/storageencryption/#geli-pool-migrations) to a non-GELI-encrypted pool before upgrading from CORE 12.0x or earlier releases! - If you do not migrate from GELI to ZFS encryption before upgrading to CORE 13.0-U# or migrating to SCALE you permanently lose access to the data in the GELI encrypted pool(s). 3. Verify the root user is not locked. Go to **Accounts > Users**, select the root user and click **Edit** to view current settings and confirm **Lock User** is not selected. @@ -43,11 +42,11 @@ Enterprise customers are encouraged to contact Support for assistance with the p 4. Write down, copy, or take screenshots of settings to use in the event of a post-upgrade/migration issue or to duplicate in SCALE. Use the checklist below to guide you through this step: + Check the release notes for each major release version. Release notes contain information on feature changes and deprecated services you need to be aware of. Record the settings for deprecated services, and take the steps documented in the release notes to deploy an alternate solution if you choose. + System dataset - Identify your system dataset. If you want to use the same dataset for the system dataset in SCALE, note the pool and system dataset. When you set up the first required pool on SCALE import this pool first. - Deprecated services - Record the settings for [services deprecated in SCALE](#deprecated-services-in-scale). - VMs - If you have virtual machines configured in CORE, write down or screenshot network and other setting information. Plugins or jails - Plugins and jails do not migrate. Record settings for each plugin/jail and back up the data associated with each. @@ -68,12 +67,7 @@ Enterprise customers are encouraged to contact Support for assistance with the p Data protection tasks - Write down or take screenshots of replication, periodic snapshot, cloud sync, or other task settings to reconfigure these in SCALE if you want to duplicate these tasks. -5. Remove all CORE SMB auxiliary parameter settings before migrating to SCALE. - As of 23.10 SCALE COBIA, the SMB **Auxiliary Parameters** option is no longer available in the UI. - Attempting to migrate with these settings can result in broken SMB shares post upgrade that require access to the CLI to fix. - We recommend removing these unsupported settings before migrating from CORE to SCALE. - -6. Write down or take screenshots of your network configuration information. +5. Write down or take screenshots of your network configuration information. Capture the global network settings, interfaces (LAGG, VLAN, bridge settings), static IP addresses, and aliases. FreeBSD and Linux use different nomenclature for network interfaces, bridges, LAGGs, and VLANs. @@ -86,106 +80,16 @@ Enterprise customers are encouraged to contact Support for assistance with the p If there are issues after a clean install of SCALE from an iso file or you are not using DHCP for network and interface configuration, use the information from your CORE settings to configure your SCALE network settings and to reconfigure your static IPs or aliases. {{< include file="/static/includes/NetworkInstallRequirementsSCALE.md" >}} -7. Migrate the deprecated S3 MinIO service (if in use). See [services deprecated in SCALE](#migrating-from-deprecated-services). +6. Migrate the deprecated S3 MinIO service (if in use). See [services deprecated in SCALE](#migrating-from-deprecated-services). This is a lengthy process depending on the amount of data stored while using the S3 service. Read and follow instructions in [Migrating MinIO Data from CORE to SCALE](https://www.truenas.com/docs/solutions/miniocoretoscale/)! + Make sure S3 MinIO data is backed up as a precaution. The migration process from the S3 service requires first [migrating to the MinIO plugin in TrueNAS CORE](https://www.truenas.com/docs/core/13.0/coretutorials/jailspluginsvms/plugins/minioplugin/#migrating-from-s3-service-to-minio-plugin), migrating from CORE to SCALE, then installing the SCALE MinIO app and importing S3 data. -8. Back up any critical data. +7. Back up any critical data. -9. Download your [system configuration file](https://www.truenas.com/docs/core/coretutorials/systemconfiguration/usingconfigurationbackups/) and a [debug file](https://www.truenas.com/docs/core/uireference/system/advanced/). +8. Download your [system configuration file](https://www.truenas.com/docs/core/coretutorials/systemconfiguration/usingconfigurationbackups/) and a [debug file](https://www.truenas.com/docs/core/uireference/system/advanced/). After updating to the latest publicly-available release of CORE and making any changes to CORE user accounts or any other settings download these files and keep them in a safe place and where you can access them if you need to revert to CORE with a clean install using the CORE iso file. After completing the steps that apply to your CORE system listed above, download the [SCALE ISO file](https://www.truenas.com/download-tn-scale/) and save it to your computer. -See [Software Releases](https://www.truenas.com/docs/softwarereleases/#upgrade-paths) for current recommended update paths to make sure you download and migrate to the correct SCALE version. Burn the iso to a USB drive (see **Installing on Physical Hardware** in [Installing SCALE]({{< relref "InstallingSCALE.md#installing-on-physical-hardware" >}})) when upgrading a physical system. - -## Deprecated Services in SCALE -The built-in services listed in this section are available in 13.0, but deprecated in 22.12.3 (Bluefin) and removed in later TrueNAS releases. -They require attention before attempting to migrate to 24.04. - -Each of the sections has information that can help you determine the best steps forward to secure any critical data before attempting to migrate from 13.0 to 24.04. -They provide details on transitioning from that service to an application with the functionality of the deprecated service. - -TrueNAS SCALE has [apps](https://www.truenas.com/docs/truenasapps/) you can deploy as replacements for these services. -SCALE 24.04 provides the option to force an upgrade without converting deprecated services to apps. -The force option is not recommended for the S3 service as forcing the upgrade results in losing access to and the ability to recover the MinIO S3 data. - -See [SCALE Bluefin Deprecated Services](https://www.truenas.com/docs/scale/22.12/gettingstarted/scaledeprecatedfeatures/) for more information. - -{{< expand "Migrating from DDNS Service" "v" >}} -Review and write down or take screenshots of your Dynamic DNS service provider, domain, IP address, port number, URL, and credential (username and password) settings to use when you reconfigure in a replacement app. -If establishing a new provider, create the user account before proceeding. Otherwise, use the existing provider details. - -To grant access to a specific user (and group) other than using the default admin user UID and GID, add a new non-root administrative user. -Note the UID and GID for this new user to enter in the application configuration screen. - -Install a replacement application such as **DDNS-Updater** using the CORE service settings from your notes. -SCALE suggests other applications to consider other than **DDNS-Updater** application. -{{< /expand >}} - -{{< expand "Migrating from OpenVPN Service" "v" >}} -Review your OpenVPN client and server service settings. -Take note of all certificate, device type, port, protocol, TLS crypt authentication, and additional parameter settings to use in a replacement app. - -A certificate configured on CORE should migrate to SCALE, but as a precaution, record the certificate authority (CA) and certificate settings, and make a copy of the the private and public keys the CA and certificate uses. - -Install a replacement application such as **WG Easy** using the CORE service settings from your notes. -SCALE suggests other applications to consider other than the **WG Easy** VPN application. -{{< /expand >}} - -{{< expand "Migrating from Rsync Service" "v" >}} -Review your rsync and module service settings. -Take note of all host path, access mode type, number of simultaneous connections, user and group IDs, allow and deny host addresses, and any auxiliary parameter settings. - -Before you configure a new rsync application like **Rsync Daemon** (Rsync-d), validate that it is needed. -When rsync is configured externally with SSH or using an rsync task in **Data Protection > Rsync Tasks**, and when **Rsync Mode** is set to SSH, the deprecated rsync service is not used or necessary for rsync to function. - -Install a replacement application such as **Rsync Daemon** using the CORE service settings from your notes. -SCALE suggests other applications to consider other than the **Rsync Daemon** application. -{{< /expand >}} - -{{< expand "Migrating from S3 MinIO" "v" >}} -You must migrate your S3 service and data before you upgrade or migrate from CORE to SCALE! - -If you have the S3 service configured in CORE, you must first [migrate to the MinIO plugin](https://www.truenas.com/docs/core/13.0/coretutorials/jailspluginsvms/plugins/minioplugin/#migrating-from-s3-service-to-minio-plugin). -After migrating from CORE to SCALE and then installing the [SCALE MinIO Enterprise app](https://www.truenas.com/docs/scale/scaletutorials/apps/enterpriseapps/minio/), you can import S3 data from the CORE plugin to the SCALE app. - -Review your S3 service settings. -Take note of the credentials (**Access Key** and **Secret Key**), and data storage volume and host path. - -If a certificate other than the default **freenas_default** is used, take note. -A certificate configured on CORE should migrate to SCALE, but as a precaution, record the certificate authority (CA) and certificate settings, especially any private and public keys the certificate uses. - -Follow the migration instructions provided in [Migrating MinIO Data from CORE to SCALE](https://www.truenas.com/docs/solutions/miniocoretoscale/). -This is an involved and time-consuming process with specific requirements. The amount of data being migrated determines how long this process takes. -{{< /expand >}} - -{{< expand "Migrating from TFTP Service" "v" >}} -Review your TFTP service settings. -Take note of all directory, host, auxiliary parameter, permission, and credential (username and password) settings. - -To grant access to a specific user (and group) other than using the default admin user UID and GID, add the new non-root administrative user. -Note the UID and GID for this new user to enter in the application configuration screen. - -To use a specific dataset or storage volume for files, create any new dataset in Bluefin before installing the application. -Install the replacement application such as **TFTP Server** (TFTP-HPA) using the CORE service settings from your notes. -SCALE suggests other applications to consider other than the **TFTP Server** (TFTP-HPA) application. -{{< /expand >}} - -{{< expand "Migrating from WebDAV Service and Shares" "v" >}} -Disable both the WebDAV share and service. -Also disable the **Start Automatically** option to prevent the service from re-enabling after a system restart. - -Review any existing WebDAV service authentication settings. -Take note of all IP addresses, port numbers, URLs and credentials (username and password). - -Remove any existing WebDAV shares. Go to **Shares > WebDAV** and use **Edit** to view any existing configurations. -Take note of the share name, path, and read only settings. Delete the WebDAV share configuration. - -In SCALE Bluefin: -To grant access to a specific user (and group) other than using the default admin user UID and GID, add a new non-root administrative user for the share(s). -Note the UID and GID for this new user to enter in the application configuration screen. - -After disabling the WebDAV service and clearing any existing share configurations from the **Shares > WebDAV** screen in Bluefin, install the **WebDAV** application to recreate your shares using the CORE service settings from your notes. Use the **webdav** user and group in control, and the UID and GID (**666**) in the application. -{{< /expand >}} \ No newline at end of file diff --git a/content/GettingStarted/Migrate/MigratingFromCORE.md b/content/GettingStarted/Migrate/MigratingFromCORE.md index 5971b091e2..81edf97b83 100644 --- a/content/GettingStarted/Migrate/MigratingFromCORE.md +++ b/content/GettingStarted/Migrate/MigratingFromCORE.md @@ -2,15 +2,10 @@ title: "Migrating TrueNAS CORE to SCALE" description: "Provides instructions on migrating from TrueNAS CORE to SCALE. Migration methods include using an ISO or manual update file." weight: 15 +aliases: tags: - migrate - install -keywords: -- enterprise data storage solution -- data migration -- nas data storage -- RAIDz -- spinning disk --- ## Migration Overview @@ -33,87 +28,37 @@ The process requires an extended maintenance window, requires executing steps in Depending on system configuration, migrating from CORE to SCALE can be more or less complicated. +{{< include file="/static/includes/RootToAdminUserAccount.md" >}} + ## Migration Methods {{< include file="/static/includes/MigrateCOREtoSCALEWarning.md" >}} ### Clean Install -You can migrate from CORE to SCALE with a clean install using an iso file. -With a clean SCALE install, you need to reconfigure your CORE settings in SCALE and import your data. -Follow the instructions in the [Install]({{< relref "InstallingSCALE.md" >}}) articles. - -When TrueNAS SCALE boots, you might need to [use the Console Setup Menu to configure networking interfaces]({{< relref "ConsoleSetupMenuScale.md" >}}) to enable GUI accessibility. -After logging in to the TrueNAS SCALE UI, use a system configuration file to restore the system settings to the SCALE installation and import the data storage pools. - -### Select SCALE Update Train - -This method is only available for non-Enterprise community systems. - -1. Go to **System > Update** - -2. From the **Train** dropdown, choose the latest stable TrueNAS SCALE release, 24.04 (Dragonfish) or newer. - -3. Review the SCALE migrations warning and verify the system is ready to migrate before confirming and continuing. - -4. When the latest update for that chosen TrueNAS release is loaded, click **Apply Pending Update** or **Download Updates** to begin the update process documented in [Updating SCALE]({{< relref "UpdateSCALE.md#performing-an-automatic-update" >}}). - It is strongly recommended to download the system configuration backup prior to starting the update. - -5. After the system installs the update and reboots, log in and review the system configuration to ensure the migration was successful. - -### Manual Update -Some CORE 13.0 releases can migrate using the CORE UI **Upgrade** function using a SCALE update file downloaded from the website. -To use this method, you must upgrade to the latest maintenance release. - -Earlier releases of CORE must upgrade to 13.0 and then the latest maintenance release (U6.2) to use this method. -For community users, 13.3 and the latest public release is acceptable. -If this process fails, retry using the iso file method above. - -1. Confirm that the TrueNAS CORE system is on the latest public release, 13.0-U6.2 (community users could have 13.3-RELEASE or newer installed). -2. Download the [SCALE manual update file](https://www.truenas.com/download-truenas-scale/). - See [Software Releases](https://www.truenas.com/docs/softwarereleases/#upgrade-paths) for current recommended update paths to make sure you download and migrate to the correct SCALE version. - -3. Click **CHECK FOR UPDATES** in the **System Information** card on the **Dashboard** or go to **System > Update**. - -4. Click **INSTALL MANUAL UPDATE FILE**. - - {{< trueimage src="/images/SCALE/SystemSettings/SidegradeInstallManualUpdate.png" alt="Install the Manual Upgrade" id="Install the Manual Upgrade" >}} - -5. Click **SAVE CONFIGURATION** to download a backup file that can restore the system configuration in the event something goes wrong with the migration. - - {{< trueimage src="/images/SCALE/SystemSettings/SidegradeSaveConfig.png" alt="Save the Config file" id="Save the Config file" >}} - -6. Select a **Temporary Storage Location** (either **Memory Device** or a **Pool**) for the manual update file. - Click **Choose File** and select the TrueNAS-SCALE.update file you downloaded. - - {{< trueimage src="/images/SCALE/SystemSettings/SidegradeSetInstallFile.png" alt="Settings for the Manual Upgrade" id="Settings for the Manual Upgrade" >}} - - Then click **APPLY UPDATE**. - -7. After the update completes, reboot the system if it does not reboot automatically. - - {{< trueimage src="/images/SCALE/SystemSettings/SidegradeRestart.png" alt="Reboot to Finish" id="Reboot to Finish" >}} - -After TrueNAS SCALE reboots, you might need to [use the Console Setup menu to configure the primary networking interfaces]({{< relref "ConsoleSetupMenuScale.md" >}}) to enable GUI accessibility. +You can migrate from 13.0-U6.x to 24.10 with a clean install using an iso file and 13.0 or 13.3 configuration file upload. +With a clean install, you need to review any settings imported from your configuration file and import your storage pools. +Follow the instructions in the [Install]({{< relref "InstallingSCALE.md" >}}) articles. -After gaining access to the UI, sign in with the admin user credentials created during installation. +After TrueNAS boots, you might need to [use the Console Setup menu to reconfigure networking interfaces]({{< relref "ConsoleSetupMenuScale.md" >}}) to enable GUI accessibility. +After logging in to the TrueNAS UI with the **truenas_admin** administrator account, go to **System > General Settings** and [upload the 13.0-U6.x system config file]({{< relref "ManageSysConfigSCALE.md#uploading-the-file" >}}). +This migrates your settings, imports your pools, shares, etc. into 24.10. -Go to **System > General Settings** and [upload the system config file](/scale/scaletutorials/systemsettings/general/managesysconfigscale/#uploading-the-file). -This migrates your CORE settings, imports your pools, shares, etc. into SCALE. -The system reboots to apply the uploaded configuration. +After uploading the config file, TrueNAS reboots. -After TrueNAS SCALE reboots, sign in with the root user credentials used in CORE. -Uploading the CORE config file deletes the **truenas_admin** user account created during a clean install and therefore requires you to [recreate an administrative user](#recreating-the-admin-user-account). +Uploading the CORE config file deletes the new admin user account created during a clean install and therefore requires you to [recreate it](#recreating-the-admin-user-account). +Log back into TrueNAS using the CORE root user credentials, and go to **Credentials > Users** to add an administration user with full control permissions. +Test the login, then disable the root user password. -After uploading the config file, review each area of the UI previously configured in CORE to validate pools imported and settings migrated correctly. Begin with your network settings. +Review each area of the UI previously configured in CORE to validate network settings, pools imported, and all other settings migrated correctly. +Begin with your network settings. -{{< hint type=info title="Component Descriptions" >}} -{{< include file="/static/includes/MigratingDescriptions.md" >}} +## Migrate to 24.04 and Update -See [Component Naming]({{< relref "ComponentNaming.md" >}}) for more information. -{{< /hint >}} +Non-Enterprise TrueNAS 13.0 and 13.3 installations can migrate to 24.04 using update trains. +See the [24.04 Migration documentation](https://www.truenas.com/docs/scale/24.04/gettingstarted/migrate/migratingfromcore/) for details on this method. -Use the information gathered during your preparation to migrate to restore settings, tasks, VMs, credentials, etc. not present in SCALE after uploading the config file. +After migrating to 24.04, you can use the [24.04 update options](https://www.truenas.com/docs/scale/24.04/scaletutorials/systemsettings/updatescale/) to update to 24.10 as a regular, non-migration update. ## Recreating the Admin User Account diff --git a/content/GettingStarted/Migrate/SCALEZFSFlagRemoval.md b/content/GettingStarted/Migrate/SCALEZFSFlagRemoval.md deleted file mode 100644 index 2efc2faaf4..0000000000 --- a/content/GettingStarted/Migrate/SCALEZFSFlagRemoval.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: "ZFS Feature Flags Removed (obsolete)" -description: " (obsolete) Provides legacy information for users of a deprecated ZFS feature flag merged into TrueNAS 22.02 and removed in 22.12." -weight: 40 -tags: -- migrate ---- - -This content is obsolete and no longer relevant to TrueNAS users. -Please refer to major version release notes for updates concerning ZFS feature flags. diff --git a/content/GettingStarted/Migrate/_index.md b/content/GettingStarted/Migrate/_index.md index 2947b00582..aa3d034a36 100644 --- a/content/GettingStarted/Migrate/_index.md +++ b/content/GettingStarted/Migrate/_index.md @@ -3,6 +3,7 @@ title: "CORE to SCALE Migrations" description: "TrueNAS CORE to TrueNAS SCALE migrations." geekdocCollapseSection: true weight: 40 +aliases: tags: - migrate related: false @@ -14,9 +15,10 @@ keywords: - data migration --- + This section provides information and instructions for TrueNAS CORE users wanting to migrate to SCALE. -{{< include file="/static/includes/MigrateCOREtoSCALEWarning.md" >}} +{{< include file="/static/includes/MigrateCOREtoSCALE24_04.md" >}} Linux treats device names differently than FreeBSD so please read [Component Naming]({{< relref "ComponentNaming.md" >}}) for more information. diff --git a/static/includes/MigrateCOREtoSCALE24_04.md b/static/includes/MigrateCOREtoSCALE24_04.md new file mode 100644 index 0000000000..b1c6b5d702 --- /dev/null +++ b/static/includes/MigrateCOREtoSCALE24_04.md @@ -0,0 +1,6 @@ + + +TrueNAS users wanting to migrate from 13.0-U6 (latest) or 13.3 to TrueNAS 24.10 or later can migrate to 24.04 and earlier using the UI, but must clean install if migrating to later releases. +Attempting to migrate directly to 24.10 or later releases fail and cannot be done. + +Download a copy of the iso for the latest maintenance release of 24.10 or earlier, then follow the migration instructions in this Getting Started section of the TrueNAS Documentation Hub to move from the FreeBSD-based version of TrueNAS to the Linux Debian-based version of TrueNAS. diff --git a/static/includes/WhatDoesNotMigrate.md b/static/includes/WhatDoesNotMigrate.md new file mode 100644 index 0000000000..1bd2fc0da5 --- /dev/null +++ b/static/includes/WhatDoesNotMigrate.md @@ -0,0 +1,24 @@ + + +Although TrueNAS attempts to keep most of your 13.0-U6.x configuration data when upgrading to TrueNAS 24.04 and later releases, some 13.0-specific items do not transfer. +These are the items that do not migrate from 13.0-U6.x: + +* Microsoft OneDrive Cloud Sync credentials and tasks. OneDrive compatibility is not available in TrueNAS. +* FreeBSD GELI encryption. If you have GELI-encrypted pools on your system that you plan to import into TrueNAS 24.04 and later, you must migrate your data from the GELI pool to a non-GELI encrypted pool before migrating to TrueNAS. +* Malformed certificates. TrueNAS validates the system certificates when a 13.0-U6.x system migrates to 24.04 or later. When a malformed certificate is found, TrueNAS generates a new self-signed certificate to ensure system accessibility. +* 13.0-U6.x plugins and jails. Save the configuration information for your plugin and back up any stored data. + After completing the TrueNAS 24.04 or later install, add the equivalent TrueNAS application using the **Apps** option. + If your 13.0-U6.x plugin is not listed as an available application in TrueNAS, use the **Custom App** option to add it as an application and import data from the backup into a new TrueNAS dataset for the application. +* NIS data. +* System tunables. +* ZFS boot environments. +* SMB auxiliary parameters. As of TrueNAS 23.10 (Cobia), the **Auxiliary Parameters** option is no longer available in the UI as a configurable option. + We recommend removing any auxiliary parameter settings in 13.-U6.x before migrating to TrueNAS 24.10. +* AFP shares also do not transfer, but migrate into an SMB share with AFP compatibility enabled. +* 13.0-U6.x `netcli` utility. A new CLI utility is used for the Console Setup Menu and other commands issued in a CLI. + By default, any TrueNAS user account with `netcli` as the chosen Shell updates to use the `nologin` option instead. + See the Users Screens reference article for descriptions of all Shell options. +* SAS multipath is not supported in TrueNAS 24.04 and later. +* TrueNAS 13 account names beginning with a number are not supported in TrueNAS 24.04 and later. + Usernames in 24.04 and later must begin with a letter or an underscore. Before attempting a migration, review the local user accounts and rename or replace any accounts that begin with a numeric character (0-9). +* VM storage and its basic configuration transfer over during a migration, but you need to double-check the VM configuration and the network interface settings specifically before starting the VM.