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

service migrate #1737

Open
crazyJerk opened this issue Dec 23, 2020 · 1 comment
Open

service migrate #1737

crazyJerk opened this issue Dec 23, 2020 · 1 comment

Comments

@crazyJerk
Copy link

Hi!Our company uses ambry as a file storage service. Now I need to migrate the ambry service to a new server. However, both servers do not have public network IP and are no longer the same network segment. Therefore, data cannot be copied through fragmentation or clustering. Can we find the storage path of ambry data, export the data directory directly and upload it to the new server After that, start the ambry service and access the data normally?Thank you

@jsjtzyy
Copy link
Contributor

jsjtzyy commented Dec 27, 2020

Hi, I suppose you are not able to migrate data through replication (although this is recommended for online migration). I don't quite understand the way you proposed but if you want to know the data directory, the mountPath defined in HardwareLayout.json should be the place to look at (in that dir, each partition has its own dir). Assuming you succeed in exporting data and transfer them to new server, you also need to update the hostname in your HardwareLayout.json and PartitionLayout.json to indicate the location change. After that, you might have to reboot all frontends and servers to honor such change(if you are using static cluster manager). Hope this helps.

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

2 participants