Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve the documentation for how to migrate data between ServiceControl instances #5801

Open
timbussmann opened this issue Dec 4, 2020 · 2 comments

Comments

@timbussmann
Copy link
Contributor

timbussmann commented Dec 4, 2020

Relevant information

When migrating a ServiceControl instance to a new server or system, it's not obvious how to transfer the data of the existing SC instance to the new SC instance.
It seems that the only approach at the moment seems to just copy the whole database (or create a backup in maintenance mode) (see https://docs.particular.net/servicecontrol/backup-sc-database#important-notes-and-restrictions) which seems to be a brittle approach, as according to our documentation, the instances need to have the same service name (which might not be desired by the user):

When restoring a ServiceControl database, the name of the ServiceControl Windows Service must be the same on the target machine as it was on the source machine.

@WilliamBZA WilliamBZA changed the title It's difficult to export/import data between ServiceControl instances Improve the documentation for how to migrate data between ServiceControl instances Dec 7, 2020
@WilliamBZA
Copy link
Member

WilliamBZA commented Dec 7, 2020

There's not much we can do without tying ourselves more the either Esent or Raven.

We can spend some time improving the documentation (perhaps having a dedicated "migrating data" section) on exporting/importing to try make the process clearer - possibly even include some powershell scripts.

@WilliamBZA WilliamBZA transferred this issue from another repository Aug 12, 2021
@kbaley kbaley transferred this issue from another repository Jul 21, 2022
@kbaley kbaley transferred this issue from another repository Jul 27, 2022
@mikeminutillo
Copy link
Member

We have guidannce for performing a zero-downtime upgrade which could be extracted and repurposed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants