Benches Networking

7

Xsan 1.4.x to Xsan 2 data migration - what is t...

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I have the unique opportunity to build an entirely new Xsan 2.x SAN alongside an existing Xsan 1.4.x deployment. The idea here is that I have a 16 TB Xsan 1.4.x system that is generally running well. However, there are needs for Xsan 2 and the environment is moving to Leopard. So to best serve the department, we are actually going to create a separate Xsan 2 SAN while the 1.4 remains in production (yes, I am blessed with a lot of hardware). This will permit us to validate the entire environment without interrupting the production environment.

The question is, what is the best way of moving the data from the Xsan 1.4.x volume to the Xsan 2.0 volume. There are the obvious methods of Ethernet or bonded ethernet. But with Ethernet at about 2 GB/minute, then I am looking at 2.8 TB per day. With 16 TB to move, that is nearly 6 days of copying.

Bonded ethernet should theoretically halve that performance to about 3 days but will require additional ethernet cards as metadata is still required for both SANS.

So, that leads to fiber channel. Is it possible to connect an Xsan 1.4 volume to an Xsan 2.0 array in a read only capacity over fibre channel? Perhaps through the switch and zoning or through vsan? My guess is no but I want to see if anyone out there has another way to move the data.

Anyone else go through the same migration? Any advice would be great.

7 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Maybe you could plug one of your extra fiber ports on your HBA, or from a second fiber card entirely, into the 2nd Xsan switch. You may need to zone that port off on the switch, but the real goal would be to use LUN-masking on the new storage to use one small LUN as direct attached to move data via Fiber instead of Ethernet. Does that make sense?

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Aha! Brilliant. I think I get the gist. I can use one of the new arrays as a shuttle between the old and the new. It will require two copies but will likely still be faster. So, you are suggesting the following. Format one of the arrays as standard HFS+ and add as direct attach. Copy data to this volume. Disconnect. Connect to XSAN 2 system and copy again. In the end, I can incorporate the transport volume into the SAN.

    I like the suggestion. Thank you very much.

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Yes, exactly. Format a small array/LUN as HFS and use this for the transport. And either use LUN-masking on the RAID to keep the LUN/array on the switch, or plug it in directly into the server/client which has the Xsan 1 volume mounted. Copy and connect it back to the other client/server on which has Xsan 2 mounted. At least copying over fiber should be faster than GIG-e.

  4. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    High,
    There is another way of copying the data. You can hang a (1.4.2) client on both xsan environments. Both sans need the same .auth_seret files in the config folder.

    With cvcp you can make fast copys of the data. You can use more clients to fasten this up. With 2GB/s FC cards you can get a 200MB/s througput for each client. This is 720 GB/hr or 18TB/day. This is theory, and I never met this speed, but in practise I had 150MB/s.

    So with one client you can do it in a weekend, with more, you can do it in a day.

    You have to calculate yourself a bit more. F.i. you might have 4GB ports, and you have to count in the number of luns to calc the max throughput of the volume. This can positively and negatively adjust your throughput.

    Regards
    Donald

  5. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    You can still use cvcp to copy the data from the Xsan volume to a non-Xsan volume. cvcp is multi-threaded so it'll be faster that cp or ditto.

  6. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Yes you can use cvcp for your procedure too. The throughput will be slower though because:
    + the small lun can not deliver high throughput on its own.
    + you have to pass the data twice.
    + you have to monitor the proces because you can copy small amounts of data.

    Regards
    Donald

  7. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Donald,

    This is a really intriguing option. But my question is how do you accomplish this? Keeping this simple, say I have my 1.4 MDC with the attached storage. Then I have my 2.1 MDC with its attached storage. For sanity sake, I have my FC switches zoned so the 1.4 and 2.0 devices are segregated. Now, I take the 1.4 client and want to bridge the two... Do I get a second FC card and plug the client into both zones? Also, you mention the .auth_secret file. Can I just hand edit this to match the two environments? Will modifying the .auth_secret file on an existing SAN cause negative results?

    And finally, if I get this set up, is added the man in the middle as simple as adding the client in both Xsan 2 and Xsan 1.4 MDCs?

    I really like the option you've presented and would like to use this approach. If you have the chance, please share your trick.