Guidance Needed: Migrating Seq To New Server

[csession93]

We’re planning to migrate our Seq instance to a new a windows server and we’d like to retain all existing logs and ensure a seamless transition to minimize downtime and data loss.

A few key points we’d like guidance on:

• Backup and Restore: What’s the best way to back up existing logs and restore them on the new server? Are there any specific tools or steps you recommend for ensuring data integrity during this process?

• Configuration Transfer: Is there a straightforward method to transfer our current Seq configurations such as settings, API keys, users to the new server?

• Compatibility with New Versions: We’re also considering upgrading to the latest Seq version during this migration. Are there any considerations or best practices for combining an upgrade with a server migration?

• Potential Pitfalls: Are there common issues or challenges we should prepare for during this process?

If there’s any existing documentation or tools that cover this type of migration, please feel free to share.

Thanks

[KodrAus]

Hi @csession93 👋

We've got some docs on how to do this here. They run through the complete process and should answer your questions.

Besides a bit of downtime taking a copy of the original server's log data the process is non-destructive for the original server.

[liammclennan]

@csession93 don't upgrade during the migration. Upgrade first, then migrate to the same version.