Before you use your server, ensure that you are familiar
with the limitations and restrictions.
Review the following limitations and restrictions:
- You cannot use SAN Volume Controller Copy
Services (FlashCopy®, Metro
Mirror, and Global Mirror) to copy VDisks that are mapped to these
servers. This limitation applies only to VDisks that are mapped to
these servers and does not restrict the use of Copy Services on other
VDisks.
- The maximum supported VDisk size is 500 GB, which equates to 500x1024x1024x1000
bytes. However, the minimum supported VDisk size is 1 GB, which
equates to 1024x1024x1024 bytes. The definition for 1 GB used in SAN Volume Controller is
1024x1024x1024 bytes, so mapping a 1GB SAN Volume Controller VDisk
to these servers works, but mapping a 500 GB SAN Volume Controller VDisk
to these servers fail.
- VDisks that are mapped to these servers can be moved between I/O
groups on SAN Volume Controller,
but you must halt the server before you do this.
- You cannot map VDisks to these servers as LUN 0. This is the default
behavior when creating a host mapping on SAN Volume Controller,
and you must override this by using the -scsi switch for the mkvdiskhostmap command.
- You can import pre-existing server LUNs to the SAN Volume Controller in
image mode, except for the server’s root volume. If the SAN Volume Controller is
introduced into an existing server installation, either:
- The server root file system must be rebuilt using a new VDisk
that is presented by the SAN Volume Controller.
- The server root file system must remain on the original controller
and be directly accessed by the server (and masked from the SAN Volume Controller by,
for example, LUN Partitioning or switch zoning).
- The server and SAN Volume Controller might
share a back-end storage controller if both of the following
apply:
- Appropriate LUN Partitioning is in place on the back-end storage
controller
- The back-end controller is supported by both the server and the SAN Volume Controller