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

Migrating PVC Volumes to a New NetApp: Best Practices and Considerations #974

Open
chrs04 opened this issue Feb 6, 2025 · 1 comment
Open

Comments

@chrs04
Copy link

chrs04 commented Feb 6, 2025

Hello everyone!

My customer needs to decommission their old test NetApp. This old NetApp also hosts a Trident vServer with PVC volumes.

Now we need to transfer the volumes to the new NetApp, and we are asking ourselves the following questions:

What is the best method for migrating PVC volumes to another NetApp?

Unfortunately, the IP address and vServer name will also change.

I have the following ideas in mind:

  • Vol Move or SnapMirror
  • Backup & Restore

What do you think?

Assuming we decide on the Vol Move or SnapMirror approach, can I simply update the Trident backends with the new values (vServer name & IP for Data+Mgmt Lif), and will the OpenShift cluster still be able to find its volumes?

Thanks & best regards,
Christopher

@ocpvkb
Copy link

ocpvkb commented Mar 3, 2025

vote +1

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

No branches or pull requests

2 participants