iomega device-device replication guide en

Download Iomega Device-Device Replication Guide En

Post on 11-Oct-2015

18 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

  • Using iomega storCenter network storage deviCes for data repliCation in remote offiCes and distribUted enterprise branCh loCations

    WHITE PAPER

    autumn 2012

    ExEcuTIvE SummARy 1introduction 2

    Solution Configuration 3

    Technology Overview 4

    Use Cases 6Data replication for business continuity 6

    Host data backup 10

    Information sharing: data center & ROBO 20

    Personal Cloud backup 22

    Conclusion 24

  • White Paper

    IOMEGA DEVICE-TO-DEVICE REPLICATION SOLUTION GUIDE

    1

    * for the purposes of this white paper, D2D represents device-to-device rather than disk-to-disk.

    ExEcuTIvE SummARyThough Business Continuity (BC) is a with critical component in an IT strategy for businesses of any size, it is particularly important for businesses with remote offices or Distributed Enterprise branch locations. Backup-to-tape and backup-to-disk are two common methods of implementing BC. However, these host-based solutions require investment in additional hardware and software, and result in extra administrative costs. A storage-device-based solution allows data to be replicated from each remote office or branch location, back to the central office, without the need for a host. Such a solution typically offers higher cost-efficiency, tighter integration with storage features, and better performance.

    The Iomega storCenter is an integrated storage device that offers both NAS and iSCSI functionality to enable flexible deployment options for remote offices and branch offices (ROBO). The StorCenter is powered by EMC LifeLine software to allow customers to protect data by replicating it using EMCs world-class storage and security technologies.

    This white paper discusses the device-to-device (D2D*) replication feature available on the StorCenter and how it can be leveraged in remote office and branch office (ROBO) use cases to achieve business continuity across multiple, geographically dispersed sites. Detailed instructions and procedures are also provided to help users plan and implement a ROBO BC strategy using the StorCenter.

    Business challenges

    Data availability is one of the biggest concerns for any IT organization. Over the past decade, the value and sheer amount of an organizations data have increased dramatically while the importance of protecting all data has grown at an even faster rate. The challenge of maintaining a highly reliable, high-performance BC strategy is becoming increasingly difficult and compounded by four factors: shrinking IT budgets, shortening backup windows, increasing amounts of data, and aggressive service-level agreements (SLAs). The challenge is even more pronounced for organizations with multiple locations.

    Data replication has increasingly become a priority for many organizations due to concerns about disaster and unplanned outages. A disaster recovery (DR) strategy requires data to be replicated to a remote site. In case of site failure, data at the remote site can quickly be made available for operational readiness. For any business, the DR consideration further adds complexity to an already demanding data availability requirement. But businesses managing storage across multiple locations face significantly higher levels of complexity, since the data from each remote or branch office must first be replicated back to the central office, before the company-wide data can be replicated to the offsite location for DR purposes.

    Host-based backup and replication solutions require at least one dedicated server installed with a software application to facilitate backup and replication jobs. Host-based solutions likely increase operational complexity, and result in extra administrative costs. In contrast, a storage-device-based solution performs backup and replication directly on the storage device without the help of a host and application. As a result, it offers better cost-efficiency and performance. Since valuable resources on the storage device are spent on such a backup or replication job, the devices capabilities of serving other functions could be impacted. Therefore, a storage device-based solution is a great complement to host-based solutions, but should not replace them completely. Today, many organizations are distributed around the world. Data synchronization between the IT data centers and the ROBO offices presents another big challenge. Moreover, the number of mobile workers is growing dramatically

  • White Paper

    IOMEGA DEVICE-TO-DEVICE REPLICATION SOLUTION GUIDE

    2

    due to advancement in technologies. How to make data available for these mobile workers on-the-go is another challenge that faces many organizations.

    InTRoducTIonAn Iomega StorCenter NAS offers great reliability, ease of use, and ease of management characteristics that are designed specifically for the needs of SMBs and ROBO offices. All Iomega StorCenter NAS devices support host-based backup solutions using applications such as EMC Retrospect and EMC NetWorker. The StorCenter adds the device-to-device replication feature to enable a device-based solution.

    With the D2D replication feature, customers can copy or back up files to and from the StorCenter whether it is local or remote; to any other StorCenter, an Iomega Personal Cloud; any other network target; or an external USB drive. Jobs can be set to run at user request, at a predetermined schedule, or at the touch of the StorCenters QuikTransfer button. The StorCenter uses either the rsync or Windows File Sharing protocol to transfer data.

    This paper examines several use cases where the D2D replication feature can be utilized to address some of the business challenges described above. Detailed instructions and procedures are provided to help guide through the planning and implementation of the solutions. The use cases include:

    t Replication between Iomega devices for BC/DR

    t Host data backup to an Iomega device

    t Data sharing between a data center and a ROBO office

    Audience

    Information contained in this white paper is intended for Iomega customers, partners, and service personnel involved in planning, architecting, or administering data backup and replication with an Iomega StorCenter.

    Terminology

    t LAn: Local Area Network. t WAn: Wide Area Network t common Internet File System (cIFS): A distributed file system providing transparent access to remote file

    systems. t Windows File Sharing: the practice of distributing or providing access to files using the CIFS protocol. t nAS: Network Attached Storage. The name given to dedicated data storage technology that can be connected

    directly to a computer network to provide centralized data access and storage to heterogeneous network clients. t rsync: an open source utility that synchronizes files and directories from one location to another while

    minimizing data transfer using delta encoding when appropriate. t universal Serial Bus (uSB): a serial bus standard to connect peripheral devices to a host computer. t virtual Private network (vPn): a set of software and hardware that enables a computer to transparently and

    securely connect to a remote network as if it was physically attached to that network. t vPn Router: a device in computer networking to provide security and connectivity at several levels, including

    encrypted VPN gateway, stateful firewall, and IP access router.

  • White Paper

    IOMEGA DEVICE-TO-DEVICE REPLICATION SOLUTION GUIDE

    3

    SoLuTIon conFIguRATIonThis section lists the overall reference architecture and hardware and software resources for the use cases demonstrated in this white paper.

    overall architecture

    Figure 1 Reference architecture

    Hardware

    Table 1 lists the hardware resources used in the testing environment for the paper.

    Hardware Quantity Configuration

    Iomega storCenter NAS Server Two 2 GB of memory Six 1 TB (5400rpm) SATA disks RAID 6 across the disks Two GbE network connections

    emC Celerra NS700G one Two Data Movers CLARiiON CX500 backend CIFS enabled Six GbE network connections

    Iomega ego Portable Hard Drive one USB 3.0 connection 500 GB

  • White Paper

    IOMEGA DEVICE-TO-DEVICE REPLICATION SOLUTION GUIDE

    4

    Dell OptiPlex 790 Two Intel i7-2600 CPU 3.4GHz 8 GB of memory One 300 GB 7200rpm SATA disk Integrated Intel 82579LM

    Ethernet LAN 10/100/1000

    Apple MacBook one Intel Core 2.26 Duo 2.2 GHz 4 GB DDR3 SDRAM One 250GB 5400rpm SATA disk Gigabit interface

    Table 1 Hardware resources

    Software

    Table 2 lists the software resources used in the testing environment for the paper.

    Software Quantity Configuration

    EMC Lifeline 3.2.3.15290 Two EMC software that runs the Iomega devices

    W2K8 SP2 one Installed on a Dell OptiPlex 755 machine

    RHEL6.2 one Installed on a Dell OptiPlex 755 machine

    Mac OS X 10.5.5 one Installed on an Apple MacBook

    EMC Celerra Dart 5.6.46-4 one EMC software that runs the Celerra NS700G storage array

    rsync 3.0.6 one rsync server on RHEL

    rsync 2.6.9 one rsync server on Mac

    cwRsync 4.0.3 one rsync server on W2K8

    Table 2 Software resources

    TEcHnoLogy ovERvIEWdevice-to-device replication

    D2D replication offers an easy-to-use interface that allows users to define and save a set of options to copy files from one device to any other device, without the need for a client computer. The devices can be:

    t Any Iomega StorCenter device, located anywhere on the network t Any other NAS device that supports CIFS, rsync, or both t Any host that runs CIFS, rsync, or both t Any external storage device connected to an Iomega StorCenter device

    The StorCenter device maintains a list of devices discovered on the subnet and devices that were ma