Bottom line: Inventory application storage before choosing a new apps pool. Keep the migration’s apps-dataset scope separate from host-path data and accept both parts of the resulting application layout.
\nThe TrueNAS 25.10 Apps reference shows Migrate existing applications when a new pool is selected after the apps service has already been configured. That option migrates installed applications to the new applications pool. Its data scope is the apps dataset, including application location and iXvolume storage; mounted host-path data is not migrated. Unset Pool is a different action that removes the pool configuration and turns off the application service.
\nThis article covers a pool-move operation, not container backup coverage or a guarantee that an application is ready afterward. It does not authorize moving host data, changing its permissions or deleting the former pool.
\nThe following steps are DSE recommendations based on the cited source.
\nDSE recommends an application-storage map before selecting a new pool. Give each application a row for its installation, iXvolume use and every host-path dependency actually present. Have the application and storage owners reconcile the map with the current configuration instead of treating the pool name as a complete data inventory.
\nWrite the intended after-move layout beside the existing layout. Mark host paths that are intentionally staying in place and any separate data operation that would need its own authorization. Keep access requirements and backup coverage with those paths; do not infer that an application-pool move has handled them.
\nRehearse with a disposable representative application containing harmless data in the two storage categories. Record the expected location of each marker after the proposed move. Choose the migration action deliberately and keep Unset Pool out of the sequence unless that different service action is separately intended and approved.
\nPreserve the starting application and path configuration before the authorized operation. Agree a service window and stopping condition with each affected owner. Keep deletion of the former pool outside the initial acceptance decision, and investigate an unexplained storage reference before attempting an unrelated permission or mount change.
\nProposed verification: inspect the selected destination and migration choice, then compare every mapped application-storage entry with the intended after-move layout. Check the harmless markers at their actual locations. Record a host path’s continued reference separately from the relocated apps-dataset entries instead of describing everything as moved.
\nExercise the agreed application read and write operations through the intended client path and retain actual outcomes. Have both owners review unresolved references and separate recovery coverage before closing the move. Accept only the demonstrated layout and workload checks; do not use a running application alone as authorization to destroy its former storage.
\nSource review completed October 30, 2026. Recheck the official documentation and deployment-specific applicability before a production change.
\n", "content_text": "Bottom line: Inventory application storage before choosing a new apps pool. Keep the migration’s apps-dataset scope separate from host-path data and accept both parts of the resulting application layout.\nSource fact: what the authority says\nThe TrueNAS 25.10 Apps reference shows Migrate existing applications when a new pool is selected after the apps service has already been configured. That option migrates installed applications to the new applications pool. Its data scope is the apps dataset, including application location and iXvolume storage; mounted host-path data is not migrated. Unset Pool is a different action that removes the pool configuration and turns off the application service.\nWhat the source does not establish\nThis article covers a pool-move operation, not container backup coverage or a guarantee that an application is ready afterward. It does not authorize moving host data, changing its permissions or deleting the former pool.\nApplicability questions\n\nWhich applications and existing pool are included in the move?\nWhat storage does each application use, with exact source paths?\nWhich entries belong to the apps dataset and which are mounted host paths?\nWhat layout and harmless application checks must be accepted afterward?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends an application-storage map before selecting a new pool. Give each application a row for its installation, iXvolume use and every host-path dependency actually present. Have the application and storage owners reconcile the map with the current configuration instead of treating the pool name as a complete data inventory.\nWrite the intended after-move layout beside the existing layout. Mark host paths that are intentionally staying in place and any separate data operation that would need its own authorization. Keep access requirements and backup coverage with those paths; do not infer that an application-pool move has handled them.\nRehearse with a disposable representative application containing harmless data in the two storage categories. Record the expected location of each marker after the proposed move. Choose the migration action deliberately and keep Unset Pool out of the sequence unless that different service action is separately intended and approved.\nPreserve the starting application and path configuration before the authorized operation. Agree a service window and stopping condition with each affected owner. Keep deletion of the former pool outside the initial acceptance decision, and investigate an unexplained storage reference before attempting an unrelated permission or mount change.\nVerification and evidence\nProposed verification: inspect the selected destination and migration choice, then compare every mapped application-storage entry with the intended after-move layout. Check the harmless markers at their actual locations. Record a host path’s continued reference separately from the relocated apps-dataset entries instead of describing everything as moved.\nExercise the agreed application read and write operations through the intended client path and retain actual outcomes. Have both owners review unresolved references and separate recovery coverage before closing the move. Accept only the demonstrated layout and workload checks; do not use a running application alone as authorization to destroy its former storage.\nOfficial references\n\nTrueNAS — Apps — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 30, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "content_markdown": "Bottom line: Inventory application storage before choosing a new apps pool. Keep the migration’s apps-dataset scope separate from host-path data and accept both parts of the resulting application layout.\n\n## Source fact: what the authority says\n\nThe [TrueNAS 25.10 Apps reference](https://www.truenas.com/docs/scale/25.10/scaleuireference/apps/) shows Migrate existing applications when a new pool is selected after the apps service has already been configured. That option migrates installed applications to the new applications pool. Its data scope is the apps dataset, including application location and iXvolume storage; mounted host-path data is not migrated. Unset Pool is a different action that removes the pool configuration and turns off the application service.\n\n## What the source does not establish\n\nThis article covers a pool-move operation, not container backup coverage or a guarantee that an application is ready afterward. It does not authorize moving host data, changing its permissions or deleting the former pool.\n\n## Applicability questions\n\n- Which applications and existing pool are included in the move?\n\n- What storage does each application use, with exact source paths?\n\n- Which entries belong to the apps dataset and which are mounted host paths?\n\n- What layout and harmless application checks must be accepted afterward?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends an application-storage map before selecting a new pool. Give each application a row for its installation, iXvolume use and every host-path dependency actually present. Have the application and storage owners reconcile the map with the current configuration instead of treating the pool name as a complete data inventory.\n\nWrite the intended after-move layout beside the existing layout. Mark host paths that are intentionally staying in place and any separate data operation that would need its own authorization. Keep access requirements and backup coverage with those paths; do not infer that an application-pool move has handled them.\n\nRehearse with a disposable representative application containing harmless data in the two storage categories. Record the expected location of each marker after the proposed move. Choose the migration action deliberately and keep Unset Pool out of the sequence unless that different service action is separately intended and approved.\n\nPreserve the starting application and path configuration before the authorized operation. Agree a service window and stopping condition with each affected owner. Keep deletion of the former pool outside the initial acceptance decision, and investigate an unexplained storage reference before attempting an unrelated permission or mount change.\n\n## Verification and evidence\n\nProposed verification: inspect the selected destination and migration choice, then compare every mapped application-storage entry with the intended after-move layout. Check the harmless markers at their actual locations. Record a host path’s continued reference separately from the relocated apps-dataset entries instead of describing everything as moved.\n\nExercise the agreed application read and write operations through the intended client path and retain actual outcomes. Have both owners review unresolved references and separate recovery coverage before closing the move. Accept only the demonstrated layout and workload checks; do not use a running application alone as authorization to destroy its former storage.\n\n## Official references\n\n- [TrueNAS — Apps](https://www.truenas.com/docs/scale/25.10/scaleuireference/apps/) — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 30, 2026. Recheck the official documentation and deployment-specific applicability before a production change." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/inventory-truenas-host-path-data-before-moving-the-apps-pool/", "url": "https://update.dsesecurity.com/updates/inventory-truenas-host-path-data-before-moving-the-apps-pool/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-30" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/inventory-truenas-host-path-data-before-moving-the-apps-pool/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Business Continuity", "item": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "ListItem", "position": 3, "name": "Inventory TrueNAS host-path data before moving the apps pool", "item": "https://update.dsesecurity.com/updates/inventory-truenas-host-path-data-before-moving-the-apps-pool/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/inventory-truenas-host-path-data-before-moving-the-apps-pool/#article", "identifier": "https://update.dsesecurity.com/updates/inventory-truenas-host-path-data-before-moving-the-apps-pool/", "url": "https://update.dsesecurity.com/updates/inventory-truenas-host-path-data-before-moving-the-apps-pool/", "headline": "Inventory TrueNAS host-path data before moving the apps pool", "description": "Separate migrated apps-dataset storage from host-path data that the documented apps-pool migration leaves in place.", "abstract": "Separate migrated apps-dataset storage from host-path data that the documented apps-pool migration leaves in place.", "articleBody": "Bottom line: Inventory application storage before choosing a new apps pool. Keep the migration’s apps-dataset scope separate from host-path data and accept both parts of the resulting application layout.\nSource fact: what the authority says\nThe TrueNAS 25.10 Apps reference shows Migrate existing applications when a new pool is selected after the apps service has already been configured. That option migrates installed applications to the new applications pool. Its data scope is the apps dataset, including application location and iXvolume storage; mounted host-path data is not migrated. Unset Pool is a different action that removes the pool configuration and turns off the application service.\nWhat the source does not establish\nThis article covers a pool-move operation, not container backup coverage or a guarantee that an application is ready afterward. It does not authorize moving host data, changing its permissions or deleting the former pool.\nApplicability questions\n\nWhich applications and existing pool are included in the move?\nWhat storage does each application use, with exact source paths?\nWhich entries belong to the apps dataset and which are mounted host paths?\nWhat layout and harmless application checks must be accepted afterward?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends an application-storage map before selecting a new pool. Give each application a row for its installation, iXvolume use and every host-path dependency actually present. Have the application and storage owners reconcile the map with the current configuration instead of treating the pool name as a complete data inventory.\nWrite the intended after-move layout beside the existing layout. Mark host paths that are intentionally staying in place and any separate data operation that would need its own authorization. Keep access requirements and backup coverage with those paths; do not infer that an application-pool move has handled them.\nRehearse with a disposable representative application containing harmless data in the two storage categories. Record the expected location of each marker after the proposed move. Choose the migration action deliberately and keep Unset Pool out of the sequence unless that different service action is separately intended and approved.\nPreserve the starting application and path configuration before the authorized operation. Agree a service window and stopping condition with each affected owner. Keep deletion of the former pool outside the initial acceptance decision, and investigate an unexplained storage reference before attempting an unrelated permission or mount change.\nVerification and evidence\nProposed verification: inspect the selected destination and migration choice, then compare every mapped application-storage entry with the intended after-move layout. Check the harmless markers at their actual locations. Record a host path’s continued reference separately from the relocated apps-dataset entries instead of describing everything as moved.\nExercise the agreed application read and write operations through the intended client path and retain actual outcomes. Have both owners review unresolved references and separate recovery coverage before closing the move. Accept only the demonstrated layout and workload checks; do not use a running application alone as authorization to destroy its former storage.\nOfficial references\n\nTrueNAS — Apps — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 30, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "datePublished": "2026-10-30T06:04:39+00:00", "dateModified": "2026-10-30T06:05:14+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/inventory-truenas-host-path-data-before-moving-the-apps-pool/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/inventory-truenas-host-path-data-before-moving-the-apps-pool/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Inventory TrueNAS host-path data before moving the apps pool" }, "articleSection": [ "Business Continuity", "Networks & Infrastructure" ], "keywords": [ "Business Continuity", "Networks & Infrastructure", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 528, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "TrueNAS — Apps", "url": "https://www.truenas.com/docs/scale/25.10/scaleuireference/apps/" } } ] } }