This page is intentionally left blank. - Fujitsustorage-system.fujitsu.com/global/doc/pdf/p3am-5482-en.pdf · Chapter 3 Connection Configurations ... 5.1 Data Protection ... Table

This page is intentionally left blank.

FUJITSU Storage ETERNUS DX60 S2 Disk storage system Overview

3

Copyright 2015 FUJITSU LIMITED P3AM-5482-08ENZ0

Preface

Fujitsu would like to thank you for purchasing our FUJITSU Storage ETERNUS DX60 S2 Disk storage system.The FUJITSU Storage ETERNUS DX60 S2 Disk storage system is designed to be connected to Fujitsu (PRIMEQUEST or PRIMERGY) or non-Fujitsu servers.This manual describes the basic knowledge that is required to use the FUJITSU Storage ETERNUS DX60 S2 Disk storage system.This manual is intended for use of FUJITSU Storage ETERNUS DX60 S2 Disk storage system in regions other than Japan.Please carefully review the information outlined in this manual.

Eighth EditionFebruary 2015

All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the United States and other countries.UNIX is a registered trademark of The Open Group in the United States and other countries.Microsoft, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.Oracle and Java are registered trademarks of Oracle and/or its affiliates.HP-UX is a trademark of Hewlett-Packard Company in the U.S. and other countries.Linux is a registered trademark of Linus Torvalds.Red Hat is a registered trademark of Red Hat, Inc. in the U.S. and other countries.SUSE is a registered trademark of Novell, Inc. in the United States and other countries.IBM, AIX, Power Systems, and System p are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.VMware, VMware logos, Virtual SMP, and VMotion are either registered trademarks or trademarks of VMware, Inc. in the U.S. and/or other countries.The company names, product names and service names mentioned in this manual are registered trademarks or trademarks of their respective companies.

About this Manual

Organization

This manual is composed of the following six chapters:

● Chapter 1 Overview

This chapter provides an overview and describes the features of the FUJITSU Storage ETERNUS DX60 S2 Disk storage system.

● Chapter 2 Specifications

This chapter describes the specifications, the function specifications, and the operating environment of the FUJITSU Storage ETERNUS DX60 S2 Disk storage system.

● Chapter 3 Connection Configurations

This chapter describes the different types of interfaces that can be used for connecting the FUJITSU Storage ETERNUS DX60 S2 Disk storage system.

● Chapter 4 System Configuration

This chapter describes the basic knowledge required for RAID, the types and capacity of disks that can be used, and hot spares.

● Chapter 5 Basic Functions

This chapter provides an overview of the basic functions that are installed in the FUJITSU Storage ETERNUS DX60 S2 Disk storage system.

● Chapter 6 Optional Function (Advanced Copy)

This chapter provides an overview of the optional functions that require license registration.


4


About this Manual

Naming Conventions

■ Product names

• The following abbreviations are used for Microsoft® Windows Server®.

• The following abbreviations are used for Red Hat Linux.

Official name Abbreviation

Microsoft® Windows Server® 2003, Datacenter Edition

Windows Server 2003Microsoft® Windows Server® 2003, Enterprise Edition

Microsoft® Windows Server® 2003, Standard Edition

Microsoft® Windows Server® 2008 Datacenter

Windows Server 2008

Microsoft® Windows Server® 2008 R2 Datacenter

Microsoft® Windows Server® 2008 Enterprise

Microsoft® Windows Server® 2008 R2 Enterprise

Microsoft® Windows Server® 2008 Standard

Microsoft® Windows Server® 2008 R2 Standard

Microsoft® Windows Server® 2008 for Itanium-Based Systems

Microsoft® Windows Server® 2008 R2 for Itanium-Based Systems

Microsoft® Windows Server® 2008 HPC Edition

Microsoft® Windows Server® 2008 R2 HPC Edition

Microsoft® Windows Server® 2012 Datacenter

Windows Server 2012Microsoft® Windows Server® 2012 Standard

Microsoft® Windows Server® 2012 Essentials

Official name Abbreviation

Red Hat Enterprise Linux AS (v.4 for x86)Red Hat Enterprise Linux AS (v.4)

Red Hat Enterprise Linux AS (v.4 for EM64T)

Red Hat Enterprise Linux AS (v.4 for Itanium)

Red Hat Enterprise Linux ES (v.4 for x86) Red Hat Enterprise Linux ES (v.4)Red Hat Enterprise Linux ES (v.4 for EM64T)

Red Hat Enterprise Linux 5 (for x86)

Red Hat Enterprise Linux 5Red Hat Enterprise Linux 5 (for Intel64)

Red Hat Enterprise Linux 5 (for Intel Itanium)

Red Hat Enterprise Linux 6 (for x86)Red Hat Enterprise Linux 6

Red Hat Enterprise Linux 6 (for Intel64)


5


About this Manual

■ Abbreviations used in this manual

• "ETERNUS DX Disk storage system" or "ETERNUS DX60 S2" refers to the FUJITSU Storage ETERNUS DX60 S2 Disk storage system.

• "Host Bus Adapter (HBA)" refers to the interface module that is normally used by the server to connect to ETERNUS DX Disk storage systems.An "FC card", "LAN card", "Network Interface Card (NIC)", or "SAS card" may be used instead, depending on the server and interface.

• Trademark symbols such as ™ and ® are omitted in this manual.


6


Table of Contents

Chapter 1 Overview .................................................................................11

Chapter 2 Specifications .........................................................................15

2.1 ETERNUS DX Disk Storage System Specifications ........................................ 15

2.2 Function Specifications .................................................................................... 16

2.3 Supported OSs ................................................................................................. 18

Chapter 3 Connection Configurations ...................................................24

3.1 Host Connections (SAN) .................................................................................. 25

3.2 LAN .................................................................................................................. 25

3.3 Power Synchronization .................................................................................... 26

Chapter 4 System Configuration ............................................................27

4.1 RAID Levels ..................................................................................................... 27

4.2 RAID Groups .................................................................................................... 33

4.3 Volumes ........................................................................................................... 34

4.4 Disks ................................................................................................................ 374.4.1 User Capacity of Disks .............................................................................................................. 38

4.4.2 User Capacity for Each RAID Level .......................................................................................... 38

4.4.3 Recommended RAID Group Configuration ............................................................................... 39

4.4.4 Adding Disks .............................................................................................................................. 40

4.5 Hot Spares ....................................................................................................... 40

4.6 System Disks ................................................................................................... 41

Chapter 5 Basic Functions......................................................................42

5.1 Data Protection ................................................................................................ 425.1.1 Data Block Guard ...................................................................................................................... 42

5.1.2 Disk Patrol ................................................................................................................................. 43

5.1.3 Redundant Copy ........................................................................................................................ 44

5.1.4 Rebuild/Copyback ..................................................................................................................... 45

5.2 Security ............................................................................................................ 465.2.1 User Authentication ................................................................................................................... 46

5.2.2 Host Affinity ............................................................................................................................... 47

5.2.3 Data Encryption ......................................................................................................................... 49

5.3 Optimization of Volume Configurations ............................................................ 505.3.1 RAID Migration .......................................................................................................................... 51

5.3.2 Logical Device Expansion ......................................................................................................... 53

5.3.3 LUN Concatenation ................................................................................................................... 55


7


Table of Contents

5.4 Environmental Burden Reduction .................................................................... 565.4.1 Eco-mode .................................................................................................................................. 56

5.4.2 Power Consumption Visualization ............................................................................................. 57

5.5 Operation Monitoring ........................................................................................ 585.5.1 Operation Management Interface .............................................................................................. 58

5.5.2 Event Notification ....................................................................................................................... 59

5.5.3 Performance Information Management ..................................................................................... 61

5.5.4 Assigned CMs ........................................................................................................................... 61

5.5.5 Connection Operation Mode ...................................................................................................... 62

5.5.6 Device Time Setup .................................................................................................................... 63

Chapter 6 Optional Function (Advanced Copy) ....................................64

6.1 Backup ............................................................................................................. 64

6.2 Available Advanced Copy Combinations ......................................................... 68


8



9


List of Figures

Figure 1.1 External view ............................................................................................................................. 11Figure 3.1 Connection configuration........................................................................................................... 24Figure 4.1 RAID0 concept .......................................................................................................................... 28Figure 4.2 RAID1 concept .......................................................................................................................... 28Figure 4.3 RAID1+0 concept ...................................................................................................................... 29Figure 4.4 RAID5 concept .......................................................................................................................... 30Figure 4.5 RAID5+0 concept ...................................................................................................................... 31Figure 4.6 RAID6 concept .......................................................................................................................... 32Figure 4.7 Example of a RAID group.......................................................................................................... 33Figure 4.8 Volume concept......................................................................................................................... 34Figure 4.9 Drive combination 1................................................................................................................... 39Figure 4.10 Drive combination 2................................................................................................................... 39Figure 4.11 Hot spares ................................................................................................................................. 40Figure 5.1 Data block guard function.......................................................................................................... 42Figure 5.2 Disk check ................................................................................................................................. 43Figure 5.3 Redundant Copy function .......................................................................................................... 44Figure 5.4 Rebuild/Copyback function........................................................................................................ 45Figure 5.5 Host affinity................................................................................................................................ 47Figure 5.6 Volume conversion encryption function..................................................................................... 49Figure 5.7 Example of RAID Migration 1 .................................................................................................... 51Figure 5.8 Example of RAID Migration 2 .................................................................................................... 52Figure 5.9 Example of Logical Device Expansion 1 ................................................................................... 53Figure 5.10 Example of Logical Device Expansion 2 ................................................................................... 54Figure 5.11 Example of LUN Concatenation ................................................................................................ 55Figure 5.12 Eco-mode mechanism............................................................................................................... 56Figure 5.13 Power consumption visualization .............................................................................................. 57Figure 5.14 Event notification ....................................................................................................................... 60Figure 5.15 Assigned CM ............................................................................................................................. 61Figure 5.16 Host response (connection operation mode)............................................................................. 62Figure 5.17 Device time setup ...................................................................................................................... 63Figure 6.1 Example of Advanced Copy ...................................................................................................... 64Figure 6.2 OPC Restoration ....................................................................................................................... 68Figure 6.3 EC Reverse ............................................................................................................................... 68Figure 6.4 Multiple Copy............................................................................................................................. 69Figure 6.5 Multiple Copy (including SnapOPC+) ........................................................................................ 69Figure 6.6 Cascade Copy ........................................................................................................................... 70


10


List of Tables

Table 2.1 ETERNUS DX Disk storage system specifications ................................................................... 15Table 2.2 Function specifications .............................................................................................................. 16Table 2.3 Supported servers and OSs (FC interface) ............................................................................... 18Table 2.4 Supported servers and OSs (iSCSI interface)........................................................................... 21Table 2.5 Supported servers and OSs (SAS interface)............................................................................. 23Table 4.1 Comparison result for each RAID level ..................................................................................... 32Table 4.2 Recommended number of disks per RAID group...................................................................... 33Table 4.3 Volumes that can be created..................................................................................................... 34Table 4.4 Unit volume size (for each RAID level) ...................................................................................... 35Table 4.5 Disk characteristics.................................................................................................................... 37Table 4.6 User capacity per disk ............................................................................................................... 38Table 4.7 Formula for calculating user capacity for each RAID level ........................................................ 38Table 4.8 Hot spare selection.................................................................................................................... 41Table 5.1 Type of client public key ............................................................................................................ 46Table 5.2 Host affinity function specifications............................................................................................ 48Table 5.3 Data encryption function specifications ..................................................................................... 49Table 6.1 Controlling software................................................................................................................... 65Table 6.2 List of functions (copy methods)................................................................................................ 65Table 6.3 Available Cascade Copy combinations ..................................................................................... 70

Chapter 1 Overview

This chapter provides an overview and describes the features of the ETERNUS DX Disk storage system.

Figure 1.1 External view

■ Space and Energy Savings

● Compact design makes effective use of rack space

- The ETERNUS DX Disk storage system is compactly-designed to use rack space efficiently, coming in a 2U size (*1) enclosure.*1: 2U is the height for a device that can be installed in two 19-inch rack units (1U = 44.45mm).

- Two types of controller enclosure are available; those for 3.5" disks and those for 2.5" disks. Optional drive enclosures are designed for 3.5" disks.Since up to twenty-four disks can be installed, the appropriate disk configuration can be based on the purpose, application, and on-site installation space that is available for the ETERNUS DX Disk storage system.

● Energy savings by the latest technology

Power efficiency and energy savings are achieved with advanced technology.

● Eco-mode to reduce environmental load

Using the Eco-mode function starts and stops the spindle rotation in the disk for each RAID group during the specified hour. Stop the spindle rotation when there is no access to the disk to reduce power consumption and decrease environmental load.

● Visualization of power consumption and ambient temperature

Power consumption and ambient temperature for the entire ETERNUS DX Disk storage system can be checked using the (optional) "ETERNUS SF Storage Cruiser" integrated management software's Graphical User Interface (GUI). Both current status and historical records (for a day, a week, or a year) can be displayed.

2.5" disk configuration 3.5" disk configuration


11


Chapter 1 Overview

■ Easy Installation and Operation Management

● Settings of the ETERNUS DX Disk storage system and its operation management can be performed by GUI that uses a Web browser (hereafter referred to as "GUI"), or CLI that uses commands and command scripts. Settings required for the ETERNUS DX Disk storage system initial installation can be easily performed by following the GUI wizard and inputting parameters for displayed setting items. The ETERNUS DX Disk storage system can be configured, and its status can be displayed and monitored using GUI or CLI.

● ETERNUS SF Express

ETERNUS SF Express is a storage system introduction and operation support software for the user who had put off the introduction of the storage system up to now because of "Difficulty" and "Introduction and operation cost increase". ETERNUS SF Express is an easy to use software addition to the ETERNUS DX Disk storage system, facilitating management of the ETERNUS DX Disk storage system and leveraging the ETERNUS DX Disk storage system functionality such as Snapshots, Cloning, or Replication.

■ High scalability and versatile connectivity

● Utilizes the latest disk technology

High performance 2.5" SAS disks (*1) (300GB/450GB/600GB/900GB/1.2TB; 10,000rpm) and 3.5" SAS disks (*1) (300GB/450GB/600GB; 15,000rpm, 300GB/600GB; 10,000rpm) can be used. For data backup and archival purposes, the ETERNUS DX Disk storage system can use large capacity, highly cost effective 2.5" Nearline SAS disks (*1) (1TB; 7,200rpm) and 3.5" Nearline SAS disks (*1) (1TB/2TB/3TB/4TB; 7,200rpm).*1: SAS: Serial Attached SCSI

● Supports capacity expansion during system operation

- Disks and drive enclosures can be added during system operation.

- Disks can be added to expand RAID group capacity during system operation.

- Volume can be expanded during system operation. Even when the work load increases rapidly, the ETERNUS DX Disk storage system can flexibly expand the volume capacity with no interruption of the operation.

● High connectivity supports the multi-platform environments

- FC-SAN, IP-SAN, and DAS environments are supported, with FC (maximum transfer speed: 4Gbit/s), iSCSI (maximum transfer speed: 1Gbit/s), and SAS (maximum transfer speed: 3Gbit/s) host interfaces being used, respectively.

- The ETERNUS DX Disk storage system supports multiple Operating Systems such as UNIX, Linux, Windows, and VMware, and can be connected as a storage system for PRIMEQUEST and PRIMERGY servers as well as for UNIX/IA servers of other companies. Also the RAID aggregation using SAN (Storage Area Network) is available.


12


Chapter 1 Overview

■ Data integrity with high-speed backup

● Nearline SAS disks for data backup and archiving

- Using large capacity / cost effective Nearline SAS disks allows low cost D2D (Disk to Disk) backup and high-speed recovery in the case of unexpected failure.

- Storing the less frequently accessed data such as archive data in the Nearline SAS disks allows easy reading. Nearline SAS disks and SAS disks can be installed in the same enclosure.

● Backup function

Using the Advanced Copy functions allows the high-speed copying of disk volumes at any given time.

■ High reliability supports 24/7/365 operation

● Duplication of important components

Important components such as controllers (for a dual-controller type), disks, and power supply units are duplicated to continue the operation in the case of unexpected failure. Also this allows the hot swapping of failed components with the device powered on.In addition, the latest firmware can be applied during system operation.

● Various supported RAID levels

The ETERNUS DX Disk storage system supports RAID5+0 that is superior to RAID5 in reliability and performance, and RAID6 that responds to the double failure of disks, as well as RAID1, RAID1+0, and RAID5. A flexible RAID configuration can be selected.

● Redundant Copy ensures disk redundancy

The ETERNUS DX Disk storage system checks disks in order to predict failures before they happen. When a disk requires preventive maintenance, a hot spare is automatically switched in to replace it, providing continued data redundancy and stable operation.

● Block Guard ensures data integrity

The ETERNUS DX Disk storage system adds check codes and checks them at multiple checkpoints on the data transfer paths to ensure the data integrity.

● System Capacitor Unit (SCU)

A SCU that does not need maintenance is installed as a backup power source in case of a power failure.The SCU is charged from an external power source while the ETERNUS DX Disk storage system is running normally. If a power outage is detected, data in the cache memory is saved to a non-volatile memory in the controller using the SCU. Therefore, there is no limit to the post-failure data retention time.

■ E-mail notification

If an error occurs in the ETERNUS DX Disk storage system, the details can be sent to a specified e-mail address.


13


Chapter 1 Overview

■ Strengthening security against information leaks

● Data encryption to prevent information leaks

Data can be encrypted and written. Data encryption can prevent information leaks caused by fraudulent decoding even if the disk is stolen.

● Protection against fraudulent access

The ETERNUS DX Disk storage system supports SSL/SSH that encrypts and communicates information on the network. This protects against malicious use of data and fraudulent access to devices via a Web browser (GUI) or CLI.

■ RoHS compliance

The ETERNUS DX Disk storage system complies with RoHS, as mandated by the European Parliament and Council. RoHS limits the use in electric and electronic equipment of six specific chemicals: lead, hexavalent chromium, mercury, cadmium, PBB (polybrominated biphenyl), and PBDE (polybrominated diphenyl ether). In addition, lead-free soldering is used for all printed-wir-ing boards.


14


Chapter 2 Specifications

This chapter explains the specifications and the operating environment for the ETERNUS DX Disk storage systems.

2.1 ETERNUS DX Disk Storage System Specifications

This section describes ETERNUS DX Disk storage system specifications.

Table 2.1 ETERNUS DX Disk storage system specifications

*1: Physical capacity is calculated based on the assumption that 1TB=1,000GB and 1GB=1,000MB.

Item

2.5" disk type 3.5" disk type

Single-controller type

Dual-controller type

Single-controller type

Dual-controller type

Maximum physical capacity (*1)

SAS disks 28.8TB 14.4TB

Nearline SAS disks 24.0TB 96.0TB

Maximum logical capacity (*2)

SAS disks 21.3TB 10.6TB

Nearline SAS disks 17.8TB 71.2TB

Number of controllers 1 2 1 2

Host interfacesFC (4Gbit/s, 2Gbit/s, 1Gbit/s)

iSCSI (1Gbit/s)SAS (3Gbit/s)

FC (4Gbit/s, 2Gbit/s, 1Gbit/s)iSCSI (1Gbit/s)SAS (3Gbit/s)

Number of host interfaces 2 4 2 4

Maximum number of servers to be connected

FC model 32 64 32 64

iSCSI model 32 64 32 64

SAS model 2 4 2 4

Cache capacity 1GB 2GB 1GB 2GB

Number of disks 2 to 24

Disk capacity (speed)

2.5" SAS disks300GB, 450GB, 600GB, 900GB,

1.2TB (10,000rpm) –

2.5" Nearline SAS disks

1TB (7,200rpm) –

3.5" SAS disks –300GB, 600GB (10,000rpm)

300GB, 450GB, 600GB (15,000rpm)

3.5" Nearline SAS disks

– 1TB, 2TB, 3TB, 4TB (7,200rpm)

Drive interface SAS (3Gbit/s)

Interfaces for remote monitoring and operation management

Ethernet (1000Base-T/100Base-TX/10Base-T) (*3)

Power control interface RS232C (*4)


15


Chapter 2 Specifications 2.2 Function Specifications

*2: Logical capacity is calculated based on the assumption that 1TB=1,024GB, 1GB=1,024MB and that disks are formatted in a RAID5 configuration. The available capacity depends on the RAID configuration.

*3: Two ports for each controller

*4: One port for each controller. Power synchronization is performed via a power synchronized unit.

2.2 Function Specifications

This section contains the specifications of the functions for the ETERNUS DX Disk storage sys-tem.

Table 2.2 Function specifications

*1: Use of RAID0 is not recommended because it is not redundant. For RAID0 configurations, data may be lost due to the failure of a single disk.

*2: The maximum number of RAID groups that can be registered (for RAID1).

*3: The maximum number of host information (HBAs) that can be registered. A WWN is registered as the host information when the HBA of the connected server is FC. A SAS address is registered for a SAS HBA and the iSCSI name and IP address are registered as a set for an iSCSI HBA.

*4: To use this function, the additional license is required (optional function).

*5: For details on the types of Advanced Copy, refer to "6.1 Backup" (page 64).

Item ETERNUS DX60 S2

Supported RAID levels 0 (*1), 1, 1+0, 5, 5+0, 6

RAID groups Number of RAID groups (max.) (*2)

12

Number of volumes per RAID group

128

Volumes Number of volumes (max.) 512

Volume capacity (max.) 8TB

Number of connectable hosts (max.) (*3)

per con-troller

FC/iSCSI 32

SAS 2

per port FC/iSCSI 16

SAS 1

Advanced Copy (*4)

Local copy Types OPC, QuickOPC, SnapOPC+, EC (*5)

Number of copy generations(SnapOPC+)

8

Number of copy sessions (max.)

512

Number of copy sessions per volume (max.)

32

Number of copy sessions for a single area (max.) (*6)

8

Copy capacity (max.) (*7) 60TB (*8)

SDP capacity (max.) 32TB


16


Chapter 2 Specifications 2.2 Function Specifications

*6: For details on the maximum number of copy sessions for a single area, refer to the Multiple Copy section in "6.2 Available Advanced Copy Combinations" (page 68).

*7: This value is the total capacity of data that can be copied simultaneously. The copy capacity differs depending on the settings and the copy conditions.The following formula can be used to calculate the copy capacity:Executable copy capacity [GB] = (S[MB] 1024 8[KB] N) M 2 (round down the result) S: copy table size, N: the number of sessions, M: bitmap ratioFor details about the setting, refer to "ETERNUS Web GUI User's Guide".

*8: This value was calculated when:

- The maximum copy table size was set for the ETERNUS DX Disk storage system.

- The maximum bitmap ratio was set for the ETERNUS DX Disk storage system.

- The maximum number of the sessions was set for the ETERNUS DX Disk storage system.

- OPC Restoration was not used.


17


Chapter 2 Specifications 2.3 Supported OSs

2.3 Supported OSs

This section explains the operating environment that is required for the ETERNUS DX Disk stor-age system operation.

Servers and OSs that are supported by the ETERNUS DX Disk storage system are shown below.For the possible combinations of servers, Host Bus Adapters (HBAs), and driver software that can be used, refer to "Server Support Matrix" by accessing the URL that is described in "README" on the Documentation CD provided with the ETERNUS DX Disk storage system.

■ FC interface

Table 2.3 Supported servers and OSs (FC interface)

ServerOS

Manufacturer Product name

Fujitsu Mission critical IA serversPRIMEQUEST 400/500/500Aseries

Windows Server 2003

Windows Server 2008

Red Hat Enterprise Linux AS (v.4)

Red Hat Enterprise Linux 5

Mission critical IA serversPRIMEQUEST 1000 series

Windows Server 2003

Windows Server 2008

Windows Server 2012



VMware vSphere 4

VMware vSphere 4.1

VMware vSphere 5

UNIX serversSPARC EnterpriseFujitsu M10 Servers

Oracle Solaris 10

Oracle Solaris 11

UNIX serversPRIMEPOWERSun Fire

Oracle Solaris 8

Oracle Solaris 9

Oracle Solaris 10


18



Fujitsu Industry standard serversPRIMERGY

Windows Server 2003

Windows Server 2008

Windows Server 2012

Red Hat Enterprise Linux AS/ES (v.4)



XenServer 5.6

VMware vSphere 4

VMware vSphere 4.1

VMware vSphere 5

SUSE Linux Enterprise Server 10


Symantec FileStore

FalconStor NSS

Oracle Sun Fire Oracle Solaris 8

Oracle Solaris 9

Oracle Solaris 10

Oracle Solaris 11

SPARC Enterprise Oracle Solaris 10

Oracle Solaris 11

IBM IBM RS/6000IBM P seriesIBM System pIBM Power Systems

AIX 5.3

AIX 6.1

AIX 7.1

System pPower Systems

VIOS 2.1

VIOS 2.2

HP HP 9000 serverHP Integrity server

HP-UX 11iV1

HP-UX 11iV2

HP-UX 11iV3

Egenera BladeFrame Pan Manager 5.2

ServerOS



19



Others Other industry standard servers Oracle Solaris 10

Oracle Solaris 11

Oracle Linux 5

Oracle Linux 6

Oracle VM Server 3

Windows Server 2003

Windows Server 2008

Windows Server 2012




VMware vSphere 4

VMware vSphere 4.1

VMware vSphere 5

VMware vSphere 5.1

XenServer 5.5

XenServer 5.6

XenServer 6




FalconStor NSS

ServerOS



20



■ iSCSI interface

Table 2.4 Supported servers and OSs (iSCSI interface)

ServerOS


Fujitsu Mission critical IA serversPRIMEQUEST 1000 series

Windows Server 2003

Windows Server 2008

Windows Server 2012



VMware vSphere 4

VMware vSphere 4.1

VMware vSphere 5

UNIX serversSPARC EnterpriseFujitsu M10 Servers

Oracle Solaris 10

Oracle Solaris 11

Industry standard serversPRIMERGY

Windows Server 2003

Windows Server 2008

Windows Server 2012



VMware vSphere 4

VMware vSphere 4.1

VMware vSphere 5

VMware vSphere 5.1



Oracle Sun Fire Oracle Solaris 10

Oracle Solaris 11

SPARC Enterprise Oracle Solaris 10

Oracle Solaris 11

HP HP 9000 serverHP Integrity server

HP-UX 11iV2

HP-UX 11iV3


21



Others Other industry standard servers Oracle Solaris 10

Windows Server 2003

Windows Server 2008

Windows Server 2012





VMware vSphere 4

VMware vSphere 4.1

VMware vSphere 5

VMware vSphere 5.1

ServerOS



22



■ SAS interface

Table 2.5 Supported servers and OSs (SAS interface)

ServerOS


Fujitsu UNIX serversSPARC EnterpriseFujitsu M10 Servers

Oracle Solaris 10

Oracle Solaris 11

Industry standard serversPRIMERGY

Windows Server 2003

Windows Server 2008

Windows Server 2012




VMware vSphere 4

VMware vSphere 4.1

VMware vSphere 5

VMware vSphere 5.1



Oracle SPARC Enterprise Oracle Solaris 10

Others Other industry standard servers Windows Server 2003

Windows Server 2008

Windows Server 2012






VMware vSphere 4

VMware vSphere 4.1

VMware vSphere 5

VMware vSphere 5.1


23


Chapter 3 Connection Configurations

This chapter explains the possible connections for ETERNUS DX Disk storage system operation.

Figure 3.1 Connection configuration

Administration terminal

Management/Monitoringserver

LAN

LAN for operation management

CA

CA

Storage Area Network (SAN)

Server (Host)

Switch

ETERNUSDX Disk storage system

Remote supportcenter

Host interface adapterThis is an interface that is used to connect to the server HBA or switch.This is used to connect a terminal for monitoring operations and device settings.This is also used to connect to the remote support center using the remote support function.

CA:

LAN:

PWC portThis is used to enable the ETERNUS DX Disk storage system to be powered on and off with servers.

PWC:

PWC

Power synchronized unit

Power control

UninterruptiblePower Supply (UPS)


24


Chapter 3 Connection Configurations 3.1 Host Connections (SAN)

3.1 Host Connections (SAN)

Storage Area Network (SAN) is a dedicated network to connect ETERNUS DX Disk storage sys-tems to servers (hosts).FC, iSCSI, and SAS are available as host interfaces.Depending on the connection configuration, the destination can be a server HBA or a LAN switch. For a SAS host interface, only direct connections to the server HBA are supported.Using driver software for multipath control enables reliable and high performance connection configurations by controlling the server and the ETERNUS DX Disk storage system with multiple paths.This section describes each host interface.

● FC (Fibre Channel)

FC enables high speed data transfer over long distances by using optical fibers and coaxial cables. FC is used for database servers where enhanced scalability and high performance are required.

● iSCSI

iSCSI is a communication protocol that transfers SCSI commands by encapsulating them in IP packets over Ethernet.Since iSCSI can be installed at a lower cost and the network configuration is easier to change than FC, iSCSI is commonly used by divisions of large companies and by small and medium-sized companies where scalability and cost-effectiveness are valued over performance.

● SAS

SAS (Serial Attached SCSI) is a serial transfer host interface that is as reliable as the normal (parallel) SCSI interface. SAS is commonly used for small-sized systems where performance and cost-effectiveness are valued over scalability.

3.2 LAN

For ETERNUS DX Disk storage systems, operations such as RAID configuration, operation management, and system maintenance are performed via the LAN.The functions of the management/monitoring server on the LAN, which include SNMP (device monitoring), SMTP (sending e-mails), and NTP (time correction), can also be used.Any errors that occur in the ETERNUS DX Disk storage system are notified to the remote sup-port center when remote support is used. An Internet connection is required for remote support.


25


Chapter 3 Connection Configurations 3.3 Power Synchronization

3.3 Power Synchronization

Powering the ETERNUS DX Disk storage system on and off can be automatically controlled with a server.

● Power synchronized unit

A power synchronized unit detects changes in the AC power output of the Uninterruptible Power Supply (UPS) unit that is connected to the server and automatically turns on and off the ETERNUS DX Disk storage system.


26


Chapter 4 System Configuration

This chapter explains points to note before configuring a system using the ETERNUS DX Disk storage system.

4.1 RAID Levels

This section explains RAID group configuration and the supported RAID levels and usage (RAID level selection criteria).

■ Supported RAID levels and mechanism

The ETERNUS DX Disk storage system supports the following RAID levels.

• RAID0 (striping)

• RAID1 (mirroring)

• RAID1+0 (striping of pairs of disks for mirroring)

• RAID5 (striping with distributed parity blocks)

• RAID5+0 (double striping with distributed parity)

• RAID6 (striping with distributed double parity blocks)

CAUTIONDo

• Remember that a RAID0 configuration is not redundant. This means that if a RAID0 disk fails, the data will not be recoverable.Therefore, using RAID1, RAID1+0, RAID5, RAID5+0, or RAID6 configuration is recommended.


27


Chapter 4 System Configuration 4.1 RAID Levels

Each RAID level description is shown below.

● RAID0 (striping)

Data is split in unit of blocks and stored across multiple disks.

Figure 4.1 RAID0 concept

● RAID1 (mirroring)

RAID1 stores the same data on two duplicated disks at the same time.If one disk fails, other disk continues operation.


A

C

B

D

Data writing request

HDD0 HDD1

A B C D

A

B

C

D

A B C D


A

B

C

D

HDD0 HDD1


28



● RAID1+0 (striping of pairs of disks for mirroring)

RAID1+0 combines the performance of RAID0 (striping) with the reliability of RAID1 (mirroring).

Figure 4.3 RAID1+0 concept

HDD3

HDD7

D

D’

HDD2

HDD6

C

C’

HDD1

HDD5

B

B’

HDD0

HDD4

A

A’

Striping (RAID0)

Mirroring (RAID1)


A B C D

Mirroring

Mirroring

Mirroring

Mirroring


29



● RAID5 (striping with distributed parity)

Data divided into units of blocks and allocated across multiple disks together with parity information created from the data. If one disk fails, the remaining data and parity blocks are sufficient to allow the recovery of the lost data.


A

E

I

M

A B C D


B

F

J

P M, N, O, P

C

G

P I, J, K, L

N

D

P E, F, G, H

K

O

H

L

P

Create parity data

P A, B, C, D

A B DC

HDD0 HDD1 HDD2 HDD3 HDD4

Parity for data A to D:Parity for data E to H:Parity for data I to L:Parity for data M to P:

P A, B, C, D

P E, F, G, H

P I, J, K, L

P M, N, O, P


30



● RAID5+0 (double striping with distributed parity)

Multiple RAID5 volumes are RAID0 striped. For large capacity configurations, use of RAID5+0 instead of RAID5 results in enhanced performance, improved reliability, and shorter rebuilding times.

Figure 4.5 RAID5+0 concept

Striping withdistributed parity(RAID5)

Striping (RAID0)

A

E

B

I

F

P A, B

P M, N

C

G H

P C, D

P O, P

HDD0 HDD1 HDD2 HDD3 HDD4 HDD5

D

KP K, L

Striping (RAID0)

Striping withdistributed parity

(RAID5)

J L

M N O P

P E, F

P I, J

P G, H

RAID5 RAID5

A B Create parity data D Create parity dataC


A

B

C

D

A B C D

A B C D


31



● RAID6 (striping with distributed double parities)

Store two different parities on different disks (double parities) to recover from up to two disk failures.


■ Reliability, performance, capacity for each RAID level

Table 4.1 shows the comparison result of reliability, performance, capacity for each RAID level.

Table 4.1 Comparison result for each RAID level

*1: Performance may differ according to the number of disks and the processing method from the host.

■ Recommended RAID level

Select the appropriate RAID level according to the usage.

• Recommended RAID level is RAID1, RAID1+0, RAID5, RAID5+0 and RAID6.

• For read and write performance, RAID1+0 configuration is recommended.

• For read only file servers and backup servers, RAID5, RAID5+0, or RAID6 can also be used. However, if the disk fails, note that data restoration from parities and rebuilding process may result in a loss in performance.

P2 M, N, O, P

P2 I, J, K, L

A

E

I

M

A B C D


B

F

J

P1 M, N, O, P

C

G

P1 I, J, K, L

D

P1 E, F, G, H P2 E, F, G, H

N

K

O

P1 A, B, C, D

H

L

P

P2 A, B, C, D

A B DC Create parity data

HDD0 HDD1 HDD2 HDD3 HDD4 HDD5

Parity for data A to D:Parity for data E to H:Parity for data I to L:Parity for data M to P:

P1 A, B, C, D and P2 A, B, C, D

P1 E, F, G, H and P2 E, F, G, H

P1 I, J, K, L and P2 I, J, K, L

P1 M, N, O, P and P2 M, N, O, P

RAID level Reliability Performance (*1) Capacity

RAID0 Poor Very Good Very Good

RAID1 Good Good Reasonable

RAID1+0 Good Very Good Reasonable

RAID5 Good Good Good

RAID5+0 Good Good Good

RAID6 Very Good Good Good


32


Chapter 4 System Configuration 4.2 RAID Groups

4.2 RAID Groups

This section explains RAID groups.A RAID group is a group of disks. It is a unit that configures RAID. Multiple RAID groups with the same RAID level or multiple RAID groups with different RAID levels can be set together in the ETERNUS DX Disk storage system. After a RAID group is created, RAID levels can be changed and disks can be added.Disks of the same type (SAS or Nearline SAS) and speed must be used to configure a RAID group.

Figure 4.7 Example of a RAID group

Table 4.2 shows the recommended number of disks that configure a RAID group.

Table 4.2 Recommended number of disks per RAID group

*1: D = Data, M = Mirror, P = Parity

An assigned CM is allocated to each RAID group. For details, refer to "5.5.4 Assigned CMs" (page 61).

RAID levelNumber of configuration

disksRecommended number of disks (*1)

RAID1 2 2(1D+1M)

RAID1+0 4 to 24 4(2D+2M), 6(3D+3M), 8(4D+4M), 10(5D+5M)

RAID5 3 to 16 3(2D+1P), 4(3D+1P), 5(4D+1P), 6(5D+1P)

RAID5+0 6 to 24 3(2D+1P) 2, 4(3D+1P) 2, 5(4D+1P) 2, 6(5D+1P) 2

RAID6 5 to 16 5(3D+2P), 6(4D+2P), 7(5D+2P)

• Sequential access performance hardly varies with the number of disks for the RAID group.

• Random access performance tends to be proportional to the number of disks for the RAID group.

• Use of higher capacity disks will increase the time required for the disk rebuild process to complete.

• The higher the number of drives in a RAID5, RAID5+0, or RAID6 configuration, the longer the period of time for data restoration and rebuilding processes from parities.

RAID group 1 RAID group 2

SAS600GB

SAS600GB

SAS600GB

SAS600GB

SAS600GB

NearlineSAS2TB

NearlineSAS2TB

NearlineSAS2TB

NearlineSAS2TB


33


Chapter 4 System Configuration 4.3 Volumes

4.3 Volumes

This section explains volumes.Logical disk areas in RAID groups are called volumes.A volume is the basic RAID unit, that can be recognized by the server.

Figure 4.8 Volume concept

A volume may be up to 8TB. However, the maximum capacity of volume varies depending on the OS of the server.A volume can be expanded or moved if required. Multiple volumes can be concatenated and treated as a single volume.

The types of volumes that are listed in the table below can be created in the ETERNUS DX Disk storage system.

Table 4.3 Volumes that can be created

*1: When multiple volumes are concatenated using the LUN Concatenation function, the maximum capacity is 32TB.

After a volume is created, formatting automatically starts. A server can access the volume while it is being formatted. Wait for the format to complete if high performance access is required for the volume.

Type Usage Maximum capacity

Open This volume is used for normal usage, such as file systems and databases. The server recognizes it as a single logical unit.

8TB (*1)

Snap Data Volume (SDV)

The area of this volume is used as the copy destination for SnapOPC+. There is a SDV for each copy destination.

8,388,607MB (8TB-1MB)

Snap Data Pool Volume (SDPV)

This volume is used to configure the Snap Data Pool (SDP) area. The SDP capacity equals the total capacity of the SDPVs. A volume is supplied from a SDP when the amount of updates exceeds the capacity of the SDV.

2TB

RAID group 1 RAID group 2

Volume 1

Volume 2Volume 3


34



Table 4.4 Unit volume size (for each RAID level)

Managing the capacity of volumes is based on the stripe size in the ETERNUS DX Disk storage system. When creating volumes, refer to the following table to set a volume size to an exact multiple of the unit size for each RAID level. The available user capacity can be fully utilized if the volume size is set to an exact multiple of the unit size.If the volume size is not set to an exact multiple of the unit size, unusable areas are created in the RAID group and user capacity may not be fully utilized.The following table shows the unit size for each RAID level.

RAID level (*1) Unit size (*2) in MB

RAID1 1D+1M 1 (MB)

RAID1+0 2D+2M 1 (MB)

3D+3M 3 (MB)

4D+4M 1 (MB)

5D+5M 5 (MB)

6D+6M 3 (MB)

7D+7M 7 (MB)

8D+8M 1 (MB)

9D+9M 9 (MB)

10D+10M 5 (MB)

11D+11M 11 (MB)

12D+12M 3 (MB)

RAID5 2D+1P 1 (MB)

3D+1P 3 (MB)

4D+1P 1 (MB)

5D+1P 5 (MB)

6D+1P 3 (MB)

7D+1P 7 (MB)

8D+1P 1 (MB)

9D+1P 9 (MB)

10D+1P 5 (MB)

11D+1P 11 (MB)

12D+1P 3 (MB)

13D+1P 13 (MB)

14D+1P 7 (MB)

15D+1P 15 (MB)


35



*1: D, M, and P indicate Data, Mirror, and Parity respectively.

*2: Unit size is calculated based on the assumption that 1MB = 1,0242 bytes.

RAID5+0 (2D+1P) 2 1 (MB)

(3D+1P) 2 3 (MB)

(4D+1P) 2 1 (MB)

(5D+1P) 2 5 (MB)

(6D+1P) 2 3 (MB)

(7D+1P) 2 7 (MB)

(8D+1P) 2 1 (MB)

(9D+1P) 2 9 (MB)

(10D+1P) 2 5 (MB)

(11D+1P) 2 11 (MB)

RAID6 3D+2P 3 (MB)

4D+2P 1 (MB)

5D+2P 5 (MB)

6D+2P 3 (MB)

7D+2P 7 (MB)

8D+2P 1 (MB)

9D+2P 9 (MB)

10D+2P 5 (MB)

11D+2P 11 (MB)

12D+2P 3 (MB)

13D+2P 13 (MB)

14D+2P 7 (MB)

RAID level (*1) Unit size (*2) in MB


36


Chapter 4 System Configuration 4.4 Disks

4.4 Disks

The ETERNUS DX Disk storage system supports the latest disks that have the high-speed Serial Attached SCSI (3Gbit/s) interface.

SAS disks and Nearline SAS disks can be installed in the ETERNUS DX Disk storage system.2.5" and 3.5" disk sizes are available.Since 2.5" disks are lighter and require less power than 3.5" disks, the total weight and power consumption when 2.5" disks are installed is less than when the same number of 3.5" disks is installed. When the data I/O count is compared based on the number of disks in an enclosure (2.5" disks: 24, 3.5" disks: 12), the Input Output Per Second (IOPS) performance for each enclosure in a 2.5" disk configuration is superior to a 3.5" disk configuration since more 2.5" disks can be installed in an enclosure than 3.5" disks.

● SAS disks (2.5"/3.5")

SAS disks are reliable disks with high performance. SAS disks support 24/7/365 operations and are used to store high performance databases and other frequently accessed data.

● Nearline SAS disks (2.5"/3.5")

Nearline SAS disks are high capacity cost effective disks for data backup and archive use. Nearline SAS disks can store information that requires a low access rate at a reasonable speed more cost effectively than SAS disks.

Table 4.5 Disk characteristics

• Nearline SAS disks are used to store data that does not need the access performance of SAS disks. They are far more cost effective than SAS disks. (It is recommended that SAS disks be used for data that is constantly accessed or when high performance/reliability is required.)

• If the ambient temperature exceeds the operating environment conditions, Nearline SAS disk performance may be reduced.

• Nearline SAS disks can be used as Advanced Copy destinations and for the storage of archived data.

• When Nearline SAS disks are used as an Advanced Copy destination, delayed access responses and slower copy speeds may be noticed, depending on the amount of I/O and the number of copy sessions.

Type Reliability Performance Price per bit

SAS disks Good Good Good

Nearline SAS disks Reasonable Reasonable Very good


37



4.4.1 User Capacity of Disks

Table 4.6 shows the user capacity for each disk.

Table 4.6 User capacity per disk

*1: The capacity that is listed above for the product names of the disks is based on the assumption that

1MB = 1,0002 bytes, while the user capacity per disk is based on the assumption that 1MB = 1,0242 bytes. Furthermore, OS file management overhead will reduce the actual usable capacity.

4.4.2 User Capacity for Each RAID Level

The user capacity depends on the capacity of disks that configure a RAID group and the RAID level.Table 4.7 shows the formula for calculating the user capacity for each RAID level.

Table 4.7 Formula for calculating user capacity for each RAID level

Some functions cannot be used with some types of disks.

• Do not use different types of disks in a RAID group. Use the same type of disks when adding capacity to a RAID group (RAID Migration, Logical Device Expansion).

• When concatenating volumes (LUN Concatenation), for performance reasons, it is recommended that all concatenated volumes be from RAID groups with same RAID level and same disk speed.

For details on each function, refer to "Chapter 5 Basic Functions" (page 42).

Product name (*1) User capacity

300GB SAS disk (2.5"/3.5") 279,040MB

450GB SAS disk (2.5"/3.5") 419,072MB

600GB SAS disk (2.5"/3.5") 559,104MB

900GB SAS disk (2.5") 839,168MB

1.2TB SAS disk (2.5") 1,119,232MB

1TB Nearline SAS disk (2.5"/3.5") 937,728MB

2TB Nearline SAS disk (3.5") 1,866,240MB



RAID level Formula for user capacity computation

RAID0 Disk capacity Number of disks

RAID1 Disk capacity Number of disks 2

RAID1+0 Disk capacity Number of disks 2

RAID5 Disk capacity (Number of disks - 1)


38



4.4.3 Recommended RAID Group Configuration

No restrictions on the installation location of drives apply if the same types of drives are used to create RAID groups.To improve reliability, the installation location of drives that configure a RAID group must be con-sidered. When a RAID level that performs mirroring (RAID1, RAID1+0) is created, installing drives that are configured in pairs to different enclosures improves reliability.

RAID1+0(4D+4M) is used in the following examples to explain the drive combinations for RAID levels that configure mirrored pairs.The drive number is determined by the DE-ID of the drive enclosure and the slot number in which the drive is installed. Starting from the smallest drive number in the configuration, half of the drives are allocated into one group and the remaining drives are allocated into the other group. Each drive in the different groups are paired for mirroring.

Example 1: All drives are installed in a single drive enclosure

Figure 4.9 Drive combination 1

Example 2: Paired drives are installed in two different drive enclosures

Figure 4.10 Drive combination 2

RAID5+0 Disk capacity (Number of disks - 2)

RAID6 Disk capacity (Number of disks - 2)

RAID level Formula for user capacity computation

DE#00

Mirroring

A B C D A' B' C' D'

DE#00

Mirroring

A B C D

DE#01

A' B' C' D'


39


Chapter 4 System Configuration 4.5 Hot Spares

4.4.4 Adding Disks

When installing 10,000rpm type 3.5" SAS disks in an ETERNUS DX Disk storage system that already has 15,000rpm type 3.5" SAS disks as hot spares, adding 10,000rpm type hot spares is not necessary. A disk with the same or larger capacity than the failed disk works as the hot spare even if the speed is different.

4.5 Hot Spares

Hot spares are used as spare disks for when disks in a RAID group fail, or are in error status.

Figure 4.11 Hot spares

The following two types of hot spare are available:

• Global Hot SpareThis is available for any RAID group. When multiple hot spares are installed, the most appropriate disk is automatically selected and incorporated into a RAID group.

• Dedicated Hot SpareThis is only available to a specified RAID group.

Register hot spares to ensure steady operation of the ETERNUS DX Disk storage system. If a free hot spare is available, when one of the RAID group disks has a problem, data from this disk is automatically replicated into the hot spare. If a mixture of SAS disks and Nearline SAS disks is installed in the ETERNUS DX Disk storage system, separate hot spares will be required for each type of disk.There are two types of SAS disks; 10,000rpm type SAS disks and 15,000rpm type SAS disks. If a disk error occurs and a hot spare is configured in a RAID group with different speed disks, the performance of all the disks in the RAID group is determined by the disk with the slowest speed. The capacity of each hot spare must be equal to the capacity of the largest same-type disk (SASdisks or Nearline SAS disks).

Assign "Dedicated Hot Spares" to RAID groups that contain important data, in order to preferentially improve their access to hot spares.

Hot spare

Failure

RAID group


40


Chapter 4 System Configuration 4.6 System Disks

Table 4.8 Hot spare selection

*1: When there are multiple hot spares with a larger capacity than the failed disk, the hot spare with the smallest capacity among them is used first.

4.6 System Disks

System disks are two disks that are installed in Slot #0 and Slot #1 of the controller enclosure.The system disk has part of its storage capacity allocated as a dedicated system area for use by ETERNUS DX Disk storage system firmware, and the remaining part is allocated as user area for use by the user.For details on the disk user capacity, refer to Table 4.6. The user capacity for the system disk is the same as other disks.

When multiple Global Hot Spares are installed, the following criteria are used to select which hot spare will replace a failed disk:

Selection order

Selection criteria

1 A hot spare with the same type, capacity and speed as the failed disk.

2 A hot spare with the same type and speed as the failed disk but with a larger capacity. (*1)

3 A hot spare with the same type and capacity as the failed disk but with a different speed.

4 A hot spare with the same type as the failed disk but with a different speed and a larger capacity. (*1)

System disks cannot be defined as hot spares.


41


Chapter 5 Basic Functions

This chapter explains the basic functions of ETERNUS DX Disk storage systems.

5.1 Data Protection

The ETERNUS DX Disk storage system has functions to securely protect user data when an error occurs.

5.1.1 Data Block Guard

When the ETERNUS DX Disk storage system receives data from the server (when data is written from the server), the Data Block Guard function adds eight bytes check codes to each block (every 512 bytes) of the user data and verifies the user data at multiple checkpoints to ensure data consistency. This function can detect a data error when data is destroyed or data corruption occurs. When the ETERNUS DX Disk storage system sends data to the server (when data is read from the server), the check codes are removed after the check, ensuring that data consistency is veri-fied in the whole storage system.If an error is detected while data is being written, the data is read again from the data that is duplicated in the cache memory. This data is checked for consistency and then written.If an error is detected while data is being read from a disk, the data is restored using RAID redun-dancy.

Figure 5.1 Data block guard function

Cache memory

2

1

2

3

Controller

Write

1 Check Code append

2 Check Code confirmation

3 Check Code confirmation & removal

A0 CC A1 CC A2 CC

A0 A1 A2

User data

A0 CC A1 CC A2 CC

A0 A1 A2

User data

CC: Check Code

Read

Eight bytes check code isappended to every 512bytes’ user data.

Written data

A0 CC A1 CC A2 CC


42


Chapter 5 Basic Functions 5.1 Data Protection

5.1.2 Disk Patrol

The Disk Patrol function regularly diagnoses and monitors the operational status of all disks that are installed in the ETERNUS DX Disk storage system. Disks are checked (read check) regularly as a background process.For disk checking, read check is performed sequentially for a part of the data in all the disks. If an error is detected, data is restored using disks in the RAID group and the data is written back to another block of the disk in which the error occurred.

Figure 5.2 Disk check

Disks that are stopped by Eco-mode are checked when the disks start run-ning again.

RAID group

D1

Data is read and checked.

D1

Datareconstruction

D1

D2 D3 P

RAID group

Errordetection

The data is written back to another block.

Error

D1 to D3: P:

DataParity

D1

RAID group

D1

Data is read and checked.

D1

Datareconstruction

D1

D2 D3 P

RAID group

Errordetection

The data is written back to another block.

Error

D1 to D3: P:

DataParity

D1


43



5.1.3 Redundant Copy

When the Disk Patrol function decides that preventative maintenance is required for a disk, the Redundant Copy function uses the remaining disks to re-create the data of the maintenance tar-get disk and writes the data to the hot spare. The Redundant Copy function enables data to be restored while maintaining data redundancy.

Figure 5.3 Redundant Copy function

If a bad sector is detected when a disk is checked, a replacement track is automatically allocated. This disk is not recognized as having a disk failure during this process. However, the disk will be disconnected by the Redundant Copy function if the spare sector is insufficient and the problem cannot be solved by allocating a replacement track.

Hot spare

Creates data from the disks other thanthe maintenance target disk, andwrites data into the hot spare.

Disconnects the maintenance target diskand switches it to the hot spare.

Disconnected

RAID5 (Redundant)

Sign offailure

RAID5 (Redundant)


44



5.1.4 Rebuild/Copyback

When a disk fails and RAID group redundancy is broken, Rebuild/Copyback restores the disk status back to normal status as a background process. If a free hot spare is available when one of the RAID group disks has a problem, data of this disk is automatically replicated in the hot spare. This ensures data redundancy.

Figure 5.4 Rebuild/Copyback function

Hot spare

Hot spare

Creates data from the disks other thanthe failed disk and writes the data intothe hot spare.

After replacing has been completed,copies the data from the hot spareto the new disk.

Replaces the failed disk with the new disk.

Failure

Rebuild

Copyback

RAID5 (Redundant)

RAID5 (No Redundancy)

RAID5 (Redundant)

RAID5 (Redundant)


45


Chapter 5 Basic Functions 5.2 Security

5.2 Security

The ETERNUS DX Disk storage system provides various enhanced security functions.

5.2.1 User Authentication

The following authentication functions are available when the ETERNUS DX Disk storage sys-tem is connected via a LAN using operation management software.

● User account authentication

User account authentication uses the user account information that is registered in the ETERNUS DX Disk storage system to verify user logins. Up to 16 user accounts can be set.

● SSL authentication

ETERNUS Web GUI supports https connections using SSL/TLS. Since data on the network is encrypted, security can be ensured. Server certifications that are required for connections are automatically created in the ETERNUS DX Disk storage system.

● SSH authentication

Since ETERNUS CLI supports SSH connections, data on the network can be encrypted and sent/received. The server key for SSH varies depending on the ETERNUS DX Disk storage system. When the server certification is updated, the server key is updated as well.Password authentication and client public key authentication are available as authentication methods for SSH connections.The following table shows the supported client public keys.

Table 5.1 Type of client public key

● iSCSI authentication

The Challenge Handshake Authentication Protocol (CHAP) is supported for iSCSI connections. For CHAP Authentication, unidirectional CHAP or bidirectional CHAP can be selected. When unidirectional CHAP is used, the target authenticates the initiator to prevent fraudulent access. When bidirectional CHAP is used, the target authenticates the initiator to prevent fraudulent access and the initiator authenticates the target to prevent impersonation. In addition, Internet Storage Name Service (iSNS) is supported as the iSCSI name solution.

Type of public key Complexity (bits)

OpenSSH style RSA for SSH v1 1024, 2048

IETF style RSA for SSH v2 1024, 2048

IETF style DSA for SSH v2 1024


46



5.2.2 Host Affinity

The host affinity function prevents data from being damaged due to inadvertent storage access. Access to volumes can be set for each host interface port.By defining a server that can access the volume, security can be ensured when multiple servers are connected.

Figure 5.5 Host affinity

By using the host affinity function, a host interface port can be shared by multiple servers in a cluster system or in a system in which servers with different OSs exist together. When multiple servers access the same volume, cluster software is required.

• When using a FC switch, perform zoning settings for the switch. For details on zone settings, refer to "Configuration Guide -Server Connection-" or the manual that is provided with the switch.

• When using a LAN switch for iSCSI connections, use a LAN switch that has the VLAN function and allocate a separate segment to each server. For details on settings, refer to "Configuration Guide -Server Connection-" or the manual that is provided with the LAN switch.

Server AWWN#A

LUN#0

:

LUN#127

Server BWWN#B

LUN#0

:

LUN#127

Server CWWN#C

LUN#0

:

LUN#127

Switch

Affinity Group #00 is set to be accessed from WWN#A (=Server A) and WWN#B (=Server B)

Affinity Group #01 is set to be accessed from WWN#C (=Server C)

ETERNUS DX Disk storage system

Volume#0

:

Volume#127

LUN#0

:

LUN#127

Affinity Group #00

Affinity Group #01

Volume#128

:

Volume#255

LUN#0

:

LUN#127

Port

Port

Restrict server access to volumes per port


47



The following table shows the specifications of the host affinity function:

Table 5.2 Host affinity function specifications

*1: The maximum number of host information (HBAs) that can be registered. A WWN is registered as the host information when the HBA of the connected server is FC. A SAS address is registered for a SAS HBA and the iSCSI name and IP address are registered as a set for an iSCSI HBA.For a single-controller type, the maximum number of connectable hosts is 32 for FC/iSCSI and two for SAS.

*2: The maximum number of LUNs that can be set varies depending on the connection operation mode of the host response settings. For details on the mode, refer to "5.5.5 Connection Operation Mode" (page 62).

Functional specification Maximum setting

Number of connectable hosts (max.) (*1)

FC/iSCSI 64

SAS 4

Number of LUNs that can be set (max.) (*2)

per port 256 (except HP-UX mode)512 (HP-UX mode)

per host 256 (except HP-UX mode)512 (HP-UX mode)


48



5.2.3 Data Encryption

Encrypting data as it is being written to the disk prevents information leakage caused by fraudu-lent decoding.Even if a disk is removed and stolen by malicious third parties, data cannot be decoded.The encryption function only encrypts the data stored on the disks, so server access results in the transmission of plain text. Therefore, this function prevents data leakage from disks that are physically removed, but does not prevent data leakage from server access.

■ Volume conversion encryption function

This function converts a volume to an encrypted volume in the ETERNUS DX Disk storage sys-tem. Encryption is performed when data is written from the cache memory to the disk.When decrypting data, the data is decrypted in the cache memory.

Table 5.3 Data encryption function specifications

The Fujitsu original encryption method uses a Fujitsu original algorithm that has been specifically created for ETERNUS DX Disk storage systems. The Fujitsu original method has practically the same security level as AES128.

Figure 5.6 Volume conversion encryption function

Functional specification Volume conversion encryption

Type of key Encryption key

Encryption unit Volume

Encryption method Fujitsu original

123 123 123

123 123 123

??? ??? ???

??? ??? ???Encrypted

Unencrypted

Setting and management of encryption

Server

Server

Server

???

Prevention of information leakage

? ? ?

ETERNUS DX Diskstorage system


49


Chapter 5 Basic Functions 5.3 Optimization of Volume Configurations

5.3 Optimization of Volume Configurations

This section explains the functions that optimize volume configurations.

Disks and drive enclosures can be added during system operation in an ETERNUS DX Disk stor-age system according to changes in the operation load and performance conditions.The ETERNUS DX Disk storage system allows for the expansion of volumes and RAID group capacities, migration among RAID groups, and the changing of RAID levels when the volumes are defined.Exact details depend on the desired operation. Select from the following procedures.

■ Expansion of logical volume capacity

• RAID Migration (with increased migration destination capacity)When volume capacity is insufficient, a volume can be moved to a RAID group that has enough free space. This function is recommended for use when the desired free space is available in the destination.

• LUN ConcatenationAdds areas of free space to an existing volume to expand its capacity. This uses existing free space to efficiently expand the volume.

■ Expansion of RAID group capacity

• Logical Device ExpansionAdds new disks to an existing RAID group to expand the RAID group capacity. This is used to expand the existing RAID group capacity instead of adding a new RAID group to add the volumes.

■ Migration among RAID groups

• RAID MigrationIf the performance of the current RAID groups is not satisfactory due to conflicting volumes, RAID Migration may be used to improve the performance by redistributing the RAID group configuration.

■ Changing the RAID level

• RAID Migration (to a RAID group with a different RAID level)Migrating to a RAID group with a different RAID level changes the RAID level of volumes. This is used to convert a given volume to a different RAID level.

• Logical Device Expansion (and changing RAID levels when adding the new disks)The RAID level may also be changed when adding new disks to a RAID group. This is used to convert the RAID level of all the volumes belonging to a given RAID group.

For details on the above procedures, refer to "ETERNUS Web GUI User's Guide" and "ETER-NUS CLI User's Guide".


50



5.3.1 RAID Migration

RAID Migration is a function that transfers a volume to a different RAID group while guaranteeing the integrity of the data. This allows easy redistribution of volumes among RAID groups in response to customer needs. RAID Migration can be carried out while the system is running, and may also be used to switch data to a different RAID level (e.g. changing from RAID5 to RAID1+0).Examples of RAID Migration are shown below.

• Example when transferring volumes from a RAID5(3+1) 300GB SAS disk configuration to a RAID5(3+1) 450GB SAS disk configuration:

Figure 5.7 Example of RAID Migration 1

RAID5(3+1)

Unused 450GB x 4 RAID5(3+1)

300GB 300GB 300GB 300GB

450GB 450GB 450GB 450GB 450GB 450GB 450GB 450GB

300GB 300GB 300GB 300GB

Unused 300GB x 4

Volume 2

Volume 1

Volume 0

Volume 1

Define Volume 2 additionallyin the surplus space

Migrate to another RAIDgroup and add the capacity

Migrate to anotherRAID group

Volume 0


51



• Example when transferring volumes from a RAID5(3+1) configuration to a RAID1+0(3+3) configuration:

Figure 5.8 Example of RAID Migration 2

300GB 300GB 300GB300GB

300GB 300GB300GB

300GB 300GB300GB

Volume 0

Volume 0

RAID1+0(3+3)

300GB 300GB300GB

300GB 300GB300GB

Unused 300GB x 6

300GB 300GB 300GB300GB

Volume 0

RAID5(3+1)

Migrate to another RAID group

Unused 300GB x 4


52



5.3.2 Logical Device Expansion

Logical Device Expansion (RAID Group Expansion) allows the capacity of an existing RAID group to be dynamically expanded by the addition of extra disks. By using Logical Device Expan-sion to expand the capacity of existing RAID group, a new volume can be added without having to add new RAID groups.The following examples show Logical Device Expansion:

• RAID5(3+1) configuration converted to a RAID5(4+1) configuration by the addition of an extra disk

Figure 5.9 Example of Logical Device Expansion 1

300GB

Unused

300GB 300GB 300GB 300GB

Volume 0

Volume 1

RAID5(3+1)

300GB 300GB 300GB 300GB 300GB

Volume 0

Volume 1

Volume 2

RAID5(4+1)

Add and define Volume 2in the free space.


53



• RAID5(3+1) configuration converted to a RAID6(4+2) configuration by the addition of extra two disks

Figure 5.10 Example of Logical Device Expansion 2

300GB

300GB

Unused

300GB 300GB 300GB 300GB

Volume 0

Volume 1

RAID5(3+1)

300GB 300GB 300GB 300GB 300GB

Volume 0

Volume 1

Free space

RAID6(4+2)

300GB


54



5.3.3 LUN Concatenation

LUN Concatenation is a function that is used to add new area to a volume for expanding the vol-ume capacity available to the server. This function enables the reuse of free area in a RAID group and can be used to solve capacity shortages. The maximum capacity of a volume that is expanded by LUN Concatenation is 32TB.The following example shows the concatenation of an unused area of a different RAID group into Volume 2 in order to expand the capacity of Volume 2.

Figure 5.11 Example of LUN Concatenation

300GB 300GB 300GB 300GB

Volume 0

Volume 2

RAID5(3+1)

300GB 300GB 300GB 300GB

Unused area

Volume 1

RAID5(3+1)

300GB 300GB 300GB 300GB

Volume 0

RAID5(3+1)

300GB 300GB 300GB 300GB

Volume 1

RAID5(3+1)

Volume 2


55


Chapter 5 Basic Functions 5.4 Environmental Burden Reduction

5.4 Environmental Burden Reduction

The ETERNUS DX Disk storage system has energy and power savings that reduce CO2 emis-sions and lessen the burden on the environment.

5.4.1 Eco-mode

Using Eco-mode allows the rotation of disks that have limited access time to be stopped for specified periods to reduce power consumption.Disk spin-up and spin-down schedules can be set for each RAID group, and can also be set to allow backup operations.

The Eco-mode concept is shown below:

Figure 5.12 Eco-mode mechanism

Online disks

Nearline disks

Online disks

Nearline disks

Online disks

Nearline disks

Disks spinning Disks stoppedDisks stopped

Control linked to usage

Working Phase Working PhaseDisk spin-up Disk spin-downBackup Phase

Backup

AM(0:00 to 5:00)

5

PM(12:00 to 24:00)

12

Off

12

OffOff

12

On

AM(5:00 to 12:00)


56


Chapter 5 Basic Functions 5.4 Environmental Burden Reduction

5.4.2 Power Consumption Visualization

The power consumption and the temperature of the ETERNUS DX Disk storage system can be visualized by a graph using the ETERNUS SF Storage Cruiser integrated management software. Cooling efficiency can be improved by understanding local temperature rises in the data center and reviewing the location of air-conditioning.Understanding the disks that have a specific time to be used from the access frequency to RAID groups enables the Eco-mode schedule to be adjusted accordingly.

Figure 5.13 Power consumption visualization

Power consumption

Collects power consumption and temperature data for each storage system.

ETERNUS DX Disk storage systems

Server

Temperature

ETERNUS SF Storage Cruiser


57


Chapter 5 Basic Functions 5.5 Operation Monitoring

5.5 Operation Monitoring

This section explains the functions related to operation management and device monitoring for the ETERNUS DX Disk storage system.A failed part can be promptly detected and diagnosed by operation management software. This enables the problem to be appropriately dealt with. Collecting and analyzing detailed perfor-mance data improves the performance of the system.

5.5.1 Operation Management Interface

Operation management software can be selected in the ETERNUS DX Disk storage system according to environment of the user.ETERNUS Web GUI (Graphical User Interface) and ETERNUS CLI (Command Line Interface) are installed in the controller of the ETERNUS DX Disk storage system.

■ ETERNUS Web GUI

ETERNUS Web GUI is a program for settings and operation management that is installed in the ETERNUS DX Disk storage system and accessed by using a web browser via http or https.ETERNUS Web GUI has an easy-to-use design that makes intuitive operation possible.The settings that are required for the ETERNUS DX Disk storage system initial installation can be easily performed by following the wizard and inputting the parameters for the displayed set-ting items.

■ ETERNUS CLI

ETERNUS CLI supports Telnet or SSH connections. The ETERNUS DX Disk storage system can be set and monitored using commands and command scripts.Most of the functions that can be executed using ETERNUS Web GUI can be executed.

■ ETERNUS SF Web GUI/ETERNUS SF CLI

"ETERNUS SF" Storage Foundation Software can manage an "ETERNUS series" centered stor-age environment. Since the complicated storage configuration designing and setting operations can be performed with an easy-to-use GUI, a storage system can be installed easily without needing to have high level skills.ETERNUS SF ensures stable operation by managing the entire storage system.

■ SMI-S

Storage systems can be managed collectively using the general storage management applica-tion that supports Version 1.2 of Storage Management Initiative Specification (SMI-S). SMI-S is a storage management interface standard developed and maintained by the Storage Network Industry Association (SNIA). SMI-S can monitor the device status and change the RAID group or volume configurations.


58



5.5.2 Event Notification

When an error occurs in the ETERNUS DX Disk storage system, this function notifies the event information to the administrator. The administrator can realize an error occurred without monitor-ing the screen all the time.The methods to notify an event are e-mail, SNMP Trap, remote support, and host sense.The notification methods and levels can be set as required.

• E-mailWhen an event occurs, an e-mail is sent to the specified e-mail address.

• SNMP TrapUsing the SNMP agent function, management information is sent to the SNMP manager (monitoring server). The ETERNUS DX Disk storage system supports SNMP v1, v2c, and v3.

• Remote supportThe errors that occur in the ETERNUS DX Disk storage system are notified to the remote support center. Additional information (logs and system configuration information) for checking the error are also sent. This shortens the time to collect information.

• Host senseThe ETERNUS DX Disk storage system returns host senses (sense codes) to notify specific status to the server. Detailed information such as error contents can be obtained from the sense code.

When using SNMP v2c or v3, the firmware version of the ETERNUS DX Disk storage system must be V20L13 or later. The settings for SNMP v2c and v3 can be performed with ETERNUS CLI when the firmware version of the ETERNUS DX Disk storage system is V20L13 or later or with ETERNUS Web GUI when the firmware version of the ETERNUS DX Disk storage system is V20L15 or later.The firmware version can be checked via ETERNUS Web GUI or ETERNUS CLI. When upgrading firmware is required, contact your sales representative.


59



Figure 5.14 Event notification

SNMPmanager

Mailserver

ETERNUS DX Diskstorage system

Remotesupportcenter

Server(host)

E-mail SNMP Trap

Host sense

REMCS/SNMP (*1)

*1: SNMP for the EMEA&I region and REMCS for all other regions


60



5.5.3 Performance Information Management

The ETERNUS DX Disk storage system supports a function that collects and displays perfor-mance data via GUI or CLI. The collected performance information shows the operation status and load status of the ETERNUS DX Disk storage system and can be used to optimize the sys-tem configuration.Performance information can be collected such as host I/O information (IOPS values, throughput values, response time, cache hit rate) and the usage information of CMs (CPU) and disks.

ETERNUS SF Storage Cruiser or ETERNUS SF Express can be used to easily understand the operation status and load status of the ETERNUS DX Disk storage system by graphically dis-playing the collected information on GUI. ETERNUS SF Storage Cruiser can also monitor the performance threshold and retain performance information for the duration that a user specifies.For details, refer to the manuals of ETERNUS SF Storage Cruiser and ETERNUS SF Express.

5.5.4 Assigned CMs

A controller that controls access is assigned to each RAID group and manages the load balance in the ETERNUS DX Disk storage system. The controller that controls a RAID group is called an assigned CM.

Figure 5.15 Assigned CM

If auto assignment is selected for an assigned CM when RAID groups are created, the RAID group number is used to determine the assigned CM. When the RAID group number is an even number, "CM#0" is allocated as the assigned CM. For odd numbers, "CM#1" is allocated. When the load is unbalanced between the controllers, change the assigned CM.


Switch

CM#1

RAID group#1RAID group#0

Switch

RAID group#2

CM#0

Assigned CM

The assigned CM of the

RAID group controls

access.

Assigned CM


61



5.5.5 Connection Operation Mode

The response from the ETERNUS DX Disk storage system can be optimized by switching the setup information of the host response for each connected server.The server requirements of the supported functions, LUN addressing, and the method for com-mand responses vary depending on the connection environments such as the server OS and the driver that will be used. A function that handles differences in server requirements is supported. This function can specify the appropriate operation mode for the connection environment and convert host responses that respond to the server in the ETERNUS DX Disk storage system.The host response settings can be specified for the server or the port to which the server con-nects. Refer to "Configuration Guide -Server Connection-" for details on the settings.

Figure 5.16 Host response (connection operation mode)

• If the host response settings are not set correctly, a volume may not be recognized or the desired performance may not be possible. Make sure to select appropriate host response settings.

• The maximum number of volumes (number of LUNs that are set) that can be recognized by the server varies depending on the connection operation mode of the host response settings. The volume settings to allow each server to access the volume can be performed in the host response settings. For details on the function, refer to "5.2.2 Host Affinity" (page 47).

Monitoring time .....

Response status .....

Conversion pattern .....

AIX mode

Convert

Command response




Command response

Host response settings (for Server A)

Server B Server C





HP-UX mode

Convert

Command response




Command response

Host response settings (for Server B)




AIX mode

Convert

Command response




Command response

Host response settings (for Server A)

Server A


62



5.5.6 Device Time Setup

The ETERNUS DX Disk storage system has a clock function and manages time information of date/time and the time zone (the region in which the ETERNUS DX Disk storage system is installed). This time information is used for internal logs and for functions such as Eco-mode and remote support.The automatic time correction by the Network Time Protocol (NTP) is recommended to synchro-nize time in the whole system.When using the NTP, specify the NTP server or the SNTP server. The ETERNUS DX Disk stor-age system supports NTP version 3. The time correction mode is Step mode (immediate correc-tion). The time is corrected every three hours once the NTP is set.

Figure 5.17 Device time setup

• If an error occurs in a system that has a different date and time for each device, analyzing the cause of this error may be difficult.

• Make sure to set the date and time correctly when using Eco-mode.The stop and start process of the disk motors does not operate according to the Eco-mode schedule if the date and time in the ETERNUS DX Disk storage system are not correct.

NTPserver


Daylight Saving Time

Date and Time

Time Zone

yyyy mm dd xx:xx:xx

GMT + 09.00

NTP


63


Chapter 6 Optional Function (Advanced Copy)

This chapter explains the optional function of the ETERNUS DX Disk storage system."Advanced Copy" is available as an optional function. For the ETERNUS DX60 S2, only a local copy, which is performed within a single ETERNUS DX Disk storage system, is available for Advanced Copy. The relevant license must be purchased to use this optional function.

6.1 Backup

The Advanced Copy function (high-speed copying function) enables data backup (data replica-tion) at any point without stopping the operations of the ETERNUS DX Disk storage system.For the ETERNUS DX Disk storage system backup operation, data can be replicated without tak-ing server resources. The replication process for large amounts of data can be performed by controlling the timing and business access so that data protection can be considered separate from operation processes.The following figure shows an example of an Advanced Copy operation using ETERNUS SF AdvancedCopy Manager.

Figure 6.1 Example of Advanced Copy

VolumeBackup Volume

Tape

Reduction of Backup Time Using Advanced Copy

Time

OperationOperation

Time

OperationOperationBackup Process (System Down Time)

System Down Time

Reduce the system down time by using the high-speed backup with Advanced Copyfunction.

Backup Software

Volume

Tape

Conventional Backup

ETERNUS SF AdvancedCopy Manager

Disk Backup Function Tape Backup Function


64


Chapter 6 Optional Function (Advanced Copy) 6.1 Backup

The following table shows the types of controlling software that are used for Advanced Copy functions:

Table 6.1 Controlling software

*1: To use the Advanced Copy functions in a VSS environment, "ETERNUS VSS Hardware Provider" must be downloaded and installed on the server. For details of "ETERNUS VSS Hardware Provider" and how to install it, refer to the following web-site:http://www.fujitsu.com/global/services/computing/storage/eternus/tools/vsshp.html

The following table shows the copy functions (copy methods) that are available by registering the license:

Table 6.2 List of functions (copy methods)

*1: When an Advanced Copy Feature License is not purchased, up to eight SnapOPC+/QuickOPC ses-sions can be used. Try using the Advanced Copy functions to evaluate them before purchase or to plan for their use after purchase.

Copying is performed for each LUN. Copying can also be performed for each logical disk (such as the partition and volume (the name differs depending on the OS)) when using ETERNUS SF AdvancedCopy Manager.

Controlling software Features

ETERNUS Web GUI or ETERNUS CLI

Copy functions are available without needing any optional software.

Volume Shadow copy Service (VSS) (*1)

VSS can meet various requirements such as data backup in a live data environment, due to its ability to link with ISV backup software or ISV business applications that support the Microsoft Windows Server VSS function.

ETERNUS SF AdvancedCopy Manager (ACM)

ACM supports various OSs and ISV applications. All Advanced Copy functions are available. This also allows data backup in a live data environment via links with Oracle, SQL Server, Exchange Server, and Symfoware Server software.

ETERNUS SF Express ETERNUS SF Express makes it easier to manage the ETERNUS DX Disk storage system and to backup data.

"ETERNUS SF AdvancedCopy Manager", "ETERNUS SF Express", or a VSS environment is required to use the Advanced Copy functions with other operations.

Copy LicenseNumber of

usable sessions

Controlling software

ETERNUS Web GUI or ETERNUS

CLI

VSSETERNUS SF

AdvancedCopy Manager

ETERNUS SF Express

No license 8 (*1) SnapOPC+ SnapOPC+QuickOPC

– SnapOPC+

License 512 SnapOPC+ SnapOPC+QuickOPC

SnapOPC+QuickOPCOPCEC

SnapOPC+QuickOPCOPCEC


65


http://www.fujitsu.com/global/services/computing/storage/eternus/tools/vsshp.html


The following methods are available as the Advanced Copy function.

● OPC (One Point Copy)

One Point Copy (OPC) is a function that copies data in the volume to another volume in the ETERNUS DX Disk storage system at a specific point in time.OPC is suitable for the following usages:

- Performing a backup

- Making system test data replication

- Restoring backup data (restoration after replacing a disk when the copy source disk has failed)

● QuickOPC

QuickOPC copies all data as initial copy in the same way as OPC. After the initial copy has completed, only updated data (differential data) is copied. QuickOPC is suitable for the following usages:

- Performing a backup of data that is not updated regularly


- Restoration from a backup

● SnapOPC+

As updates occur in the source data, SnapOPC+ saves the data prior to change to the copy destination (Snap Data Volume (SDV)). Prepare a Snap Data Pool (SDP) before performing SnapOPC+. When an amount of data that exceeds the SDV capacity is saved, volumes are supplied from a SDP. The SnapOPC+ function only copies data that is to be updated and performs generation management of the copy source volume. SnapOPC+ is suitable for the following usages:

- Performing temporary backup for tape backup

- Performing a backup of data that is not updated regularly

● EC (Equivalent Copy)

EC makes a mirror copy of the copy source to the copy destination beforehand, and then suspends the copy and treats all data as independent data.When copying is resumed, only updated data in the copy source is copied to the copy destination. If the copy destination data has been changed, copy the copy source data again. EC is suitable for the following usages:

- Performing a backup



66



• LUN Concatenation cannot be performed for volumes with copy ses-sions set.

• RAID Migration cannot be performed for volumes with copy sessions set.

• Copy sessions cannot be set for volumes when RAID Migration is being performed for these volumes.

• Prepare an encrypted SDP when an encrypted SDV is used.

• If the SDP capacity is insufficient, a copy cannot be performed. In order to avoid this situation, an operation that notifies the operation adminis-trator of event information according to the remaining SDP capacity is recommended. For more details on event notification, refer to "5.5.2 Event Notification" (page 59).


67


Chapter 6 Optional Function (Advanced Copy) 6.2 Available Advanced Copy Combinations

6.2 Available Advanced Copy Combinations

Different Advanced Copy types can be combined and used together.

● OPC Restoration

For OPC and QuickOPC, restoration of the copy source from the copy destination is complete immediately upon request.

Figure 6.2 OPC Restoration

● EC Reverse

Restoration of the copy source from the copy destination is possible by switching the EC copy source and destination.

Figure 6.3 EC Reverse

Copy source Copy destination

OPC or QuickOPC

Restoration from the copy destination to the copy source (OPC Restoration)

Copy source Copy destination

EC

Copy destination Copy source

EC

Reverse


68



● Multiple Copy

Multiple Copy destinations can be set for a single copy source area to obtain multiple backups. Up to eight OPC, QuickOPC, or EC sessions can be set for a Multiple Copy.

Figure 6.4 Multiple Copy

Up to maximum number of SnapOPC+ copy session generations can be set for a single copy source area when seven or less Multiple Copy sessions are already set.

Figure 6.5 Multiple Copy (including SnapOPC+)

Copy destination 1

Copy sourceCopy destination 2

Copy destination 3

Copy destination 4

Copy destination 5

Copy destination 6

Copy destination 7

Copy destination 8

Copy destination 1

Copy sourceCopy destination 2

Copy destination 3 Copy destination 4

Copy destination 6

Copy destination 7

Copy destination 5

Copy destination (SnapOPC+ generation data)


69



● Cascade Copy

A copy destination with a copy session that is set can be used as the copy source of another copy session.A Cascade Copy is performed by combining two copy sessions. Table 6.3 shows the sup-ported combinations of copy sessions for cascade copies.

Figure 6.6 Cascade Copy

Table 6.3 Available Cascade Copy combinations

*1: Copy session 2 backs up data in the copy destination of copy session 1. Data is not backed up in the copy source of copy session 1.

Copy session 2Copy session 1

OPC QuickOPC SnapOPC+ EC

OPC No No No No

QuickOPC No Yes (*1) No No

SnapOPC+ No No No No

EC No No No No

To acquire valid backup data in the copy destination for copy session 2, a physical copy must be completed in all of the copy sessions that configure the Cascade Copy.Check the copy status for copy sessions 1 and 2 when using the backup data.

Copy source Copy source + Copy destination Copy destination

QuickOPC QuickOPC

: Copy session 1

: Copy session 2


70


• The content of this manual is subject to change without notice.

• This manual was prepared with the utmost attention to detail.However, Fujitsu shall assume no responsibility for any operational problems as the result of errors, omissions, or the use of information in this manual.

• Fujitsu assumes no liability for damages to third party copyrights or other rights arising from the use of any information in this manual.

• The content of this manual may not be reproduced or distributed in part or in its entirety without prior permission from Fujitsu.


P3AM-5482-08ENZ0

Date of issuance: February 2015

Issuance responsibility: FUJITSU LIMITED

Documents

This page is intentionally left blank. - Fujitsustorage-system.fujitsu.com/global/doc/pdf/p3am-5482-en.pdf · Chapter 3 Connection Configurations ... 5.1 Data Protection ... Table