Friday, 7 February 2014

EMC Avamar Deduplication

EMC Avamar enables fast, efficient backup and recovery by reducing the size of backup data at the client—before it’s transferred across the network and stored. Avamar's variable-length deduplication dramatically reduces network traffic by only sending unique blocks, compressed and encrypted over local area networks (LANs) or wide area networks (WANs). Blocks that were previously stored are never backed up again.

Avamar is a sourcebase global deduplication solution which enables fast, efficient backup and recovery by reducing the size of backup data at the client before it is transferred across the network and stored. Avamar’s data deduplication dramatically reduces network traffic by only sending unique blocks over LAN/WAN. Blocks that were previously stored are never backed up again.

This means huge savings in bandwidth for backup, a lot less disk storage needed on the back end, and most importantly very fast backups often as much as ten times faster.

Avamar backups can be quickly recovered in just one step eliminating the hassle of restoring full and subsequent incremental backups to reach the desired recovery point. Backup data is encrypted during transit across the network and at rest for added security.

There are three ways to define data deduplication:

File-Level 
File level deduplication reduce storage needs for file servers by identifying duplicate files and providing an efficient mechanism for consolidating them. The most common implementation of single instance storage is at the file level. With this method, a single change in a file results in the entire file being identified as unique. Example: If there were 3 versions of a file in a backup environment, the 3 files in their entirety are stored.

Fixed Block 
Fixed block deduplication is commonly employed in snapshot and replication technologies. This method breaks a file into fixed length sub-objects. However, even with small changes to the data, all fixed length segments in a dataset can change despite the fact that very little of the dataset has actually changed.

Variable Block 
With variable block level deduplication, a change in a file results in only the variable-sized block containing the change being identified as unique. Consequently, more data is identified as common data, and in the case of backup, there is less data to store as only the unique data is backed up. This is the method used by Avamar

Saturday, 1 February 2014

NetApp Common Terminology

NetApp Common Terminology  - Storage Terms

storage controller
The component of a storage system that runs the Data ONTAP operating system and controls its disk subsystem. Storage controllers are also sometimes called controllers, storage appliances, appliances, storage engines, heads, CPU modules, or controller modules.

storage system
The hardware device running Data ONTAP that receives data from and sends data to native disk shelves, third-party storage, or both. Storage systems that run Data
ONTAP are sometimes referred to as filers, appliances, storage appliances, VSeries systems, or systems.

Cluster and high-availability terms below:

cluster

  • In Data ONTAP 8.x Cluster-Mode, a group of connected nodes (storage systems) that share a global namespace and that you can manage as a single virtual server or multiple virtual servers, providing performance, reliability, and scalability benefits.
  • In the Data ONTAP 7.1 release family and earlier releases, a pair of storage systems (sometimes called nodes) configured to serve data for each other if one of the two systems stops functioning.
  • In the Data ONTAP 7.3 and 7.2 release families, this functionality is referred to as an active/active configuration.
  • For some storage array vendors, cluster refers to the hardware component on which host adapters and ports are located. Some storage array vendors refer to this component as a controller.


HA (high availability)

  • In Data ONTAP 8.x, the recovery capability provided by a pair of nodes (storage systems), called an HA pair, that are configured to serve data for each other if one of the two nodes stops functioning.
  • In the Data ONTAP 7.3 and 7.2 release families, this functionality is referred to as an active/active configuration.


HA pair 

  • In Data ONTAP 8.x, a pair of nodes (storage systems) configured to serve data for each other if one of the two nodes stops functioning.
  • In the Data ONTAP 7.3 and 7.2 release families, this functionality is referred to as an active/active configuration.