Xsan1 & Xsan2 Volume

francisyo's picture

Hello Guys,

My client is asking me to copy his files on Xsan1 volume to Xsan2 volume. Here's my question. For those who already done this, sharing of knowledge would be greatly appreciated. Thanks in advance.

1. My client wants me to create a new Xsan2 with complete set of mdc1 and mdc2 for failover. He wants it to be on the same domain and connected on his old and still on use ldap directory. Is it possible? Users on xsan1 are still on that directory. Does it trigger problems?

2. My client wants to mount Xsan1 volume and the new Xsan2 Volume on 1 of its user. Is it possible to mount Xsan1 volume and Xsan2 volume on that client? He just want to copy its file to xsan2 volume so we can delete the old xsan1 and add it to xsan2(another volume) in the future.

3. Would this be possible 1 ldap + 1 dns + 1 xsan1 + 1 xsan2 = mount on same client?

Just need your ideas, I haven't done this before. thanks.

singlemalt's picture

Hi Francisyo,
1. Shouldn't be a problem. Directory services doesn't really know or care about
xsan. It just provides well… directory services.

2. It sounds like you're proposing that a client be a member of two different SANS at the same time.
Nope. Not gonna happen. Any system, client or meta data controller can only be a member of one SAN at a time.
What might work better is to update the XSAN1 to XSAN2. Then create the new volume and copy the data over.

francisyo's picture

Hi Singlemalt,

Thanks for the quick reply. I hope its that easy but i'm facing a huge terabyte here on a single volume and its operating 24/7. And also I haven't done that on a live volume(updating to xsan2). What i usually propose is clean installation. But this one, i think fresh install is bad idea. So whats the best way to copy the files from Xsan1 to xsan2? Any suggestion?

singlemalt's picture

No really good suggestions. Since they have to be different SANs I guess a
network protocol like afp/smb or nfs is the next best choice.

mw10dot1's picture

Hi francisyo

I would say you have two main options.

1. Create a new volume on the existing mdc's. Then copy over all the files. Remove the config files for the volume and add it to the new mdc's.

2. Create the new volume on the new mdc's. Then i would use prestore to copy all the data over. Rather then using afp/smb etc.

A big factor is how much data you are looking at and what sort of window of down time is possible.

Michael

francisyo's picture

Hello guys especially to SingleMalt and Mw10dot1,

Thanks for your suggestions, I will be speaking to my client and propose what i have in mind and all your suggestions. by the way I also read from this link to support more on what SingleMalt said about 1 xsan and 1 client per single time. It really put an end on my quest to solve and find solution on the "2 xsans mounting on 1 client."

http://www.xsanity.com/forum/viewtopic.php?t=988

Thank you very much all and God bless.

matx's picture

singlemalt wrote:
Hi Francisyo,
2. It sounds like you're proposing that a client be a member of two different SANS at the same time.
Nope. Not gonna happen. Any system, client or meta data controller can only be a member of one SAN at a time./quote

You can have one client be a member of two different SANs if you want to set it up that way. It would be redundant. It has been done.

However it wouldn't run Xsan 1 client and Xsan 2 client software simultaneously. Xsan 2, would work.

matx's picture

francisyo wrote:
Hello guys especially to SingleMalt and Mw10dot1,

Thanks for your suggestions, I will be speaking to my client and propose what i have in mind and all your suggestions./quote

Even though it is possible to have one client on two SANs. I would recommend backing up the first SAN to a fibre attached RAID and moving the data that way, or better still -- restore from tape. Test that backup solution you have in place.

lucasnap's picture

I've done this before.. Xsan1 volume to Xsan2 new volume. Same environment, but different MDC's.

One client on both volumes doesn't work of course due to version differences. So I went with the AFP re-share setup (as you could imagine there was also a time pressure).

It worked out, but not one of my finest moments... Not a move I would suggest for next time. I would definitely go for a hired fibre RAID (simple HFS+) or Prestore next time.

francisyo's picture

Hi All especially toMatx, Lucasnap,

Just another question on 2 different xsan and 1 client but different mdc's. This that means that you connect your ethernet1 one xsan2 to your network1(xsan1 public network) switch and connect your ethernet2 of your xsan2 to your network2(xsan1 private network) and fibre to the same fibre switch? No problem at all? No issues?
As usual, I haven't done this that why I'm thinking of just putting another switch for xsan2 private network and another switch for fibre channel. And for the public switch, it would be on the same public switch of xsan1.

Thanks by the way for the help. Really appreciated it!!!!!

matx's picture

francisyo wrote:
Hi All especially toMatx, Lucasnap,

Just another question on 2 different xsan and 1 client but different mdc's. /quote

You can have one client on two different SANs. Not just different MDCs on the same SAN. There's a known hack with switching the auth_secret for one SAN to the other SAN. Not supported. Back up your data first, but it can be done.

That being said it means having two separate (actually redundant) SAN infrastructures, i.e. fibre channel, ethernet, etc