Upgrading Considerations - Windows Server Version

1. Do you need or want to upgrade to a newer Windows Server version?

If yes:

  • Not recommended: In-place upgrade of Windows Server, followed by in-place upgrade of K2. Only consider this with careful backups and testing.
  • Recommended: Set up a new Windows Server. This involves:
    • Backing up the database
    • Installing K2 on the new server
    • Preserving the option to roll back to the old server if needed

2. Is your K2 setup standalone or a farm?

If standalone:

  • Using hostname for K2 site binding: This requires the most migration work, especially with a new server hostname. Consider reconfiguring to a farm setup for easier future migrations.
    • New server with same hostname: Less manual updates needed.
    • New server with different hostname: More manual reconfigurations required, including SharePoint integrations.
  • Using DNS for K2 site binding: Migration is simpler. Consider reconfiguring to a farm setup for future benefits.

If farm setup:

  • Using DNS for K2 site binding: This is the simplest migration scenario. The farm DNS handles server changes seamlessly. DNS can point to a single server or a load balancer for flexibility.

If you don't need to upgrade Windows Server:

  • Perform an in-place upgrade of K2 on the same server.
  • Take a database backup and VM snapshot for rollback options if necessary.

Comments

Popular posts from this blog

Blocking Error during K2 5.6 Server migration

Client Credentials flow with K2 Cloud with Odata, Workflow REST or SCIM

Blocking error RegisterServiceInstanceObjects when upgrading to K2 5.6/5.7