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

[Bug]: How do I migrate one of my milvus databases offline to another server? #37005

Open
1 task done
0sengseng0 opened this issue Oct 19, 2024 · 3 comments
Open
1 task done
Assignees
Labels
help wanted Extra attention is needed

Comments

@0sengseng0
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:2.3.1
- Deployment mode(standalone or cluster):standalone 
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

I transferred the volume of the source server, packaged, and offline to the target location of another server. After restarting the milvus of the target server, the data on the source server could not be smoothly recognized. Milvus-backup does not seem to be able to transfer milvus data offline to another server.

Expected Behavior

How do I migrate one of my milvus databases offline to another server?

Steps To Reproduce

How do I migrate one of my milvus databases offline to another server?

Milvus Log

No response

Anything else?

No response

@0sengseng0 0sengseng0 added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 19, 2024
@yanliang567
Copy link
Contributor

@0sengseng0 as you get the backup files with milvus-backup, you can restore them you any other milvus servers. I don't find any other options for now.

/assign @0sengseng0
/unassign

@yanliang567 yanliang567 added help wanted Extra attention is needed and removed kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 19, 2024
@0sengseng0
Copy link
Author

@0sengseng0 as you get the backup files with milvus-backup, you can restore them you any other milvus servers. I don't find any other options for now.

/assign @0sengseng0 /unassign

After I do./milvus-backup create -n bk3. I see that the storage directory of minIO is about 500M, and the storage space of milvus is 5G. This storage gap left me wondering what I should download from the minIO in order to migrate the entire milvus data offline to another server.

@deep1401
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants