PageRenderTime 5406ms CodeModel.GetById 18ms RepoModel.GetById 1ms app.codeStats 0ms

/articles/storsimple/storsimple-overview.md

https://gitlab.com/yeah568/azure-content
Markdown | 279 lines | 193 code | 86 blank | 0 comment | 0 complexity | 0e21377d0b2294e337b8b45648982d4d MD5 | raw file
  1. <properties
  2. pageTitle="What is StorSimple? | Microsoft Azure"
  3. description="Describes StorSimple tiering, the device, virtual device, services, and storage management, and introduces key terms used in StorSimple."
  4. services="storsimple"
  5. documentationCenter="NA"
  6. authors="SharS"
  7. manager="carmonm"
  8. editor=""/>
  9. <tags
  10. ms.service="storsimple"
  11. ms.devlang="NA"
  12. ms.topic="article"
  13. ms.tgt_pltfrm="NA"
  14. ms.workload="TBD"
  15. ms.date="04/26/2016"
  16. ms.author="v-sharos@microsoft.com"/>
  17. # StorSimple 8000 series: a hybrid cloud storage solution
  18. ## Overview
  19. Welcome to Microsoft Azure StorSimple, an integrated storage solution that manages storage tasks between on-premises devices and Microsoft Azure cloud storage. StorSimple is an efficient, cost-effective, and easily manageable storage area network (SAN) solution that eliminates many of the issues and expenses associated with enterprise storage and data protection. It uses the proprietary StorSimple 8000 series device, integrates with cloud services, and provides a set of management tools for a seamless view of all enterprise storage, including cloud storage. (The StorSimple deployment information published on the Microsoft Azure website applies to StorSimple 8000 series devices only. If you are using a StorSimple 5000/7000 series device, go to [StorSimple Help](http://onlinehelp.storsimple.com/).)
  20. StorSimple uses [storage tiering](#automatic-storage-tiering) to manage stored data across various storage media. The current working set is stored on-premises on solid state drives (SSDs), data that is used less frequently is stored on hard disk drives (HDDs), and archival data is pushed to the cloud. Moreover, StorSimple uses deduplication and compression to reduce the amount of storage that the data consumes. For more information, go to [Deduplication and compression](#deduplication-and-compression). For definitions of other key terms and concepts used in the StorSimple 8000 series documentation, go to [StorSimple terminology](#storsimple-terminology) at the end of this article.
  21. With StorSimple Update 2, you can identify appropriate volumes as *locally pinned* to ensure that primary data stays local to the device and does not tier to the cloud. This enables you to run workloads that are sensitive to cloud latency, such as SQL and virtual machine workloads, on locally-pinned volumes, while continuing to use the cloud for backup. For more information about locally pinned volumes, see [Use the StorSimple Manager service to manage volumes](storsimple-manage-volumes-u2.md).
  22. Update 2 also enables you to create StorSimple virtual devices that take advantage of the low latencies and high performance provided by Azure premium storage. For more information about StorSimple premium virtual devices, see [Deploy and manage a StorSimple virtual device in Azure](storsimple-virtual-device-u2.md). For more information about Azure premium storage, go to [Premium Storage: High-Performance Storage for Azure Virtual Machine Workloads](../storage/storage-premium-storage.md).
  23. In addition to storage management, StorSimple data protection features enable you to create on-demand and scheduled backups, and then store them locally or in the cloud. Backups are taken in the form of incremental snapshots, which means that they can be created and restored quickly. Cloud snapshots can be critically important in disaster recovery scenarios because they replace secondary storage systems (such as tape backup), and allow you to restore data to your datacenter or to alternate sites if necessary.
  24. ![video icon](./media/storsimple-overview/video_icon.png) Watch the video for a quick introduction to Microsoft Azure StorSimple.
  25. > [AZURE.VIDEO storsimple-hybrid-cloud-storage-solution]
  26. ## Why use StorSimple?
  27. The following table describes some of the key benefits that Microsoft Azure StorSimple provides.
  28. | Feature | Benefit |
  29. |---------|---------|
  30. |Transparent integration | Microsoft Azure StorSimple uses the iSCSI protocol to invisibly link data storage facilities. This ensures that data stored in the cloud, at the datacenter, or on remote servers appears to be stored at a single location.|
  31. |Reduced storage costs|Microsoft Azure StorSimple allocates sufficient local or cloud storage to meet current demands and extends cloud storage only when necessary. It further reduces storage requirements and expense by eliminating redundant versions of the same data (deduplication) and by using compression.|
  32. |Simplified storage management|Microsoft Azure StorSimple provides system administration tools that you can use to configure and manage data stored on-premises, on a remote server, and in the cloud. Additionally, you can manage backup and restore functions from a Microsoft Management Console (MMC) snap-in. StorSimple provides a separate, optional interface that you can use to extend StorSimple management and data protection services to content stored on SharePoint servers. |
  33. |Improved disaster recovery and compliance|Microsoft Azure StorSimple does not require extended recovery time. Instead, it restores data as it is needed. This means normal operations can continue with minimal disruption. Additionally, you can configure policies to specify backup schedules and data retention.
  34. |Data mobility|Data uploaded to Microsoft Azure cloud services can be accessed from other sites for recovery and migration purposes. Additionally, you can use StorSimple to configure StorSimple virtual devices on virtual machines (VMs) running in Microsoft Azure. The VMs can then use virtual devices to access stored data for test or recovery purposes.|
  35. |Support for other cloud service providers |The StorSimple 8000 series with software update 1 or later supports Amazon S3 with RRS, HP, and OpenStack cloud services, as well as Microsoft Azure. (You will still need a Microsoft Azure storage account for device management purposes.) For more information, go to [What's new in Update 1.2](storsimple-update1-release-notes.md#whats-new-in-update-12).|
  36. |Business continuity | Update 1 or later provides a new migration feature that allows StorSimple 5000-7000 series users to migrate their data to a StorSimple 8000 series device.|
  37. |Availability in the Azure Government Portal | StorSimple Update 1 or later is available in the Azure Government Portal. For more information, see [Deploy your on-premises StorSimple device in the Government Portal](storsimple-deployment-walkthrough-gov.md).|
  38. |Data protection and availability | The StorSimple 8000 series with Update 1 or later supports Zone Redundant Storage (ZRS), in addition to Locally Redundant Storage (LRS) and Geo-redundant storage (GRS). Refer to [this article on Azure Storage redundancy options](https://azure.microsoft.com/documentation/articles/storage-redundancy/) for ZRS details.|
  39. |Support for critical applications | With StorSimple Update 2, you can identify appropriate volumes as locally pinned. This capability ensures that data required by critical applications is not tiered to the cloud. Locally pinned volumes are not subject to cloud latencies or connectivity issues. For more information about locally pinned volumes, see [Use the StorSimple Manager service to manage volumes](storsimple-manage-volumes-u2.md).|
  40. |Low latency and high performance | StorSimple Update 2 enables you to create virtual devices that take advantage of the high performance, low latency features of Azure premium storage. For more information about StorSimple premium virtual devices, see [Deploy and manage a StorSimple virtual device in Azure](storsimple-virtual-device-u2.md).|
  41. ![video icon](./media/storsimple-overview/video_icon.png) Watch [this video](https://www.youtube.com/watch?v=4MhJT5xrvQw&feature=youtu.be) for an overview of the StorSimple 8000 series features and benefits.
  42. ## StorSimple components
  43. The Microsoft Azure StorSimple solution includes the following components:
  44. - **Microsoft Azure StorSimple device** an on-premises hybrid storage array that contains SSDs and HDDs, together with redundant controllers and automatic failover capabilities. The controllers manage storage tiering, placing currently used (or hot) data on local storage (in the device or on-premises servers), while moving less frequently used data to the cloud.
  45. - **StorSimple virtual device** also known as the StorSimple Virtual Appliance, this is a software version of the StorSimple device that replicates the architecture and most capabilities of the physical hybrid storage device. The StorSimple virtual device runs on a single node in an Azure virtual machine. Premium virtual devices, which take advantage of Azure premium storage, are available in Update 2 and later.
  46. - **StorSimple Manager service** an extension of the Azure classic portal that lets you manage a StorSimple device or StorSimple virtual device from a single web interface. You can use the StorSimple Manager service to create and manage services, view and manage devices, view alerts, manage volumes, and view and manage backup policies and the backup catalog.
  47. - **Windows PowerShell for StorSimple** a command-line interface that you can use to manage the StorSimple device. Windows PowerShell for StorSimple has features that allow you to register your StorSimple device, configure the network interface on your device, install certain types of updates, troubleshoot your device by accessing the support session, and change the device state. You can access Windows PowerShell for StorSimple by connecting to the serial console or by using Windows PowerShell remoting.
  48. - **Azure PowerShell StorSimple cmdlets** a collection of Windows PowerShell cmdlets that allow you to automate service-level and migration tasks from the command line. For more information about the Azure PowerShell cmdlets for StorSimple, go to the [cmdlet reference](https://msdn.microsoft.com/library/dn920427.aspx).
  49. - **StorSimple Snapshot Manager** an MMC snap-in that uses volume groups and the Windows Volume Shadow Copy Service to generate application-consistent backups. In addition, you can use StorSimple Snapshot Manager to create backup schedules and clone or restore volumes.
  50. - **StorSimple Adapter for SharePoint** a tool that transparently extends Microsoft Azure StorSimple storage and data protection to SharePoint Server farms, while making StorSimple storage viewable and manageable from the SharePoint Central Administration portal.
  51. The diagram below provides a high-level view of the Microsoft Azure StorSimple architecture and components.
  52. ![StorSimple architecture](./media/storsimple-overview/overview-big-picture.png)
  53. The following sections describe each of these components in greater detail and explain how the solution arranges data, allocates storage, and facilitates storage management and data protection. The last section provides definitions for some of the important terms and concepts related to StorSimple components and their management.
  54. ## StorSimple device
  55. The Microsoft Azure StorSimple device is an on-premises hybrid storage array that provides primary storage and iSCSI access to data stored on it. It manages communication with cloud storage, and helps to ensure the security and confidentiality of all data that is stored on the Microsoft Azure StorSimple solution.
  56. The StorSimple device includes SSDs and hard disk drives HDDs, as well as support for clustering and automatic failover. It contains a shared processor, shared storage, and two mirrored controllers. Each controller provides the following:
  57. - Connection to a host computer
  58. - Up to six network ports to connect to the local area network (LAN)
  59. - Hardware monitoring
  60. - Non-volatile random access memory (NVRAM), which retains information even if power is interrupted
  61. - Cluster-aware updating to manage software updates on servers in a failover cluster so that the updates have minimal or no effect on service availability
  62. - Cluster service, which functions like a back-end cluster, providing high availability and minimizing any adverse effects that might occur if an HDD or SSD fails or is taken offline
  63. Only one controller is active at any point in time. If the active controller fails, the second controller becomes active automatically.
  64. For more information, go to [StorSimple hardware components and status](storsimple-monitor-hardware-status.md).
  65. ## StorSimple virtual device
  66. You can use StorSimple to create a virtual device that replicates the architecture and capabilities of the physical hybrid storage device. The StorSimple virtual device (also known as the StorSimple Virtual Appliance) runs on a single node in an Azure virtual machine. (A virtual device can only be created on an Azure virtual machine. You cannot create one on a StorSimple device or an on-premises server.)
  67. The virtual device has the following features:
  68. - It behaves like a physical appliance and can offer an iSCSI interface to virtual machines in the cloud.
  69. - You can create an unlimited number of virtual devices in the cloud, and turn them on and off as necessary.
  70. - It can help simulate on-premises environments in disaster recovery, development, and test scenarios, and can help with item-level retrieval from backups.
  71. With Update 2 and later, the StorSimple virtual device is available in two models: the 8010 device (formerly known as the 1100 model) and the 8020 device. The 8010 device has a maximum capacity of 30 TB. The 8020 device, which takes advantage of Azure premium storage, has a maximum capacity of 64 TB. (In local tiers, Azure premium storage stores data on SSDs whereas standard storage stores data on HDDs.) Note that you must have an Azure premium storage account to use premium storage. For more information about premium storage, go to [Premium Storage: High-Performance Storage for Azure Virtual Machine Workloads](../storage/storage-premium-storage.md).
  72. For more information about the StorSimple virtual device, go to [Deploy and manage a StorSimple virtual device in Azure](storsimple-virtual-device-u2.md).
  73. ## StorSimple Manager service
  74. Microsoft Azure StorSimple provides a web-based user interface (the StorSimple Manager service) that enables you to centrally manage datacenter and cloud storage. You can use the StorSimple Manager service to perform the following tasks:
  75. - Configure system settings for StorSimple devices.
  76. - Configure and manage security settings for StorSimple devices.
  77. - Configure cloud credentials and properties.
  78. - Configure and manage volumes on a server.
  79. - Configure volume groups.
  80. - Back up and restore data.
  81. - Monitor performance.
  82. - Review system settings and identify possible problems.
  83. You can use the StorSimple Manager service to perform all administration tasks except those that require system down time, such as initial setup and installation of updates.
  84. For more information, go to [Use the StorSimple Manager service to administer your StorSimple device](storsimple-manager-service-administration.md).
  85. ## Windows PowerShell for StorSimple
  86. Windows PowerShell for StorSimple provides a command-line interface that you can use to create and manage the Microsoft Azure StorSimple service and set up and monitor StorSimple devices. It is a Windows PowerShellbased, command-line interface that includes dedicated cmdlets for managing your StorSimple device. Windows PowerShell for StorSimple has features that allow you to:
  87. - Register a device.
  88. - Configure the network interface on a device.
  89. - Install certain types of updates.
  90. - Troubleshoot your device by accessing the support session.
  91. - Change the device state.
  92. You can access Windows PowerShell for StorSimple from a serial console (on a host computer connected directly to the device) or remotely by using Windows PowerShell remoting. Note that some Windows PowerShell for StorSimple tasks, such as initial device registration, can only be done on the serial console.
  93. For more information, go to [Use Windows PowerShell for StorSimple to administer your device](storsimple-windows-powershell-administration.md).
  94. ## Azure PowerShell StorSimple cmdlets
  95. The Azure PowerShell StorSimple cmdlets are a collection of Windows PowerShell cmdlets that allow you to automate service-level and migration tasks from the command line. For more information about the Azure PowerShell cmdlets for StorSimple, go to the [cmdlet reference](https://msdn.microsoft.com/library/dn920427.aspx).
  96. ## StorSimple Snapshot Manager
  97. StorSimple Snapshot Manager is a Microsoft Management Console (MMC) snap-in that you can use to create consistent, point-in-time backup copies of local and cloud data. The snap-in runs on a Windows Serverbased host. You can use StorSimple Snapshot Manager to:
  98. - Configure, back up, and delete volumes.
  99. - Configure volume groups to ensure that backed up data is application-consistent.
  100. - Manage backup policies so that data is backed up on a predetermined schedule and stored in a designated location (locally or in the cloud).
  101. - Restore volumes and individual files.
  102. Backups are captured as snapshots, which record only the changes since the last snapshot was taken and require far less storage space than full backups. You can create backup schedules or take immediate backups as needed. Additionally, you can use StorSimple Snapshot Manager to establish retention policies that control how many snapshots will be saved. If you subsequently need to restore data from a backup, StorSimple Snapshot Manager lets you select from the catalog of local or cloud snapshots.
  103. If a disaster occurs or if you need to restore data for another reason, StorSimple Snapshot Manager restores it incrementally as it is needed. Data restoration does not require that you shut down the entire system while you restore a file, replace equipment, or move operations to another site.
  104. For more information, go to [What is StorSimple Snapshot Manager?](storsimple-what-is-snapshot-manager.md)
  105. ## StorSimple Adapter for SharePoint
  106. Microsoft Azure StorSimple includes the StorSimple Adapter for SharePoint, an optional component that transparently extends StorSimple storage and data protection features to SharePoint server farms. The adapter works with a Remote Blob Storage (RBS) provider and the SQL Server RBS feature, allowing you to move BLOBs to a server backed up by the Microsoft Azure StorSimple system. Microsoft Azure StorSimple then stores the BLOB data locally or in the cloud, based on usage.
  107. The StorSimple Adapter for SharePoint is managed from within the SharePoint Central Administration portal. Consequently, SharePoint management remains centralized, and all storage appears to be in the SharePoint farm.
  108. For more information, go to [StorSimple Adapter for SharePoint](storsimple-adapter-for-sharepoint.md).
  109. ## Storage management technologies
  110. In addition to the dedicated StorSimple device, virtual device, and other components, Microsoft Azure StorSimple uses the following software technologies to provide quick access to data and to reduce storage consumption:
  111. - [Automatic storage tiering](#automatic-storage-tiering)
  112. - [Thin provisioning](#thin-provisioning)
  113. - [Deduplication and compression](#deduplication-and-compression)
  114. ### Automatic storage tiering
  115. Microsoft Azure StorSimple automatically arranges data in logical tiers based on current usage, age, and relationship to other data. Data that is most active is stored locally, while less active and inactive data is automatically migrated to the cloud. The following diagram illustrates this storage approach.
  116. ![StorSimple storage tiers](./media/storsimple-overview/hcs-data-services-storsimple-components-tiers.png)
  117. To enable quick access, StorSimple stores very active data (hot data) on SSDs in the StorSimple device. It stores data that is used occasionally (warm data) on HDDs in the device or on servers at the datacenter. It moves inactive data, backup data, and data retained for archival or compliance purposes to the cloud.
  118. >[AZURE.NOTE] In Update 2 or later, you can specify a volume as locally pinned, in which case the data remains on the local device and is not tiered to the cloud.
  119. StorSimple adjusts and rearranges data and storage assignments as usage patterns change. For example, some information might become less active over time. As it becomes progressively less active, it is migrated from SSDs to HDDs and then to the cloud. If that same data becomes active again, it is migrated back to the storage device.
  120. The storage tiering process occurs as follows:
  121. 1. A system administrator sets up a Microsoft Azure cloud storage account.
  122. 2. The administrator uses the serial console and the StorSimple Manager service (running in the Azure classic portal) to configure the device and file server, creating volumes and data protection policies. On-premises machines (such as file servers) use the Internet Small Computer System Interface (iSCSI) to access the StorSimple device.
  123. 3. Initially, StorSimple stores data on the fast SSD tier of the device.
  124. 4. As the SSD tier approaches capacity, StorSimple deduplicates and compresses the oldest data blocks, and moves them to the HDD tier.
  125. 5. As the HDD tier approaches capacity, StorSimple encrypts the oldest data blocks and sends them securely to the Microsoft Azure storage account via HTTPS.
  126. 6. Microsoft Azure creates multiple replicas of the data in its datacenter and in a remote datacenter, ensuring that the data can be recovered if a disaster occurs.
  127. 7. When the file server requests data stored in the cloud, StorSimple returns it seamlessly and stores a copy on the SSD tier of the StorSimple device.
  128. ### Thin provisioning
  129. Thin provisioning is a virtualization technology in which available storage appears to exceed physical resources. Instead of reserving sufficient storage in advance, StorSimple uses thin provisioning to allocate just enough space to meet current requirements. The elastic nature of cloud storage facilitates this approach because StorSimple can increase or decrease cloud storage to meet changing demands.
  130. >[AZURE.NOTE] Locally pinned volumes are not thinly provisioned. Storage allocated to a local-only volume is provisioned in its entirety when the volume is created.
  131. ### Deduplication and compression
  132. Microsoft Azure StorSimple uses deduplication and data compression to further reduce storage requirements.
  133. Deduplication reduces the overall amount of data stored by eliminating redundancy in the stored data set. As information changes, StorSimple ignores the unchanged data and captures only the changes. In addition, StorSimple reduces the amount of stored data by identifying and removing unnecessary information.
  134. >[AZURE.NOTE] Data on locally pinned volumes is not deduplicated or compressed. However, backups of locally pinned volumes are deduplicated and compressed.
  135. ## StorSimple terminology
  136. Before deploying your Microsoft Azure StorSimple solution, we recommend that you review the following terms and definitions.
  137. ### Key terms and definitions
  138. | Term (Acronym or abbreviation) | Description |
  139. | ------------------------------ | ---------------- |
  140. | access control record (ACR) | A record associated with a volume on your Microsoft Azure StorSimple device that determines which hosts can connect to it. The determination is based on the iSCSI Qualified Name (IQN) of the hosts (contained in the ACR) that are connecting to your StorSimple device.|
  141. | AES-256 | A 256-bit Advanced Encryption Standard (AES) algorithm for encrypting data as it moves to and from the cloud. |
  142. | allocation unit size (AUS) | The smallest amount of disk space that can be allocated to hold a file in your Windows file systems. If a file size is not an even multiple of the cluster size, extra space must be used to hold the file (up to the next multiple of the cluster size) resulting in lost space and fragmentation of the hard disk. <br>The recommended AUS for Azure StorSimple volumes is 64 KB because it works well with the deduplication algorithms.|
  143. | automated storage tiering | Automatically moving less active data from SSDs to HDDs and then to a tier in the cloud, and then enabling management of all storage from a central user interface.|
  144. | backup catalog | A collection of backups, usually related by the application type that was used. This collection is displayed in the Backup Catalog page of the StorSimple Manager service UI.|
  145. | backup catalog file | A file containing a list of available snapshots currently stored in the backup database of StorSimple Snapshot Manager. |
  146. | backup policy | A selection of volumes, type of backup, and a timetable that allows you to create backups on a predefined schedule.|
  147. | binary large objects (BLOBs) | A collection of binary data stored as a single entity in a database management system. BLOBs are typically images, audio, or other multimedia objects, although sometimes binary executable code is stored as a BLOB.|
  148. | Challenge Handshake Authentication Protocol (CHAP) | A protocol used to authenticate the peer of a connection, based on the peer sharing a password or secret. CHAP can be one-way or mutual. With one-way CHAP, the target authenticates an initiator. Mutual CHAP requires that the target authenticate the initiator and that the initiator authenticates the target. |
  149. | clone | A duplicate copy of a volume. |
  150. |Cloud as a Tier (CaaT) | Cloud storage integrated as a tier within the storage architecture so that all storage appears to be part of one enterprise storage network.|
  151. | cloud service provider (CSP) | A provider of cloud computing services.|
  152. | cloud snapshot | A point-in-time copy of volume data that is stored in the cloud. A cloud snapshot is equivalent to a snapshot replicated on a different, off-site storage system. Cloud snapshots are particularly useful in disaster recovery scenarios.|
  153. | cloud storage encryption key | A password or a key used by your StorSimple device to access the encrypted data sent by your device to the cloud.|
  154. | cluster-aware updating | Managing software updates on servers in a failover cluster so that the updates have minimal or no effect on service availability.|
  155. | datapath | A collection of functional units that perform inter-connected data processing operations.|
  156. | deactivate | A permanent action that breaks the connection between the StorSimple device and the associated cloud service. Cloud snapshots of the device remain after this process and can be cloned or used for disaster recovery.|
  157. | disk mirroring | Replication of logical disk volumes on separate hard drives in real time to ensure continuous availability.|
  158. | dynamic disk mirroring | Replication of logical disk volumes on dynamic disks.|
  159. | dynamic disks | A disk volume format that uses the Logical Disk Manager (LDM) to store and manage data across multiple physical disks. Dynamic disks can be enlarged to provide more free space.|
  160. | Extended Bunch of Disks (EBOD) enclosure | A secondary enclosure of your Microsoft Azure StorSimple device that contains extra hard drive disks for additional storage.|
  161. | fat provisioning | A conventional storage provisioning in which storage space is allocated based on anticipated needs (and is usually beyond the current need). See also *thin provisioning*.|
  162. | hard disk drive (HDD) | A drive that uses rotating platters to store data.|
  163. | hybrid cloud storage | A storage architecture that uses local and off-site resources, including cloud storage.|
  164. | Internet Small Computer System Interface (iSCSI) | An Internet Protocol (IP)based storage networking standard for linking data storage equipment or facilities.|
  165. | iSCSI initiator | A software component that enables a host computer running Windows to connect to an external iSCSI-based storage network.|
  166. | iSCSI Qualified Name (IQN) | A unique name that identifies an iSCSI target or initiator.|
  167. | iSCSI target | A software component that provides centralized iSCSI disk subsystems in storage area networks.|
  168. | live archiving | A storage approach in which archival data is accessible all the time (it is not stored off-site on tape, for example). Microsoft Azure StorSimple uses live archiving.|
  169. |locally pinned volume | a volume that resides on the device and is never tiered to the cloud. |
  170. | local snapshot | A point-in-time copy of volume data that is stored on the Microsoft Azure StorSimple device.|
  171. | Microsoft Azure StorSimple | A powerful solution consisting of a datacenter storage appliance and software that enables IT organizations to leverage cloud storage as though it were datacenter storage. StorSimple simplifies data protection and data management while reducing costs. The solution consolidates primary storage, archive, backup, and disaster recovery (DR) through seamless integration with the cloud. By combining SAN storage and cloud data management on an enterprise-class platform, StorSimple devices enable speed, simplicity, and reliability for all storage-related needs.|
  172. | Power and Cooling Module (PCM) | Hardware components of your StorSimple device consisting of the power supplies and the cooling fan, hence the name Power and Cooling module. The primary enclosure of the device has two 764W PCMs whereas the EBOD enclosure has two 580W PCMs.|
  173. | primary enclosure | Main enclosure of your StorSimple device that contains the application platform controllers.|
  174. | recovery time objective (RTO) | The maximum amount of time that should be expended before a business process or system is fully restored after a disaster.|
  175. |serial attached SCSI (SAS) | A type of hard disk drive (HDD).|
  176. | service data encryption key | A key made available to any new StorSimple device that registers with the StorSimple Manager service. The configuration data transferred between the StorSimple Manager service and the device is encrypted using a public key and can then be decrypted only on the device using a private key. Service data encryption key allows the service to obtain this private key for decryption.|
  177. | service registration key | A key that helps register the StorSimple device with the StorSimple Manager service so that it appears in the Azure classic portal for further management actions.|
  178. | Small Computer System Interface (SCSI) | A set of standards for physically connecting computers and passing data between them.|
  179. | solid state drive (SSD) | A disk that contains no moving parts; for example, a flash drive.|
  180. | storage account | A set of access credentials linked to your storage account for a given cloud service provider.|
  181. | StorSimple Adapter for SharePoint| A Microsoft Azure StorSimple component that transparently extends StorSimple storage and data protection to SharePoint server farms.|
  182. | StorSimple Manager service | An extension of the Azure classic portal that allows you to manage your Azure StorSimple on-premises and virtual devices.|
  183. | StorSimple Snapshot Manager | A Microsoft Management Console (MMC) snap-in for managing backup and restore operations in Microsoft Azure StorSimple.|
  184. | take backup | A feature that allows the user to take an interactive backup of a volume. It is an alternate way of taking a manual backup of a volume as opposed to taking an automated backup via a defined policy.|
  185. | thin provisioning | A method of optimizing the efficiency with which the available storage space is used in storage systems. In thin provisioning, the storage is allocated among multiple users based on the minimum space required by each user at any given time. See also *fat provisioning*.|
  186. | tiering | Arranging data in logical groupings based on current usage, age, and relationship to other data. StorSimple automatically arranges data in tiers. |
  187. | volume | Logical storage areas presented in the form of drives. StorSimple volumes correspond to the volumes mounted by the host, including those discovered through the use of iSCSI and a StorSimple device.|
  188. | volume container | A grouping of volumes and the settings that apply to them. All volumes in your StorSimple device are grouped into volume containers. Volume container settings include storage accounts, encryption settings for data sent to cloud with associated encryption keys, and bandwidth consumed for operations involving the cloud.|
  189. | volume group | In StorSimple Snapshot Manager, a volume group is a collection of volumes configured to facilitate backup processing.|
  190. | Volume Shadow Copy Service (VSS)| A Windows Server operating system service that facilitates application consistency by communicating with VSS-aware applications to coordinate the creation of incremental snapshots. VSS ensures that the applications are temporarily inactive when snapshots are taken.|
  191. | Windows PowerShell for StorSimple | A Windows PowerShellbased command-line interface used to operate and manage your StorSimple device. While maintaining some of the basic capabilities of Windows PowerShell, this interface has additional dedicated cmdlets that are geared towards managing a StorSimple device.|
  192. ## Next steps
  193. Learn about [StorSimple security](storsimple-security.md).