System physical capacity
|The total physical capacity that can be allocated within a single system.|
|System virtual capacity||The maximum system capacity that can be defined by pools. This capacity can be larger than the system physical capacity.|
|System free virtual capacity||The system virtual capacity minus the sum of the pools virtual capacity.|
|Pool physical capacity||The maximum usable net capacity that can be allocated to the pool entities.|
|Pool virtual capacity||The limit on the size of all volumes (thin and thick provisioned), excluding snapshots.|
|Pool allocated virtual space||The sum of all volumes (thick and thin, excluding thin snapshots). The allocated space cannot exceed the pool virtual capacity.|
|Pool allocated physical space||The sum of all thick volumes, plus the physical space consumed by all the thin volumes and snapshots. The used space cannot exceed the pool physical capacity.|
|Pool free physical space||The defined pool physical capacity minus the allocated physical space.|
|Pool free virtual space||The defined pool virtual capacity minus the allocated virtual space.|
|Reserved space||Automatically defined spare physical space for the pool, to support pool physical space depletion behavior.|
|Emergency buffer||A policy for automatically extending of the pool physical capacity in the event of pool physical space depletion.|
|Limited state||Upon further accepting writes, the pool enters a Limited state where no new volumes can be created, but the existing volumes can be written into.|
|Locked state||If the pool can no longer expand, it enters a Locked state and its entities can no longer accept writes.|
A set of consecutively addressed disk blocks that are presented to the storage controller as a range of consecutively numbered logical blocks with disk-like storage and I/O semantics.
The InfiniBox volume accepts the following attributes: capacity (size, used capacity, tree allocation), thin provisioning, mapping to a host, write protection, ability to use the system's SSD drives.
|Thick volume||Reserved-space volume. Virtual and Physical space allocation is done immediately as Thick Volume is created, at the amount of the volume size.|
|Thin volume||Shared-space volume. Thin volumes consume physical space upon writes. The virtual space is allocated upon volume creation to the amount of the volume size. |
The initially allocated physical space is 0 (zero). In a case of space depletion, the allocation is not guaranteed for thin volumes.
|Filesystem||The filesystem controls the way data is stored on the storage system by providing a name to each piece of data (file). The file system allows to search for and access the files.|
|Consistency Group (CG)||Container of volumes|
|Group-consistent snapshot||Snapshot operation that is performed on the consistency group entities which ensures that write-order-fidelity is maintained across all the objects in the group|
|Snapshot Group (SG)||Container of snapshots created through a group-consistent snapshot|
|Replica consistency group||Consistency group that belongs to a replica (either as a source or as a target)|
|WWPN||World Wide Port Name. A globally unique ID for each FC port. The equivalent of MAC address in Fiber Channel.|
|WWNN||World Wide Node Name. A globally unique ID for a system / group of WWPNs.|
|Multipath driver||Host-side driver that allows the host to leverage more than 1 path to a LUN.|
|Node||An InfiniBox server. Typically, there are 3 nodes in a system.|
|Ethernet Port (Port)||Physical Ethernet port (copper / optical).|
|Ethernet Interface||One or more Ethernet Ports that are grouped together for the purpose of redundancy and/or performance using LACP.|
|Service||A network data service, e.g. NFS, iSCSI, Replication|
|IP address||A group of floating IP addresses that will offer the service (Each IP offers 1 service). It is recommended that each Network Space will have 6 IP Addresses to ensure even workload distribution.|
|Network||A set of definitions for a network address space, annotated using CIDR. Example: 10.0.0.0/24.|
The InfiniBox system whose volume is replicated.
The InfiniBox system that the volume is replicated to.
A volume on the source system that is replicated (or planned to be replicated).
A volume on the target system that is the destination of the replicated data. A target volume that is part of a replica cannot accept host writes.
An entity that matches a pair of source and target volumes and other settings essential for the replication.
The InfiniBox system through which the user manages the replica.
The InfiniBox system at the other end of the replica.
Both local and remote system may contain source and target datasets.
A bidirectional means of communication between local and remote systems.
The link is defined via Management.
The process of creating a snapshot of the source and delivering it to the target.
The amount of time between two planned sync jobs.