IBM DS4000 ユーザーズマニュアル
Digital Media Storage Solution Installation Guide
17
© Copyright 2010, IBM Corporation. All rights reserved.
MIGRATING FROM XSAN MDC TO STORNEXT MDC
Q. Are there new features in Xsan 2.2 that make it harder to swap out XServe MDCs and replace them with
StorNext Linux MDCs?
A:
“NamedStreams” is the Apple Xsan feature that causes some problems with StorNext. If you don‟t turn it on,
you‟re fine. By default, “NamedStreams” is turned on. NamedStreams will make things like the basic StorNext
command line copy command, cvcp, not work. Before Xsan 2.2, you could have it copy the
command line copy command, cvcp, not work. Before Xsan 2.2, you could have it copy the
“._” files, but now you
can't, so you're stuck doing a move with the Apple Finder (which is basically as good as cvcp anyway). Other
than that, it shouldn't be much of an issue since it doesn't affect clients that don't know about it, and by definition
Windows/Linux clients don't know about resource forks.
Q. Does a customer need to buy A special level of StorNext support to support StorNext in Xsan environments? Is
this true whether you are using SN MDCs or Apple MDCs?
A: No,
than that, it shouldn't be much of an issue since it doesn't affect clients that don't know about it, and by definition
Windows/Linux clients don't know about resource forks.
Q. Does a customer need to buy A special level of StorNext support to support StorNext in Xsan environments? Is
this true whether you are using SN MDCs or Apple MDCs?
A: No,
You don‟t need to buy any special support to get support for StorNext in an Xsan environment. See next
page.