Saturday, 1 September 2012

Vfiler

MultiStore
  1. MultiStore is a software product you can use optionally.
  2. MultiStore enables you to partition the storage and network resources of a single storage system so that it appears as multiple storage systems on the network.
  3. Each "storage system" created as a result of the partitioning is called a vFiler unit.
  4. A vFiler unit, using the resources assigned, delivers file services to its clients as a storage system does.The storage resource assigned to a vFiler unit can be one or more qtrees or volumes. The network resource assigned can be one or more base IP addresses or IP aliases associated with network interfaces.
  5. You can add or remove resources at any time.
  6. we don't need additional license for the vfiler unit, we can use physical filer license to vfiler unit.
Reasons for using MultiStore

MultiStore has many features that you can use for your provisioning needs.
  1. To consolidate multiple servers to one storage system.
  2. To use the storage system to host data for multiple customers, such as clients of a service provider or different organizations within an enterprise.
  3. To use the SnapMirror technology for migrating data from one storage system to another
    transparently.
Some limitations of MultiStore
  1. You can have a maximum of 65 vFiler units on a storage system. You can create 64 vFiler units on a storage system. The 65th vFiler unit is vfiler0, which is created automatically when MultiStore is licensed on the storage system.
  2. In an active/active configuration, you can create up to 64 vFiler units on each node of the active/active configuration, for a maximum of 130 vFilers in the active/active configuration.
  3. Only Ethernet interfaces are supported for vFiler units
  4. Only the NFS, CIFS, iSCSI, HTTP, and FTP protocols are supported for the vFiler units. However, protocols not supported on vFiler units are supported on vfiler0, the default vFiler unit.


Related Topic

VFILER COMMANDS



Please write your valuable comments, About this Blogspot.

No comments:

Post a Comment