|
|
| (998 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | The QuantaStor Administrators Guide is intended for all administrators and cloud users who plan to manage their storage using QuantaStor Manager as well as for those just looking to get a deeper understanding of how the QuantaStor Storage System Platform (SSP) works. | + | [[Category:admin_guide]] |
| | + | The QuantaStor Administrator Guide is intended for all IT administrators working to setup or maintain a QuantaStor system or grid of systems as well as for those just looking to get a deeper understanding of how the QuantaStor software defined storage platform works. |
| | | | |
| − | == Definitions == | + | == Administrator Guide Topic Links == |
| | | | |
| − | The following series of definitions are here to lay the ground work and context for the rest of the document. Here we define all the various objects and elements that can be managed using QuantaStor.
| + | [[Storage System]] |
| | | | |
| − | === Storage System ===
| + | [[Grid Configuration]] |
| | | | |
| − | The storage system is the object that represents the entire iSCSI server both from a physical and logical standpoint. This includes all the physical disks, fans, enclosures, power supplies and other physical elements of the system as well as all the logical elements including the storage pools, volumes, users, and storage clouds.
| + | [[License Management]] |
| | | | |
| − | === Storage Pool === | + | === Hardware Configuration === |
| − | The storage pool is an aggregation of one or more physical disks into a larger entity. Each storage pool has a single RAID type associated with it, and all storage volumes that are created within that storage pool inherit RAID type. For example, if a given storage pool of type RAID1 (mirroring) is made up to two 1TB disks, then there is 1TB of usable storage available to create storage volumes (LUNs) with.
| + | |
| | | | |
| − | === Storage Volume ===
| + | [[Network Port Configuration]] |
| − | The storage volume is the most important object in the system as it represents the virtual disk device that is presented to the host a LUN. Each storage volume has a unique name and a unique target number and a unique IQN associated with it. Storage volumes can be created "thin" which means they do not use up any disk space until the device has been written to. Or "thick" which means that all the space for the storage volume is pre-reserved up front.
| + | |
| | | | |
| − | === Storage Volume Group ===
| + | [[Physical Disk/Device Management]] |
| − | Often times hosts and virtual machines will be comprised of more than one storage volume. Sometimes one storage volume is dedicated as a boot disk and another as a swap disk. In other cases there are multiple disks utilized to separate out the elements of a database application (index, data, log) into separate storage volumes for improved performance. Whatever the reason, it can become difficult to manage you storage system without a way to group these storage volumes together so that they can be operated on as a single unit. That's what Storage Volume Groups provide. They're simple containers for collecting together an arbitrary set of storage volumes so that they can be cloned, snapshot, or even deleted as a group.
| + | |
| | | | |
| − | === Snapshot Schedules ===
| + | [[Hardware Controller & Enclosure Management]] |
| − | Snapshot schedules are a powerful tool for automatically generating recovery points (snapshots), on a schedule so that you don't have to think about it. The snapshot schedule consists of a list of storage volumes to be snapshot, and a list of days of the week and hours of the day at which the snapshots are to be taken. A 'max snapshots' parameter sets the point at which the oldest snapshot created by the schedule should be cleaned up (default: 10).
| + | |
| | | | |
| − | === Host ===
| + | [[Multipath Configuration]] |
| | | | |
| − | A host represents a server, workstation, laptop, or virtual machine that has a software or hardware iSCSI initiator by which it can access storage volumes (iSCSI targets) exposed by the storage system. Hosts are identified by one or more initiator IQNs and IP addresses. We recommend that you identify your hosts by [http://en.wikipedia.org/wiki/ISCSI IQN] as that has the most flexibility since IP addresses can frequently change, especially if a host is using DHCP to acquire it's IP address.
| + | === Storage Provisioning === |
| | | | |
| − | === Host Group ===
| + | [[Storage Pool Management]] |
| − | A host group is an arbitrary collection of hosts that have been grouped together for some purpose. Sometimes they're grouped together by location, but more ofter Host Groups are used to group together hosts that have been formed into a cluster such as a Microsoft Fail-over Cluster / MSCS. In other cases as with VMWare or XenServer multiple hosts can be combined together to form "resource pools" in which the virtual machines can live migrate from one host to another. In all these cases, each host typically needs access to all the same storage volumes in order to facilitate fail-over. This can be a tedious process with many storage systems as most require that an assignment operation be executed for each host and each volume. If you have 10 hosts and 100 volumes, that amounts to 1000 storage assignment tasks and potentially days of work. With QuantaStor we've tried our best to make that a snap, and Host Groups are key to making that possible. Using the same scenario but with 1 host group and 100 volumes, the storage assignment to the group of 10 hosts can be done in a single operation through QuantaStor manager in less than a minute.
| + | |
| | | | |
| − | === Storage Cloud ===
| + | [[Storage Volume Management]] |
| − | === Storage Quota ===
| + | |
| − | === Roles ===
| + | |
| − | === Permissions ===
| + | |
| − | === Users ===
| + | |
| − | === User Groups ===
| + | |
| − | === Target Port ===
| + | |
| − | === Sessions ===
| + | |
| − | === CHAP Authentication ===
| + | |
| − | === Alerts ===
| + | |
| − | === Events ===
| + | |
| − | === Tasks ===
| + | |
| | | | |
| − | == Target Port Configuration ==
| + | [[Network Share Management]] |
| | | | |
| − | === NIC Bonding / Trunking ===
| + | [[Cloud Containers/NAS Gateway]] |
| | | | |
| − | == Alert Settings == | + | === Security, Alerting & Upgrades === |
| | | | |
| − | == Managing Hosts ==
| + | [[Call-home/Alert Management]] |
| | | | |
| − | == Managing Snapshot Schedules ==
| + | [[Security Configuration]] |
| − | === Near Continuous Data Replication (N-CDP) ===
| + | |
| | | | |
| − | == Managing Sessions ==
| + | [[Upgrade Manager]] |
| − | === Dropping Sessions ===
| + | |
| | | | |
| − | == Managing Storage Volumes == | + | === Snapshots & Replication === |
| − | === Creating & Deleting Storage Volumes ===
| + | |
| − | === Creating Snapshots ===
| + | [[Snapshot Schedules]] |
| − | === Creating Clones ===
| + | |
| − | === Restoring from Snapshots === | + | [[Backup Policies]] |
| − | === Converting a Snapshot into a Primary === | + | |
| | + | [[Remote-replication (DR)]] |
| | + | |
| | + | === Cluster Configuration === |
| | + | |
| | + | [[HA Cluster Setup (JBODs)]] |
| | + | |
| | + | [[HA Cluster Setup (external SAN)]] |
| | + | |
| | + | [[Scale-out_Block_Setup_(ceph)|Scale-out Block Setup (ceph)]] |
| | + | |
| | + | [[Scale-out Object Setup (ceph)|Scale-out Object Setup (ceph)]] |
| | + | |
| | + | [[Scale-out File Setup (glusterfs)|Scale-out File Setup (glusterfs)]] |
| | + | |
| | + | === Optimization === |
| | + | |
| | + | [[Performance Tuning]] |
The QuantaStor Administrator Guide is intended for all IT administrators working to setup or maintain a QuantaStor system or grid of systems as well as for those just looking to get a deeper understanding of how the QuantaStor software defined storage platform works.
