Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
think about an external storage sytem which you want to migrate with NetApp tools.
I got several LUNs in an external storage system. Now I map that LUNs to the NetApp
and use a SnapMirror to migrate them to another NetApp system. Is that possible?
It´s just an idea!
What do you think about that?
Greetings, Chris
4 REPLIES 4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No. You can't map a lun with an existing file system to NetApp and expect to read the data. NetApp will see it as an array lun, and will put it in the spare pool (possibly overwriting some of the data on the lun in the process).
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Bill,
thanks for your response! Any other idea how to handle on that?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It'd have to be a host-side migration. Create the lun on your target NetApp system, present it up to the client, migrate the data, then cutover. If it's just filesystem data, something like rsync or robocopy do a good job of minimizing downtime. If you're using LVM on the client you can mirror the disks, then remove the old lun from the mirror for a seamless migration.
There are appliances out there that would handle the migration, but (in my opinion) they're expensive and out of scope for most migration needs.
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks. You are right ... I will think about some possibilities to migrate.
Greetings, Chris
