是否可以多次执行从nexus 2到nexus 3的迁移? [英] Is it possible to perform a nexus 2 to nexus 3 migration multiple times?

问题描述

我们已完成从nexus 2到nexus 3的迁移，并且在nexus 2中有很多对象，因此即使进行了硬链接过程，迁移也有些慢.

We have a nexus 2 to nexus 3 migration being done and we have A LOT of objects in our nexus 2 so the migration is somewhat slow even with the hardlink process.

联系文档: https://books.sonatype.com/nexus- book/reference3/upgrading.html#upgrade-process-expectations

具有以下内容:

使用现有的安装有数据和配置的Nexus Repository Manager 3，因为目标存储库管理器会受到限制，使升级变得更加复杂，并且可能需要在升级之前重新配置版本2实例以及重新配置升级后的Nexus Repository Manager 3.

Using an existing installation of Nexus Repository Manager 3 populated with data and configuration as the target repository manager incurs restrictions that make the upgrade more complex and potentially requires re-configuring the version 2 instance prior to the upgrade as well as re-configuring Nexus Repository Manager 3 after the upgrade.

我希望最大程度地减少停机时间，因此我想我们将对备份快照进行一次初始迁移，然后锁定对现有Nexus 2服务器的访问，将快照重新同步到最新数据，然后执行进行第二次迁移(希望此后第二次迁移应该更快)

I'm hoping to minimize downtime so was thinking we'd do the initial migration once on a backup snapshot, then lock down access to the existing Nexus 2 server, re-sync the snapshot to the latest data and then do the migration a second time (with the hopes that the second migration should be faster since)

1. 这可能吗?
2. 如果是这样，这是否会真正减少停机时间，还是会尝试再次重新处理相同的文件?

blurb尚不清楚，这使它变得更加复杂以及为什么需要重新配置版本2实例.

The blurb is not entirely clear what makes this more complex and why it requires re-configuring the version 2 instance.

推荐答案

这可能是可行的，但实际上并不受支持.升级是增量的，可以在应用程序仍在运行并为用户提供服务并继续同步内容的同时完成.因此，您已经可以最大程度地减少停机时间.

It might be possible but it is not really supported. The upgrade is incremental and can be done while the app is still running and serving users and continues to sync content. As such you can minimize downtime already.

这篇关于是否可以多次执行从nexus 2到nexus 3的迁移?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！