{"text_format":"2","workbook":"xlsx","n_sheets":1,"sheets":["checklist"],"not_rendered":{"charts":0,"images":0,"macros":0,"external_links":0,"defined_names":0,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"run_cost":"one","rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"checklist","index":0,"n_rows":37,"n_cols":5,"rows_kept":37,"cut":false,"hidden":false,"merged":[[2,0,4,0],[5,0,5,4],[6,0,21,0],[22,0,22,4],[23,0,32,0],[33,0,36,0]]}
[]
["Stage ","Task ","Notes","Status","Comments"]
["Research & Decision","RD1. Review and understand NXRM 3 architecture","NXRM 3 replaces xml based config files with an in-memory database running on OrientDB and 'blob stores' have replaced the storage directory for storing artifact/component binaries. \n\nSee the following documentation to better understand NXRM 3:\nhttps://help.sonatype.com/display/NXRM3/Repository+Manager+Pro+Features\nhttps://help.sonatype.com/display/NXRM3/Repository+Manager+Concepts\nhttps://help.sonatype.com/display/NXRM3/Directories "]
[null,"RD2. Review and understand feature differences between NXRM 2 and NXRM 3","There are significant differences between NXRM 2 and NXRM 3 that need to be taken into consideration before you commence with the migration. \n\nUse the following documentation to compare features:\nhttps://help.sonatype.com/display/NXRM3/Repository+Manager+2+to+3+Feature+Equivalency \nhttps://help.sonatype.com/display/NXRM3/Repository+Manager+Feature+Matrix"]
[null,"RD3. Ensure all stakeholders understand the upgrade process and expectations.","Review https://help.sonatype.com/repomanager3/installation/upgrading-from-nexus-repository-manager-2/upgrade-process-and-expectations to understand what happens during an upgrade.\n\nFor example, you cannot migrate a NXRM 2 to an existing in-use NXRM 3 instance. You must start the migration with a fresh/clean NXRM 3 instance.\n\nAlso, for certain NXRM 2 features there isn't an automatic migration to NXRM 3 e.g. Yum repos. This is because NXRM 2 Yum is based on maven repo, but NXRM 3 has a pure Yum repo.\n\nStaging repositories also cannot be automatically migrated (for staging also review https://guides.sonatype.com/repo3/technical-guides/staging-v2-v3-upgrade/).\n\nIf you have any questions further to reviewing the upgrade process and expectations, please either contact our Support team (support@sonatype.com) or your designated Sonatype Customer Success Engineer."]
["Perform the migration in a test environment first"]
["Preparation & Testing","PT1. Check version compatibility","Migrating from Nexus Repository Manager 2 to 3 also requires the involved repository managers to use a compatible version of Nexus Repository Manager 2 and 3. Always upgrade to the latest version of Repository Manager 2, before starting the upgrade to Nexus Repository Manager 3. https://help.sonatype.com/repomanager3/installation/upgrading-from-nexus-repository-manager-2#UpgradingfromNexusRepositoryManager2-Upgradingfrom2.xto3.y"]
[null,"PT2. Set-up NXRM 2 test environment ","Your test environment should be a replica of your NXRM 2 production instance, including sizing (CPU and Memory). Furthermore, if NXRM 3 will be installed on the same server then take into consideration the extra sizing requirements as stated in task PT6 below.\n\nIf you do not have an existing test environment, then please see the following KB article for details on copying your production instance to your test server:\nhttps://support.sonatype.com/hc/en-us/articles/213465118-How-to-Back-up-Nexus-for-Active-Standby-Failover"]
[null,"PT3. Ensure NXRM 2 work-directory integrity","Issue with filenames, file paths and file ownership on the NXRM 2 work directory can cause a migration to fail. Before commencing, perform the following checks:\n\n• Ensure all files in the work directory are owned by the 'nexus' user. The following Linux command can be used to find files in the work directory not owned by the user running nexus:\nfind . \\! -user nexus -print\n\n• There should be zero length files in the work directory.  The following Linux command can be used to find zero length files in work directory, these could be a result of previous disk issues:\nfind . \\! -user nexus -print"]
[null,"PT4. Review NXRM 2 and NXRM 3 security compatibility","Before you upgrade from version 2 to version 3 review the differences in security settings along the upgrade path. Known changes may affect privileges, roles and repository targets.\n\nSee: https://help.sonatype.com/repomanager3/installation/upgrading-from-nexus-repository-manager-2/security-compatibility"]
[null,"PT5. Review NXRM 2 Optimizations","When considering upgrade time and speed, take into account all enabled features on your Nexus Repository Manager 2 instance that you may not need. You can optimize the performance of your upgrade by disabling specific features.\n\nSee: https://help.sonatype.com/repomanager3/installation/upgrading-from-nexus-repository-manager-2/optimization%2C-performance%2C-and-tuning"]
[null,"PT6. Review NXRM 2 and NXRM 3 API differences","The REST API for NXRM 3 is entirely different from NXRM 2, as such, automations based on NXRM 2 REST APIs will need to be rewritten. \n\nNXRM 3 REST API documentation is available here: https://help.sonatype.com/repomanager3/rest-and-integration-api\n\nTo determine what existing API calls are being made, review the NXRM 2 request logs for /service/local calls that are not made by the UI. The user agent string and timestamp parameters can be used to find these calls."]
[null,"PT7. Decide on a transfer method","The migration agent offers 3 methods of transferring data from NXRM 2 to NXRM 3 as documented in: https://help.sonatype.com/repomanager3/installation/upgrading-from-nexus-repository-manager-2/data-transfer-methods\n\nReview and select the most appropriate one."]
[null,"PT8. Install NXRM 3","The migration should take place against a fresh/clean NXRM 3 install.\nDownload and install the latest available version from https://help.sonatype.com/repomanager3/download. For installation instructions see: https://help.sonatype.com/repomanager3/installation.\n\nAs stated in PT2, if NXRM 3 will be installed on the same test server as NXRM 2, then ensure the environment is sized adequately (see NXRM 3 sizing guidelines: https://help.sonatype.com/repomanager3/installation/system-requirements).\n\nNB. For HA-C users. A migration must be performed against a single NXRM 3 instance. HA-C can be enabled after the migration has been completed as a separate procedure."]
[null,"PT9. Configure NXRM 3","Perform any post-install steps as required e.g. SSL, Port configuration, HTTP Proxy, etc.\n\nPort configuration - If NXRM 2 and NXRM 3 are running on the same server, NXRM 3 should be configured with a different application-port in-order to avoid port conflicts.\n\nSSL Trust - If NXRM 2 is using a self-signed certificate for inbound SSL, please ensure this certificate is trusted by NXRM 3 (see: https://help.sonatype.com/repomanager3/system-configuration/configuring-ssl#ConfiguringSSL-OutboundSSL-TrustingSSLCertificatesGlobally)\n\nHTTP Proxy - If configured, add the NXRM 2 hostname to the proxy bypass list. The hostname added should be the same as what the NXRM 3 migration agent will use to communicate to NXRM 2 with. However, if both are running on the same server, then the migration agent can use localhost:<NXRM2_Port> instead."]
[null,"PT10. Perform migration","Following steps provided in https://help.sonatype.com/repomanager3/installation/upgrading-from-nexus-repository-manager-2/upgrade-procedures\nIf a failure occurs during migration, it may need to be restarted. If so, follow the steps outlined in https://help.sonatype.com/repomanager3/installation/upgrading-from-nexus-repository-manager-2/upgrade-procedures#UpgradeProcedures-RestartinganUpgrade\n\nIf further assistance is needed incase of a failure, please contact our Support team via https://support.sonatype.com"]
[null,"PT11. Upgrade integrations/plugins","Upgrade/Install any integration plugins to ensure compatibility with NXRM 3. This can include:\n• Nexus Firewall: https://help.sonatype.com/integrations/iq-server-and-repository-management/iq-server-and-nxrm-3.x\n• Nexus Platform plugin for Jenkins: https://help.sonatype.com/integrations/nexus-and-continuous-integration/nexus-platform-plugin-for-jenkins\n• Repository Manager for Maven Plugin: https://help.sonatype.com/integrations/nexus-and-continuous-integration/repository-manager-for-maven-plugin"]
[null,"PT12. Test migration","Ensure testing covers:\n• UI (in particular login, browse and search).\n• Builds (for all formats in use).\n• Integrations and plugins."]
[null,"PT13. Review post migration guidance.","See the following 'After the Upgrade' section of the migration documentation: https://help.sonatype.com/repomanager3/installation/upgrading-from-nexus-repository-manager-2/upgrade-procedures#UpgradeProcedures-AftertheUpgrade"]
[null,"PT14. Review and document process.","Document any incidents and observations that need to be taken into consideration when performing the production migration. \n\nFurther to this review, update the 'Production' stage of this checklist with any additional steps that will need to be performed for the production migration."]
[null,"PT15. Create migration timeline in preparation for production.","Use this test migration to estimate the time needed to complete the production migration and communicate this to all stakeholders"]
[null,"PT16. Prepare NXRM 3 training plans for end users (if applicable)","If your end-users will need training to use NXRM 3, you can prepare your training plans using the user guides available at https://guides.sonatype.com/repo3/"]
["Perform the migration in production"]
["Production Migration","PROD1. Check version compatibility","Migrating from Nexus Repository Manager 2 to 3 also requires the involved repository managers to use a compatible version of Nexus Repository Manager 2 and 3. If the source repository manager uses a version prior to 2.14.1, you must upgrade it as detailed in https://help.sonatype.com/repomanager3/upgrading#Upgrading-Upgradingfrom2.xto3.y before starting the upgrade to Nexus Repository Manager 3."]
[null,"PROD2. Ensure NXRM 2 work-directory integrity","Issue with filenames, file paths and file ownership on the NXRM 2 work directory can cause a migration to fail. Before commencing, perform the following checks:\n\n• Ensure all files in the work directory are owned by the 'nexus' user. The following Linux command can be used to find files in the work directory not owned by the user running nexus:\nfind . \\! -user nexus -print\n\n• There should be zero length files in the work directory.  The following Linux command can be used to find zero length files in work directory, these could be a result of previous disk issues:\nfind . \\! -user nexus -print"]
[null,"PROD3. Review NXRM 2 and NXRM 3 security compatibility","Before you upgrade from version 2 to version 3 review the differences in security settings along the upgrade path. Known changes may affect privileges, roles and repository targets.\n\nSee: https://help.sonatype.com/repomanager3/installation/upgrading-from-nexus-repository-manager-2/security-compatibility"]
[null,"PROD4. Review NXRM 2 Optimizations","When considering upgrade time and speed, take into account all enabled features on your Nexus Repository Manager 2 instance that you may not need. You can optimize the performance of your upgrade by disabling specific features.\n\nSee: https://help.sonatype.com/repomanager3/installation/upgrading-from-nexus-repository-manager-2/optimization%2C-performance%2C-and-tuning"]
[null,"PROD5. Review NXRM 2 and NXRM 3 API differences","The REST API for NXRM 3 is entirely different from NXRM 2, as such, automations based on NXRM 2 REST APIs will need to be rewritten. \n\nNXRM 3 REST API documentation is available here: https://help.sonatype.com/repomanager3/rest-and-integration-api\n\nTo determine what existing API calls are being made, review the NXRM 2 request logs for /service/local calls that are not made by the UI. The user agent string and timestamp parameters can be used to find these calls."]
[null,"PROD6. Decide on a transfer method","The migration agent offers 3 methods of transferring data from NXRM 2 to NXRM 3 as documented in: https://help.sonatype.com/repomanager3/installation/upgrading-from-nexus-repository-manager-2/data-transfer-methods\n\nReview select the most appropriate one."]
[null,"PROD7. Install NXRM 3","The migration should take place against a fresh/clean NXRM 3 install.\nDownload and install the latest available version from https://help.sonatype.com/repomanager3/download. For installation instructions see: https://help.sonatype.com/repomanager3/installation.\n\nIf NXRM 3 will be installed on the same production server as NXRM 2, then ensure the environment is sized adequately (see NXRM 3 sizing guidelines: https://help.sonatype.com/repomanager3/installation/system-requirements).\n\nNB. For HA-C users. A migration must be performed against a single NXRM 3 instance. HA-C can be enabled after the migration has been completed as a separate procedure."]
[null,"PROD8. Configure NXRM 3","Perform any post-install steps as required e.g. SSL, Port configuration, HTTP Proxy, etc.\n\nPort configuration - If NXRM 2 and NXRM 3 are running on the same server, NXRM 3 should be configured with a different application-port in-order to avoid port conflicts.\n\nHTTP Proxy - If configured, add the NXRM 2 hostname to the proxy bypass list. The hostname added should be the same as what the NXRM 3 migration agent will use to communicate to NXRM 2 with. However, if both are running on the same server, then the migration agent can use localhost:<NXRM2_Port> instead."]
[null,"PROD9. Perform migration","Following steps provided in https://help.sonatype.com/repomanager3/installation/upgrading-from-nexus-repository-manager-2/upgrade-procedures\n\nIf a failure occurs during migration, it may need to be restarted. If so, following steps outlined in https://help.sonatype.com/repomanager3/installation/upgrading-from-nexus-repository-manager-2/upgrade-procedures#UpgradeProcedures-RestartinganUpgrade\n\nIf further assistance is needed incase of a failure, please contact our Support team via https://support.sonatype.com"]
[null,"PROD10. Upgrade integrations/plugins","Upgrade/Install any integration plugins to ensure compatibility with NXRM 3. This can include:\n• Nexus Firewall: https://help.sonatype.com/integrations/iq-server-and-repository-management/iq-server-and-nxrm-3.x\n• Nexus Platform plugin for Jenkins: https://help.sonatype.com/integrations/nexus-and-continuous-integration/nexus-platform-plugin-for-jenkins\n• Repository Manager for Maven Plugin: https://help.sonatype.com/integrations/nexus-and-continuous-integration/repository-manager-for-maven-plugin"]
["Post Migration","PM1. Test migration (include end-users)","Ensure testing covers:\n• UI (in particular login, browse and search).\n• Builds (for all formats in use).\n• Integrations and plugins.\n• End-user testing should also be included."]
[null,"PM2. Review post migration guidance","See the following 'After the Upgrade' section of the migration documentation: https://help.sonatype.com/repomanager3/installation/upgrading-from-nexus-repository-manager-2/upgrade-procedures#UpgradeProcedures-AftertheUpgrade. In particular review the following guidance:\n\nWith the upgrade completed and all components transferred, you can perform the next steps in your upgrade plan. These can include:\n\n• Stopping Nexus Repository Manager 2.\n• Archiving Nexus Repository Manager 2 and delete the install from the server.\n• Reconfiguring Nexus Repository Manager 3 to use the HTTP port, context path and repository paths of version 2, if desired.\n• Alternatively updating all tool configurations pointing to the repository manager, such as Maven settings files and POM files.\n"]
[null,"PM3. Carry out end-user training","If applicable carry out NXRM 3 training for end-users using the plans from PT16."]
[null,"PM4. Configure HA-C (if planned)","Once testing is complete and the migration is complete, you can proceed to configure HA-C if it is part of your plans/design."]