eternus cs800 user guide - fujitsumanuals.ts.fujitsu.com/file/9283/cs800_ug.pdf · contents 6...

Edition April 2010

© S

iem

ens

Nix

dor

f In

form

atio

nssy

ste

me

AG

19

95

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

0501

_U

serG

uid

e\0_

Cov

er.f

m

English

ETERNUS CS800User Guide

Comments… Suggestions… Corrections…The User Documentation Department would like to know your opinion on this manual. Your feedback helps us to optimize our documentation to suit your individual needs.

Feel free to send us your comments by e-mail to: [email protected]

Certified documentation according to DIN EN ISO 9001:2000To ensure a consistently high quality standard anduser-friendliness, this documentation was created tomeet the regulations of a quality management system which complies with the requirements of the standardDIN EN ISO 9001:2000.

cognitas. Gesellschaft für Technik-Dokumentation mbHwww.cognitas.de

Copyright and Trademarks

This manual is printed on paper treated with chlorine-free bleach.

Copyright © Fujitsu Technology Solutions GmbH 2010.

All rights reserved.Delivery subject to availability; right of technical modifications reserved.

This document includes trademarks and copyrights of Quantum Corporation. All rights reserved.

Microsoft®, Microsoft Windows®, and Windows Server® are U.S. registered trademarks of Microsoft Corporation.

Linux is a registered trademark of Linus Torvalds.

Fujitsu and the Fujitsu Logo are trademarks of Fujitsu Limited.

All hardware and software names used are trademarks of their respective manufacturers.

http://www.cognitas.de

mailto:[email protected]

U41840-J-Z125-1-76 3

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku\

1000

501

_Use

rGu

ide\

0_C

S8

00_U

ser_

Gui

deT

OC

.fm

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Important Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Safety Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Before Starting up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Installation and Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Working with CDs/DVDs and CD/DVD Drives . . . . . . . . . . . . . . . . . . . . . 15Laser Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Modules with Electrostatic-Sensitive Devices . . . . . . . . . . . . . . . . . . . . . 17Notes on Cleaning the Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Other Important Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

FCC Class A Compliance Statement . . . . . . . . . . . . . . . . . . . . . . . . 19

Transporting the Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Notes on Installing in the Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Environmental Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

System Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Features and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Data Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Data Deduplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Space Reclamation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Remote Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

ETERNUS CS800 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Hard Drive Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Network Attached Storage (NAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Supported RAID Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Contents

4 U41840-J-Z125-1-76

Hardware Description and Basic Operations . . . . . . . . . . . . . . . . . . . . 33

CS800 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Front View – Features and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . 33Rear View – PCI Slots and Panel Connectors . . . . . . . . . . . . . . . . . . . . . 36

CS800 Basic Storage Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Front View – Panel Features and Indicators . . . . . . . . . . . . . . . . . . . . . . 41Rear View – Connectors and Indicators . . . . . . . . . . . . . . . . . . . . . . . . 43

CS800 Storage Expansion Module . . . . . . . . . . . . . . . . . . . . . . . . . . 45Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Rear Panel Features and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Hard Drive Carrier Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Turning On and Shutting Down the System . . . . . . . . . . . . . . . . . . . . . 50

Locating the System Serial Number . . . . . . . . . . . . . . . . . . . . . . . . . 51

Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Data Storage Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Network Attached Storage (NAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Open Storage (OST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Data Deduplication Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Enable Data Deduplication (Adaptive In-line Data Deduplication) . . . . . . . . . . . 54Enable Backup Window (Deferred Processing Data Deduplication) . . . . . . . . . . 55

Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56NAS Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56OST Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Recovering Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Recovery Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Recovery Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Recovery Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Network Segmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Network Segmentation Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Remote Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

CS800 Web Pages – Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Contents

U41840-J-Z125-1-76 5

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku\

1000

501

_Use

rGu

ide\

0_C

S8

00_U

ser_

Gui

deT

OC

.fm

Accessing CS800 Web Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Using the CS800 Web Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Disk Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Data Reduction Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Cumulative Replication Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Configuration with the CS800 Web Pages . . . . . . . . . . . . . . . . . . . . . . 75

NAS & OST Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75NAS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75OST Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Windows Domain Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Access Control Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Advanced Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

PTT Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Physical Device Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Backup Application Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Initiators and Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Segmentation and Bonding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Date and Time Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Security Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Email Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Email Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

SNMP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Contacts Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

AIS Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Contents

6 U41840-J-Z125-1-76

Configurations for NetBackup and OST Replication . . . . . . . . . . . . . . . 137

OST Optimized Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Initiating an OST Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Installing the OST Plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Configuring the NetBackup Media Server . . . . . . . . . . . . . . . . . . . . . 144

Registering the Storage Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Registering the Storage Server on Windows Platforms via NetBackup 7.0 GUI . . . 145Registering the Storage Server on Windows Platforms via CLI . . . . . . . . . . . . 149

Configuring Disk Pools and Storage Units . . . . . . . . . . . . . . . . . . . . 152

CS800 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Data Deduplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Ingest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Disk Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

CS800 Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Admin Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Service Tickets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Space Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Configuring Replication for the First Time . . . . . . . . . . . . . . . . . . . . . . . 181

Contents

U41840-J-Z125-1-76 7

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku\

1000

501

_Use

rGu

ide\

0_C

S8

00_U

ser_

Gui

deT

OC

.fm

Replication Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Directory/File Based Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Directory/File Based Replication NAS Configuration Steps . . . . . . . . . . . . . . 182Replication Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Accessing Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Source Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Source Role General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Source Role NAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Source Role Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Target Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Target Role General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Target Role NAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Target Role Actions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Uploading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200System Diagnostics File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Storage Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Healthchecks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Network Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Disk Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Node Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Troubleshooting via CS800 Web Pages . . . . . . . . . . . . . . . . . . . . . . . 209

CS800 Problem Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Using CS800 Status Page for Troubleshooting . . . . . . . . . . . . . . . . . . . 210Downloading the System Diagnostics File . . . . . . . . . . . . . . . . . . . . . . . 211

Common Problems and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . 212Start-up Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Hardware Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Ethernet Network Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Replication Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Contents

8 U41840-J-Z125-1-76

Temperature Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Service Tickets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Implementing a Data Replication Plan . . . . . . . . . . . . . . . . . . . . . . . 221

Setting Up Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221Setting Up the Target CS800 System . . . . . . . . . . . . . . . . . . . . . . . . . 221Setting Up the Source CS800 System . . . . . . . . . . . . . . . . . . . . . . . . 222Enabling and Running Replication . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Recovering Replicated Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Data Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Data Failback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Removal and Replacement Procedures for CRUs . . . . . . . . . . . . . . . . . 229

ETERNUS CS800 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Hot-Plug Power Supply Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229ETERNUS CS800 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

System Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

System Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Additional Server Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Additional Storage Module Specifications . . . . . . . . . . . . . . . . . . . . . 242

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

U41840-J-Z125-1-76 9

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mä

rz 2

010

Sta

nd 1

9:2

3.50

Pfa

d: P

:\allg

eme

in\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uide

\1_P

refa

ce.fm

PrefaceThis manual introduces the ETERNUS CS800 enhanced data protection system and provides information mainly about:

● Features and Hardware

● Configuration

● Web interface

● Basic troubleshooting

Audience

This manual is written for ETERNUS CS800 system administrators and field service engineers.

I It is useful for the audience to have a basic understanding of UNIX® and backup/recovery systems.

Document Organization

Following is a brief description of chapter contents.

● Chapter "Important Information" provides essential information regarding safety when working on your ETERNUS CS800.

● Chapter "System Description" provides an overview of the ETERNUS CS800 system.

● Chapter "Hardware Description and Basic Operations" provides basic operating instructions for the CS800 system.

● Chapter "Concepts" discusses key concepts and terminology used in the CS800.

● Chapter "Remote Management" discusses using the CS800 system management pages to control the system remotely.

● Chapter "Configuration with the CS800 Web Pages" discusses the configuration of the CS800 system.

● Chapter "Configurations for NetBackup and OST Replication" discusses configurations for usage of OST Optimized Replication in combination with NetBackup.

● Chapter "CS800 Status" discusses CS800 status information.

● Chapter "CS800 Alerts" discusses the CS800 alert information and service tickets.

Preface

10 U41840-J-Z125-1-76

● Chapter "Data Services" discusses the CS800 data services such as space recla-mation and remote replication.

● Chapter "Utilities" discusses CS800 utilities such as diagnostic tools and rebooting the system.

● Chapter "Troubleshooting via CS800 Web Pages" discusses problems you may encounter during the setup and operation of the CS800 system.

● Chapter "Implementing a Data Replication Plan" discusses the common ways to implement a data replication plan.

● Chapter "Removal and Replacement Procedures for CRUs" describes how the Customer can exchange Customer Replaceable Units.

● Chapter "Expansion" describes how additional storage modules are introduced into an existing CS800 system.

● Appendix "System Specifications" provides system specifications for the CS800.

● Glossary provides definitions of terms used in this guide.

Notational Conventions

This manual uses the following conventions:

I Note emphasizes important information related to the main topic.

V Caution indicates potential hazards to equipment or data.

W Warning indicates potential hazards to personal safety.

● Right side of the system - Refers to the right side as you face the component being described.

● Left side of the system - Refers to the left side as you face the component being described.

● Data sizes are reported in base 1000 rather than base 1024. For example:

● 1 MB = 1,000,000 bytes

● 1 GB = 1,000,000,000 bytes

● 1 TB = 1,000,000,000,000 bytes

Preface

U41840-J-Z125-1-76 11

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mä

rz 2

010

Sta

nd 1

9:2

3.50

Pfa

d: P

:\allg

eme

in\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uide

\1_P

refa

ce.fm

Related Documents

The following documents are also available for CS800 systems:

Support and Help

Where to Find Information

Information and documentation on Fujitsu’s ETERNUS CS800 product can be obtained as follows:

Technical Support

The CS800 system includes AIS real-time support via remote access (see "AIS Connect" on page 133).

The Support section of the Fujitsu Technology Solutions web site at http://ts.fujitsu.com/services provides links with contact information and information about available support programs.

Order Number Document Title Document Description

A26361-F1452-Z253-3-8N19

Safety Notes and Other Important Information

Lists Fujitsu’s general safety and regulatory information

U41842-J-Z125-1-76 ETERNUS CS800 Getting Started Guide

Provides information about instal-lation of the CS800

U41841-J-Z125-1-76 ETERNUS CS800 Command Line Interface (CLI) Guide

Provides information about the CS800 command line interface

– ETERNUS CS800 Online Help

Provides task-oriented information about a running CS800 system

Resource Address

Product information and documentation

http://ts.fujitsu.com/products/storage/eternus/cs

ETERNUS CS800 manuals http://manuals.ts.fujitsu.com

Release notes http://manuals.ts.fujitsu.com

Downloads and Software patches

http://support.ts.fujitsu.com/com/support/downloads.html

Select Storage – ETERNUS CS.

http://ts.fujitsu.com/services

http://ts.fujitsu.com/services

http://ts.fujitsu.com/products/storage/eternus/cs

http://manuals.ts.fujitsu.com

http://manuals.ts.fujitsu.com

http://support.ts.fujitsu.com/com/support/downloads.html

Preface

12 U41840-J-Z125-1-76

If you have an active support agreement, you may contact your service provider.

If you do not have an active support agreement, contact your Fujitsu Technology Solutions sales representative to purchase a service contract or updates.

Customer Service

Your Comments

Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to:

[email protected]

If you have issues, comments, or questions about specific information or procedures, please include the title and, if available, the part number, the page numbers, and any other details that will help us locate the subject you are addressing.

Fujitsu Home Page

Visit the home page of Fujitsu Technology Solutions at:

http://ts.fujitsu.com

Fujitsu Compliance Link

See the compliance link of Fujitsu Technology Solutions at:

https://sp.ts.fujitsu.com/sites/certificates/default.aspx

Worldwide End-User Product Warranty

For information the Fujitsu Worldwide End-User Standard Limited Product Warranty look at:

http://support.ts.fujitsu.com/com/support/warranty/product_warranty.html

Resource Address

Education and training Fujitsu Technology Solutions Mies-van-der-Rohe-Str. 8 80807 Munich, Germany

[email protected]

Support phone +49-180-54040

Support fax +49-180-5336779

https://sp.ts.fujitsu.com/sites/certificates/default.aspx

http://support.ts.fujitsu.com/com/support/warranty/product_warranty.html

http://www.quantum.com

http://www.quantum.com/pdf/QuantumWarranty.pdf

http://www.quantum.com

http://ts.fujitsu.com

U41840-J-Z125-1-76 13

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uid

e\2

_Ge

ttin

gSta

rte

d.k0

2

Important InformationIn this chapter you find essential information regarding safety when working on your system.

Safety Instructions

I For safety instructions see also the manual "Safety notes and other important information".

This system meets the relevant safety regulations for IT equipment. If you have any questions about whether you can install the CS800 system in the intended environment, please contact your sales outlet or our customer service team.

V CAUTION!

● The actions described in this manual shall be performed by technical specialists. A technical specialist is a person who is trained to install the system including hardware and software.

● Some components of the ETERNUS CS800 system may be replaced by the customer if they fail. These components are called Customer Replaceable Units (CRUs). Other units may not be replaced by the customer. Please note that unauthorized interference with the system will void the warranty and exempt the manufacturer from all liability.

● Any failure to observe the guidelines in this manual, and any improper repairs could expose the user to risks (electric shock, energy hazards, fire hazards) or damage the equipment.

Before Starting up

V CAUTION!

● During installation and before operating the device, observe the instructions on environmental conditions for your device.

● If the system has been moved from a cold environment, condensation may form both inside and on the outside of the machine.

● Wait until the system has acclimatized to room temperature and is absolutely dry before starting it up. Material damage may be caused to the system if this requirement is not met.

Safety Instructions Important Information

14 U41840-J-Z125-1-76

● Only transport the system units in the original packaging or in packaging that protects it from impacts and jolts.

Installation and Operation

V CAUTION!

● This unit should not be operated in ambient temperatures above 35 °C.

● If the unit is integrated into an installation that draws power from an industrial power supply network with an IEC309 connector, the power supply's fuse protection must comply with the requirements for non-industrial power supply networks for type A connectors.

● The unit automatically adjusts itself to a mains voltage in a range of 100-240 V (50-60 Hz). Ensure that the local mains voltage lies within these limits.

● This device must only be connected to properly grounded shock-proof sockets or insulated sockets of the rack's internal power supply with tested and approved power cables.

● Ensure that the device is connected to a grounded shockproof socket close to the device.

V CAUTION!

● Ensure that the power sockets on the device and the grounded shockproof sockets are freely accessible.

● The On/Off button or the main power switch (if present) does not isolate the device from the mains power supply. To disconnect it completely from the mains power supply, unplug all network power plugs from the grounded shockproof sockets.

● Always connect the CS800 components and the attached peripherals to the same power circuit. Otherwise you run the risk of losing data if, for example, the CS800 server unit is still running but a storage subsystem fails during a power outage.

● Data cables must be adequately shielded.

● The EN 50173 and EN 50174-1/2 standards apply for LAN cabling. The minimum requirement is the use of a category 5 screened LAN cable for 10/100 Mbit/s Ethernet, or a category 5e cable for Gigabit Ethernet. The requirements from the ISO/IEC 11801 specification must also be met.

● Route the cables in such a way that they do not create a potential hazard (make sure no-one can trip over them) and that they cannot be damaged.

Important Information Safety Instructions

U41840-J-Z125-1-76 15

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uid

e\2

_Ge

ttin

gSta

rte

d.k0

2

● Never connect or disconnect data transmission lines during a storm (risk of lightning strike).

● Make sure that no objects (e.g. jewelry, paperclips etc.) or liquids can get inside the system (risk of electric shock, short circuit).

● In emergencies (e.g. damaged casing, controls or cables, penetration of liquids or foreign bodies), switch off the system immediately, remove all power plugs and contact your sales outlet or customer service team.

V CAUTION!

● Proper operation of the system (in accordance with IEC 60950-1/ EN 60950-1) is only ensured if the casing is completely assembled (electric shock, cooling, fire protection, interference suppression).

● Only install system expansions that satisfy the requirements and rules governing safety and electromagnetic compatibility and those relating to telecommunication terminals. If you install other expansions, they may damage the system or violate the safety regulations. Information on which system expansions are approved for installation can be obtained from our customer service center or your sales outlet.

● The components marked with a warning notice (e.g. lightning symbol) may only be opened, removed or exchanged by authorized, qualified personnel. Exception: CRU (Customer Replaceable Units) components can be replaced.

● The warranty is void if the system is damaged during installation or replacement of system expansions.

● Only set screen resolutions and refresh rates that are specified in the operating manual for the monitor. Otherwise, you may damage your monitor. If you are in any doubt, contact your sales outlet or customer service center.

Working with CDs/DVDs and CD/DVD Drives

When working with devices with CD/DVD drives, these instructions must be followed.

V CAUTION!

● Only use CDs/DVDs that are in perfect condition in your server's CD/DVD drive, in order to prevent data loss, equipment damage and injury.


16 U41840-J-Z125-1-76

● Check each CD/DVD for damage, cracks, breakages etc. before inserting it in the drive.

Note that any additional labels applied may change the mechanical properties of a CD/DVD and cause imbalance.

Damaged and imbalanced CDs/DVDs can break at high drive speeds (data loss).

Under certain circumstances, sharp CD/DVD fragments can pierce the cover of the CD/DVD drive (equipment damage) and can fly out of the device (danger of injury, particularly to uncovered body parts such as the face or neck).

I You can prevent mechanical damage and damage to the CD/DVD drive, as well as premature CD/DVD wear, by observing the following suggestions:

● Only insert CDs/DVDs in the drive when needed and remove them after use.

● Store the CDs/DVDs in suitable sleeves.

● Protect the CDs/DVDs from exposure to heat and direct sunlight.

Laser Information

The CD/DVD drive complies with IEC 60825-1 laser class 1.

V CAUTION!

The CD/DVD drive contains a light-emitting diode (LED), which under certain circumstances produces a laser beam stronger than laser class 1. Looking directly at this beam is dangerous.

Never remove parts of the CD/DVD drive casing!

The FC HBAs (Fibre Channel Host Bus Adapters) also comply with IEC 60825-1 laser class 1.

Class 1M Laser Product (PRO/10GbE SR Server Adapter)

The Laser device must be factory serviced ONLY by the responsible manufacturer! NO adjustments, service or maintenance is to be performed otherwise.

V CAUTION! Use of controls or adjustments or performance of procedures other than those specified herein may result in hazardous radiation exposure.

Important Information Safety Instructions

U41840-J-Z125-1-76 17

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uid

e\2

_Ge

ttin

gSta

rte

d.k0

2

Batteries

V CAUTION!

● Incorrect replacement of batteries may lead to a risk of explosion. The batteries may only be replaced with identical batteries or with a type recommended by the manufacturer (see the technical manual for the system board).

● Do not throw batteries into the trash can. They must be disposed of in accor-dance with local regulations concerning special waste.

● The battery must be disposed of in accordance with local regulations concerning special waste.

● Replace the lithium battery on the system board in accordance with the instruc-tions in the technical manual for the system board.

● All batteries containing pollutants are marked with a symbol (a crossed-out garbage can). In addition, the marking is provided with the chemical symbol of the heavy metal decisive for the classification as a pollutant:

Cd Cadmium Hg Mercury Pb Lead

Modules with Electrostatic-Sensitive Devices

Modules with electrostatic-sensitive devices are identified by the following sticker:

Figure 1: ESD label

When you handle components fitted with ESDs, you must always observe the following points:

● Switch off the system and remove the power plugs from the power outlets before installing or removing components with ESDs.

● You must always discharge static build-up (e.g. by touching a grounded object) before working with such components.


18 U41840-J-Z125-1-76

● Any devices or tools that are used must be free of electrostatic charge.

● Wear a suitable grounding cable that connects you to the external chassis of the system unit.

● Always hold components with ESDs at the edges or at the points marked green (touch points).

● Do not touch any connectors or conduction paths on an ESD.

● Place all the components on a pad which is free of electrostatic charge.

I For a detailed description of how to handle ESD components, see the relevant European or international standards (EN 61340-5-1, ANSI/ESD S20.20).

Notes on Cleaning the Devices

V CAUTION!

● Switch the device off and disconnect the power plugs from the grounded shock-proof sockets.

● Do not clean any interior parts yourself; leave this job to a service technician.

● Do not use any cleaning agents that contain abrasives or may corrode plastic.

● Ensure that no liquid enters the system. Ensure that the ventilation areas of the device are clear.

Wipe the device casing with a dry cloth. If particularly dirty, use a cloth that has been moistened in a mild domestic detergent and then carefully wrung out.

Other Important Information

Keep this operating manual and the other documentation (such as the Technical Manual, DVD) close to the device. All documentation must be included if the equipment is passed on to a third party.

Important Information FCC Class A Compliance Statement

U41840-J-Z125-1-76 19

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uid

e\2

_Ge

ttin

gSta

rte

d.k0

2

FCC Class A Compliance Statement

If there is an FCC statement on the device, then:

The following statement applies to the products covered in this manual, unless otherwise specified herein. The statement for other products will appear in the accompanying documentation.

NOTE

This equipment has been tested and found to comply with the limits for a "Class A" digital device, pursuant to Part 15 of the FCC rules and meets all requirements of the Canadian Interference-Causing Equipment Standard ICES-003 for digital apparatus. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in strict accordance with the instructions, may cause harmful interference to radio communications. However, there is no warranty that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

● Reorient or relocate the receiving antenna.

● Increase the separation between equipment and the receiver.

● Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

● Consult the dealer or an experienced radio/TV technician for help.

Fujitsu Technology Solutions is not responsible for any radio or television interference caused by unauthorized modifications of this equipment or the substitution or attachment of connecting cables and equipment other than those specified by Fujitsu Technology Solutions. The correction of interferences caused by such unauthorized modification, substitution or attachment will be the responsibility of the user.

The use of shielded I/O cables is required when connecting this equipment to any and all optional peripheral devices. Failure to do so may violate FCC and ICES rules.

W WARNING!This is a class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures.

Transporting the Devices Important Information

20 U41840-J-Z125-1-76

Transporting the Devices

V CAUTION!

Only transport the devices in their original packaging or in packaging that protects them from impacts and jolts. Do not unpack the devices until they are at their instal-lation location.

If you need to lift or transport the CS800 devices, ask other people to help you.

Never lift or carry the devices by the handles on the front panel.

Notes on Installing in the Rack

V CAUTION!

● For safety reasons, at least two people are required to install the rack model because of its weight and size.

● Never lift the devices into the rack using the handles on the front panel.

● When connecting and disconnecting cables, observe the relevant instructions in the "Important Information" chapter of the technical manual for the corre-sponding rack. The technical manual is supplied with the corresponding rack.

● When installing the rack, make sure that the anti-tilt mechanism is correctly fitted.

● For safety reasons, no more than one unit may be removed from the rack at any one time during installation and maintenance work.

● If several units are simultaneously removed from the rack, there is a risk that the rack could tip over.

● The rack must be connected to the power supply by an authorized specialist (electrician).

● If the rack model is integrated into an installation that draws power from an industrial power supply network with an IEC309 type connector, the power supply's fuse protection must comply with the requirements for non-industrial power supply networks for the type A connector.

Important Information Environmental Protection

U41840-J-Z125-1-76 21

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uid

e\2

_Ge

ttin

gSta

rte

d.k0

2

Environmental Protection

Environmentally-friendly product design and development

This product has been designed in accordance with the Fujitsu Technology Solutions standard for "environmentally friendly product design and development". This means that key factors such as durability, selection and labeling of materials, emissions, packaging, ease of dismantling and recycling have been taken into account.

This saves resources and thus reduces the harm done to the environment.

Energy-saving information

Devices that do not need to be constantly switched on should be switched off until they are needed as well as during long breaks and after completion of work.

Packaging information

Do not throw away the packaging. You may need it later for transporting the system. If possible, the equipment should only be transported in its original packaging.

Information on handling consumables

Please dispose of printer consumables and batteries in accordance with the applicable national regulations.

In accordance with EU directives, batteries must not be disposed of with unsorted domestic waste. They can be returned free of charge to the manufacturer, dealer or an authorized agent for recycling or disposal.

All batteries containing pollutants are marked with a symbol (a crossed-out garbage can). They are also marked with the chemical symbol for the heavy metal that causes them to be categorized as containing pollutants:

Cd CadmiumHg MercuryPb Lead

Labels on plastic casing parts

Please avoid sticking your own labels on plastic parts wherever possible, since this makes it difficult to recycle them.

Environmental Protection Important Information

22 U41840-J-Z125-1-76

Returns, recycling and disposal

Details regarding the return and recycling of devices and consumables within Europe can also be found in the "Returning used devices" manual, via your local Fujitsu Technology Solutions branch or from our recycling center in Paderborn:

Fujitsu Technology SolutionsRecycling CenterD-33106 Paderborn

Tel. +49 5251 8 18010Fax +49 5251 8 333 18010

The device must not be disposed of with domestic waste. This device is labeled in compliance with European directive 2002/96/EC on waste electrical and electronic equipment (WEEE).

This directive sets the framework for returning and recycling used equipment and is valid across the EU. When returning your used device, please use the return and collection systems available to you. Further information can be found at www.ts.fujitsu.com/recycling.

http://www.ts.fujitsu.com/recycling

U41840-J-Z125-1-76 23

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uide

\3_S

yste

m_

De

scri

ptio

n.fm

System DescriptionThis chapter describes the features and build-up of the ETERNUS CS800 system. The chapter consists of the following sections:

● "Overview"

● "Features and Benefits"

● "Data Reduction"

● "Space Reclamation"

● "Remote Replication"

● "ETERNUS CS800 System"

● "Hard Drive Storage"

● "Supported RAID Configurations"

Overview

The ETERNUS CS800 is Fujitsu’s midrange Enterprise disk backup solution that integrates data deduplication and replication technology to connect backup and disaster recovery protection across distributed corporate environments. The ETERNUS CS800 disk-based backup appliance uses data deduplication technology to decrease the typical disk capacity requirements very efficiently, and make WAN replication a practical, cost-effective part of disaster recovery planning. Scalable to 80 TB usable capacity, the ETERNUS CS800 is designed for departmental and medium business customers.

Major features of the ETERNUS CS800 include:

● Data deduplication and multi-site remote replication

● High ingest rate in adaptive-deduplication mode with NAS attachment (depending on configuration, network bandwidth and network latency)

Advanced Data Deduplication Increasing Disk Retention for Backup Data

The ETERNUS CS800 leverages data deduplication technology to dramatically increase the role that disk can play in the protection of critical data. With the ETERNUS CS800 solution, users can retain much more backup data on fast recovery disk than with conven-tional arrays.

Features and Benefits System Description

24 U41840-J-Z125-1-76

Remote Replication of Backup Data Providing Automated Disaster Recovery Protection

With the ETERNUS CS800, users can transmit backup data from a remote site to a central, secure location to reduce or eliminate media handling. CS800 replication is asynchronous, automated, and operates as a background process.

Configurable Post-Processing Techniques and Storage Presentation

Policy-based data deduplication lets users select either in-line or post-processing techniques. Storage is presented as NAS shares (CIFS and NFS) or OST storage servers.

Features and Benefits

The ETERNUS CS800 system provides the following features and benefits:

● Industry-unique, policy-based data deduplication matches different data deduplication methods to different backup tasks

● NAS or OST presentation layer

● 10 source to one target LAN/WAN replication

● OST Optimized Duplication support with Symantec NetBackup™ 6.5.3 or higher.

● OST direct path to tape support with Symantec NetBackup™ 6.5.4.

● Supported by every major backup software vendor

● Rack space requirements: 4 HU (Height Units) up to 22 HU (2 HU for each expansion module)

● Installs in a ETERNUS DX80 rack, PRIMECENTER rack, DataCenter rack or any 3rd party rack for standard servers (installation depth 735 – 770 mm) without restrictions.

I It is recommended to install the ETERNUS CS800 system in a controlled or restricted area to prevent access by untrained personnel. In addition, it is recommended that system installation is performed only by qualified IT personnel.

System Description Data Reduction

U41840-J-Z125-1-76 25

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uide

\3_S

yste

m_

De

scri

ptio

n.fm

Data Reduction

Data reduction is the process of reducing the amount of storage capacity required to store your data. The ETERNUS CS800 system provides two techniques to optimize the storage space required on your system:

● "Data Deduplication"

● "Compression"

Data Deduplication

The ETERNUS CS800 system reduces the amount of storage capacity required through a data deduplication process. The term data deduplication refers to the elimination of redundant data. Data deduplication works by recognizing repeated variable-length blocks of data in a stream of data. Only a single instance of each blocklet is stored in a so called block pool (a pool of all unique data blocks) and references (tags) are made for all of the duplicate variable-length blocks of data. These references or tags are stored in an index for use later to reconstitute the deduplicated data. When subsequent backup jobs occur, the data deduplication engine searches for new data entering the CS800 and uses a “variable length compression type algorithm” to compare this with existing data in the block pool. Unique blocks are added to the block pool and known blocks are indexed.

By only storing one instance of the blocklet, a great deal of capacity is saved. For a NAS share, the CS800 system waits for 60 seconds of inactivity before a file can be dedupli-cated.

The CS800 solution supports both in-line and post-processing data deduplication method-ologies — allowing users to realize optimal use of disk resources and achieve the perfor-mance needed to complete critical jobs during short backup windows.

Compression

The ETERNUS CS800 system uses compression technology after duplicate blocks have been identified and replaced as part of the deduplication process. With compression, unique data that has been through the data deduplication process can be compressed at a typical ratio of approximately 2:1. This enables you to maximize the storage capacity of your system.

Space Reclamation System Description

26 U41840-J-Z125-1-76

Space Reclamation

The space reclamation function searches the block pool for data blocks that are not refer-enced by any pointers (that is, the files associated with the block have been expired and removed). Once such a data block is identified, the index count is decremented, and the block is removed to make the space reusable.

Note that the space reclamation process can use a significant amount of CPU processing and disk I/O. Therefore it is important to know when to schedule the space reclamation process. By default the process will commence daily at 01:00 pm. To maximize perfor-mance and capacity utilization, it is highly recommended that this process is performed on a daily basis. As best practice it is recommended that this process commences at least two hours after your backup job has completed on a daily basis. It is far more efficient to process a day’s worth of new data than a week’s worth.

Remote Replication

Today most backup occurs on isolated devices, making it difficult to deploy disk backup when disaster recovery protection is required. The ETERNUS CS800 solution uses data deduplication and replication to decrease the bandwidth required to move backup data over networks and between sites dramatically. This dramatic gain makes it practical and cost-effective for users to replicate backup data over WANs for secure, network-based disaster recovery protection, and it lets users combine rapid, local restores with sound disaster recovery protection.

With CS800 replication, users can transmit data from a single site or multiple sites to a central location using any CS800. The replication is an asynchronous, automated background process that includes encryption of data in transit. This model for protecting the distributed enterprise allows users to combine disk storage, remote replication and tape backup for an optimal combination of performance, simplicity and security.

For information on implementing a replication plan, see Chapter "Implementing a Data Replication Plan".

System Description ETERNUS CS800 System

U41840-J-Z125-1-76 27

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uide

\3_S

yste

m_

De

scri

ptio

n.fm

ETERNUS CS800 System

The ETERNUS CS800 system consists of a server component, which is the PRIMERGY RX300 S5 server, and at least one storage component, which is the ETERNUS DX80 basic storage module (with two controllers). The system can be extended by up to 9 DX80 storage expansion modules.

Figure 2: Front View of an ETERNUS CS800

Two versions of the ETERNUS CS800 are provided:

● "CS800 NAS Basic"

● "CS800 NAS Performance"

CS800 NAS Basic

This version provides a base amount of network throughput, full data storage facility and optionally path-to-tape capability. It includes the following features:

● 1 server unit with 48 GB RAM and RAID1 (1 + 1) for the Operating System and for StorNext and Block pool metadata

● 1 basic storage module with 8 TB usable storage capacity and RAID 6 (4 + 2)

● 0 to 9 storage expansion modules, with 8 TB usable capacity and RAID 6 (4 + 2) each

● 7 x 1 GbE ports to the customer LAN plus one 1 GbE service port

● 2 x 4 Gb Fibre Channel ports (optionally, for OST path to tape only, not for ingestion)

For more details, see Chapter "System Specifications".

MinimumConfiguration

Expansion(Example)

ETERNUS CS800 System System Description

28 U41840-J-Z125-1-76

CS800 NAS Performance

This system provides fast network throughput and full data storage and optionally path-to-tape capability. It includes the following features:

● 1 server unit with 48 GB RAM and RAID1 (1 + 1) for the Operating System and for StorNext and Block pool metadata

● 1 basic storage module with 8 TB usable storage capacity and RAID 6 (4 + 2)

● 0 to 9 storage expansion modules, with 8 TB usable capacity and RAID 6 (4 + 2) each

● 2 x 10 GbE ports and 3 x 1 GbE ports to the customer LAN plus one 1 GbE service port

● 2 x 4 Gb Fibre Channel ports (optionally, for OST path to tape only, not for ingestion)

The difference to the CS800 NAS Basic configuration is the increased capacity of the GbE connections to the customer LAN.

For more details, see Chapter "System Specifications".

ETERNUS CS800 Capacity Configurations

The ETERNUS CS800 is available in the following capacity configurations:

Table 1: ETERNUS CS800 Configurations

Configuration Capacity

CS800 minimum = 1 PRIMERGY RX300 S5 +1 ETERNUS DX80 basic 8 TB

CS800 minimum + 1 ETERNUS DX80 expansion module 16 TB

CS800 minimum + 2 ETERNUS DX80 expansion modules 24 TB








System Description Hard Drive Storage

U41840-J-Z125-1-76 29

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uide

\3_S

yste

m_

De

scri

ptio

n.fm

ETERNUS CS800 Internal Structure

Figure 3 shows the components of the CS800 system and their interconnection.

Figure 3: CS800 Logical Structure

Hard Drive Storage

The ETERNUS CS800 system is based upon high speed disk drives instead of tape drives. The drive storage area is presented as NAS shares (see "Network Attached Storage (NAS)" on page 30) or OST LSUs (Logical Storage Units).

4 x

1G

bE

thern

et

2 x

1 G

bE

thern

et

2 x

4G

bF

C (

PT

T o

pti

on

al)

.

300 GB

SAS

10k

300 GB

SAS

10kempty 100 M

b E

th. iR

MC

(em

pty

)

4 x

1G

b / 2

x 1

0G

b E

th.

2 x

4G

bF

C Q

LE

2462

2 x

4G

bF

C Q

LE

2462

LS

I 1078 –

SA

S 3

G

DX80 Base

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

300 GBSAS10k

300 GBSAS10k

300 GBSAS10k

300 GBSAS10k

300 GBSAS10k

6 123457

CPU E5540

2.53 GHz

QC

CPU E5540

2.53 GHz

QC

6 x 4 GB, DDR3, 1333

6 x 4 GB, DDR3, 1333

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

1 TB

SAS

7.2k

300 GBSAS10k

300 GBSAS10k

300 GBSAS10k

300 GBSAS10k

MNT

Service Port

2 x 8 Gb FC

Customer

LAN

Customer

LAN

...

OUT

IN

..

OUT

IN

..

OUT

.

MNT 2 x 8 Gb FC

...

OUT

DX80 Exp.

CS

800 m

inim

um

=1 P

RIM

ER

GY

RX

300 S

5 +

1 E

TE

RN

US

DX

80 B

ase

CS

800 m

inim

um

+1 E

TE

RN

US

DX

80

expansio

n m

odu

le

RX300-S5

Hard Drive Storage System Description

30 U41840-J-Z125-1-76

By making use of high speed drives, the ETERNUS CS800 greatly reduces the time required for backup/restore functions and improves confidence in completing the backup in the time allowed.

ETERNUS CS800 uses large capacity, highly cost effective Nearline SAS disks (Serial Attached SCSI). In the server component disks of size 2.5’’ with a capacity of 300 GB each and a speed of 7,200 rpm are implemented. In the storage and expansion components disks of size 3.5’’ with a capacity of 1 TB each and a speed of 7,200 rpm are implemented.

Network Attached Storage (NAS)

The ETERNUS CS800 system has the ability to serve as a NAS backup system (see Figure 4) where the following protocols are supported:

● "CIFS Protocol"

● "NFS Protocol"

Figure 4: NAS Backup using CIFS and NFS

I In the ETERNUS CS800, NAS shares are optimized for backup rather than file sharing.

CIFS Protocol

The CIFS (Common Internet File System) protocol defines a standard for remote file access from many computers at a time. This protocol allows users with different platforms to share files without installing additional software. This protocol is used with Windows networks.

Active Directory Support

The ETERNUS CS800 supports ADS (Active Directory Services) as well as ACLs (Access Control Lists).

System Description Supported RAID Configurations

U41840-J-Z125-1-76 31

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uide

\3_S

yste

m_

De

scri

ptio

n.fm

This provides the following benefits:

● Compatibility with CIFS domains - NAS shares are able to join CIFS domains and use domain authentication.

● Precise control of file system permissions - Administrators can specify which users and groups can perform what actions.

● Robust administrative support - Administrators have the same implicit permissions as they do in Windows operating systems.

I When you create a CIFS share, the initial permissions are the same as the default permissions for a Windows 2003 share with the addition of an ACE (Access Control Entry) that permits full access to the share for all authenticated users. Administrators can choose to remove this full access ACE, set up custom permissions, or leave the ACL (Access Control List) as is if the server is set up in a fully trusted environment.

NFS Protocol

The NFS (Network File System) protocol was originally designed by Sun™ Microsystems and allows all network users to access shared files stored on computers of different types. NFS provides access to shared files through an interface called the Virtual File System (VFS) that runs on top of TCP/IP. Users can manipulate shared files as if they were stored locally on the user's own hard disk. With NFS, computers connected to a network operate as clients while accessing remote files, and as servers while providing remote users access to local shared files. This protocol is used with UNIX and Linux networks. It can also be used with Windows networks.

Supported RAID Configurations

RAID is short for Redundant Array of Independent (or Inexpensive) Disks, which is a category of storage that employs two or more drives in combination for fault tolerance and performance. There are a number of RAID levels in use today such as 0, 1, 3, 5, 6 and 10.

The ETERNUS CS800 uses the following RAID levels:

● "RAID 1 Configuration"

● "RAID 6 Configuration"

Supported RAID Configurations System Description

32 U41840-J-Z125-1-76

RAID 1 Configuration

RAID 1 provides redundancy and fault tolerance by mirroring disks. Each disk in the RAID set contains a copy of the same data. For example, in a RAID set with two disks, if one disk fails, all of the data still exists on the other disk.

The ETERNUS CS800 uses RAID 1 for internal data (system, block pool, file system meta data etc.).

RAID 6 Configuration

RAID 6 uses block-level striping with two parity blocks distributed across all member disks. Dual parity provided by a RAID 6 configuration ensures that your data retains full integrity even in the event of two hard drive failures. Since single parity RAID levels are vulnerable to data loss until the failed drive is rebuilt: the larger the hard drive, the longer the rebuild will take and the longer the system is vulnerable to possible data loss.

The ETERNUS CS800 uses RAID 6 volumes for data storage, i.e. in the DX80 storage modules.

U41840-J-Z125-1-76 33

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\4_

Ba

sic_

Ope

ratio

ns.

fm

Hardware Description and Basic OperationsMost CS800 system operations are performed using the remote management pages (see Chapter "Remote Management"). This chapter describes the hardware features and basic operation of the CS800 hardware, including:

● "CS800 Server"

● "CS800 Basic Storage Module"

● "CS800 Storage Expansion Module"

● "Hard Drive Carrier Indicators"

● "Turning On and Shutting Down the System"

For information about installation and cabling, see the descriptions and instructions in the „Getting Started“ manual.

CS800 Server

The CS800 server is a PRIMERGY RX300 S5 that provides control for the CS800 software (Operating System and software applications).

All CS800 systems have one server.

Front View – Features and Indicators

Figure 5 shows the front side of the CS800 server component containing 11 2.5-inch SAS hard disk drives.

Figure 5: CS800 Server Front View

System ID Card

CS800 Server Hardware Description and Basic Operations

34 U41840-J-Z125-1-76

Figure 6 shows the indicators, buttons and connectors on the right side of the front panel of the server. Table 2 describes each item. For information about the HDD indicators see "Hard Drive Carrier Indicators".

Figure 6: Front Panel Indicators, Buttons and Connectors

Item Indicator, Button, Port Description

1 3 x USB ports For connection with external devices

2 Monitor port (optional) For connection with a monitor

3 RST (Reset) button Pressing the Reset button reboots the system.

V CAUTION!Risk of loss of data!

4 NMI button V CAUTION!Do not press! Risk of loss of data! The NMI button may only be used by service.

1 2

34

59 68 710

Hardware Description and Basic Operations CS800 Server

U41840-J-Z125-1-76 35

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\4_

Ba

sic_

Ope

ratio

ns.

fm

Table 2: Front Panel Indicators, Buttons and Connectors

5 Power-on indicator(green/orange)/ON/OFF button

Power-on indicator lights up green when the server is switched on.

It lights up orange when the server is switched off, but mains voltage is present (standby mode).

When the system is switched off, it can be switched on again by pressing the ON/OFF button. When the system is operating, pressing the ON/OFF button will switch off the system.

I The ON/OFF button does not disconnect the server from the mains voltage. To disconnect from the mains completely, remove the power plug(s).

6 Hard disk activity indicator

(green)

Lights up green when an internal drive (HDD or backup drive) is being accessed.

7 Global Error indicator

(orange)

Lights up orange if a prefailure event has been detected that requires (precautionary) service intervention. Flashes orange if an error was detected that requires service intervention.Does not light up if there is no critical event.If the event is still acute after a power failure, the indicator is activated after the restart.The indicator also lights up in standby mode.

8 CSS indicator(yellow)

Lights up yellow if a prefailure event was detected for a CSS component that you can fix yourself (for reasons of precaution) with the CSS concept.Flashes yellow if an error was detected that you can fix yourself with the CSS concept.Does not light up when the system is OK.If the event is still acute after a power failure, the indicator is activated after the restart.The indicator also lights up in standby mode.

9 ID indicator / ID button

(blue)

The ID indicator lights up blue on the front and on the rear of the server when the ID button is pressed. Both ID indicators are synchronized.

10 DVD drive activity indicator

(green)

DVD drive activity indicator: Lights up green when the storage medium is being accessed.

Item Indicator, Button, Port Description


36 U41840-J-Z125-1-76

Rear View – PCI Slots and Panel Connectors

Figure 7 shows the rear panel of the CS800 server component (for a NAS basic configu-ration).

Figure 7: Rear Panel of the CS800 Server

Figure 8 shows the connectors and indicators located on the left side of the rear panel. Table 3 describes each item.

Figure 8: Connectors on the Rear Panel of the CS800 Server

1 2 3 5 6 74

8 89 9


U41840-J-Z125-1-76 37

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\4_

Ba

sic_

Ope

ratio

ns.

fm

Table 3: Rear Panel Connectors and indicators of the CS800 Server

The following table describes the indicators of the three LAN ports.

Figure 9: LAN Port LEDs

Item Description

1 Serial port COM 2 (turquoise)

2 Serial port COM 1 (turquoise)

3 Monitor port - VGA (blue)

4 USB ports

5 Port LAN service (10/100 Mbit/s) for iRMC service access

6 Port LAN 2 (100/1000 Mbit/s) for management connection to the basic storage module

7 Port LAN 1 (100/1000 Mbit/s) for management connection to the basic storage module

8 Power supply indicator

● Flashes green when the server is switched off, but mains voltage is present (standby mode).

● Lights up green when the server is switched on and functioning properly.

● Lights up orange if the power supply unit has failed.

9 Power supply connector

Activity indicator Transfer rate indicator


38 U41840-J-Z125-1-76

Table 4: LAN Port Indicators

Figure 10 and Figure 11 show the numbering of the PCI slots on the right side of the rear panel and the indicators for the basic and the performance configuration (four 1 Gb / two 10 Gb Ethernet ports on slot 5) and with PTT facility which is optional.

Figure 10: Numbering of PCI Slots and Indicators (CS800 Basic)

Item Left Indicator Right Indicator

5 LAN activity indicator

● Lights up green if a LAN connection exists.

● Does not light up if no LAN connection exists.

● Flashes green when a LAN transfer is in progress.

LAN transfer rate indicator

● Lights up green for a LAN transfer rate of 100 Mbit/s.

● Does not light up for a LAN transfer rate of 10 Mbit/s.

6,

7

LAN activity indicator




LAN transfer rate indicator

● Lights yellow for a LAN transfer rate of 1 Gbit/s.

● Lights up green for a LAN transfer rate of 100 Mbit/s.

● Does not light up for a LAN transfer rate of 10 Mbit/s.

1234567

a b c fea b c

Slot Numbers:

fe


U41840-J-Z125-1-76 39

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\4_

Ba

sic_

Ope

ratio

ns.

fm

Figure 11: Numbering of PCI Slots and Indicators (CS800 Performance)

Table 5 shows the usage of the PCI slots. Table 6 describes the indicators.

Table 5: Usage of PCI Slots

Slot number

Usage

1 LSI 1078 – SAS 3G RAID Controller

2 4 x 1 Gb Ethernet (3 ports for connection to the customer LAN, 1 service port)

3 2 x 4 Gb Fibre Channel (optionally) for PTT

4 Empty

5 4 x 1 Gb (NAS Basic) / 2 x 10 Gb Ethernet (NAS Performance) for connection to the customer LAN

6 2 x 4 Gb Fibre Channel QLE2462 for connection to the basic storage module

7 2 x 4 Gb Fibre Channel QLE2462 for connection to the basic storage module

1234567

a b c d fea b c

Slot Numbers:

CS800 Basic Storage Module Hardware Description and Basic Operations

40 U41840-J-Z125-1-76

Table 6: Indicators on the PCI Cards

CS800 Basic Storage Module

A CS800 system contains one DX80 basic storage module providing 8 TB effective capacity for backup data storage.

The DX80 basic storage module contains 12 (3 x 4) 3.5-inch SAS hard disk drives in the front and two controller modules (connecting to the host/server) in the rear. Each controller module includes a power supply (with fans) and an SCU (System Capacitor Unit) used as backup power source in case of power outage.

Item Indicator Description

a LED 1

(orange)

Link/Activity indicator

● Lights up orange if a 4 Gb/s link exists.

● Flashes in case of input/output activity with 4 Gb/s

b LED 2

(green)




c LED 3

(amber)




d LED

(green)





e LED 1

(orange)

Activity indicator

● Blinks when network data is being sent or received.

f LED 2

(green)

Link indicator




Hardware Description and Basic Operations CS800 Basic Storage Module

U41840-J-Z125-1-76 41

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\4_

Ba

sic_

Ope

ratio

ns.

fm

Front View – Panel Features and Indicators

Figure 12 and Figure 13 show the front side of the DX80 basic storage component with and without cover. The DX80 contains twelve (3 x 4) 3.5-inch SAS hard disk drives.

Figure 12: Front View of DX80 Storage Module with Cover

Figure 13: Front View of DX80 Storage Module without Cover

Figure 14 shows the indicators on the left side. For information about the HDD indicators see "Hard Drive Carrier Indicators".

Figure 14: Indicators and Switches on the Front Side of DX80 (with Cover and with Front Cover Removed)

12345

6

1

2

3


42 U41840-J-Z125-1-76

Table 7: DX80 Indicators and Buttons on the Left Side of the Front Panel (with Front Cover)

Table 8: DX80 Switches on the Left Side of the Front Panel (with Front Cover Removed)

Item Indicator, Button Description

1 POWER LED

(green)

Glows green when the power is turned on.

2 READY LED

(green)

Glows green when device is available for use.

3 FAULT LED

(orange)

Glows orange when an internal device part abnormality has been detected.

Blinks orange when a device part which needs preventive replacement has been detected.

4 IDENTIFY LED

(blue)

Not used with CS800.

5 CACHE LED

(green)

Glows green when there is data in the device cache.

Blinks when a power failure has occurred and the cache data is being saved to flash memory.

6 Power Switch Used to turn the device on and off.


1 AutoPWR Enables the AC Auto-Link Mode

This function automatically turns on the linked device once AC power is supplied if the switch is set to "ON".

This switch is set to "OFF" as the factory setting.

2 MODE SEL Enables the device power to be turned on via power linkage.

This switch is set to "ON" as the factory setting and should not be set to "OFF".

3 IP RST IP Reset.

V CAUTION!Do not use!

Clicking once would switch the IP addresses of the two controller modules of the storage unit.

Clicking twice in succession within a two second interval would revert the IP addresses to their factory settings.

Hardware Description and Basic Operations CS800 Basic Storage Module

U41840-J-Z125-1-76 43

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\4_

Ba

sic_

Ope

ratio

ns.

fm

Rear View – Connectors and Indicators

Figure 15 shows the rear of the DX80 basic storage component which has two identical controller modules.

Figure 15: Rear View of the DX80 Storage Component

Table 9: Indicator and Power Supply

Figure 16 shows details about the connectors and indicators. Table 10 describes each item.

Figure 16: Connectors and Indicators on the Rear Panel of the DX80 Basic Storage Component


1 Status LED

(green/orange)

Blinks green when AC power is supplied (power cord is connected) but DC power is turned off.

Glows green when AC power is supplied (power cord is connected) and DC power is turned on.

Glows orange to indicate a fault has been detected in a fan or power supply.

2 Power Supply Connector for power supply

2 21 1

21 3 6 8 8 11 124 5 7 5 7 9 9 106


44 U41840-J-Z125-1-76

Table 10: DX80 Indicators and Buttons on the Left Side of the Front Panel (with Front Cover)


1 SCU Status LED

(green)

Grows green when the SCU (System Capacitor Unit) is normal.

Blinks green when being charged (for about one minute after the device power is turned on).

2 ID (Identify) LED

(blue)


3 SAS (DE) Link LED

(green/orange)

Glows green when link has been established.

Blinks orange when preventive replacement is being performed.

4 SAS (OUT) port Connector for a miniSAS cable

Used to connect the basic DX80 module to a DX80 expansion module.

5 Act LED

(green)

Glows green when data is being sent and received.

6 RMT port (left)

MNT port (right)

LAN ports (1000Base-T / 100Base-TX / 10Base-T) for device management(MNT: Management, RMT: Remote Management)

RJ45 connectors for LAN cables

7 Link LED

(green)

Glows green when the related link has been established.

8 Host Linkup/Fault LED

(orange)

Glows orange when a fault has been detected in the Fibre Channel port.

9 Host FC port 0 (left), 1 (right)

Dual LC connectors for Fibre Channel cables connecting the DX80 with the RX300 S5.

10 PWC port Not used.

11 STS (Status; Unit Ready/Fault) LED

(green/orange)

Glows green during normal operation.

Glows orange during the post power on initialization phase.

Also glows orange to indicate a fault has been detected.

12 MST (Master) LED

(green)

Glows green when this unit acts as the master controller module.

Hardware Description and Basic Operations CS800 Storage Expansion Module

U41840-J-Z125-1-76 45

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\4_

Ba

sic_

Ope

ratio

ns.

fm

CS800 Storage Expansion Module

DX80 storage expansion modules are used in the CS800 system to provide additional capacity (backup data storage). Each expansion module contains 12 (3 x 4) 3.5-inch SAS hard disk drives in the front providing 8 TB of effective storage (in the same way as the basic DX80 storage module) and two power supplies (with fans) in the rear.

Front View

The front view of the DX80 storage expansion module is very similar to that of the DX80 basic storage module except for a different cover which also hides the Power On button on the left side, see Figure 17 and Figure 18.

Figure 17: Front View of the DX80 Storage Expansion Module with Cover

Figure 18: Indicators and Switches on the Front Side of DX80 (with Cover and with Front Cover Removed)

1

2

3

4 1

2

3

4

CS800 Storage Expansion Module Hardware Description and Basic Operations

46 U41840-J-Z125-1-76

Table 11: DX80 Indicators on the Left Side of the Front Panel (without Front Cover)

Table 12: DX80 Switches on the Left Side of the Front Panel (with Front Cover Removed)


1 POWER LED

(green)

Glows green when the power is turned on.

2 READY LED

(green)

Glows green when device is available for use.

3 FAULT LED

(orange)

Glows orange when an internal device part abnormality has been detected.

Blinks orange when a device part which needs preventive replacement has been detected.

4 IDENTIFY LED

(blue)



1 AutoPWR Enables the AC Auto-Link Mode (this function automatically turns on the linked device once AC power is supplied).

This switch is set to "OFF" as the factory setting.

2 MODE SEL Enables the device power to be turned on via power linkage.

This switch is set to "ON" as the factory setting and should not be set to "OFF".

3 IP RST IP Reset. Not used in DX80 expansion modules.

4 Power Switch Not used in the DX80 expansion modules.

Hardware Description and Basic Operations CS800 Storage Expansion Module

U41840-J-Z125-1-76 47

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\4_

Ba

sic_

Ope

ratio

ns.

fm

Rear Panel Features and Indicators

Figure 19 shows the rear panel of the DX80 storage expansion module.

Figure 19: Rear View of the DX80 Storage Expansion Module

Table 13: Indicator and Power Supply

Figure 20 shows details about the connectors and indicators. Table 14 describes each item.

Figure 20: Connectors and Indicators on the Rear of the DX80 Storage Component


1 Status LED

(green/orange)

Blinks green when AC power is supplied (power cord is connected) but DC power is turned off.

Glows green when AC power is supplied (power cord is connected) and DC power is turned on.

Glows orange to indicate a fault has been detected in a fan or power supply.

2 Power Supply Connector for power supply

1 12 2

1 2 3 4 5 6 7

Hard Drive Carrier Indicators Hardware Description and Basic Operations

48 U41840-J-Z125-1-76

Table 14: Indicators on the Rear of the DX80 Expansion Module

Hard Drive Carrier Indicators

3.5’’ hard drive carriers are used in the storage modules. The 3.5’’ hard drive carrier itself has no LED indicator; instead at the storage frame, there is one LED indicator for each hard drive carrier (see red arrows in Figure 22).

Figure 21: 3.5’’ Hard Drive Carrier


1 ID (Identify) LED

(blue)


2 – Not used with CS800.

3 SAS (DE) Linkup LED

(green/orange)



4 SAS (OUT) port Connector for a miniSAS cable to the following DX80 module (if existent)

5 SAS (DE) Linkup LED

(green/orange)




6 SAS (IN) port Connector for a miniSAS cable from the previous DX80 module

7 STS (Status; Unit Ready/Fault) LED

(green/orange)

Glows green during normal operation.

Glows orange during the post power on initialization phase.


Hardware Description and Basic Operations Hard Drive Carrier Indicators

U41840-J-Z125-1-76 49

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\4_

Ba

sic_

Ope

ratio

ns.

fm

Figure 22: LED Indicators for the 3.5’’ HDDs

Table 15 describes the behavior of the LED indicator.

Table 15: 3.5’’ Hard Drive Disk Indicator

2.5’’ hard drive carriers are used in the server module. Each 2.5’’ hard drive carrier has two LED indicators (see Figure 23) which are described in Table 16.

Figure 23: 2.5’’ Hard Drive Carrier

Colour Description

Green HDD BUSY

● Lights up: HDD in active phase

● Does not light: HDD inactive (drive inactive)

Amber HDD FAULT

● Does not light: no HDD error

● Lights up: HDD Faulty or Rebuild Stopped (drive defective/needs replacing, a rebuild process was stopped or the HDD module is not correctly inserted)

1 2

Turning On and Shutting Down the System Hardware Description and Basic Operations

50 U41840-J-Z125-1-76

Table 16: 2.5’’ Hard Drive Disk Indicators

I If a drive fails, you will be notified by an admin alert in the remote management pages (see "Admin Alerts" on page 169).

Turning On and Shutting Down the System

Turning on the System

To turn on the CS800, proceed as follows:

1. At the basic storage module, press the power ON/OFF button which is located at the front panel on the left side.

I If there are storage expansion modules, these shall not be powered on manually. Instead they are automatically turned on when the power of the basic storage module is turned on.

2. Wait until the READY LEDs (also on the front panel on the left side) of all storage modules glow green.


1 LED 1

(green)

HDD BUSY

● Lights up: HDD in active phase

● Does not light: HDD inactive (drive inactive)

2 LED 2

(amber)

HDD FAULT(in conjunction with a RAID controller)

● Does not light: no HDD error

● Lights up: HDD Faulty or Rebuild Stopped (drive defective/needs replacing, a rebuild process was stopped or the HDD module is not correctly inserted)

● Slow flashing: HDD Rebuild (the data is being restored after changing a drive)

● Fast flashing: HDD Identify

● Four fast blinks/pause: HDD Predicted Fault

● Two fast flashes/pause: HDD Hot Spare (Hot spare drive active. The corresponding drive has failed).

Hardware Description and Basic Operations Locating the System Serial Number

U41840-J-Z125-1-76 51

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\4_

Ba

sic_

Ope

ratio

ns.

fm

3. At the server module, press the power ON/OFF button which is located at the front panel on the right side. The server is switched on, performs a system test and boots the operating system.

4. Wait about 15 minutes before starting any further actions (such as configurations via software).

Shutting Down the System

To shut down the CS800, use the remote management pages (see "Node Management" on page 207). Shutting down the system can take up to 15 minutes. The server is switched off and goes into standby mode. The power-on indicator lights up orange.

I If the operating system does not switch the server off automatically, press the ON/OFF button for at least 4 seconds and/or send a corresponding control signal.

The DX80 storage modules are not switched off by shutting down the CS800 via the remote management pages. If you want to switch off the DX80 storage modules completely, wait until the server has shut down, then press the Power ON/OFF button of the basic DX80 storage module for several seconds until the READY LED does not glow any more. This can take about 10 seconds.

Locating the System Serial Number

You will need the system serial number at various times. For example, you need the system serial number if you want to contact Fujitsu Support.

You can locate the system serial number from the Home page of the remote management pages. It is located in the System Details section.

You can also locate the system serial number by looking at the system ID card on the front panel of the server (green, to be pulled) or at the small label on the server’s rear, left side. An example system serial number is YKJB004368.

Locating the System Serial Number Hardware Description and Basic Operations

52 U41840-J-Z125-1-76

U41840-J-Z125-1-76 53

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uid

e\5

_Con

cep

ts.fm

ConceptsThis chapter provides detailed explanations for several concepts which are:

● "Data Storage Presentation"

● "Data Deduplication Policy"

● "Data Replication"

● "Recovering Data"

● "Network Segmentation"

Data Storage Presentation

The ETERNUS CS800 can present itself to your remote host computers in two ways:

● "Network Attached Storage (NAS)"

● "Open Storage (OST)"

Network Attached Storage (NAS)

The ETERNUS CS800 can present itself to your remote host computers as Network Attached Storage (NAS). A NAS share can be configured on the CS800 so it can be used as a NAS appliance for backup purposes.

Figure 24: NAS Shares

Network

Data Deduplication Policy Concepts

54 U41840-J-Z125-1-76

Open Storage (OST)

For Symantec NetBackup users on remote host computers, the ETERNUS CS800 can present itself as storage servers including LSUs (Logical Storage Units). This represen-tation and the corresponding replication option is available for the ETERNUS CS800 through the Symantec Open Storage (OST) API.

Figure 25: LSU Shares

Data Deduplication Policy

The data deduplication policy is selected by default when a NAS share is created. Once the NAS share is created, the data deduplication policy cannot be changed. There are two policies for data deduplication to consider:

● "Enable Data Deduplication (Adaptive In-line Data Deduplication)"

● "Enable Backup Window (Deferred Processing Data Deduplication)"

Enable Data Deduplication (Adaptive In-line Data Deduplication)

When you select Enable Data Deduplication for the NAS share, data deduplication is running all of the time and cannot be disabled. Backup data is sent to the CS800 and deduplication is performed on data as it is ingested. Data deduplication begins when the backup begins.

I The data deduplication setting for OST storage servers is not configurable. It is always adaptive in-line data deduplication.

Network

Concepts Data Deduplication Policy

U41840-J-Z125-1-76 55

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uid

e\5

_Con

cep

ts.fm

Advantages - The advantage of selecting adaptive in-line data deduplication is that there is no need to reserve any extra disk space for the backup, minimizing disk requirements, and replication of new blocks takes place while the backup is in progress.

Disadvantages - Because the system resources are always performing data deduplication while ingest is going on, there are situations in which the backup window can be negatively affected.

Enable Backup Window (Deferred Processing Data Deduplication)

When you select Enable Backup Window for the NAS share, data deduplication is disabled for a specific time period which can boost ingest speeds and shorten the backup window. All of the backup data is sent to the CS800 immediately in its raw form without deduplication. After the backup window is closed and data deduplication is re-enabled, the data that was moved during the backup windows is now deduplicated on the CS800.

Advantages - When all the system resources are dedicated to ingest, and data dedupli-cation is deferred, ingest speeds can be boosted.

Disadvantages - The downside to any post processing approach is that some disk space must be reserved to hold the backup, and the replication of unique blocks will be delayed until data deduplication is begun.

Since the CS800 allows users to select either mode on a share-by-share basis, it allows them to match the right data deduplication approach to specific jobs. For most user share and e-mail backup, for example, the adaptive approach makes the most sense, but when backing up a large, active database where the primary concern is the shortest possible backup window, the deferred approach makes more sense.

Data Replication Concepts

56 U41840-J-Z125-1-76

Data Replication

Data replication is the process of creating and managing duplicate versions of your data. The data is copied to a (remote) target CS800 system.

Figure 26: Replication Facilities (Example)

There are two replication possibilities:

● "NAS Data Replication"

● "OST Data Replication"

For data replication to operate:

● Only NAS shares or OST storage servers with data deduplication enabled can be repli-cated to another CS800 system (NAS to NAS, or OST to OST).

● Multiple source CS800 systems can replicate to a single target; however, a source CS800 system cannot replicate to multiple targets.

NAS Data Replication

The replication process not only copies the data but also allows you to schedule the repli-cation process so it can run automatically. For optimization purposes, the underlying data is continuously updated and will become available when the replication is either run manually or via a scheduled replication. When replication is configured on the ETERNUS CS800, copies of data in a NAS share can be copied to a remote CS800 system (see "Data Replication" on page 180).

Satellite Office(source)

Corporate Headquarters(target)

Dataset

Copy on Source Copy on Target

quartersrtersrtersquaSateSate

Concepts Data Replication

U41840-J-Z125-1-76 57

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uid

e\5

_Con

cep

ts.fm

This concept consists of the following sections:

● "Data Replication Processes"

● "New CS800 Installations"

● "Directory/File Based Replication"

Data Replication Processes

Data replication consists of two processes:

● Continuous Replication: The process of replicating deduplicated, unique data. Once configured, when backup data is ingested into the system, it is automatically (and continuously) replicated from the source to the target system.

● Namespace Replication: The process of sending the metadata associated with data at the start of each replication. The metadata is what is used to retrieve the data if its ever needed for a restore operation. Namespace replication begins when a replication is started either manually or during a scheduled replication. It is NOT automatic or part of the Continuous Replication process.

V Restoring replicated data is dependant on the metadata stored in the namespace file. This file is updated after each replication that is completed successfully. You must schedule replication to occur regularly and often or manually run replication often enough to keep the namespace file up to date.

New CS800 Installations

For a new CS800 installation, or immediately after a new share has been created, be sure to replicate the namespace (via the on-demand Replicate Now function, see Step 7 on page 225) for each share as soon as it is created and before any data is written to it.

This action establishes the namespace file on the target. Establishing the namespace file before any data is written will expedite the first replication that occurs after the first backup.

Failure to replicate the empty namespace is not fatal, but the speed of the first replication after the first backup will be up to twice as fast if you did replicate the empty namespace. This could be especially important when backing up a significant amount of data.

Directory/File Based Replication

Directory/File Based Replication, when configured, automatically replicates file data without user intervention or a schedule. The replication is “triggered” by a CLI command for file data (NAS share). This greatly enhances replication performance since only the file or directory specifically mentioned in the command is replicated.

Recovering Data Concepts

58 U41840-J-Z125-1-76

After a Directory/File Based Replication, NAS share files are automatically Recovered on the target system. You may also initiate a synchronization from the Source system to the Target system on NAS shares that have been configured for Directory/File Based Replication. This will replace all files on the Target NAS share with the most up-to-date files on the Source system.

Directory/File Based Replication Process

The process for directory/file based replication is as follows:

1. Directory/File Based Replication is configured on both the Source and Target. Configuring the directory/file based replication consists of enabling Directory/File Based Replication on both the source and target systems and setting the Sync ID. The Sync ID is used to identify the corresponding target share that will receive the data repli-cated from this source share (see "Source Role NAS Directory/File Based Replication Configuration" on page 188 for more information).

2. Data is backed up to the NAS share.

3. A post backup script is executed that triggers the replication of specified files or direc-tories in the NAS share.

I For examples of post backup scripts, see "Directory/File Based Replication Post Backup Scripts" on page 195.

OST Data Replication

For Symantec NetBackup users with a specific version of the software (NetBackup 6.5.3 or later), data replication for OST storage servers is available for the ETERNUS CS800 through the Symantec OpenStorage (OST) API. In this case the data replication is initiated, managed, and controlled by the remote NetBackup media server. The replication deploys the CS800 deduplication capabilities and is thus called „optimized“. For more information, see "OST Optimized Replication" on page 137.

Recovering Data

I The information in this section applies to recoveries for NAS configurations. Data recovery for OST configurations are managed via Symantec NetBackup. Please refer to your NetBackup documentation.

Concepts Recovering Data

U41840-J-Z125-1-76 59

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uid

e\5

_Con

cep

ts.fm

When replication is enabled and configured, two copies of the data exist, the original on the source system and a copy on the target system. If the data on the source is destroyed or corrupted, the replicated copy on the target system can be accessed through the Recover process or through the Failback and Recover process (for more detailed information on data recovery, see "Recovering Replicated Data" on page 225).

This section is divided into the following sections:

● "Recovery Processes"

● "Recovery Requirements"

● "Recovery Features"

Recovery Processes

The differences between these two data recovery processes are explained in the following sections:

● "Recover Process"

● "Failback and Recover Process"

Recover Process

The Recover process is used when the source system where the original data stored is unavailable or the original data is corrupted. The Recover process takes the metadata on the target system and creates a copy of this data in a new NAS share. This new NAS share will now be accessible for use on the Target system.

Failback and Recover Process

The Failback and Recover process is used when the source system has been replaced or the original data on the source system has been corrupted or destroyed. This process takes the data from the target system and copies it back to the source system. This data once copied to the source system must be recovered before it can be accessible.

Recovery Requirements

The following items are required for recovering data:

● CIFS NAS shares can only be recovered to identical CIFS shares.

● NFS NAS shares can only be recovered to identical NFS shares.

Network Segmentation Concepts

60 U41840-J-Z125-1-76

Recovery Features

Up to 24 replicated versions of a NAS share can exist on the target system.

● The 24 versions represent the 24 most recent replications.

● You can selectively delete versions to keep some longer than the default 24 replications.

● You can failback and recover any one of those 24 versions.

Network Segmentation

Network segmentation provides the ability to split your network into subnetworks or segments. There are two main purposes for segmenting your network:

● Separate Physical Interfaces: If your network is physically partitioned with no connec-tivity between the partitions, the CS800 needs the ability to communicate with each partition individually.

● Combine or Separate Network Traffic: Network traffic is either separated according to specific network needs or combined on a single IP address for simplicity. The CS800 has the capability of separating data traffic, replication traffic, and management traffic. Each traffic type can have its own IP address or they can be combined on a single IP address.

The network segmentation options are described in Chapter "Segmentation and Bonding".

Network Segmentation Scenarios

The following scenarios provide common examples of network segmentation.

● "Un-Segmented Network"

● "Data and Replication Separate from Management"

● "Data and Management Separate from Replication"

● "Replication and Management Separate from Data"

Un-Segmented Network

This is the most common network configuration (and also the default setting for the CS800). In this example, the user has no need to separate network traffic types. All traffic will occur on a single IP address.

Concepts Network Segmentation

U41840-J-Z125-1-76 61

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku

\10

0050

1_U

serG

uid

e\5

_Con

cep

ts.fm

Segmentation and Bonding page selection:

● CS800 Basic: Select BOND ALL (not segmented)

● CS800 Performance: Select BOND ALL 1 GB (not segmented) or BOND ALL 10 GB (not segmented)

Data and Replication Separate from Management

In this example, the user has a dedicated low bandwidth wide area network (WAN) that is used to manage network resources. This network does not have the capacity for data and replication traffic. Replication is between two CS800 systems that are in the same location with a dedicated network connection.


● CS800 Basic: Select ETH7 (Management), BOND ALL-1 (Replication/Data)

● CS800 Performance: Select BOND ALL 1GB (Management), BOND ALL 10GB (Replication/Data)

Data and Management Separate from Replication

In this example, the user has a dedicated local high bandwidth network used for data ingest and resource management. The user also has high bandwidth WAN used for offsite data movement. Data and management traffic can share the local network and replication traffic between CS800 systems in two locations uses a dedicated WAN.


● CS800 Basic: Select ETH7 (Replication), BOND ALL-1 (Management/Data)

● CS800 Performance: Select BOND ALL 1GB (Replication), BOND ALL 10GB (Management/Data)

Replication and Management Separate from Data

In this example, the user has a dedicated local high bandwidth network used for data ingest. The user also has a dedicated low bandwidth wide area network (WAN) that is used for replication and to manage network resources.


● CS800 Basic: Select BOND ALL-1 (Data), ETH7 (Replication/Management)

● CS800 Performance: Select BOND ALL 10GB (Data), BOND ALL 1GB (Repli-cation/Management)

Network Segmentation Concepts

62 U41840-J-Z125-1-76

U41840-J-Z125-1-76 63

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mä

rz 2

010

Sta

nd

19:2

3.50

Pfa

d: P

:\allg

eme

in\C

S8

00\1

000

500

_FT

S-D

oku

\100

050

1_U

serG

uide

\6_R

emo

te_M

ana

gem

ent

.fm

Remote ManagementThe ETERNUS CS800 system utilizes a Web-based interface which allows you to configure and manage the system via Web pages from a remote workstation on the same network (a Command Line Interface is also available, see the „ETERNUS CS800 Command Line Interface (CLI) Guide“). This chapter gives you an overview about the CS800 Web interface and how to access it. The Web pages are described in the following chapters:

● Chapter "Configuration with the CS800 Web Pages" allows you to set up information about the CS800 system such as NAS shares, network configuration, date and time settings, and passwords.

● Chapter "Configurations for NetBackup and OST Replication" describes the configura-tions needed to perform OST optimized replication via NetBackup.

● Chapter "CS800 Status" allows you to view the status of the hardware components and system performance.

● Chapter "CS800 Alerts" allows you to view and close admin alerts and service tickets.

● Chapter "Data Services" allows you to view and configure the space reclamation and the replication services.

● Chapter "Utilities" allows you to upload software, download diagnostic files, perform network analysis and shutdown or restart the system.

CS800 Web Pages – Overview

This section lists the menu items, commands, and information available from the CS800 Web pages.

Home Menu

Home

Configuration Menu

NAS & OST

NAS

Summary

Add

Edit

Delete

OST

CS800 Web Pages – Overview Remote Management

64 U41840-J-Z125-1-76

Storage Servers

Summary

Add

Edit

Delete

LSU

Summary

Add

Edit

Delete

OST Client Plug-In

Windows Domain

Access Control

Summary

Add

Delete

Advanced Setting

PTT (if available)

Physical Device Discovery

Backup Application Specific

Summary

Add

Edit

Delete

Initiators & Ports

Network

General

IP

Segmentation and Bonding

Date & Time

Remote Management CS800 Web Pages – Overview

U41840-J-Z125-1-76 65

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mä

rz 2

010

Sta

nd

19:2

3.50

Pfa

d: P

:\allg

eme

in\C

S8

00\1

000

500

_FT

S-D

oku

\100

050

1_U

serG

uide

\6_R

emo

te_M

ana

gem

ent

.fm

Security

Passwords

SSL

Login Session

Email

Recipients

Summary

Add

Edit

Delete

Server

Test

Email Home

Schedule

On Demand

SNMP Destinations

Summary

Add

Edit

Delete

Community

Summary

Add

Edit

Delete

Test

Contacts

Company

Primary

Secondary

AISConnect

CS800 Web Pages – Overview Remote Management

66 U41840-J-Z125-1-76

Status Menu

Hardware

Summary

Details

Node 1

System Board

Network Adapters

Network Ports

Common

System

CPU

RAID

Ethernet

Data Deduplication

Ingest

Disk Usage

Alerts Menu

Alerts

Admin Alerts

Service Tickets

Data Services Menu

Space Management

General

Schedule

Replication

Source Role

General

NAS

Actions

Remote Management CS800 Web Pages – Overview

U41840-J-Z125-1-76 67

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mä

rz 2

010

Sta

nd

19:2

3.50

Pfa

d: P

:\allg

eme

in\C

S8

00\1

000

500

_FT

S-D

oku

\100

050

1_U

serG

uide

\6_R

emo

te_M

ana

gem

ent

.fm

Target Role

General

NAS

Replicated Shares

Recovery Jobs

Failback Jobs

Directory/File Based Targets

Actions

Reports

Utilities Menu

Software

Diagnostics

System

Storage Array

Healthchecks

General

Status

Schedule

Analyzer

Network

Performance

Settings

Disk

Node Management

Accessing CS800 Web Pages Remote Management

68 U41840-J-Z125-1-76

Accessing CS800 Web Pages

The Internet browser software is not supplied with the CS800 system; you must obtain and install it independently. Table 17 shows the Internet browsers supported by the CS800 system.

Table 17: Supported Internet Browsers

I For correct operation of the software, disable any pop-up blockers and enable JavaScript in your Web browser.

To access the CS800 web pages, proceed as follows:

1. On your (remote) computer, open the Internet browser software.

2. In the Address field, type http://IPaddress/ where IPaddress is the IP address for the system.

The default IP address is: 10.1.1.1. This IP address can be changed during installation using the Setup Wizard.

The Login page displays (see Figure 27):

Figure 27: Login Page

Operating System Internet Browser

Windows IE 6.x or later

Firefox 2.x or later

Linux Firefox 2.x or later

Solaris Firefox 2.x or later

Remote Management Accessing CS800 Web Pages

U41840-J-Z125-1-76 69

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mä

rz 2

010

Sta

nd

19:2

3.50

Pfa

d: P

:\allg

eme

in\C

S8

00\1

000

500

_FT

S-D

oku

\100

050

1_U

serG

uide

\6_R

emo

te_M

ana

gem

ent

.fm

3. Select the login type and enter the appropriate password.

I Change your passwords as soon as possible.

I For more information about allowed passwords and password setting, see "Security Configuration" on page 117.

4. Click Login.

The Home page displays (see Figure 28):

Figure 28: Home Page

Login Type Default Password Description

Monitor password The monitor user is allowed to view the CS800 system management pages, but cannot change them.

Administrator spcc The administrator user can both view and change the management pages.

Multiple administrators can log on to the system at the same time, so it is possible for the actions of one administrator to overwrite the actions of another.

NAS data services

Contents frame

Systemdetails

Data reductionstatus

System statusbuttons

Quick status

Using the CS800 Web Pages Remote Management

70 U41840-J-Z125-1-76

Using the CS800 Web Pages

The first page that displays after you login to the CS800 web pages is the system Home page (see Figure 28).

I Disk statistics are not maintained on a “moment-to-moment” basis and should be used for planning purposes only.

V When using the remote management pages, never double-click the Apply, OK, or any other button. Doing so could result in performing an action twice, for example, creating two NAS shares instead of one. Make sure to click buttons only once.

The Home page contains the following sections:

● "Contents Section"

● "Quick Status Section"

● "Data Reduced By Section"

● "System Details Section"

● "NAS Data Services Section"

● "System Status Information"

Table 18: Contents Section

Contents Section

The contents frame displays the CS800 main menu. Click a menu item to display the corresponding management pages.

Remote Management Using the CS800 Web Pages

U41840-J-Z125-1-76 71

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mä

rz 2

010

Sta

nd

19:2

3.50

Pfa

d: P

:\allg

eme

in\C

S8

00\1

000

500

_FT

S-D

oku

\100

050

1_U

serG

uide

\6_R

emo

te_M

ana

gem

ent

.fm

Table 19: Quick Status Section

Table 20: Data Reduced By Section

Quick Status Section

The quick status section displays the system status, hostname, IP address, and provides storage capacity infor-mation (see "Disk Usage" on page 73). The Status information describes the current state of the system. Clicking the Info button links you to the Hardware Status page.

Data Reduced By Section

The data reduced by section displays the current data reduction status. The percentage reduced indicates the total amount of data reduction through both compression and data deduplication.

Using the CS800 Web Pages Remote Management

72 U41840-J-Z125-1-76

Table 21: System Details Section

Table 22: NAS Data Services Section

System Details Section

The upper part of the System Details section displays general system infor-mation such as the software version, serial number, and model number.I Disk statistics are not maintained

on a “moment-to-moment” basis and should be used for planning purposes only.

The Data Reduction Statistics area displays the amount of data ingested before reduction and after reduction, as well as the reduction ratio.

The Cumulative Replication Statistics area displays the total data sent and received, as well as the average send and receive rates (see "Cumulative Replication Statistics" on page 74).

NAS Data Services Section

The NAS Data Services section displays NAS data deduplication and replication status. Clicking the Info button in the NAS Data Deduplication area displays the NAS Configuration page. Clicking the Info button in the NAS Replication area displays the NAS Replication page.

Remote Management Disk Usage

U41840-J-Z125-1-76 73

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mä

rz 2

010

Sta

nd

19:2

3.50

Pfa

d: P

:\allg

eme

in\C

S8

00\1

000

500

_FT

S-D

oku

\100

050

1_U

serG

uide

\6_R

emo

te_M

ana

gem

ent

.fm

Table 23: System Status Information

Disk Usage

The quick status section displays the following disk usage information:

● Capacity - Total raw storage minus space reserved for system use.

● Used - Total space occupied by all of the following:

● Deduplicated data

● Data waiting to be deduplicated

● Data not intended for deduplication

● Data eligible for reclamation

● System metadata

● Available - Capacity minus Used space.

I Note that the Used space includes data eligible for reclamation. Therefore, it may appear that your system is using more space than expected. Space is only reclaimed as necessary to allow for optimal performance in the event you need to restore your data.

System Status Information Buttons

The system status buttons display at the top of the Home page.

● Admin - The Admin button turns yellow when an administrator alert has occurred. The administrator alert description displays on the Alerts page.

● Ticket - The Ticket button turns yellow when open service tickets are present. The service ticket description displays on the Alerts page.

Data Reduction Statistics Remote Management

74 U41840-J-Z125-1-76

Data Reduction Statistics

The Data Reduction Statistics area displays the following information:

● Total Data Reduced - The original, native size of all existing data that has been processed by the data deduplication and compression engines.

● Total Reduction Ratio - The total reduction ratio of all existing data that has been processed by the data deduplication and compression engines (Total Data Reduced by Reduced Size).

● Reduced Size - The final, reduced size of all existing data that has been processed by the data deduplication and compression engines.

I Because these values are calculated as data is deduplicated and compressed, they will not be completely up-to-date until all data that is eligible for deduplication is processed by the data deduplication and compression engines.

Cumulative Replication Statistics

The Cumulative Replication Statistics area displays the following information:

● Total Data Sent - The original, native size of the data transferred during replication or failback. This value does not indicate the amount of bytes that actually crossed the network during replication or failback.

● Total Bytes Sent, Total Bytes Received - The number of bytes actually transferred over the network during replication or failback. These values are usually much less than the native size due to the benefits of data deduplication.

● Average Send Rate, Average Receive Rate - The average number of bytes actually transferred over the network during replication or failback. These values are calculated as the total number of bytes sent or received (in MB/s) divided by the amount of time required to complete replication or failback.

I The Cumulative Replication Statistics can be cleared on the Source Role Actions and the Target Role Actions pages (see "Source Role Actions" on page 189 and "Target Role Actions Page" on page 196).

U41840-J-Z125-1-76 75

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Configuration with the CS800 Web PagesUse the Configuration pages to set or configure the following areas of the CS800:

● "NAS & OST Configuration"

● "PTT Configuration"

● "Network Configuration"

● "Date and Time Configuration"

● "Security Configuration"

● "Email Configuration"

● "SNMP Configuration"

● "Contacts Configuration"

● "AIS Connect"

NAS & OST Configuration

The CS800 has the ability to serve as a NAS appliance or OST storage server for backup purposes. Use the NAS & OST page to configure NAS shares as well as OST storage servers.

The NAS & OST page contains the following tabs:

● "NAS Configuration"

● "OST Configuration"

● "Windows Domain Configuration"

● "Access Control Configuration"

● "Advanced Setting"

To access the NAS & OST page, from the Configuration menu, click the NAS & OST tab.

NAS Configuration

The CS800 has the ability to serve as a NAS appliance for backup purposes. Use the NAS page to add, edit, or delete NAS shares.

NAS & OST Configuration Configuration with the CS800 Web Pages

76 U41840-J-Z125-1-76

I If this is a Windows NAS share, you must configure the Windows domain (see "Windows Domain Configuration" on page 89) prior to creating your NAS share.

V Filenames on NAS shares are limited to a length of 256 bytes. If a filename uses Japanese characters, the filename can be no longer than 85 characters. This is because each Japanese character is represented by 3 bytes.

To access the NAS page:

1. From the NAS & OST page, click the NAS tab.

I Ensure that the CS800 is online before continuing with the NAS configuration.

The NAS page contains the following tabs:

● "Summary Page"

● "Add NAS Share"

● "Edit NAS Share"

● "Delete NAS Share"

Summary Page

To access the NAS share Summary page:

1. On the NAS page, click the Summary tab.

The NAS Shares Summary page displays (see Figure 29).

I You can click the Share Name, Protocol, Export Path, Data deduplication, Backup Window, Permissions, Access, and Description column headings to sort the rows in the media by the data in the respective column. Click the column heading again to invert the sorting sequence from ascending order to descending order.

Configuration with the CS800 Web Pages NAS & OST Configuration

U41840-J-Z125-1-76 77

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Figure 29: NAS Shares Summary Page

The Summary page lists the information described in Table 24.

Table 24: NAS Shares Summary Information

Column Description

Share Name This column lists the NAS share name.

Protocol This column lists the NAS protocol (CIFS or NFS) in use on the NAS share.

Export Path This column lists the location of the export path for this NAS share.

Data Dedupli-cation

This column displays the data deduplication setting (Enabled or Disabled) for the NAS share.

Backup Window This column displays (if enabled) the time window where data deduplication will not be used.

Permissions This column displays the permission (Read & Write or Read Only) for the NAS share.

Access This column lists the access type (All Users or specific users) for this NAS share.

Description This column lists the description for the NAS share (if available).


78 U41840-J-Z125-1-76

Add NAS Share

To add a NAS share:

1. On the NAS page, click the Add tab.

The Add NAS Share page displays (see Figure 30).

Figure 30: Add NAS Share Page

2. Edit the NAS share information as desired (see Table 25 for a description of the fields).

3. Click Apply.

I When you create a CIFS share, the initial permissions are the same as the default permissions for a Windows 2003 share with the addition of an ACE (Access Control Entry) that permits full access to the share for all authenticated users. Administrators can choose to remove this full access ACE, set up custom permissions, or leave the ACL (Access Control List) as is if the server is set up in a fully trusted environment.


U41840-J-Z125-1-76 79

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Table 25: Add NAS Share Fields

Edit NAS Share

To edit a NAS share:

1. On the NAS page, click the Edit tab.

The Edit NAS Share page displays (see Figure 31).

Field Description

Name Enter a name for the NAS share.

Description (optional)

Enter a desciption for this NAS share (optional).

Enforce read-only access to this share

Select this option to make this NAS share read only. If selected, the share is locked and you will not be able to write to it. Clear the check box to unlock the share.

Hide this share from network browsing

Select this option to hide this network share from network browsing (CIFS shares only).

Export using CIFS

Select this option for use on a Windows network.

Export using NFS Select this option for use on a Linux network.

Enable Data Deduplication

Enable data deduplication to optimize disk usage. Data deduplication can only be enabled or disabled while a share is being created.I Data deduplication is enabled by default.

Enable Backup Window

Select Enable Backup Window to enable data deduplication for a particular time period. By default, Enable Backup Window is not enabled.

● Using the drop down boxes, select the start time for the backup window.

● Using the drop down boxes, select the end time for the backup window.


80 U41840-J-Z125-1-76

Figure 31: Edit NAS Share Page

2. Select the NAS share to edit in the Name drop down box.

3. Edit the NAS share information as desired (see Table 25 for a description of the fields).

I If you are editing a share, only the Description, Enforce read-only access to this share, Hide this share from network browsing (CIFS shares only), Enable Backup Window, and Allow all hosts to access this share options can be edited.

4. Click Apply.

I If you modify a NAS share that uses the CIFS protocol, a message displays stating that the CIFS service must be restarted for the changes to take effect. Click Yes to restart the CIFS service. Restarting the CIFS service will close all active connections to the NAS share. Most Windows workstations will automatically reconnect, but some applications may be affected.


U41840-J-Z125-1-76 81

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Table 26: Edit NAS Share Fields

Delete NAS Share

To delete a NAS share:

1. On the NAS page, click the Delete tab.

The Delete NAS Shares page displays.

2. Select the NAS share to delete.

3. Click Apply to delete the selected NAS share.

The NAS share is deleted.

OST Configuration

Use the OST (Open Storage Technology) page to configure storage servers and also LSUs (Logical Storage Units).

To access the OST page:

● From the NAS & OST page, click the OST tab.

I Ensure that the node is online before continuing with the OST configuration

Field Description


Enter a description for this NAS share (optional).

Enforce read-only access to this share

Select this option to make this NAS share read only. If selected, the share is locked and you will not be able to write to it. Clear the check box to unlock the share.

Hide this share from network browsing

Select this option to hide this network share from network browsing. (CIFS shares only.)

Enable Backup Window

Select Enable Backup Window to enable data deduplication for a particular time period. By default, Enable Backup Window is not enabled.

Allow all hosts to access this share

If this is selected, all users (hosts) can access this share. If not selected, you can click the Add button to specify a user to access the share. Once a user is added, permissions for that user cannot be changed. In order to change the permissions, you must delete the user from the list and add it as a new user with updated permissions.


82 U41840-J-Z125-1-76

The OST page contains the following tabs:

● "Storage Servers"

● "LSU"

● "OST Client Plug-In"

Storage Servers

Use the Storage Servers page to add, edit, or delete OST storage servers.

I The connections of a storage server that are used equals the data streams plus one for each LSU polling. A backup job may generate more than one data stream if the data can be read in parallel. For example, a policy that is backing up A, B, C, and D drives of a Windows system can generate four data streams in parallel.

To access the Storage Servers page:

1. From the OST page, click the Storage Servers tab.

The Storage Servers Summary page displays (see Figure 32).

Figure 32: Storage Servers Summary Page


U41840-J-Z125-1-76 83

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

The Storage Servers Summary page lists the configured storage servers on the system as well as the maximum number of OST storage servers allowed (100), number of storage servers created, and number of Logical Storage Units (LSUs) created.

Adding a Storage Server

To add a storage server:

I If the storage server is used by a Windows Media Server, you must configure the Windows domain (see "Windows Domain Configuration" on page 89) prior to creating your storage server.

1. From the Storage Servers page, click the Add tab.

The Add Storage Server page displays (see Figure 33).

Figure 33: Add Storage Server Page

2. Enter the Storage Server information as desired (see Table 27 for a description of the fields).


84 U41840-J-Z125-1-76

Table 27: Storage Server Fields

3. Click Apply.

Editing a Storage Server

To edit a storage server:

1. From the Storage Servers page, click the storage server name link on the Summary page, or click the Edit tab.

2. Edit the Storage Server information as desired (see Table 27 for a description of the fields).

Field Description

Name Enter a name for the storage server.I Storage server names must be unique and not used again

on other CS800 systems.If NetBackup is using the OST interface, the storage server name must not be the name of the Master Server/Media Server.


Enter a description for the storage server (optional).

Max Connections Enter the maximum number of connections to the storage server. This is an integer field.

It is recommended to set this value to 100 so that media servers never run out of storage server connections.

Enforce read-only access to this Storage Server

Select this option to make this storage server read only. If selected, the storage server is locked and you will not be able to write to it. Clear the check box to unlock the storage server.

Export using CIFS Select CIFS protocol for use on a Windows network.

Export using NFS Select NFS protocol for use of a Unix/Linux network.

Allow all users to access this share

If this is selected, all users (hosts) can access this share. If not selected, you can click the Add button to specify a user to access the storage server. Once a user is added, permissions for that user cannot be changed. In order to change the permissions, you must delete the user from the list and add it as a new user with updated permissions.


U41840-J-Z125-1-76 85

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

I Only the Description, Max Connections, Enforce read-only access to this Storage Server, and Allow all hosts to access this share options can be edited. The maximum connections cannot be edited if the storage server has non zero current connections (see the Summary page for the current connections).

3. Click Apply.

I If you modify a storage server that uses the CIFS protocol, a message displays stating that the CIFS service must be restarted for the changes to take effect. Click Yes to restart the CIFS service. Restarting the CIFS service will close all active connections to the storage server. Most Windows workstations will automatically reconnect, but some applications may be affected.

Deleting a Storage Server

I If you have deleted the storage server from NetBackup, you must wait several minutes before deleting the storage server from the CS800.

To delete a storage server:

1. From the Storage Servers page, click the Delete tab.

The Delete Storage Servers page displays (see Figure 34).

Figure 34: Delete Storage Servers Page


86 U41840-J-Z125-1-76

2. Select the storage server to delete.

I Storage servers containing active connections (non zero current connections) and storage servers containing LSUs cannot be deleted.

3. Click Apply to delete the selected storage server.

The storage server is deleted.

LSU

Use the LSU (Logical Storage Units) page to add, edit, or delete LSUs.

To access the LSU page:

1. From the OST page, click the LSU tab.

The LSU Summary page displays (see Figure 35).

Figure 35: LSU Summary Page

Adding or Editing an LSU

After a storage server has been created, LSUs can be created (added) within this storage server. To add an LSU:


U41840-J-Z125-1-76 87

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

1. From the LSU page, click the Add tab.

The Create LSU page displays (see Figure 36).

I To edit an LSU, click the LSU name link on the Summary page, or click the Edit tab.

Figure 36: Create LSU Page

Figure 37: Edit LSU Page


88 U41840-J-Z125-1-76

2. Edit the LSU information as desired (see Table 28 for a description of the fields).

I If you are editing an LSU, only the Description and Physical Capacity options can be edited. Physical Capacity cannot be edited when the storage server in which this LSU is created has active connections.

3. Click Apply.

Table 28: LSU Fields

Deleting an LSU

I If you have deleted a logical storage unit from NetBackup, you must wait several minutes before deleting the LSU from the CS800.

To delete an LSU:

1. From the LSU page, click the Delete tab.

The Delete LSU page displays.

2. Select the Storage Server.

3. Select the LSUs in the selected storage server to delete.

4. Click Apply.

The LSU is deleted.

I LSUs in the storage server with active connections (non-zero current connections) cannot be deleted.

OST Client Plug-In

The OST Client Plug-In allows the NetBackup software running on your backup host to communicate with the CS800 OST service. The OST Client Plug-In will be provided on a data medium which will be shipped together with the CS800. Install and configure the client to allow your NetBackup software to use the OST feature.

Field Description

Storage Server Select the Storage Server in which the LSU has to be created.

LSU Name Enter a name for the LSU.

Description (optional) Enter a description for this LSU.

Physical Capacity Enter a physical capacity for the LSU. The maximum capacity is 8192 GB.


U41840-J-Z125-1-76 89

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Figure 38: OST Client Plug-In Page

For installing the OST client Plug-In and further configurations, proceed as described in Chapter "Installing the OST Plug-In".

Windows Domain Configuration

The CS800 uses a Samba server to provide the NAS shares. Samba is a free, open source implementation of networking protocols to share files and printers between Unix/Linux and Windows computers. See www.samba.org for more information. Use the Windows Domain page to join the Samba server running at the CS800 to a Windows workgroup or a Windows domain.

I Ensure that your system has the date and time set correctly and is in sync with your domain controller.

To configure Windows domain information:

1. From the NAS & OST page, click the Windows Domain tab.

The Windows Domain page displays (see Figure 39).


90 U41840-J-Z125-1-76

Figure 39: Windows Domain Page

2. Edit the Windows Domain information to join a workgroup or an Active Directory domain.

I You must disjoin a domain before you can delete a domain.

For detailed information, see the following sections:

● "Joining a Windows Workgroup"

● "Joining a Windows Domain"

● "Joining a Domain Using a Domain User Credential"

● "Troubleshooting ADS (Active Directory Services) Join Issues"

Joining a Windows Workgroup

1. Edit the page information as follows:

● Domain Type - Select Workgroup.

● Domain/Workgroup Name - Enter the Workgroup name. This can be the name of an existing workgroup or a new workgroup (for example, Workgroup or Sales).

2. Click Apply.


U41840-J-Z125-1-76 91

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

I When a Samba server is joined to a workgroup, the share security is managed directly from the remote management pages. For a CIFS share, security is provided through the read only or read/write access to the share. By default, when a CIFS share is created the default security setting is to allow access for all users. Further access restrictions on individual users can be managed from the following page: NAS > Edit.

Joining a Windows Domain

It is necessary to synchronize the server clock and the ADS (Active Directory Services) server so that the time difference is less than 300 seconds. This can be done by having both servers use the same NTP server. Once the clocks have been verified:

1. Edit the Windows Domain information as desired (see below):

● Domain Type - Select Active Directory.

● Domain/Workgroup Name - Enter the domain name.

● Primary Domain Controller - Enter the fully qualified name of the Primary Domain Controller (PDC). Choose one of these options:

● Use DNS discovery - Let the PDC be discovered automatically.

● Specify Address - Enter the fully qualified name, or the IP address, of the PDC.

● Organization Unit (optional) - Enter the name of the organizational unit in the domain. This is the organization of which the CS800 will become a member.

● Administrator Name - Enter Administrator or any user who has the right to join a domain. By default any user belonging to the Administrators group or the Domain Admins group has the right to join the domain. In addition, any domain user can join the domain if he is specifically delegated this right by a member of the Admin-istrators group. See "Joining a Domain Using a Domain User Credential" for an example.

● Administrator Password - Enter the Administrator Password.

2. Click Apply.

I When the system is joined to the Active Directory domain all the share security is managed by the MMC (Microsoft Management Console) that is running on the domain controller. By default, when a CIFS share is created the default security setting is to allow access for all users. Any access restriction on individual users will have to be managed from the MMC.


92 U41840-J-Z125-1-76

Joining a Domain Using a Domain User Credential

Many large companies do not want to use the Administrator account to join the ADS (Active Directory Services) domain. They prefer to delegate a normal domain user account with special rights to join the domain. The purpose of this section is to provide an example of delegating a normal domain user account with special rights to join the domain.

To facilitate this example, the following information is assumed:

● The ADS is running on a Windows 2003 Server system.

● ADS domain name: abc.def.xyz.com

● user1 is a normal domain user that has basically no administrative privileges.

● The server host name is cs800-abc.

● DNS domain name: abc.def.xyz.com

● DNS IP address: 10.20.30.40

1. Steps to complete on the Windows 2003 MMC:

a) Delegate the right to join the domain:

● Select the domain name abc.def.xyz.com.

● Right-click and choose: Delegate Control | Next | Add

● Type the username: user1

● OK | Next

b) Delegate the following common tasks:

● Join a computer to the domain.

● Next | Finish

c) Delegate the right to read/write dNSHostname and servicePrincipalName:

● Select the organizational unit Computers or the appropriate name. This is the folder that contains individual computers that belong to the domain.

● Right-click and choose: Delegate control | Next | Add

● Type the username: user1

● OK | Next | Create a custom task to delegate

● Next | Only the following objects in the folder:

Check the box: Computer objects

Check the box: Create selected objects in this folder


U41840-J-Z125-1-76 93

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

● Next | Check box: Property-specific

● Scroll down the list and check the boxes for:Read dNSHostName Write dNSHostName Read servicePrincipalName Write servicePrincipalName

● Next | Finish

2. Steps to complete on the GUI:

a) Network page:

Note on these fields:

● Hostname: cs800-abc

● Domain name: Enter abc.def.xyz.com.

This is the DNS domain name. The DNS domain name is usually, but not neces-sarily, identical with the ADS domain name.

● Domain name server IP address: Enter 10.20.30.40.

This is the IP address of the domain name server that can resolve the domain name abc.def.xyz.com that you are trying to join to.

b) Windows Domain page:

● Domain type: Active Directory

● Domain name: abc.def.xyz.com

I You must use a fully qualified domain name; character case is not important.

● Primary Domain Controller (PDC):

Preferred option if DNS is working: Use DNS discovery

If DNS is not working well or if you cannot ping abc.def.xyz.com, then use the IP address of the PDC explicitly.

If you cannot ping the domain name abc.def.xyz.com, you may not join success-fully unless you can resolve abc.def.xyz.com using the command:

# host abc.def.xyz.com ip_address

where the ip_address is the IP address of DNS as specified at the bottom of the network page.


94 U41840-J-Z125-1-76

● Organizational Unit:

This is optional. There is usually a default organizational unit such as Computers. If you want to join to an organizational unit that is different from the default, then enter the name of that organizational unit as seen in MMC.

● Administrator Name - user1

● Password - <enter password>

Troubleshooting ADS (Active Directory Services) Join Issues

For troubleshooting purposes we will assume that the sample settings in "Joining a Domain Using a Domain User Credential" were used to join the domain abc.def.xyz.com through the remote management pages, but the operation failed. This assumption is important in that all the necessary settings were already written in relevant files and you can log on the server to perform a number of tests to determine the root cause.

1. Is the DNS server specified on the Network page capable of resolving the domain name?

# nslookup abc.def.xyz.com

or

# host abc.def.xyz.com 10.20.30.40

to see if the DNS server 10.20.30.40 can resolve abc.def.xyz.com. If it cannot, change to a different DNS server IP address on the Network page.

2. Specify the fully qualified domain name on the Windows Domain page.

Do not specify the short name abc. You must specify abc.def.xyz.com.

3. Check the Primary Domain Controller (PDC).

To avoid any DNS issue, enter the IP address of the PDC on the Windows Domain page. Make sure you can ping the PDC successfully.

4. Check the clock time difference:

Time on the ADS server:

# net time -S abc.def.xyz.com

Time on the local server:

# date

Make sure the time difference is less than 300 seconds.


U41840-J-Z125-1-76 95

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

5. Make sure the username exists in the ADS.

Test by logging in the Kerberos server:

# kinit [email protected]

Note that the name after '@' must be all capitalized. If the command fails, it should tell what happened. Again, must make sure ABC.DEF.XYZ.COM can be resolved by the DNS. If the command succeeds, you should run the next two commands:

# klist

This command is to list all the Kerberos tickets just issued to user1.

# kdestroy

This command is to destroy all the Kerberos tickets issued to user1.

6. If the username is not a member of the Administrator or Domain Admins group, then check to make sure he has the correct rights to join a domain:

# net ads status -U [email protected]

Make sure you see the following lines in the output:

dNSHostName: cs800-abc.abc.def.xyz.com

servicePrincipalName: HOST/cs800-abc.abc.def.xyz.com

servicePrincipalName: HOST/cs800-abc

7. Finally, the errors from joining ADS domain are logged in:

/tmp/nas/cifs.ads.join

The contents are overwritten each time you join the domain either from the GUI or by running an appropriate CLI command. The CLI command is not officially supported. You can run

# nastool

without options to show the syntax. Note that certain subcommands require a password. If you do not type the password option, you will be prompted interactively and the password entered will not be echoed on screen.


96 U41840-J-Z125-1-76

Access Control Configuration

Use the Access Control page to add, edit or delete workgroup users.

I For an ADS CIFS configuration there is no need to configure access control.

To configure access control information:

1. From the NAS & OST page, click the Access Control tab.

The Access Control page displays (see Figure 40).

Figure 40: Access Control Page

2. Click Add to add a workgroup user.

I To edit a workgroup user, click the user name link on the Summary page, or click the Edit tab.

The Add Workgroup User page displays (see Figure 41).


U41840-J-Z125-1-76 97

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Figure 41: Add Workgroup User Page

3. Edit the Workgroup Users information as desired (see Table 29 for a description of the fields).

I If you are editing a workgroup user, you cannot change the User Name.

4. Click Apply.

I To delete a workgroup user, click the Delete tab. Select the user and click Delete.

Table 29: Workgroup User Fields

Field Description

User Name Enter a user name for the workgroup user.

Password Enter a password for the workgroup user.

Confirm Password Enter the password again to confirm it.

Description (optional) Enter a description for the workgroup user (optional).

Grant Administrator Privileges

Select this check box to add the workgroup user to the Windows Administrators group. This allows the workgroup user to override certain permissions settings and prevents the workgroup user from being locked out of shares or directories.


98 U41840-J-Z125-1-76

ADS Share Permissions

To set the ADS (Active Directory Service) share permissions:

1. Log into the primary domain controller as an administrator.

2. From the Administrative Tools, select the MMC Computer Management tool (MMC: Microsoft Management Console).

3. Access the CS800 system from the Action menu. Enter the system hostname and click Enter.

4. In the lower left field, expand System Tools and Shared Folders to access the Shares.

5. Right-click the share in the lower right field and select Properties.

6. Select the Share Permissions tab.

7. Select Add/Remove Share users/groups. Adding a user/group will display a dialog. You can enter a user/group to select and then click OK.

8. Set permissions for each user.

9. Click Apply/OK.

I In some cases, when you view file permissions on a Windows system, you will not see the user and group information. Instead you will see the SID (security ID) which appears as a series of numbers. This occurs when you move files (for example, using a backup utility or DOS xcopy) from one system to another system, and the user and group from the source system do not exist on the target system.

Often users and groups are unique to a particular scope, such as a Windows system or an ADS domain. As a result, some assigned permissions might not be available on the target system because the associated user and group do not exist there. However, common groups (for example, Administrators, Users, and Everyone) are recognized on most Windows systems and domains.

Advanced Setting

Use the Advanced Setting page to adjust the settings of the Samba server running at the CS800.

Opportunistic locking lets clients lock files and locally cache information without the risk of another user changing the file. This increases performance for many file operations but may decrease performance in other operations because the server that grants the opportunistic lock must manage the breaking of that lock when another user requests access to the file.

To access the Advanced Setting page:

Configuration with the CS800 Web Pages PTT Configuration

U41840-J-Z125-1-76 99

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

1. From the NAS & OST page, click the Advanced Setting tab.

The Advanced Setting page displays (see Figure 42).

Figure 42: Advanced Setting Page

2. To enable opportunistic locking, select the Enable Opportunistic Locking check box. To disable opportunistic locking, clear the check box.

3. Click Apply.

PTT Configuration

Path to Tape (PTT) provides the ability to move data to physical tape cartridges in an attached tape library using a Fibre Channel connection.

The CS800 supports Backup Application Specific PTT: This option allows a physical tape library to be directly connected to a CS800 through an NDMP (Network Data Management Protocol) connection. The CS800 supports OST path to tape using Symantec NetBackup.

The PTT (Path to Tape) page provides the following discovery and configuration options:

● "Physical Device Discovery"

● "Backup Application Specific"

● "Initiators and Ports"

PTT Configuration Configuration with the CS800 Web Pages

100 U41840-J-Z125-1-76

To access the PTT page, from the Configuration menu, click the PTT tab.

I The PTT page is available only on CS800 systems equipped with a related Fibre Channel card.

Physical Device Discovery

Use the Physical Device Discovery page to discover and configure attached physical libraries and tape drives. The attached libraries cannot be recognized and used for path to tape data movement until they have been discovered through physical device discovery.

To access the Physical Device Discovery page:

1. From the PTT page, click the Physical Device Discovery tab.

The Physical Device Discovery page displays (see Figure 43).

Figure 43: Physical Device Discovery Page

To configure an attached physical library:

I Clicking the Information button displays a window that provides additional physical library information such as SCSI ID and LUN assignment.


U41840-J-Z125-1-76 101

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

1. Click Scan for Devices to detect attached physical libraries.

Any attached physical libraries are shown in the Medium Changers (Physical Libraries) list.

2. Select the new attached library by selecting the check box to the left of the library serial number.

3. Select an intended use for this library:

● Backup Application Specific - Uses the library as a backup application specific server.

● Remove - Removes the attached library from the CS800 configuration.

V The physical library MUST be physically disconnected from the CS800 before it can be removed from the configuration.

● Ignore - Ignores the attached physical library.

4. Click Apply.

The library devices changes are applied.

5. To view the library media changer and configured drives, click the Serial Number link for the library.

The tape drives are shown in the Tape Drives list.

6. Choose an intended use for the tape drives:

● Backup Application Specific - Configures the tape drive for use as a backup appli-cation specific enabled tape drive.

I Tape drives that will be utilized for backup application specific path to tape must be mapped to a host access group prior being configured as a backup application specific (NDMP) tape drive. It is recommended that you add a "fake" host using a WWPN that does not exist within your SAN. Then, create a new host access group using that host (and any target) to map all of your drives dedicated to application specific path to tape.

● Remove - Removes the tape drive from the CS800 configuration.

V The tape drive MUST be physically disconnected or removed from the CS800 before it can be removed from the configuration.

● Ignore - Ignores the tape drive.

7. Click Apply.

Once the tape library and tape drives are configured, they display in the Medium Changer list located at the bottom of the page.


102 U41840-J-Z125-1-76

Backup Application Specific

Use the Backup Application Specific page to configure user settings for the backup appli-cation specific path to tape option. Symantec NetBackup is supported for OST path to tape:

To access the Backup Application Specific page:

1. On the PTT page, click the Backup Application Specific tab.

The Backup Application Specific page contains the following tabs:

● "Summary"

● "Add"

● "Edit"

● "Delete"

Summary

To access the Summary page:

1. On the Backup Application Specific page, click the Summary tab.

The Backup Application Specific Summary page displays (see Figure 44).

Figure 44: Backup Application Specific Summary Page


U41840-J-Z125-1-76 103

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

The Summary page lists all backup application specific users that have been configured on the system.

Add

To add a backup application specific user:

1. On the Backup Application Specific page, click the Add tab.

The Backup Application Specific Add page displays (see Figure 45).

Figure 45: Backup Application Specific Add Page

2. Enter the following backup application specific user information:

a) Enter a Username.

b) Enter a Password.

c) Confirm the password in the Confirm Password box.

d) Add a Description (optional).

e) Click Apply to add the backup application specific user.

Edit

To edit a backup application specific user:


104 U41840-J-Z125-1-76

1. On the Backup Application Specific page, click the Edit tab.

The Backup Application Specific Edit page displays (see Figure 46).

Figure 46: Backup Application Specific Edit Page

2. Edit the following backup application specific user information:

a) From the Username drop down box, select the backup application specific username to edit.

b) Edit the Password.

c) Confirm the password in the Confirm Password box.

d) Add a Description (optional).

e) Click Apply to edit the backup application specific user.

Delete

To delete a backup application specific user:

1. On the Backup Application Specific page, click the Delete tab.

The Backup Application Specific Delete page displays.

2. Select the check box for backup application specific user to delete.

Configuration with the CS800 Web Pages Network Configuration

U41840-J-Z125-1-76 105

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

3. Click Delete to delete the selected backup application specific user.

The backup application specific user is deleted.

Initiators and Ports

Use the Initiators & Ports page (see Figure 47) to see a list of all path-to-tape initiator ports and their associated World Wide Port Numbers (WWPNs). The Initiators & Ports page also displays a map of all Fibre Channel and Ethernet ports on the node. Initiator ports are shown in bold on the map.

Figure 47: Initiators & Ports Page

Network Configuration

The network configuration information was entered during the initial setup of the CS800. Consult your network administrator prior to changing any of the information.

I The CS800 Network page differs depending on the number of Ethernet ports available on your system. There are two possible Ethernet port configurations: 7 x 1 GbE ports, and 3 x 1 GbE ports plus 2 x 10 GbE ports.

Use the Network page to view and edit the network configuration information.

Network Configuration Configuration with the CS800 Web Pages

106 U41840-J-Z125-1-76

To access the Network page:

1. From the Configuration menu, click the Network tab.

The Network page contains the following tabs:

● "General"

● "IP"

● "Segmentation and Bonding"

V Changing the network configuration requires a system reboot in order for all system services to function correctly. The system automatically reboots immediately after changes are applied.

I Rebooting the system can take several minutes. After the network configuration is saved, close your Web browser and wait 15 minutes before logging in again. If the IP address that you use to log in to the system is changed, you will temporarily lose your connection to the remote management pages. Because of this, you might not see a confirmation page informing you that settings have been saved.

General

Use the General tab to specify the hostname and domain name server (DNS) search path.

To specify the hostname and domain search path:

1. From the Network page, click the General tab.

The Network General page displays (see Figure 48).


U41840-J-Z125-1-76 107

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Figure 48: Network General Page

2. Under System, enter the Hostname for the CS800.

3. (Optional) Under DNS, enter a Domain Search Path. This is either a single domain name or a comma separated list (no spaces) of up to 6 domain names

The first domain name listed is used as the local domain. Domain names must contain only letters (A-Z or a-z), numbers (0-9), dots (.), and hyphens (-).

4. Click Apply.

IP

Use the IP tab to set the network IP addresses for the CS800.

To configure the network on a CS800:

1. From the Network page, click the IP tab.

The Network IP page displays (see Figure 49).

The grid shows a graphical representation of the Ethernet ports as they appear on the rear of the system, i.e. it depends on the configuration level of the machine. The grid also indicates how the ports are currently bonded. For more information see "Segmen-tation and Bonding" on page 109


108 U41840-J-Z125-1-76

Figure 49: Network IP Page

2. Under System, enter the IP address and netmask information for the CS800.

The information you must enter varies depending on the segmentation option selected on the Segmentation and Bonding page.

3. (Optional) Under System, enter the Default Gateway IP Address for the CS800.

4. (Optional) Under DNS, enter the IP address of up to three servers where the domain name is resolved or translated into an IP address.

I If you are using network segmentation, you must specify a DNS server for the Data IP address to enable NAS access.

5. Click Apply.


U41840-J-Z125-1-76 109

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Segmentation and Bonding

Network segmentation is the process of splitting a single network into several subnetworks or segments. The advantages of a segmented network are improved performance and security. Performance is improved because there are fewer hosts on the segmented network, which in turn minimizes local traffic. Security is improved because the data traffic is contained on this segment and not visible to the outside network.

I If you are using network segmentation and Automated Deployment Services (ADS), you must use the data segment IP information for ADS management, NOT the management segment. ADS uses the Server Message Block (SMB) data protocol to manage the NAS shares on your system, which requires that the management traffic use the data segment.

The CS800 allows you to configure your network for separate segment types. The three primary segments are defined by the type of network traffic that can be used on that segment. The three types of network traffic are:

● Replication traffic - This segment is be used exclusively for replication data movement

● Management traffic - This segment is be used exclusively for CS800 remote management (Web page access)

● Data traffic - This segment is used exclusively for NAS data movement

Each network segment has its own network interface (IP address, network mask, and default gateway). In this way, the segment is separated from other network segment traffic.

I Print out Table 30 on page 114, or Table 31 on page 115 to gather the network configuration information for your configuration.

Using Round Robin (Mode 0) With a Dell or CISCO Switch

If you are using the Round Robin (Mode 0) option and you have a Dell or CISCO switch, then the ports that connect to the CS800 must be bonded.

For example, specify the following settings from the switch CLI:

● Interface Ethernet - If both ports connect to the same switch, set to 1/gX where X is the port number. If there two or more switches, replace “1” with the correct ID number (2 or 3).

● Switchport mode - Set to trunk.

● Channel-group 1 mode - Set to on.

Configuring the Network on a CS800

To configure the network on the CS800:


110 U41840-J-Z125-1-76

1. From the Network page, click the Segmentation and Bonding tab.

The Network Segmentation and Bonding page displays (see Figure 50 for a NAS basic configuration and Figure 52 for a NAS performance configuration).

Figure 51 and Figure 53 show how the numbering of the Ethernet ports used in the grid corresponds to the physical ports on the rear of the CS800.

Figure 50: Network Segmentation and Bonding Page (Configuration for CS800 Basic)

Figure 51: Numbering of the Ethernet Ports (Configuration for CS800 Basic)

ETH2

ETH3

ETH4

ETH5

ETH6 (service)

ETH7

ETH8

ETH9


U41840-J-Z125-1-76 111

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Figure 52: Network Segmentation and Bonding Page (Configuration for CS800 Performance)

Figure 53: Numbering of the Ethernet Ports (Configuration for CS800 Performance)

The Network Segmentation and Bonding page lists the segmentation options that are available for your configuration. The grid shows a graphical representation of the Ethernet ports as they appear on the rear of the system, i.e. it depends on the configu-ration level of the machine. The grid also indicates how the ports are currently bonded.

Physical Ethernet ports that are bonded together act as a single logical port. That is, multiple ports that are bonded together behave like a single port and require one set of network settings. Ports that are bonded together in the currently selected segmentation option are shaded the same color in the grid. For example:

ETH6

ETH7

ETH2 (service)

ETH3

ETH4

ETH5


112 U41840-J-Z125-1-76

● If you select BOND ALL (not segmented), all Ethernet ports are bonded together into a single logical port and are shaded blue in the grid.

● CS800 Performance: If you select BOND ALL 1GB (Replication), BOND ALL 10GB (Management/Data), Ethernet ports ETH3, ETH4 and ETH5 are bonded together into a single logical port and are shaded blue in the grid, while Ethernet ports ETH6 and ETH7 are bonded together into a single logical port and are shaded purple in the grid.

2. Under Segmentation, select the type of network segmentation for your system:

CS800 Basic (7 x 1 GbE ports)

● BOND ALL (Not segmented) - All ports are bonded together and require a single set of network settings on the IP page.

● BOND ALL (Replication/Management/Data) - All ports are bonded together for all traffic types. Each segment (Data, Management, and Replication) requires a set of network settings on the IP page.

● ETH7 (Replication), BOND ALL-1 (Management/Data) - All Replication traffic takes place on port ETH7. Data and Management traffic take place on ports ETH2, ETH3, ETH4, ETH5, ETH8 and ETH9. Each segment (Data, Management, and Replication) requires a set of network settings on the IP page.

● ETH7 (Management), BOND ALL-1 (Replication/Data) - All Management traffic takes place on port ETH7. Data and Replication traffic take place on ports ETH2, ETH3, ETH4, ETH5, ETH8 and ETH9. Each segment (Data, Management, and Replication) requires a set of network settings on the IP page.

● BOND ALL-1 (Data), ETH7 (Replication/Management) - All Data traffic takes place on ports ETH2, ETH3, ETH4, ETH5, ETH8 and ETH9. Management and Replication traffic take place on port ETH7. Each segment (Data, Management, and Replication) requires a set of network settings on the IP page.

CS800 Performance (3 x 1 GbE ports and 2 x 10 GbE ports)

● BOND ALL 1GB (not segmented) - All 1 GbE ports (ETH3, ETH4 and ETH5) are bonded together and require a single set of network settings on the IP page.

● BOND ALL 10GB (not segmented) - Both 10 GbE ports (ETH6 and ETH7) are bonded together and require a single set of network settings on the IP page.

● BOND ALL 1GB (Replication/Management/Data) - All 1 GbE ports (ETH3, ETH4 and ETH5) are bonded together for all traffic types. Each traffic type (Data, Management, and Replication) requires a set of network settings on the IP page.

● BOND ALL 10GB (Replication/Management/Data) - Both 10 GbE ports (ETH6 and ETH7) are bonded together for all traffic types. Each traffic type (Data, Management, and Replication) requires a set of network settings on the IP page.


U41840-J-Z125-1-76 113

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

● BOND ALL 1GB (Replication), BOND ALL 10GB (Management/Data) - All Repli-cation traffic takes place on ports ETH3, ETH4 and ETH5. Data and Management traffic take place on ports ETH6 and ETH7. Each traffic type (Data, Management, and Replication) requires a set of network settings on the IP page.

● BOND ALL 1GB (Management), BOND ALL 10GB (Replication/Data) - All Management traffic takes place on ports ETH3, ETH4 and ETH5. Data and Repli-cation traffic take place on ports ETH6 and ETH7. Each traffic type (Data, Management, and Replication) requires a set of network settings on the IP page.

● BOND ALL 10GB (Data), BOND ALL 1GB (Replication/Management) - All Data traffic takes place on ports ETH6 and ETH7. Management and Replication traffic take place on ports ETH3, ETH4 and ETH5. Each traffic type (Data, Management, and Replication) requires a set of network settings on the IP page.

3. Under Bonding, select a bonding option:

● Round Robin (Mode 0) - This option sends Ethernet frames using the bonded Ethernet ports with a valid MII link. Frames are sent in a round-robin fashion, starting with the first slave device and then the rest of the devices. This only applies to the traffic sent from the CS800. Your Ethernet switch needs to aggregate the ports, so the connected ports are treated as a logical port. The frame reception is completely dependent on the transmission algorithm of your Ethernet switch. The bonding mechanism does not balance the frame reception.

● LACP (Mode 4) - This option (Link Aggregation Control Protocol) is based on the 802.3ad IEEE standard for aggregating Ethernet ports. If the bonding algorithm is set to LACP, your Ethernet switch ports need to be configured in a 802.3ad based Link Aggregation group (LAG) in LACP mode. The frame reception and trans-mission is controlled by the LACP between the bonded ports and your Ethernet switch ports.

I Note: In order to maintain network connectivity to your system, you must reconfigure the switch that is connected to your system to use the same bonding mode. The best time for you to change the bonding mode on your switch will be during the next reboot of your system, after you have saved the new network settings. Changing the bonding mode on your switch before saving these settings and rebooting may result in the loss of network connectivity to your system.

4. Click Apply.


114 U41840-J-Z125-1-76

Table 30: Network Configuration Information (7 x 1GbE Configuration)

Segmentation Option

Network Information

BOND ALL (not segmented)

Bond All IP Address:

Bond All Netmask:

Replication Network Information

Management Network Information

Data Network Infor-mation

BOND ALL (Replication/Management/Data)

IP Address:

Netmask:

Gateway:

IP Address:

Netmask:

Gateway:

IP Address:

Netmask:

Gateway:

ETH7 (Replication), BOND ALL-1 (Management/Data)

ETH7

IP Address:

Netmask:

Gateway:

BOND ALL-1

IP Address:

Netmask:

Gateway:

BOND ALL-1

IP Address:

Netmask:

Gateway:

ETH7 (Management), BOND ALL-1 (Replication/Data)

BOND ALL-1

IP Address:

Netmask:

Gateway:

ETH7

IP Address:

Netmask:

Gateway:

BOND ALL-1

IP Address:

Netmask:

Gateway:

BOND ALL-1 (Data), ETH7 (Replication/Management)

ETH7

IP Address:

Netmask:

Gateway:

ETH7

IP Address:

Netmask:

Gateway:

BOND ALL-1

IP Address:

Netmask:

Gateway:


U41840-J-Z125-1-76 115

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Table 31: Network Configuration Information (3 x 1GbE and 2 x 10GbE Configuration)

Segmentation Option

Network Information

BOND ALL 1GB (not segmented)


Bond All Netmask:

BOND ALL 10GB (not segmented)


Bond All Netmask:

Replication Network Information

Management Network Information

Data Network Infor-mation

BOND ALL 1GB (Replication/Management/Data)

IP Address:Netmask:Gateway:

IP Address:

Netmask:

Gateway:

IP Address:

Netmask:

Gateway:

BOND ALL 10GB (Replication/Management/Data)

IP Address:

Netmask:

Gateway:

IP Address:

Netmask:

Gateway:

IP Address:

Netmask:

Gateway:

BOND ALL 1GB (Replication), BOND ALL 10GB (Management/Data)

BOND ALL 1GB

IP Address:

Netmask:

Gateway:

BOND ALL 10GB

IP Address:

Netmask:

Gateway:

BOND ALL 10GB

IP Address:

Netmask:

Gateway:

BOND ALL 1GB (Management), BOND ALL 10GB (Replication/Data)

BOND ALL 10GB

IP Address:

Netmask:

Gateway:

BOND ALL 1GB

IP Address:

Netmask:

Gateway:

BOND ALL 10GB

IP Address:

Netmask:

Gateway:

BOND ALL 10GB (Data), BOND ALL 1GB (Replication/Management)

BOND ALL 1GB

IP Address:

Netmask:

Gateway:

BOND ALL 1GB

IP Address:

Netmask:

Gateway:

BOND ALL 10GB

IP Address:

Netmask:

Gateway:

Date and Time Configuration Configuration with the CS800 Web Pages

116 U41840-J-Z125-1-76

Date and Time Configuration

The date and time can be set from the CS800 pages. Setting the correct date and time allows the system to provide accurate reports when events occur on the system.

Use the Date & Time page to set the system date and time.

To access the Date & Time page:

1. From the Configuration menu, click the Date & Time tab.

The System Date and Time Settings page displays (see Figure 54).

Figure 54: System Date and Time Settings Page

2. There are two options for setting the system date and time (select one):

● (Recommended) Select Use NTP (Network Time Protocol) to synchronize the CS800 to an NTP timeserver or timeserver pool.

The Select a Timeserver Pool drop down box provides a list of well-known, geographically-based, NTP timeserver pools. This option is recommended if you configured at least one DNS IP address during network configuration.

The Specify a Timeserver or Pool box lets you type the name or IP address of any desired NTP server/pool. (See http://support.ntp.org for information on publicly available NTP servers)

Configuration with the CS800 Web Pages Security Configuration

U41840-J-Z125-1-76 117

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

● Select Manual to manually set the system date and time. Click Edit to specify the system date. Use the drop down boxes to specify the system time.

3. Select the Timezone.

4. Select the desired time format (24 hours or 12 hours).

5. Click Apply.

Security Configuration

To access the Security page, from the Configuration menu, click the Security tab.

The Security page contains the following tabs:

● "Passwords"

● "SSL"

● "Login Session"

Passwords

I Change the default passwords as soon as possible.

The CS800 has two levels of security built into the system:

● The Monitor user is allowed to view the CS800 management pages, but not change them.

● The Administrator user can view and edit the management pages.

To set the monitor and administrator passwords:

1. From the Security page, click the Passwords tab.

The Passwords page displays (see Figure 55).

Security Configuration Configuration with the CS800 Web Pages

118 U41840-J-Z125-1-76

Figure 55: Passwords Page

2. Under Monitor Password, enter the desired password in the New Password field and again in the Confirm New Password field.

I The passwords are limited to 15 characters. All alpha numeric characters, _ and - are allowed.

3. Click Apply.

4. Under Administrator Password, enter the desired password in the New Password field and again in the Confirm New Password field.


U41840-J-Z125-1-76 119

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

I The passwords are limited to 15 characters. All alpha numeric characters, _ and - are allowed.

5. Click Apply.

6. To reset the CLI (command line interface) monitor or administrator password to factory default, select Reset Password to Factory Default and click Apply.

The password is returned to the factory default.

7. To set the CLI monitor or administrator passwords, select Change Password, enter the new password, confirm the new password, and click Apply.

8. To enable or disable the CLI monitor or administrator account, select or clear the Enable CLI Monitor Account check box or the Enable CLI Administrator Account check box, and click Apply.

SSL

SSL (Secure Sockets Layer) is a protocol that provides security and privacy over the Internet by negotiating encryption keys before transmitting data between a client and a server.

To establish a secure SSL connection, your CS800 must have an encryption key assigned to it by a Certification Authority in the form of a certificate file, private key file, and pass phrase. Once you install these components, you can establish a secure connection using the SSL protocol. The CS800 comes with a SSL certificate. In addition, you can purchase other certificates and add them to the CS800 SSL configuration.

Server Authentication Warnings

Enabling SSL with the default Fujitsu certificate allows you to securely communicate with the CS800 Web-based interface using SSL encryption. However, you may receive a warning from your Web browser stating that the server you are attempting to connect to does not match the server embedded within the certificate. This is expected behavior since the default certificate can only be used for encryption and not server authentication. You may install your own custom certificate in order to take advantage of server authentication in addition to encrypted communication.

To suppress server authentication warnings for the default certificate:

● Internet Explorer - If a dialog box displays warning you of a possible certificate error, add the IP address for your CS800 to the Trusted Sites list (Tools > Internet Options > Security > Trusted Sites). If you receive subsequent warning pages and the option to close the browser or continue to the Web site, click Continue. This suppresses the warnings until you restart the browser.

Security Configuration Configuration with the CS800 Web Pages

120 U41840-J-Z125-1-76

● Firefox - If the Secure Connection Failed dialog box displays, click the link at the bottom of the dialog box and follow the instructions to add an exception for your CS800.

Configuring SSL

To access the SSL page:

1. From the Security page, click the SSL tab.

The SSL page displays (see Figure 56).

Figure 56: SSL Page

2. To enable SSL, select Enabled and click Apply.

I The default setting for SSL is Disabled.

3. To add an SSL certificate, click New.

The Install New Certificate page displays (see Figure 57).


U41840-J-Z125-1-76 121

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Figure 57: Install New Certificate Page

4. Under Upload your SSL certificate file, type the location and filename of the new SSL certificate file.

I Use the Browse button to browse the system and locate the desired SSL certificate file. The SSL certificate file must be named server.crt.

5. Click Upload to install the SSL certificate file.

6. Type your private key and press Enter.

7. Type your pass phrase and press Enter.

A Successful Upload page displays indicating that the SSL certificate file has been installed on the system.

8. Click OK to continue.

The certificate displays in the certificate area on the SSL page.

Login Session

Use the Login Session page to specify an inactivity time-out value from 1 to 60 minutes. The default setting is 30 minutes. When the remote management pages are inactive for this period of time, the user is automatically logged out of the session and must log back in to continue.

To access the Login Session page:

Email Configuration Configuration with the CS800 Web Pages

122 U41840-J-Z125-1-76

1. From the Security page, click the Login Session tab.

The Session Configuration page displays (see Figure 58).

Figure 58: Session Configuration Page

2. Enter an Inactivity Timeout (1 to 60 minutes) and click Apply.

The inactivity timeout value is set.

Email Configuration

Use the Email page to specify e-mail server settings as well as recipients who should be contacted when service tickets or administrator alerts occur. You can specify e-mail recip-ients, notification levels, and information about your e-mail configuration.

To access the Email page, from the Configuration menu, click the Email tab.

The Email page contains the following tabs:

● "Recipients"

● "Server"

● "Test"

● "Email Home"

Configuration with the CS800 Web Pages Email Configuration

U41840-J-Z125-1-76 123

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Recipients

Use the Recipients page to add, edit, and delete e-mail recipients.

I To enable the CS800 to send notifications to recipients, you must configure the e-mail server settings (see "Server" on page 125).

To access the Recipients page:

1. From the Email page, click the Recipients tab.

The Email Recipient Configuration page displays (see Figure 59).

Figure 59: Email Recipient Configuration Page

The Recipients page contains the following tabs:

● "Summary"

● "Add"

● "Edit"

● "Delete"

Summary

The Summary page lists all configured e-mail recipients.

To edit information for an e-mail recipient, click the Name link.


124 U41840-J-Z125-1-76

Add

Use the Add page to configure an e-mail recipient.

To add an e-mail recipient:

1. From the Recipients page, click the Add tab.

2. Enter the Name of the recipient.

3. Enter the e-mail address of the recipient.

4. Select a notification type:

● High - Send e-mail notifications for High service tickets (see "Service Tickets" on page 171 for more information).

High service tickets indicate that a critical event has occurred which needs to be resolved immediately. The operation and performance of the CS800 is degraded and there is a risk of impending system failure or data loss

● High and Medium - Send e-mail notifications for High and Medium service tickets.

Medium service tickets indicate that a more serious event has occurred which needs to be resolved, but it does not necessarily need to be fixed immediately. The operation and performance of the CS800 may be degraded.

● All - Send e-mail notifications for High, Middle, and Low service tickets as well as any administrator alerts (see "Admin Alerts" on page 169 for more information).

Low service tickets indicate that an event has occurred which needs to be resolved, but it generally does not affect the operation or performance of the CS800.

5. Select the Notification Enabled check box. When notifications are enabled, the recipient receives notifications.

6. Click Apply.

The e-mail recipient is added.

Edit

Use the Edit page to edit the e-mail recipient information for a specific recipient.

To access the Edit page, from the Recipients page, click the Edit tab.

Delete

Use the Delete page to delete a previously configured e-mail recipient.

To delete an e-mail recipient:

Configuration with the CS800 Web Pages Email Configuration

U41840-J-Z125-1-76 125

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

1. From the Recipients page, click the Delete tab.

2. Select the e-mail recipient.

3. Click Delete.

The e-mail recipient is deleted.

Server

Use the Server page to edit the outgoing e-mail server information.

1. From the Email page, click the Server tab.

2. Enter the Host Name or IP Address for the outgoing e-mail server (for example, the DNS name).

3. Enter the return e-mail address in the From Email Address box.

Specify a return address that lets you easily identify the system that generated the e-mail (for example, [email protected]). The return address must contain an @ symbol and a valid domain name including a period.

4. Click Apply.

Test

Use the Test page to send a test e-mail to verify the e-mail configuration.

To access the Test page, from the Email page, click the Test tab. To send a test e-mail, select a recipient from the list and click Send.

Email Home

Use the Email Home page to configure the CS800 to automatically send XML-based reports to e-mail recipients.

The report represents a snapshot of the system information at the time the report is generated. It is recommended to generate and save a report before performing a software upgrade or reconfiguring the system.

The system can generate two types of reports:

● Status Data - System status information

● Configuration Data - System configuration data


126 U41840-J-Z125-1-76

The report is contained in an e-mail that also includes the following information:

● System serial number

● Date and time

● A message with the e-mail origin that informs the user it is an automated e-mail and that they should not respond to it.

To access the Email Home page, from the Email page, click the Email Home tab.

The Email Home page contains the following tabs:

● "Schedule"

● "On Demand"

Schedule

Use the Schedule page to enable the Email Home Scheduler, set the day and time when the Status Data or Configuration Data reports are sent, and configure up to three e-mail recipients.

The Email Home Scheduler feature automatically sends an e-mail to the configured recip-ients once a week.

To configure the Email Home Scheduler:

1. From the Email Home page, click the Schedule tab.

2. To enable the Email Home Scheduler, select the Enable Email Home Scheduler check box.

● The Email Home Scheduler is enabled by default.

● To disable the Email Home Scheduler, clear the Enable Email Home Scheduler check box.

3. Specify the day and hour of the week when reports are sent.

4. Specify up to four e-mail recipients.

5. Click Apply.

Configuration with the CS800 Web Pages SNMP Configuration

U41840-J-Z125-1-76 127

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

On Demand

Use the On Demand page to immediately send a Status Data or Configuration Data report to a recipient.

1. From the Email Home page, click the On Demand tab.

2. Select the type of report to send (Status Data or Configuration Data).

3. In the Send To box, specify the e-mail address where you want to send the report.

4. Click Send.

SNMP Configuration

SNMP is short for Simple Network Management Protocol, a set of protocols for managing complex networks. SNMP works by sending messages, called protocol data units (PDUs), to different parts of a network. SNMP-compliant devices, called agents, store data about themselves in Management Information Bases (MIBs) and return this data to the SNMP requesters.

To access the SNMP page, from the Configuration menu, click the SNMP tab.

The SNMP page contains the following tabs:

● "Destinations"

● "Community"

● "Test"

Destinations

Use the Destinations page to add, edit, or delete SNMP destinations.

To access the Destinations page:

1. From the SNMP page, click the Destinations tab.

The Trap Destination Configuration page displays (see Figure 60).

SNMP Configuration Configuration with the CS800 Web Pages

128 U41840-J-Z125-1-76

Figure 60: Trap Destination Configuration Page

To add an SNMP destination:

1. From the Destinations page, click the Add tab.

2. Enter the IP Address that will receive the traps generated by the CS800 (for example, 12.34.56.78).

3. Enter a Name for the SNMP destination.

4. Select the traps to be reported (see Table 32):

Table 32: SNMP Trap Selections

5. Click Apply.

Field Description

Failure If selected, Failure Traps are enabled.

Warning If selected, Warning Traps are enabled.

Informational If selected, Informational Traps are enabled.

Available If selected, a trap is generated every time the system transitions from an unavailable to an available state.

Unavailable If selected, a trap is generated every time the system transitions from an available to an unavailable state.

Configuration with the CS800 Web Pages SNMP Configuration

U41840-J-Z125-1-76 129

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Community

Use the Community page to add, edit, and delete the SNMP community information.

To access the Community page:

1. From the SNMP page, click the Community tab.

The SNMP Community Configuration page displays (see Figure 61).

Figure 61: SNMP Community Configuration Page

To add a community:

1. From the Community page, click the Add tab.

2. Enter a unique Name (up to 20 characters). Valid characters are letters, numbers, hyphens, and underscores.

V If no communities are defined, the SNMP agent is not accessible.

3. Enter a valid IP Address and Network Mask pair.

A pair is valid if performing a logical bitwise AND operation on the IP address and the network mask results in the IP address. See the following table for examples:

SNMP Configuration Configuration with the CS800 Web Pages

130 U41840-J-Z125-1-76

I If you define a single community and set both the IP address and network mask to 0.0.0.0 (or leave both blank), then IP address-based access control is disabled. In this case, the SNMP agent is accessible from any IP address.

4. Select the Access Type for the new community:

● Get allows SNMP get operations.

● Get/Set allows both SNMP get and put operations.

5. Select the Community Status check box to enable this SNMP community.

6. Click Apply.

An Information page displays indicating the community has been added.

Test

Use the Test page to send a test SNMP trap.

To send a test SNMP trap:

1. From the SNMP page, click the Test tab.

2. Select an SNMP destination.

3. Click Send to send a test SNMP trap.

The test trap is sent. Verify the destination to ensure the SNMP trap was sent.

IP Address / Network Mask

Result

10.40.166.87

255.255.255.255

Allows access only from 10.40.166.87

10.40.166.87

10.40.166.87

Allows access only from 10.40.166.87

10.40.166.87

10.40.166.0

Invalid because the logical bitwise operation (address AND mask) is not equal to the address

10.40.166.87

255.255.0.0

Invalid because the logical bitwise operation (address AND mask) is not equal to the address

10.40.0.0

255.255.0.0

Allows access from any client with address 10.40.xx.xx

Configuration with the CS800 Web Pages Contacts Configuration

U41840-J-Z125-1-76 131

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Contacts Configuration

Use the Contacts page to enter company contact information.

To access the Contacts page:

1. From the Configuration menu, click the Contacts tab.

The Company Information page displays (see Figure 62).

Figure 62: Company Information Page

The Contacts page contains the following tabs:

● "Company"

● "Primary and Secondary"

Company

Use the Company page to enter company specific information.

1. From the Contacts page, click the Company tab.

2. Edit the company information as desired (see Table 33 for a description of the fields).

3. Click Apply.

Contacts Configuration Configuration with the CS800 Web Pages

132 U41840-J-Z125-1-76

Table 33: Company Information

Primary and Secondary

Use the Primary and Secondary pages to enter primary and secondary contact infor-mation.

1. From the Contacts page, click the Primary or Secondary tab.

2. Edit the primary or secondary contact information as desired (see Table 34 for a description of the fields).

3. Click Apply.

Field Description

Company Name View or edit the company name where the CS800 system resides.

Street View or edit the street name where the company is located.

City View or edit the city where the company is located.

State View or edit the state where the company is located.

Postal Code View or edit the postal code.

Country View or edit the country where the company is located.

Eternus CS800 Location

View or edit the physical location of the CS800 system (for example, data center).

Support Contract View or edit the support contract number.

Configuration with the CS800 Web Pages AIS Connect

U41840-J-Z125-1-76 133

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Table 34: Primary and Secondary Contact Information

AIS Connect

AIS (Advanced Infrastructure Solutions) Connect provides a real-time remote access service for the CS800. After you allow the individual access, a Fujitsu system specialist can remotely access to ensure fast analysis in case of failure.

The AISConnect page consists of 4 tabs:

● "Proxy"

● "Control"

● "Remote Access Policies"

● "Smart Poll"

To access the AISConnect page, from the Configuration menu, click the AISConnect tab.

Field Description

Name View or edit the primary/secondary contact name.

Email Address View or edit the primary/secondary contact e-mail address.

Phone View or edit the primary/secondary contact phone number.

Fax View or edit the primary/secondary contact fax number.

Pager View or edit the primary/secondary contact pager number, if available.

Street View or edit the primary/secondary contact street address.

City View or edit the primary/secondary contact city location.

State View or edit the primary/secondary contact state location.

Postal Code View or edit the primary/secondary contact postal code.

Country View or edit the primary/secondary contact country location.

AIS Connect Configuration with the CS800 Web Pages

134 U41840-J-Z125-1-76

Proxy

Use the Proxy page to specify proxy server information for AIS Connect. If your network environment requires use of a proxy server, you must specify the proxy server settings to enable AIS Connect

To specify proxy server information:

1. From the Configuration menu, click the AISConnect tab.The AISConnect Proxy page displays (see Figure 63).

.

Figure 63: AISConnect Proxy Page

2. Edit the access information as desired (see Table 35 for a description of the fields).

3. Click Apply.

Configuration with the CS800 Web Pages AIS Connect

U41840-J-Z125-1-76 135

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

7_C

onfig

ura

tion_

via

_Web

_P

age

s.fm

Table 35: AIS Connect Information

Control

Use the Control page to stop or start the AIS Connect service.

Figure 64: AISConnect Control Page

The AIS Connect service is required for the following functionality:

● Call-home - Provides integrated monitoring. Events with medium or high priority are a

● Dial-in - Provides remote access. Allows a Fujitsu support representative to remotely connect to the system.

I If the AIS Connect service is stopped, call-home and dial-in functionality is disabled.

Field Description

Proxy Server Edit the IP address of your AISConnect proxy server by which the remote specialist accesses your system.

Proxy Port Edit the port related to the AISConnect proxy server.

Proxy Authenti-cation Enabled

Activate the checkbox if the remote specialist shall be authenti-cated before getting access.

Proxy Username Edit the name by which the remote specialist has to log in if proxy authentication is enabled.

Proxy Password Edit the password related to the proxy username.

Country Select the country where your CS800 is located.

AIS Connect Configuration with the CS800 Web Pages

136 U41840-J-Z125-1-76

To stop or start the AIS Connect service:

1. From the AISConnect page, click the Control tab.

2. Do one of the following actions:

● Click Start to start the AIS Connect service.

● Click Stop to stop the AIS Connect service.

Remote Access Policies

Use the Remote Access Policies page to view the current remote access policies status, or to enable or disable remote access policies.

Remote access policies must be enabled for a Fujitsu support representative to remotely connect to the system using SSH or HTTP. If remote access policies are disabled, remote connection using SSH or HTTP is not allowed by the system.

To enable or disable remote access policies:

1. From the AISConnect page, click the Remote Access Policies tab.The Remote Access Policies page displays the current remote access policies status.

2. Do one of the following actions:

● Click Enable to enable remote access policies.

● Click Disable to disable remote access policies.

Smart Poll

Use the Smart Poll page to immediately establish contact with the central AIS server. This allows a support representative to remotely access the ETERNUS CS800 to diagnose a problem.

I Activate Smart Poll only if you are instructed to do so by a Fujitsu support representative.

To activate Smart Poll:

1. From the AISConnect page, click the Smart Poll tab.

2. When instructed to do so by a Fujitsu support representative, click Smart Poll.

U41840-J-Z125-1-76 137

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\8_

Co

nfig

urat

ion_

with

_N

etB

ack

up.fm

Configurations for NetBackup and OST ReplicationThis chapter contains the following sections related to OST optimized replication in combi-nation with NetBackup:

● "OST Optimized Replication"

● "Initiating an OST Backup"

● "Installing the OST Plug-In"

● "Configuring the NetBackup Media Server"

● "Registering the Storage Server"

● "Configuring Disk Pools and Storage Units"

The section "OST Optimized Replication" describes the main configuration lines. Details and single steps are discussed in the subsequent sections.

OST Optimized Replication

The CS800 has the capability to copy data organized with OST storage servers from one appliance to another appliance (OST data replication). NetBackup uses this capability to initiate optimized off host copy of backup images between these appliances: Copying is initiated, managed, and controlled by the (remote) NetBackup media server (for information about NetBackup terminology, see e.g. NetBackup User’s Guide or NetBackup Adminis-trator’s Guide) while the actual copy process is done on the CS800 by OST data replication. Replication can be done in the background very quickly (optimized) as it uses the CS800 data deduplication capabilities to reduce the copy bandwidth. The duplicate operation of NetBackup triggers the replication function in OST if both the source and destination volumes for the copy are OST disk volumes. OST optimized off host replication reduces the workload on the NetBackup media server because the copy process does not require host resources.

Requirements

For NetBackup to use OST off host optimized replication when image duplication is attempted, the following items are required:

● The source and destination storage units used for the copy are OST disk volumes created from OST shares on the CS800. Source and destination storage units could be created from the same CS800 or they could be located on different CS800 systems.

● The CS800 is running in a normal state.

OST Optimized Replication Configurations for NetBackup and OST Replication

138 U41840-J-Z125-1-76

● The source image is deduplicated completely and tags are generated for this file before optimized duplication is attempted.

● The target system must be configured to enable replication using NetBackup OST optimized copy (see Chapter "Data Services").

● NetBackup 6.5.3 or higher is running on the media server.

Initiating Optimized Copy

I The Life Cycle Policy Management policy of NetBackup allows the user to automate backup and copy operations. When this feature of NetBackup is used, copy operations will fail if the backup image is not deduplicated. Data deduplication takes time to finish after a backup is completed while Life Cycle Policy Management triggers copy operations immediately after a backup operation.

The source and target storage units could be on the same CS800 system or on a different CS800 system. If the copy is to a different CS800, ensure that there is connectivity from the source CS800 to the destination CS800.

The following steps assume that the storage units are located on different CS800 systems, though the same steps can be applied even for storage units on the same CS800.

1. Ensure that the source and target CS800 systems are running the latest CS800 software and NetBackup 6.5.3 or higher is running on the media server.

2. At the NetBackup media server (refer to the NetBackup Documentation):

a) Configure NetBackup media server for OST.

b) Install the OST client plug-in on the media server.

3. At the source and target CS800 systems:

a) Configure OST storage servers.

I If you are using Network Segmentation, you must use the Data IP address when registering a storage server.

b) Configure logical storage units.

4. Register source and target storage servers with NetBackup.

5. Configure source and target disk pools respectively from the storage servers registered in step 4 above.

6. Backup the required data set (refer to the NetBackup documentation for more infor-mation).

7. Once the backup is successfully completed, wait for the backup image to be completely deduplicated at the source CS800 system.

Configurations for NetBackup and OST Replication Initiating an OST Backup

U41840-J-Z125-1-76 139

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\8_

Co

nfig

urat

ion_

with

_N

etB

ack

up.fm

8. Select the backup images you want to duplicate

1. In the NetBackup Administration Console, expand the NetBackup Management Catalog.

2. Set up the search criteria for the image you want to duplicate.

3. Click Search Now.

9. Right-click an image you want to duplicate and select Duplicate from the shortcut menu. This will open a duplication window showing the default target storage units and other options. Change the target storage unit appropriately and continue with the copy. Repeat this for all the images to be replicated.

To check the status of the duplicate operation, read job details in the Activity Monitor from the NetBackup Administration Console.

I For versions of NetBackup prior to 6.5.4, no more than two optimized duplication streams per source CS800 to a target CS800 are supported.

I You must designate an OST storage unit as the destination for the duplication. Use the Storage Unit field in the Setup Duplication Variables dialog box.

I If the optimized duplication fails, the duplication will be attempted using the default duplication method used in versions of NetBackup prior to 6.5.4. With NetBackup 6.5.4, the administrator can control this failover using a configurable option. Refer to the Symantec Technote at http://seer.entsupport.symantec.com/docs/323669.htm for more information on this option.

Initiating an OST Backup

Please consult your Veritas NetBackup User’s Guide for information on creating a backup policy to backup data to your OST disk pool.

After the backup policies are configured, the process is as follows:

Backup Completes > Data Deduplication completes > Optimized Replication begins.

http://seer.entsupport.symantec.com/docs/323669.htm




Installing the OST Plug-In Configurations for NetBackup and OST Replication

140 U41840-J-Z125-1-76

Installing the OST Plug-In

I The OST Client Plug-in must be installed on the NetBackup media server configured with NetBackup 6.5.3 or later.

The OST Client Plug-in will be provided on a data medium which will be shipped together with the CS800. A README file is included which contains detailed instructions about the installation. The right OST plug-in variant depends on the operating system of your NetBackup Media Server.

Installation Procedure on a Windows NetBackup media server

Proceed as follows in order to install the OST clien plug-in:

1. Save the OST client plug-in files on the hard disk of your NetBackup media server.

2. If older OST plugins are already installed, uninstall them:

1. Wait until all the NetBackup jobs are finished, then stop the NetBackup processes (see the Netbackup Administrator Guide).

2. Go to Start > Control Panel > Add/Remove Programs and select ABC OST Plugin for Windows.

3. Click on the Remove button to start the uninstallation.

3. If your NetBackup media server operates with 64 bit Windows, then run the FTSOSTPluginWinX64.msi file you saved in step 1.

Else if your NetBackup media server operates with 32 bit Windows, then run the FTSOSTPluginWinX32.msi file you saved in step 1.

The installation wizard displays.

Figure 65: OST Plug-in Installation Wizard

Configurations for NetBackup and OST Replication Installing the OST Plug-In

U41840-J-Z125-1-76 141

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\8_

Co

nfig

urat

ion_

with

_N

etB

ack

up.fm

4. Follow the instructions given by the installation wizard to complete the installation.When you are asked to select the Backup Application, only select the checkbox for Symantec NetBackup.

Figure 66: OST Plug-in Installation – Select Backup Application

5. The installation ends with the Installation Complete screen. Click Close to exit.

Installation Procedure on a Linux NetBackup media server

OST plugins for RedHat Linux x86 are present in the FTSOSTPluginlinuxR_x86.32.tar file.

Proceed as follows in order to install the OST clien plug-in:

1. If older OST plugins are already installed, uninstall them first:

1. Wait until all the NetBackup jobs are finished, then stop the NetBackup processes (see the Netbackup Administrator Guide).

2. Remove older plugins by running the following command:

/bin/rm /usr/openv/lib/ost-plugins/libstspiFTS*

/bin/rm /usr/FTS/FTSPlugin.conf

2. Copy the FTSOSTPluginlinuxR_x86.32.tar file to the following directory:/usr/openv/lib/ost-plugins/

3. Change to that directory:cd /usr/openv/lib/ost-plugins/

4. Untar the files:/bin/tar xvf FTSOSTPluginlinuxR_x86.32.tar

5. Move the configuration file as follows:/bin/mkdir -p /usr/FTS; /bin/mv FTSPlugin.conf /usr/FTS

Now you can start NetBack processes to initiate backups and restores.

Installing the OST Plug-In Configurations for NetBackup and OST Replication

142 U41840-J-Z125-1-76

OST Plug-in Log

The OST Plug-in logs various messages to log files under: /var/log/ostlog/client directory on a Linux or Unix media server host and to %WINDIR%\libstspiFTS*.log on Windows.

Example

# tail -f /var/log/ostlog/client/ost_client.log

DEBUG - 20080725 16:12:43 15982 pgnapi.c:57 Plugin Prefix FTS claimed.

DEBUG - 20080725 16:12:43 15982 pgnapi.c:58 stspi_claim exited

DEBUG - 20080725 16:12:43 15982 pgnapi.c:754 stspi_get_server_prop_byname_v9 entered

DEBUG - 20080725 16:12:43 15982 comm.c:939 ostSendRequest: message:0x20000005

DEBUG - 20080725 16:12:43 15982 pgnapi.c:798 stspi_get_server_prop_byname_v9 exited

DEBUG - 20080725 16:12:43 15982 pgnapi.c:44 stspi_claim_v9 entered

DEBUG - 20080725 16:12:43 15982 pgnapi.c:57 Plugin Prefix FTS claimed.

DEBUG - 20080725 16:12:43 15982 pgnapi.c:58 stspi_claim exited

DEBUG - 20080725 16:12:43 15982 pgnapi.c:207 stspi_open_server_v9 entered

DEBUG - 20080725 16:12:43 15982 comm.c:939 ostSendRequest: message:0x20000002

OST Plug-in Configurable Options

The following OST Plug-in configurable options are supported:

Linux/Unix

The following Linux and Unix configurable options are supported:

1. DEBUG_LEVEL: Defines the level of logging to enable. The value of this option defines the level of log messages to output. It is set to one of the following values:

● EMERGENCY

● ALERT

Configurations for NetBackup and OST Replication Installing the OST Plug-In

U41840-J-Z125-1-76 143

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\8_

Co

nfig

urat

ion_

with

_N

etB

ack

up.fm

● CRITICAL

● ERROR

● WARNING

● NOTICE

● INFO

● DEBUG

By default, DEBUG_LEVEL is set to ERROR.

2. OPDUP_TIMEOUT:The Optimized copy option of NetBackup uses the replication feature of the OST server. The OST server replication feature cannot replicate unless the backup image file is deduplicated.On demand deduplication of the backup image file can take an unknown amount of time. OPDUP_TIMEOUT is the time in seconds to wait for deduplication of backup image file extent of 256 MB or smaller before giving up on the replication attempt.If the file copy extent length is larger than 256 MB, then the wait time will be a propor-tional multiple of OPDUP_TIMEOUT. For example, if the extent length is X*256 MB, wait time will be X*OPDUP_TIMEOUT, where X need not be an integer. By default, OPDUP_TIMEOUT is set to 180 seconds.

I This option is available only on Linux and Unix platforms. On Windows the timeout is fixed at 180 seconds.

To change the default value of any of these options, edit the /usr/FTS/FTSPlugin.conf file and set the desired values.

Windows

The following Windows configurable options are supported:

1. LOG_LEVEL: This is similar to the DEBUG_LEVEL on Linux and Unix. It defines the level of logging to enable. The value of this option defines the level of log messages to output.

● NONE - Disables logging for the logger.

● TRACE - Enables tracing to error messages.

● DEBUG - Enables debug to error messages.

● INFO - Enables information to error messages.

● WARN - Enables warning and error messages.

● ERROR - Enables only error messages.

Configuring the NetBackup Media Server Configurations for NetBackup and OST Replication

144 U41840-J-Z125-1-76

2. LOG_LIMIT: It defines the maximum file size (in byte) for the logger. Default size of the log file is 10MB. Increase this value if more logging has to be captured.Edit %WINDIR%\libstspiFTS*.ini to change the default values.

Configuring the NetBackup Media Server

Refer to the Veritas NetBackup User’s Guide for information about Veritas NetBackup instal-lation and basic configuration. Also, refer to the Veritas NetBackup Shared Storage Guide before proceeding further.

V You MUST have all NetBackup 6.5.3 or later updates applied (including the Java client) before continuing with configuration.

In addition to the basic configuration of the NetBackup media server, in Windows 2003 (32-bit and 64-bit) operating system, the following NetBackup services have to be logged in with administrative credentials:

● NetBackup Device Manager

● NetBackup Client Service

● NetBackup Remote Manager and Monitor Service

To login with administrative credentials:

1. Open the Services window.

2. Right-click the service and select Properties.

3. In the Properties window of the service, click Log on tab.

4. Select This Account Option and enter the administrative login name and password.

5. Click OK and restart the service to login with the new credentials.

Registering the Storage Server

NetBackup on a media server must get knowledge of the OST storage servers which have been created on a CS800 system in order to use the storage servers. This is done via a registration procedure on the NetBackup media server once the OST Client Plug-in is installed and the NetBackup media server is configured. On Windows platforms and with NetBackup 7.0 (and higher versions) the registration can be performed via NetBackup GUI. Alternatively and with NetBackup 6.5.3 or 6.5.4 registration is done via the command line interface (CLI). On Unix/Linux platforms the registration is also performed via CLI.

Configurations for NetBackup and OST Replication Registering the Storage Server

U41840-J-Z125-1-76 145

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\8_

Co

nfig

urat

ion_

with

_N

etB

ack

up.fm

Registering the Storage Server on Windows Platforms via NetBackup 7.0 GUI

To register the storage server on a Windows NetBackup media server platform where NetBackup 7.0 or higher is running, perform the following steps:

1. Start the NetBackup GUI by double-clicking the NetBackup Administration Console icon.

2. Start the Storage Server Configuration Wizard by selecting the Configure Disk Storage Servers from the NetBackup Adminstration Console (see Figure 67).

Figure 67: Storage Server Configuration Wizard.

3. Click Next (see Figure 68) on the bottom of the Welcome screen to continue.

Registering the Storage Server Configurations for NetBackup and OST Replication

146 U41840-J-Z125-1-76

Figure 68: Storage Server Configuration Wizard

4. On the Add Storage Server page, select OpenStorage as the type of disk storage to configure and click Next to continue.

Figure 69: Add Storage Server Page


U41840-J-Z125-1-76 147

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\8_

Co

nfig

urat

ion_

with

_N

etB

ack

up.fm

5. On the next Add Storage Server page enter details and credentials:

● Storage server type: FTS

● Storage server name: ssn01_172.25.182.41

I You must include both the name and IP address of the storage server separated by an underscore.

I If the CS800 is configured with network segmentation, the data IP address should be used to register the storage server.

● Select Media Server: efm-nbu02

Select a Media Server with the OST plug-in installed.

● User Name

● Password

● Confirm Password

I The username and password should match the credentials to your Windows Active Directory or workgroup account as configured in the CS800 remote management pages.

Figure 70: Add Storage Server Page – Details


148 U41840-J-Z125-1-76

I No message displays if the credentials are added successfully. However, an error message displays if the credentials are incorrect.

I If you are using Windows Active Directory, both the NetBackup Media Server and the CS800 must be on the same domain.

6. Click Next to continue.

7. The Configure Additional Media Servers page displays. Click Next to continue (no additional Media Servers).

8. The Storage Server Configuration Summary page displays. To execute the configu-ration of the storage server click Next.

Figure 71: Storage Server Configuration Summary Page

9. During the execution of the configuration process the Storage Server Creation Status page shows the task performed.

10. Click Next to continue when demanded.

11. After the message is displayed that the storage server is successfully created, click Close to finish and close the wizard.Alternatively you can click Next to continue with the wizard for Disk Pool creation which is described in "Configuring Disk Pools and Storage Units" on page 152.


U41840-J-Z125-1-76 149

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\8_

Co

nfig

urat

ion_

with

_N

etB

ack

up.fm

Registering the Storage Server on Windows Platforms via CLI

To register the storage server on a Windows NetBackup media server platform, perform the following steps:

1. Add the storage server to NetBackup:

C:\Program Files\Veritas\NetBackup\bin\admincmd\nbdevconfig -creatests -storage_server <storage_server_name_ip> -stype FTS -media_server <media_servername> -st 9

Example: Add a storage server by name nbussn and a media server by name nbumedia.

C:\Program Files\Veritas\NetBackup\bin\admincmd\nbdevconfig -creatests -storage_server nbussn_192.168.1.100 -stype FTS -media_server nbumedia -st 9

I When specifying the -storage_server variable (passed to the nbdevconfig command), you must include both the name and IP address of the storage server separated by an underscore. For example: nbussn_192.168.1.100

I If the CS800 is configured with network segmentation, the data IP address should be used to register the storage server.

I A message from the prompt indicates that the storage server was added successfully. Otherwise, an error message is displayed.

2. Add credentials of the storage server:

C:\Program Files\Veritas\Volmgr\bin\tpconfig -add -storage_server <storage_server_name_ip> -stype FTS -sts_user_id <username> -password <password>

Example: Add credentials for storage server nbussn.

If the credentials belong to Workgroup User:

C:\Program Files\Veritas\Volmgr\bin\tpconfig -add -storage_server nbussn_192.168.1.100 -stype FTS -sts_user_id Administrator -password password

If the credentials belong to Active Directory User:

C:\Program Files\Veritas\Volmgr\bin\tpconfig -add -storage_server nbussn_192.168.1.100 -stype FTS -sts_user_id XYZ\user1 -password password

I When specifying the -storage_server variable, you must include both the name of the storage server defined in teh ETERNUS CS8000 storage server configuration and the IP address of the ETERNUS CS800 separated by an underscore. For example: nbussn_192.168.1.100

I No message displays if the credentials are added successfully. However, an error message displays if the credentials are incorrect.


150 U41840-J-Z125-1-76

I If you are using Windows Active Directory, both the NetBackup Media Server and the CS800 must be on the same domain.

I The username and password should match the credentials to your Windows Active Directory or workgroup account as configured in the CS800 remote management pages.

Verifying the LSU Discovery

After you have registered the storage server, verify the discovery of LSUs by performing the following step:

1. From the command line on the master server, type:

<install path>\netbackup\bin\admincmd\nbdevconfig –previewdv -stype FTS –storage_server <storage_server_name_ip>

Example: verify LSU discovery for storage server nbussn.

C:\Program Files\Veritas\NetBackup\bin\admincmd>nbdevconfig -previewdv -stype FTS -storage_server nbussn_192.168.1.100

I When specifying the -storage_server variable, you must include both the name and IP address of the storage server separated by an underscore. For example: nbussn_192.168.1.100

This will show if the LSU has been discovered by NetBackup and if the password is correct.

Registering the Storage Server on Unix/Linux Platforms

To register the storage server on Solaris or Linux NetBackup media server platforms:

1. Add the storage server to NetBackup by executing the following command on the NetBackup media server as root:

/usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server <storage_server_name_ip> -stype FTS -media_server <media_servername> -st 9

Example: Adding a storage server by name nbussn and a media server by name nbumedia.

/usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server nbussn_192.168.1.100 -stype FTS -media_server nbumedia -st 9

I When specifying the -storage_server variable (passed to the nbdevconfig command), you must include both the name and IP address of the storage server separated by an underscore. For example: nbussn_192.168.1.100


U41840-J-Z125-1-76 151

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\8_

Co

nfig

urat

ion_

with

_N

etB

ack

up.fm

I If the CS800 is configured with network segmentation, the data IP/hostname should be used to register the storage server.

I A message from the prompt indicates that the storage server was added successfully. Otherwise, an error message is displayed.

2. Add the credentials of the storage server:

/usr/openv/volmgr/bin/tpconfig -add -storage_server <storage_server_name> -stype FTS -sts_user_id root -password <password>

Example: Adding credentials for storage server nbussn.

/usr/openv/volmgr/bin/tpconfig -add -storage_server nbussn_192.168.1.100 -stype FTS -sts_user_id root -password password

I When specifying the -storage_server variable, you must include both the name and IP address of the storage server separated by an underscore. For example: nbussn_192.168.1.100

I No message displays if the credentials are added successfully. But an error message displays if the credentials are incorrect.

Verifying the LSU Discovery

After you have registered the storage server, verify the discovery of LSUs by performing the following step:

1. From the command line on the master server, type:

/usr/openv/netbackup/bin/admincmd/nbdevconfig –previewdv –stype FTS –storage_server <storage_server_name_ip>

Example: Verify LSU discovery for storage server nbussn.

/usr/openv/netbackup/bin/admincmd/nbdevconfig –previewdv –stype FTS –storage_server nbussn_192.168.1.100

I When specifying the -storage_server variable, you must include both the name and IP address of the LSU separated by an underscore. For example: nbussn_192.168.1.100

This will show if the LSU has been discovered by NetBackup and if the password is correct.

Configuring Disk Pools and Storage Units Configurations for NetBackup and OST Replication

152 U41840-J-Z125-1-76

Configuring Disk Pools and Storage Units

After the Storage Server has been registered to NetBackup, disk pools and storage units have to be configured in NetBackup. Proceed as follows:

1. Start the NetBackup GUI:

● In Windows, double-click the NetBackup Administration Console icon.

● In Solaris and Linux, run the following command:/usr/openv/NetBackup/bin/jnbSA &

2. Start the Disk Pool Configuration Wizard that appears in the right-hand pane of the console by clicking Configure Disk Pool.

3. The Disk Pool Configuration Wizard displays (see Figure 72).Click Next to continue.

Figure 72: Starting the Disk Pool Configuration Wizard

4. Select OpenStorage (FTS) for the disk pool type to create and click Next.

5. The Select Storage Server screen displays (see Figure 73).

Configurations for NetBackup and OST Replication Configuring Disk Pools and Storage Units

U41840-J-Z125-1-76 153

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\8_

Co

nfig

urat

ion_

with

_N

etB

ack

up.fm

Figure 73: Select Storage Server Screen

6. Select the storage server that you have previously registered the NetBackup media server and click Next. The Select Volume screen displays (see Figure 74).

Figure 74: Select Volume Screen


154 U41840-J-Z125-1-76

7. Select an LSU and click Next.

8. In the following screen, enter a name for disk pool, provide details and click Next.

Figure 75: Disk Pool Properties

9. A summary of your disk pool configuration is displayed. Check if the information is correct and click Next.

10. After the disk pool has been created successfully, click Next.

11. Select the Create a Storage Unit that uses… check box and click Next. The Storage Unit Creation screen displays.

12. Enter details to create a NetBackup Storage Unit:

● Enter a name for the storage unit. Configure the Maximum concurrent jobs and Maximum fragment size field to your backup specifications.

Configurations for NetBackup and OST Replication Configuring Disk Pools and Storage Units

U41840-J-Z125-1-76 155

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\8_

Co

nfig

urat

ion_

with

_N

etB

ack

up.fm

Figure 76: Storage Unit Creation

13. Click Next. The Finished screen displays.

The Disk Pool is now fully configured and ready for use. You may view or change current configuration settings within Device Management or Storage Unit Management.

Configuring Spanning on Disk Pools

If you configure disk pools using multiple LSUs, you MUST enable the image spanning attribute on both the storage server and the disk pools. Enabling image spanning allows full use of the disk pool storage capacity.

Use the following NetBackup commands to enable image spanning:

nbdevconfig -changests -storage_server <storage_server_name_ip> -stype FTS -setattribute SpanImages

nbdevconfig -changedp -dp <disk_pool_name> -stype FTS -setattribute SpanImages

I When specifying the -storage_server variable, you must include both the name and IP address of the LSU separated by an underscore. For example: nbussn_192.168.1.100


156 U41840-J-Z125-1-76

U41840-J-Z125-1-76 157

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

9_S

tatu

s.fm

CS800 StatusThe Status pages allow you to view information on the ETERNUS CS800 hardware as well as performance information. The status information is polled by the system every two minutes.

To access the Status pages, from the contents frame, click the Status menu.

Use the Status pages to view the following status information:

● "Hardware"

● "Summary"

● "Details"

● "System"

● "CPU"

● "RAID"

● "Ethernet"


● "Ingest"

● "Disk Usage"

Hardware

The ETERNUS CS800 provides a variety of hardware information from the Hardware page. The Hardware page gives the current status of the CS800 and its components such as the hard drives, power supplies, fan modules, and temperature of the system board compo-nents.

To access the Hardware page, from the Status menu, click the Hardware tab.

The Hardware Status page contains the following tabs:

● "Summary"

● "Details"

Hardware CS800 Status

158 U41840-J-Z125-1-76

Summary

The Summary page displays the status of the CS800 and its components. The overall status information for each component is reported as Normal, Attention, or Failed.

To access the Summary page:

1. From the Hardware page, click the Summary tab.

The Summary page displays (see Figure 77); the Node 1 area shows components of the CS800 server:

Figure 77: Hardware Summary Page

2. Click a component link to display detailed information for that component.

Details

Use the Details page to view detailed information for each component. To access the Details page, from the Hardware page, click the Details tab.

The Details page contains the following tabs:

● Node 1 - View hardware details for the following components of the CS800 server:

● "System Board"

CS800 Status Hardware

U41840-J-Z125-1-76 159

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

9_S

tatu

s.fm

● "FC Adapters"

● "Network Ports"

● Common - View hardware details for the following components:

● "Storage Arrays"

To view hardware details for a component, click the appropriate tab on the Node 1 or Common page.

System Board

The CS800 server contains a system board that provides the following types of information:

● System temperature

● CPU temperature

● System voltages

● Fan status

● Power supply status

The status for each component is shown in the Status column:

● Normal - The component is operating within normal operating parameters.

● Attention - The component passed the attention threshold. Action may be required on the system.

● Warning - The component has passed the warning threshold and requires attention.

● Failure - The component has failed.

● NA - The node (CS800 server) has been removed.

● Down - The node is not connected.

FC Adapters

The CS800 server contains several Fibre Channel adapters (depending on the configu-ration), each with two Fibre Channel ports.

Each Fibre Channel adapter is shown in the Name column. The status for each adapter is shown in the Status column.

● Normal - The Fibre Channel adapter is operating within normal operating parameters.

● Failure - The Fibre Channel adapter has failed and must be replaced.

The port status is shown for each Fibre Channel adapter. The port Name is shown as well as the Value. The Value shows the current throughput capacity in MB/s.

System CS800 Status

160 U41840-J-Z125-1-76

The port can have one of the following statuses:

● Up - The port is connected.

● Down - The port is not connected.

Network Ports

Each CS800 node contains several Ethernet ports (depending on the configuration). Each Ethernet port is shown in the Name column. The speed of the port is shown in the Value column. The status for each port is shown in the Status column.

● Up - The port is connected.

● Down - The port is not connected.

Storage Arrays

All storage arrays, components, and controllers in the system appear in the Name column. The status for each array is shown in the Status column.

● Normal - The array is operating within normal operating parameters.

● Failure - The array has failed and requires attention.

● Missing - The array has been removed.

● Attention - The array is operable but performance is degraded.

Click an array link to display the components for that array. Click a component link to display the status for that component.

System

To access the System page, from the Status menu, click the System tab.

The System page provides performance information for the following components:

● "CPU"

● "RAID"

● "Ethernet"


● "Ingest"

● "Disk Usage"

CS800 Status System

U41840-J-Z125-1-76 161

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

9_S

tatu

s.fm

CPU

To access the CPU performance page:

1. From the System page, click the CPU tab.

The CPU page displays (see Figure 78):

Figure 78: CPU Page

The CPU page displays the system CPU performance in a dynamic graph.

● Horizontal axis (Seconds): 100 – 0 seconds

● Vertical axis (Data in Percentage): 0 – 100%.

● Vertical bars represent approximately 1 second intervals.

● Moving your mouse over a bar will display its value.

You can monitor a specific CPU or an average of CPUs by selecting an option in the CPU drop down box.

System CS800 Status

162 U41840-J-Z125-1-76

RAID

To access the RAID performance page:

1. From the System page, click the RAID tab.

The RAID page displays (see Figure 79):

Figure 79: RAID Page

The RAID page displays the system RAID performance in a dynamic graph.


● Vertical axis (Amount of Read/Write): 0 – 100 OPS/sec.

● Values exceeding the vertical axis max are shown in brighter green.



CS800 Status System

U41840-J-Z125-1-76 163

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

9_S

tatu

s.fm

Ethernet

To access the Ethernet performance page:

1. From the System page, click the Ethernet tab.

The Ethernet page displays (see Figure 80):

Figure 80: Ethernet Page

The Ethernet page displays the system Ethernet performance in a dynamic graph.


● Vertical axis (Data in MB): 0 – 125 MB/sec.




You can monitor a specific port or an average of ports by selecting an option in the Ethernet drop down box.

System CS800 Status

164 U41840-J-Z125-1-76

Data Deduplication

The Data Deduplication page displays the data deduplication performance for the system

To access the Data Deduplication performance page:

1. From the System page, click the Data Deduplication tab.

The Data Deduplication page displays (see Figure 81):

Figure 81: Data Deduplication Page

The Data Deduplication page displays the system data deduplication performance in a dynamic graph.

● Horizontal axis (Minutes): 60 – 0 minutes.

● Vertical axis (Data in MB): 0 – 111 MB/s

● Vertical bars represent 1 minute intervals.


You can select the time period to view from the Last drop down box.

CS800 Status System

U41840-J-Z125-1-76 165

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

9_S

tatu

s.fm

Ingest

The Ingest page displays the throughput performance for the system.

To access the Ingest performance page:

1. From the System page, click the Ingest tab.

The Ingest page displays (see Figure 82):

Figure 82: Ingest Page

The Ingest performance page provides the following information for the system:


● Vertical axis (Data in MB): 0 – 1000 MB/sec.




System CS800 Status

166 U41840-J-Z125-1-76

Disk Usage

To access the Disk Usage performance page:

1. From the System page, click the Disk Usage tab.

The Disk Usage page displays (see Figure 83):

Figure 83: Disk Usage Page

The Disk Usage page provides the following information for the system:

● "Available (System Capacity)"

● "Used (System Capacity)"

● "Data Reduction"

Available (System Capacity)

Available space is the area that is available for data storage. The Available value is displayed as an amount and as a percentage of the total capacity in the system.

Available space is divided into the following categories:

● Free Space - This area is available for data storage.

CS800 Status System

U41840-J-Z125-1-76 167

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

9_S

tatu

s.fm

● Cached data eligible for truncation - After data is deduplicated, the native format is cached to allow for higher performance should you need to read the data back. When necessary, the system will automatically begin to delete some of this cached data in order to increase free space. The process of deleting this cached data is called truncation (see "Space Management" on page 177).

Used (System Capacity)

Used space is the area that already holds data. The Used value is displayed as an amount and as a percentage of the total capacity in the system.

Used space is divided into the following categories:

● Deduplicated data - The amount of data that has already been deduplicated.

● Data waiting to be deduplicated - The amount of data that is waiting to be dedupli-cated.

● Data not intended for data deduplication - The amount of data that will NOT be deduplicated.

● System metadata - The area on the system that is occupied by the system metadata.

Data Reduction

The data reduction area displays the data reduction performance for the system. Data reduction is divided into the following categories:

I Since these values are calculated as data is deduplicated and compressed, they will not be completely up-to-date until all data that is eligible for deduplication is processed by the data deduplication and compression engines.

● Total Data Reduced - The original, native size of all existing data that has been processed by the data deduplication and compression engines.

● Data Deduplication Ratio - The deduplication ratio of all existing data that has been processed by the data deduplication engine.

● Compression Ratio - The compression ratio of all existing data that has been processed by the data deduplication and compression engines.

● Total Reduction Ratio - The total reduction ratio of all existing data that has been processed by the data deduplication and compression engines (calculated by dividing Total Data Reduced by Reduced Size).

● Reduced Size - The final, reduced size of all existing data that has been processed by the data deduplication and compression engines.

System CS800 Status

168 U41840-J-Z125-1-76

U41840-J-Z125-1-76 169

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\10

_Ale

rts.

fm

CS800 AlertsUse the Alerts page to view administrator alerts (admin alerts) and service tickets. These alerts are generated by the system when hardware or software events have occurred.

To access the Alerts page, from the contents frame, click the Alerts menu.

The Alerts page contains the following tabs:

● "Admin Alerts"

● "Service Tickets"

Admin Alerts

Admin alerts are generated by the system when the condition of the system has changed, such as going from the offline state to the online state.

I You must complete e-mail configuration (see "Email Configuration" on page 122) before administrator alerts can be sent.

To access the Admin Alerts page:

1. From the Alerts page, click the Admin Alerts tab.

The Administration Alerts page displays (see Figure 84):

Admin Alerts CS800 Alerts

170 U41840-J-Z125-1-76

Figure 84: Administration Alerts Page

The Administration Alerts page displays administration alerts for the ETERNUS CS800 (see Table 36).

I You can click the Alert, Last Update, and Summary column headings to sort the rows in the report by the data in the respective column. Click the column heading again to invert the sorting sequence from ascending order to descending order.

Table 36: Administration Alerts Columns

Column Description

Alert Name of the admin alert. Click the link to see the activity status history for the admin alert.

Last Updated Date when the admin alert was last opened or closed.

Summary Summary description of the admin alert.

Delete Click to delete the selected admin alert.

CS800 Alerts Service Tickets

U41840-J-Z125-1-76 171

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\10

_Ale

rts.

fm

Service Tickets

When an event in the ETERNUS CS800 is detected, it is reported to one of the monitoring daemons. The monitoring daemon reports the event to the service daemon. The service daemon then logs the event and applies additional logic to determine whether the event warrants a service ticket.

If the event is not critical, the process for the event is completed. If the event is critical, the service daemon creates and logs a service ticket and notifies the user interface that a new service event needs attention. If the CS800 detects that the problem is resolved, the ticket is closed. If the user indicates that the problem has been resolved, the ticket can be closed manually. At this point, the service daemon updates the ticket database and notifies the CS800 Web pages.

I Tickets that are not resolved are generated again after 24 hours. You must complete e-mail configuration (see "Email Configuration" on page 122) before service tickets can be sent.

To help users determine the criticality of events occurring in the CS800, service tickets grade events as Low, Middle, or High severity.

● Low (green) - An event has occurred which needs to be resolved, but it generally does not affect the operation or performance of the CS800.

● Middle (yellow) - A more serious event has occurred which needs to be resolved, but it does not necessarily need to be fixed immediately. The operation and performance of the CS800 may be degraded.

● High (red) - A critical event has occurred which needs to be resolved immediately. The operation and performance of the CS800 is degraded and there is a risk of impending system failure or data loss.

Service tickets or recommended action tickets (RAS) provide guidance to users on how to resolve certain events in the CS800. Some service tickets (and associated recommended actions files) guide users through a series of steps that may resolve the problem prior to contacting Fujitsu customer support.

The procedures described in system status tickets are intended to be performed by users who are familiar with the CS800. At any time, a user may contact Fujitsu customer support for assistance.

Viewing Service Tickets

Viewing service tickets can be performed by users with the following access privilege:

● Monitor

● Administrator

Service Tickets CS800 Alerts

172 U41840-J-Z125-1-76

To view service tickets:

1. From the Alerts page, click the Service Tickets tab.

The Service Tickets page displays (see Figure 85):

Figure 85: Service Tickets Page

The Service Tickets page lists the information described in Table 37.

I You can click the Ticket, Request ID, State, Priority, Last Update, and Details column headings to sort the rows in the report by the data in the respective column. Click the column heading again to invert the sorting sequence from ascending order to descending order.


U41840-J-Z125-1-76 173

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\10

_Ale

rts.

fm

Table 37: Service Tickets

2. To view details for a ticket, click the ticket number.

The Ticket Details display at the bottom of the screen (see Figure 86).

Figure 86: Ticket Details

Column Description

Ticket Service ticket numbers.

Request ID Request ID for the ticket.

State Current status of the service ticket (Open or Closed).

Priority Severity level of the problem described in the service ticket (Low, Middle, or High).

Last Updated Date when the service ticket was last opened or closed.

Details Summary description of the problem reported by the CS800.

Ticket details


174 U41840-J-Z125-1-76

The Ticket Details area lists the service ticket number, date and time when the ticket was last accessed (either opened or closed), ticket status (open or closed), a summary of the problem, and detailed information about the problem.

I The time indicated in the service ticket may not match the CS800 system time.

Most service tickets also include a View Recommended Actions link. Click the link opens a separate window with recommended steps to resolve the problem. To close the window, click x in the upper right corner.

I For information on analyzing service tickets and obtaining additional information about a reported problem, see "Modifying Service Tickets".

Figure 87 shows a sample Recommended Actions window.

Figure 87: Recommended Actions Window

Modifying Service Tickets

Modifying service tickets can be performed by users with this access privilege:

● Administrator

Use this procedure to add information to a service ticket related to system troubleshooting and to view the current status of a problem reported by the CS800. All modified entries are kept with the ticket number and ticket summary when the service ticket is closed.


U41840-J-Z125-1-76 175

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\10

_Ale

rts.

fm

1. View a service ticket and show the ticket details.

See "Viewing Service Tickets" on page 171.

2. Click Analysis.

The Ticket Analysis page displays.

3. Enter all relevant information regarding actions taken to resolve the issue, click Apply.

Sending Service Tickets by E-mail

Sending service tickets by e-mail can be performed by users with this access privilege:

● Administrator

CS800 service tickets can be sent to a designated recipient via e-mail. Optionally, the sender can include a comment about the service ticket with the e-mail message.



2. Select a service ticket to send by e-mail and click Email.

a) In the Email Recipient box, enter an e-mail address where the service ticket should be sent.

b) (Optional) In the Comment box, enter a comment to send with the service ticket.

c) Click Send.

Closing Service Tickets

Closing service tickets can be performed by users with this access privilege:

● Administrator

Use this procedure to close a service ticket.

I You can analyze a service ticket after it has been closed (see "Modifying Service Tickets" on page 174).



2. Click Analysis.

The Ticket Analysis page appears.

3. Select the Close Ticket check box.

4. Click Apply to close the service ticket.


176 U41840-J-Z125-1-76

U41840-J-Z125-1-76 177

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\11

_D

ata

_Se

rvic

es.

fm

Data ServicesUse the Data Services pages to configure space management and configure the system replication capability.

To access the Data Services pages, from the contents frame, click the Data Services menu.

The Data Services pages contain the following tabs:

● "Space Management"

● "Data Replication"

Space Management

When data deduplication is enabled on the ETERNUS CS800, it is not possible to accurately predict the amount of storage space required because the data deduplication process depends on the type of data being stored. This makes it necessary to define storage space thresholds so the user can be notified when storage space begins to run low. Space management provides the ability to monitor the storage space available on the system and notify the user if storage space begins to run low.

I When a “low-disk-space” condition occurs on a system, the current system will pause its replication activity and any source systems that are currently replicating to this system are paused. When the “low-disk-space” condition ends, the current system will resume its replication activity and the source systems that were replicating to this system resume.

To access the Space Management page, from the Data Services menu, click the Space Management tab.

The Space Management page contains the following tabs:

● "General"

● "Schedule"

General

Use the General page to start or stop space reclamation and to monitor the progress of space reclamation.

To run space reclamation:

Space Management Data Services

178 U41840-J-Z125-1-76

1. From the Space Management page, click the General tab.

The General page displays (see Figure 88).

Figure 88: Space Management General Page

2. To run space reclamation immediately, click Start.

The space reclamation process begins immediately. The Status section displays the space reclamation status.

The Space Reclaimed value indicates the amount of space that has been reclaimed so far during the active space reclamation process. If space reclamation is not running, the Space Reclaimed value indicates the amount of space reclaimed by the previous space reclamation.

I The space reclamation process will effect system performance. If possible, ensure that space reclamation occurs when the system is idle.

3. To stop a reclamation in process, click Stop.

The status of space reclamation can be:

● Reclamation Completed - Space reclamation has completed without errors.

● Reclamation Started by User - Space reclamation has been started manually by a user.

Data Services Space Management

U41840-J-Z125-1-76 179

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\11

_D

ata

_Se

rvic

es.

fm

● Reclamation Interrupted - Space reclamation has been interrupted. Space recla-mation must be restarted.

● Reclamation Interrupted by User - Space reclamation has been interrupted by a user. Space reclamation must be restarted.

● Reclamation Interrupted - Error Encountered - Space reclamation has been interrupted because an error was encountered. Space reclamation must be restarted.

● Reclamation Completed - No Candidates To Delete = Space reclamation completed, but there were no candidates for reclamation.

● Reclaim Existing Blockpool Freed space - The existing blockpool space has been reclaimed for use.

● Stage 1 of 4 - Delete Existing Candidates

● Stage 2 of 4 - Calculating Deletion Candidates

● Stage 3 of 4 - Delete New Candidates

● Stage 4 of 4 - Reclaim disk space

Schedule

The block pool data area of the CS800 is used to store tags that reference deduplicated and replicated data. Tags are used to rebuild a deduplicated file if it needs to be recovered. If this deduplicated or replicated data has been deleted from the system, the tags need to be removed from the block pool so the space can be used for additional reference tags.

To schedule space reclamation:

1. From the Space Management page, click the Schedule tab.

The Schedule page displays (see Figure 89).

Data Replication Data Services

180 U41840-J-Z125-1-76

Figure 89: Schedule Page

Use the Schedule page to schedule periodic space reclamation either daily or weekly.

2. To schedule periodic space reclamation:

a) Select Daily or Weekly and set the day and time information.

Or to disable periodic space reclamation, select No Schedule.

b) Click Apply.

The schedule information is set.

Data Replication

I The information in this section applies to native NAS replication. OST optimized duplication using NetBackup is described separately (see "OST Optimized Replication").

The CS800 can be configured to automatically replicate data on another CS800 system as part of a disaster recovery plan. Replication is the process of sending a deduplicated data copy from a source NAS share to a target NAS share. This process is configurable on a per

Data Services Data Replication

U41840-J-Z125-1-76 181

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\11

_D

ata

_Se

rvic

es.

fm

NAS share basis. The source system must have replication enabled. The target system can store replicated NAS share data for one or more source systems. A system can be both a source (NAS share sending replicated data) and target (receiving replicated data).

Configuring Replication for the First Time

For a new CS800 installation, or immediately after a new share has been created, be sure to replicate the namespace (using the on demand Replicate Now function, see Step 7 on page 225) for each share as soon as it is created and before any data is written to it.

This action establishes the namespace structure on the target. Establishing the namespace structure before any data is written will expedite the first replication that occurs after the first backup.

Failure to replicate the empty namespace is not fatal, but the speed of the first replication after the first backup will be up to twice as fast if you did replicate the empty namespace. This could be especially important when backing up a significant amount of data.

Replication Configuration Steps

Configuring Replication consists of the following steps:

1. Before data can be replicated from a source system to a target system, the target must be authorized to receive data from a specific source. To authorize a target system to receive data from a source, you must add the source host name or IP address to the Source Host List on the target system (see "Target Role" on page 190).

2. Once you have added the source system hostname or IP address to the target system, you must add the target system hostname or IP address to the source system. The source system can only replicate data to one target (see "Source Role" on page 183).

3. Now that both the target and source systems are setup for replication, you can enable replication and either schedule the replication process or manually replicate a share (see "Source Role NAS" on page 185).

Directory/File Based Replication

Directory/File Based Replication, when configured, automatically replicates file data without user intervention or a schedule. The replication is triggered by a CLI command for file data (NAS share). This greatly enhances replication performance since only the file data in a NAS share that has changed will be replicated instead of the entire NAS share.

Data Replication Data Services

182 U41840-J-Z125-1-76

After Directory/File Based Replication, NAS share files are automatically recovered on the Target system. You may also initiate a synchronization from the Source system to the Target system on NAS shares that have been configured for Directory/File Based Repli-cation. This will replace all files on the Target NAS share with the most up to date files on the Source system.

Directory/File Based Replication NAS Configuration Steps

Configuring Directory/File Based Replication consists of the following steps:

● On the Target system, create a new NAS share with the EXACT name as the NAS share on the Source system.

● On the Target system, access the Directory/File Based Targets page and set the share Sync ID. The Sync ID is used to synchronize the Source Role NAS share with the Target Role NAS share (see "Target Role NAS Directory/File Target Configuration" on page 194).

● On the Source system, edit the NAS share that is enabled for replication and enter the Sync ID previously configured on the Target system (see "Source Role NAS" on page 185).

● Your system is configured for NAS Directory/File Based Replication.

Replication Requirements

The following list provides requirements for replication:

● Only NAS shares with data deduplication enabled can be replicated.

● One to one replication only (a NAS share cannot be replicated to more than one target NAS share).

● All source NAS shares must replicate to the same target system.

● All files that are in use in a NAS share during replication are skipped.

● The Target system must specify which Source systems (up to 10) it will accept repli-cated data from.

I For optimization purposes, the underlying data is continuously updated and will become available when the replication is either run manually or using a scheduled replication.

Data Services Source Role

U41840-J-Z125-1-76 183

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\11

_D

ata

_Se

rvic

es.

fm

Data Transmission

Once a data set has been deduplicated, it may be replicated (non-redundant data is trans-mitted from a source system to a target). Data deduplication tags representing files with a high probability of being replicated (for example, NAS shares marked for replication) are queued for replication after data deduplication is complete without regard to the replication schedule. This continuous transmission of data is an optimization allowing replication to be used with low bandwidth networks.

Replication Set Transmission and Accounting

When a replication set is scheduled for transmission, the system scans the files comprising the replication set and a namespace file is created. A namespace file contains the complete set of data deduplication tags for the replication set. Data that is active (a NAS file that is open) or data that is not yet deduplicated is not included in the namespace file. The namespace file is then deduplicated and transmitted to the target system after the data transmission of the replication set is complete. Once both the replication set and namespace file have been transmitted to the target system, the replication can be recovered.

Accessing Replication

To access the Replication page, from the Data Services menu, click the Replication tab.

The Replication page contains the following tabs:

● "Source Role"

● "Source Role NAS Directory/File Based Replication Configuration"

● "Target Role"

● "Target Role NAS Directory/File Target Configuration"

● "Reports"

Source Role

Use the Source Role page to define the NAS shares that will be replicated and the target that will receive the replicated data.

I You must configure the target system prior to configuring the source. If the target system is not configured first, you will not be able to designate the replication target.

Source Role Data Services

184 U41840-J-Z125-1-76

I You MUST have at least one NAS share created on the source before you can configure it for replication.

I If you need to add, delete or change a replication target, you must first pause replication from the Source Role - Actions page. After the replication target has been changed, you must resume replication from the Source Role - Actions page.

Source Role General

To configure the source system for replication:

1. From the Replication page, click the Source Role tab.

The Source Role General page displays (see Figure 90).

Figure 90: Source Role General Page

2. Enter the hostname or IP address for the replication target and click Apply.

Use Encryption is selected by default. When Use Encryption is enabled, data that is replicated is encrypted before it is replicated to another system. If your data network is already secured, disable Use Encryption for increased replication performance.


U41840-J-Z125-1-76 185

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\11

_D

ata

_Se

rvic

es.

fm

Source Role Performance

The Source Role Performance information on the bottom of the Source Role General page displays the following statistics:

● Total Data Sent - This field indicates the original, native size of the data transferred during replication or failback. This does not indicate the actual number of bytes sent over the network during replication or failback.

● Total Bytes Sent - This field indicates the actual number of bytes transferred over the network during replication or failback, and is usually much less than the native size due to the benefits of data deduplication.

● Average Send Rate - This field is based on the actual number of bytes transferred over the network during replication or failback. They are a measure of the total, number of bytes sent (in MB/s) divided by the amount of time required to complete the replication or failback job(s).

Source Role NAS

Use the Source Role NAS page to select and configure NAS shares for replication.

To replicate NAS shares:

1. From the Source Role page, click the NAS tab.

The Source Role NAS page displays (see Figure 91).


186 U41840-J-Z125-1-76

Figure 91: Source Role NAS Page

The Source Role NAS page displays the available NAS shares that have been dedupli-cated. The page also displays the current replication status for the share and infor-mation on the most recent replication that was run.

I The Last Replication and Last Synchronization columns display status information only for the most recent manual replication or synchronization. To view status information for Directory/File Based Replication, use the File Based Queue page (see "Source Role NAS File Based Queue" on page 187). To view complete replication history, generate a replication report (see "Reports" on page 197).

The replication status can display the following states:

● In Progress - The replication job is in progress.

● Partial - The replication job was partially completed. Refer to the log file to view the files that were not replicated.

● Queued and Waiting - The replication job is queued and waiting for another job to complete before beginning.

● Success - The replication job was completed successfully.


U41840-J-Z125-1-76 187

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\11

_D

ata

_Se

rvic

es.

fm

● Failure - The replication job was not completed.

The synchronization status can display the following states:

● Queued - Synchronization has been queued and will continue when ready.

● Success - Synchronization has completed successfully.

● Recovering - The recover operation is in process.

● Replicating - The replication operation is in process.

● Failed - Synchronization has failed.

The Information page displays during a replication in progress or a replication successfully completed. The Information page displays the amount of data transferred as well as the average MB/s for a replication job.

2. To enable or disable replication on the share, or to schedule a replication time, select the share and click Edit.

3. To manually run the replication process, select the share and click Replicate/Abort.

V If a node fails during a replication job, the replication job must be restarted.

The NAS share replication process begins. The status of the current replication displays in the Status area.

4. To abort the replication, click the Replicate/Abort button.

5. To synchronize the NAS share configured for Directory/File Based Replication, click Synchronize/Abort. The system will update all files in the share.

I Only NAS shares enabled for Directory/File Based Replication may be synchronized.

6. To abort the synchronization, click Synchronize/Abort.

Source Role NAS File Based Queue

To access the File Based Queue page:

1. Select a share and click File Based Queue at the bottom of the Source Role NAS page.

The system displays Directory/File Based Replication statistics for data sent to the target system.

I The contents of the File Based Queue are dynamic, so the estimated time for completion and the list of files are subject to change if items are added.


188 U41840-J-Z125-1-76

Source Role NAS Directory/File Based Replication Configuration

Before you can execute a Directory/File Based Replication, you must assign the NAS share on the Source system a Sync ID so it can be replicated automatically to the Target system.

To assign the NAS share a Sync ID:

1. Select the NAS share from the Source Role NAS page and click Edit.

The Source Role NAS Settings page displays (see Figure 92).

Figure 92: Source Role NAS Settings

2. Select Enable Directory/File Based Replication and enter a Sync ID in the box. The Sync ID for this NAS share MUST match the Sync ID configured for this NAS share on the Target system.

I The Target system must have the corresponding NAS share configured with a Sync ID prior to configuring the Source system share (see "Target Role NAS Directory/File Target Configuration" on page 194).

3. Click Apply.

The NAS share is now configured for Directory/File Based Replication.

I The replication can ONLY be executed by a post backup script run on an external host (see "Directory/File Based Replication Post Backup Scripts" on page 195).


U41840-J-Z125-1-76 189

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\11

_D

ata

_Se

rvic

es.

fm

Source Role Actions

Use the Source Role Actions page to pause or resume the replication service and enable or disable the replication state.

If you need to add, delete, or change a replication Target, you must first pause replication service from the Source Role Actions page.

I After the replication Target has been changed, you must resume the replication service from the Source Role Actions page.

To access the Source Role Actions page:

1. From the Source Role page, click the Actions tab.

The Source Role Actions page displays (see Figure 93).

Figure 93: Source Role Actions Page

Target Role Data Services

190 U41840-J-Z125-1-76

The Replication Service area controls both replication and failback traffic.

● Click Pause to pause both replication and failback traffic for a replication in process. When you click Pause, the system will continue to replicate the current block of infor-mation in process. Since the block can be as large as 250 MB, the process of completing the current block replication can take up to 15 minutes to complete. Once that block has completed replication, the system will pause and wait to resume.

I If you pause a replication in process, a Failure event will be generated on the Replication Events page. When the replication is resumed, the replication process will continue.

● Click Resume to resume replication and failback traffic.

You may enable or disable replication for all deduplicated NAS shares by clicking the appro-priate button in the Replication State area.

● Click Enable to enable replication for all deduplicated NAS shares.

● Click Disable to disable replication for all deduplicated NAS shares.

I If you click Disable during a replication in process, the system will complete the entire replication and then disable replication on the system. The system will be unable to replicate until you click Enable.

The Replication Performance area includes statistics gathered while replicating or failing back shares to target systems.

● To clear these statistics, click Clear.

Target Role

Use the Target Role page to define up to 10 source systems that the target can accept replicated data from. The Target Role page is also used to perform actions upon replicated NAS shares that have been received. The source systems must be defined in the Target Role page prior to defining the target systems in the Source Role page.

Target Role General

To configure the target system for replication:

1. From the Replication page, click the Target Role tab.

The Target Role General page displays (see Figure 94).

Data Services Target Role

U41840-J-Z125-1-76 191

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\11

_D

ata

_Se

rvic

es.

fm

Figure 94: Target Role General Page

The Target Role General page displays the following information for each replication source.

● Host Name or IP Address - The source system replicating to the target system

● Total Bytes Received - The actual number of bytes received over the network from the corresponding Allowed Replication Source.

● Average Receive Rate - The average rate at which actual bytes are being received over the network from the corresponding Allowed Replication Source.

2. Enter the Host Names or IP Address for the replication source and click Add. Up to 10 sources can be defined.

3. To delete a host name or IP address, select the appropriate check box and click Delete.

Replicated Snapshots

Use the Replicated Snapshots area to configure the number of saved replicated snapshots on the Target. A snapshot is a NAS share that has been replicated to the Target system. Up to 24 snapshots for each NAS share can be saved on the target.


192 U41840-J-Z125-1-76

Having snapshots configured allows you to return to a previously replicated NAS share if necessary.

To configure the number of replicated snapshots:

1. From the Target Role page, click the General tab.

2. Under Replicated Snapshots, select the Maximum Snapshots Per Share from the drop down box.

3. Click Apply.

Target Role NAS

Use the Target Role NAS page to select and perform actions on replicated NAS shares such as Recover, Failback, or Delete replicated NAS shares.

Figure 95: Target Role NAS Page


U41840-J-Z125-1-76 193

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\11

_D

ata

_Se

rvic

es.

fm

To display replicated NAS shares:

1. From the Target Role page, click the NAS tab.

The Target Role NAS page displays (see Figure 95).

The Target Role NAS page displays the available NAS shares that have been repli-cated. The page also displays information on failback jobs.

2. To recover a NAS share, select the share and click Recover.

The NAS share is recreated on the target system and is ready for use.

You can view details about previously completed recovery jobs on the Recovery Jobs tab.

I If the source share is an NFS share, then the target NFS share is restored as an NFS share. If the source share is a CIFS share, then the target CIFS share is restored as a CIFS share.

3. To failback a NAS share:

a) Select the share and click Failback.

b) Enter the Host Name or IP Address for the source system where you want the replicated share to failback and click Apply.

The NAS share is failed back to the source system. On the source system, select the recovered NAS share from the replicated share list and click Recover. The NAS share is recreated on the source system.

You can view details about previously completed failback jobs, or abort a failback job that is in progress, on the Failback Jobs tab.

V If a node fails during a recover job, the recover job must be restarted.

4. To delete a replicated share, select the share and click Delete.

Before you can delete a replicated share, you must take one of the following actions:

● Change the replication state of the share on the source system to Disabled (see "Source Role NAS" on page 185).

● Delete the source system from the list of allowed replication sources on the Target Role > General page (see "Target Role" on page 190).

Also, you cannot delete a share if a failback is in progress for the share. Wait for the failback to complete, or abort the failback job on the Failback Jobs tab.


194 U41840-J-Z125-1-76

Target Role NAS Directory/File Target Configuration

To configure the Directory/File Based Target, you must first create a NAS share on the Target system that matches the NAS share on the Source system (name of NAS share). See "NAS Configuration" on page 75 for more information on creating a NAS share. Once the NAS share has been created on the Target system, it will display in the Directory/File Based Targets page.

To configure the Directory/File Based Target:

1. From the Target Role NAS page, click the Directory/File Based Targets tab.

The Directory/File Based Targets page displays (see Figure 96).

Figure 96: Directory/File Based Targets Page

2. Select the Share Name and click Edit.

3. Select Enable as Directory/File Based Replication Target and enter a Sync ID in the box (see Figure 97).


U41840-J-Z125-1-76 195

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\11

_D

ata

_Se

rvic

es.

fm

Figure 97: Directory/File Based Targets Settings Page

4. Select Unlocked to allow this NAS share to be used as a Directory/File Based Repli-cation target. Select Locked to deny use of this NAS share as a Directory/File Based Replication target.

5. Click Apply.

The NAS Share Directory/File Based Replication configuration is complete.

Unpack Queue

Click Unpack Queue in the Directory/File Based Targets page to view Directory/File Based Replication statistics for data received from the source system.

Directory/File Based Replication Post Backup Scripts

After the NAS shares are configured for Directory/File Based Replication (with Sync IDs), the replication can ONLY be executed by a post backup script run on an external host. The following post backup scripts are provided as examples only. Your specific post backup script may differ from the examples below.


196 U41840-J-Z125-1-76

I You will be prompted for a password on the remote host. Alternately you can copy the authorized_keys generated from the remote host to the cliadmin user home directory to remove the password login requirement.

● Directory Replication Script:

ssh [email protected] syscli --replicate nas --name /nas/path/

● File Replication Script:

ssh [email protected] syscli --replicate nas --name /nas/path/file

Target Role Actions Page

Use the Target Role Actions page to display the replication performance.

To view replication performance:

1. From the Target Role page, click the Actions tab.

The Target Role Actions page displays (see Figure 98).

Figure 98: Target Role Actions Page

Target role performance data includes statistics gathered while receiving replicated or failed back shares from source systems.

● To clear these statistics, click Clear.


U41840-J-Z125-1-76 197

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\11

_D

ata

_Se

rvic

es.

fm

Reports

Use the Reports page to generate and download a zip file containing .csv (comma separated value) files suitable for importing into a spreadsheet. The replication report contains a namespace replication summary and details as well as a Directory/File based replication summary and details.

To create and download a new replication report:

1. From the Replication page, click the Reports tab.

2. Click Generate New to generate a new replication report.

3. Click Download Current to download the current replication report.


198 U41840-J-Z125-1-76

U41840-J-Z125-1-76 199

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku\

1000

501

_Use

rGu

ide

\12_

Util

itie

s.fm

UtilitiesUse the Utilities pages to perform maintenance functions on the ETERNUS CS800, including uploading and activating software images as well as generating and downloading diagnostic files. The Utilities pages also allow you to reboot or shut down the CS800.

To access the Utilities pages, in the contents frame, click the Utilities menu.

The Utilities pages contain the following tabs:

● "Software"

● "Diagnostics"

● "Analyzer"

● "Node Management"

Software

Use the Software page to upload a new software image to the CS800.

Uploading Software

I The system should be scheduled for downtime during a software upgrade. Before you start the upgrade, ensure that all replication and backup jobs are completed, all space management tasks are completed, and all hardware statuses on the system are Normal (see "Hardware" on page 157).

To upload a new software image:

1. From the Utilities menu, click the Software tab.

The Software page displays (see Figure 99).

Diagnostics Utilities

200 U41840-J-Z125-1-76

Figure 99: Software Page

2. Type the location and filename of the new software image, or click the Browse button and locate the new software image.

3. Click Upload to place the new software image in a temporary area of the system.

A Successful Upload page displays indicating that the software has been uploaded. Click OK to continue.

4. Click Activate to activate the new software image or Remove to remove the software image from the system.

An Information page indicates the software has been either activated or removed. If activated, the system enters limited mode and displays activation progress until the system reboots.

V The system reboots automatically following the software activation. After the reboot process begins, wait at least 15 minutes before attempting to log in to the system.

Diagnostics

The ETERNUS CS800 allows you to download diagnostic files to your local host. These diagnostic files are helpful when troubleshooting problems on the system. Have the diagnostic files available prior to contacting Fujitsu customer support.

To access the Diagnostics page:

Utilities Diagnostics

U41840-J-Z125-1-76 201

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku\

1000

501

_Use

rGu

ide

\12_

Util

itie

s.fm

1. From the Utilities menu, click the Diagnostics tab.

The Diagnostics page contains the following tabs:

● "System Diagnostics File"

● "Storage Array"

● "Healthchecks"

System Diagnostics File

The System Diagnostics file contains the diagnostic logs for all of the system components.

To generate and download a system diagnostics file:

1. On the Diagnostics page, click the System tab.

The System Diagnostics page displays (see Figure 100).

Figure 100: System Diagnostics Page

2. Click Generate New to generate a new system diagnostics file.

The system generates a new diagnostics file. This can take several minutes.

3. After the report finishes generating, refresh the Web browser to enable the Download Current button.

Diagnostics Utilities

202 U41840-J-Z125-1-76

4. To download the newly generated diagnostics file, click Download Current.

A dialog box displays asking if you want to open or save the file.

5. Click Save or OK to download the file.

Storage Array

The Storage Array Diagnostics file contains the diagnostics logs for the storage arrays.

To generate and download a storage array diagnostics file:

1. On the Diagnostics page, click the Storage Array tab.

The Storage Array page displays (see Figure 101).

Figure 101: Storage Array Page

2. Click Generate New to generate a new storage array diagnostics file.


3. After the report finishes generating, refresh the Web browser to enable the Download Current button.




Utilities Diagnostics

U41840-J-Z125-1-76 203

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku\

1000

501

_Use

rGu

ide

\12_

Util

itie

s.fm

Healthchecks

Use the Healthchecks page to configure the automatic healthcheck function on the CS800. When configured, the system periodically runs a system-wide healthcheck that determines the status of the overall CS800.

To access the Healthchecks page:

1. From the Utilities menu, click the Healthchecks tab.

The Healthchecks page displays (see Figure 102).

Figure 102: Healthchecks Page

The Healthchecks page contains the following tabs:

● "General"

● "Healthchecks Status"

● "Healthchecks Schedule"

General

The General page displays the overall status of all the healthchecks as they are being run. Use this page to run healthchecks on demand or to stop them if they are already running. When healthchecks are started, only those healthchecks that are enabled are run. The progress of the healthcheck is displayed as well as the start and completion time.

Analyzer Utilities

204 U41840-J-Z125-1-76

● To start a healthcheck, click Start.

● To stop a healthcheck in progress, click Stop.

Healthchecks Status

The Healthchecks Status page displays a list of recently completed healthcheck tests. The outcome of each healthcheck is displayed as well as when the healthcheck was last run and the status.

This page also shows the state of the healthcheck (enabled or disabled). To enable a specific healthcheck, select the test and then click Edit. Select the Enable check box, and then click Apply.

Healthchecks Schedule

Use the Healthchecks Schedule page to configure the CS800 to automatically run a healthcheck. This allows users to control the frequency at which the healthchecks are run. The schedule applies to all healthchecks. Healthchecks can be scheduled to run daily, weekly, or not at all.

● To set a healthchecks schedule, select Daily or Weekly. Use the drop down boxes to select a start time, and click Apply.

● To disable running healthchecks on an automatic schedule, select Never, and click Apply.

Analyzer

Use the Analyzer page to analyze network information and disk information.

To access the Analyzer page:

1. From the Utilities menu, click the Analyzer tab.

The Analyzer page displays (see Figure 103).

Utilities Analyzer

U41840-J-Z125-1-76 205

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku\

1000

501

_Use

rGu

ide

\12_

Util

itie

s.fm

Figure 103: Analyzer Page

The Analyzer page contains the following tabs:

● "Network Analysis"

● "Disk Analysis"

Network Analysis

Use the Network page to measure network performance with another system.

To access the Network page, from the Analyzer page, click the Network tab.

The Network page contains the following tabs:

● "Performance"

● "Settings"

Performance

Use the Performance page to perform network analysis with another system.

To perform network analysis:

Analyzer Utilities

206 U41840-J-Z125-1-76

1. From the Network page, click the Performance tab.

2. Enter the IP Address of another system.

The system you specify in the IP Address box requires a NetPerf server (NetServer) to be running. If you specify the IP Adress of a further CS800, on this machine you should have NetServer enabled (see "Settings" on page 206).

I NetPerf for Microsoft Windows and Unix/Linux platforms is available from the Internet.

3. Click Start to begin the analysis.

I It takes approximately 5 seconds to refresh the results.

The throughput result is displayed below in MB/sec.

Settings

This page allows you to start or to stop running the NetPerf server (NetServer) at the CS800. You have to enable NetServer if you want to initiate a network performance test by a remote machine. The remote machine may be either a CS800 (see "Performance") or a host on which you run the NetPerf client.

To enable or disable NetServer:

1. From the Network page, click the Settings tab.

2. Select Enabled or Disabled and click Apply.

3. When you are done testing the network performance, disable the network performance monitor.

Disk Analysis

Disk analysis measures the hard disk performance (disk read and write performance) on the system.

To perform hard disk analysis:

1. From the Analyzer page, click the Disk tab.

2. Click Start to begin the analysis.

I It takes approximately 5 seconds to refresh the results.

The throughput result is displayed below in KB/sec.

Utilities Node Management

U41840-J-Z125-1-76 207

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku\

1000

501

_Use

rGu

ide

\12_

Util

itie

s.fm

Node Management

Use the Node Management page to reboot or shut down the CS800.

To reboot or shutdown the CS800:

1. From the Utilities menu, click the Node Management tab.

The Node Management page displays (see Figure 104).

Figure 104: Node Management Page

2. Under Select Node Action, select an action:

● Reboot - This action restarts the CS800. Rebooting the system closes the Web browser connection. You must log on again after the system has rebooted.

● Shutdown - This action shuts down the CS800.

I Shutting down the system can take up to 15 minutes.

● Reset Diagnostic State - If the node is degraded, this action restarts the services on the node without rebooting the system.

3. Click Apply.

I Shutting down the system can take up to 15 minutes.

Node Management Utilities

208 U41840-J-Z125-1-76

U41840-J-Z125-1-76 209

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:2

3.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\13

_Tr

oubl

esh

ootin

g.fm

Troubleshooting via CS800 Web PagesThis chapter describes problems you may encounter during the setup and operation of the ETERNUS CS800 system. Corrective information is provided to help you resolve the problems.

This chapter consists of the following sections:

● "CS800 Problem Reporting"

● "Using CS800 Status Page for Troubleshooting"

● "Common Problems and Solutions"

● "Service Tickets"

CS800 Problem Reporting

The CS800 reports status information through the remote management pages (see "Remote Management" on page 63). The following actions are performed by the CS800 remote management pages:

● Monitors both the system software and hardware components.

● Detects system problems.

● Attempts to isolate each problem to a specific field replaceable component.

● Attempts to recover from the problem.

● Logs the problem.

● If the problem requires service, the system reports the problem in a service ticket associated with the field replaceable component.

Service tickets include time and date information, status (open or closed), information about each error, and links to recommended troubleshooting procedures. The CS800 generates service tickets according to the following scenarios:

● If the component associated with the problem does not have an open service ticket, the CS800 opens a service ticket for the component and reports the problem in a service ticket.

● If the problem reoccurs, the CS800 logs the number of times that it detects the problem in the existing report.

● If a different problem occurs with the same component, the CS800 adds a new report to the same service ticket.

Using CS800 Status Page for Troubleshooting Troubleshooting via CS800 Web Pages

210 U41840-J-Z125-1-76

● If a problem occurs with a different component, the CS800 uses the above scenario to open a new service ticket for the component or report the problem in an existing service ticket associated with the component.

Using CS800 Status Page for Troubleshooting

The CS800 Status page can be used to verify the overall status of the CS800 system. A failed status indicator can help troubleshoot a problem in the CS800.

To view the hardware status:

1. From the Status menu, click the Hardware tab.

The Hardware Summary page displays (see Figure 105):

Figure 105: Hardware Summary Page

The Hardware Summary page displays the overall health status of the CS800 system. All components are listed as links on this page. Click a link to see detailed information on specific component status.

Troubleshooting via CS800 Web Pages Using CS800 Status Page for Troubleshooting

U41840-J-Z125-1-76 211

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:2

3.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\13

_Tr

oubl

esh

ootin

g.fm

Downloading the System Diagnostics File

The CS800 system allows you to download a system diagnostics file to your local host. This file is helpful when troubleshooting problems on the system. Have this file available prior to contacting Fujitsu customer support.

To generate and download a system diagnostics file:

1. On the Diagnostics page, click the System tab.

The System Diagnostics page displays (see Figure 106).

Figure 106: System Diagnostics Page

2. Click Generate New to generate a new system diagnostics file.





Common Problems and Solutions Troubleshooting via CS800 Web Pages

212 U41840-J-Z125-1-76

Common Problems and Solutions

The troubleshooting information in this section covers the following topics:

● "Start-up Problems"

● "Hardware Problems"

● "Ethernet Network Problems"

● "Replication Problems"

● "Temperature Problems"

Start-up Problems

Table 38 describes problems that can occur during system start-up.

Table 38: Start-up Problems

Problem Corrective Action

FATAL ERROR Unable to start SNFS!

Message displays.

Contact your Fujitsu Customer Support representative (see "Support and Help" on page 11).

FATAL ERROR Unable to start blockpool!

Message displays.

Contact your Fujitsu Customer Support representative (see "Support and Help" on page 11).

Troubleshooting via CS800 Web Pages Common Problems and Solutions

U41840-J-Z125-1-76 213

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:2

3.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\13

_Tr

oubl

esh

ootin

g.fm

Hardware Problems

Table 39 describes corrective actions for problems occurring with the system hardware.


The system does not power on.

Make sure the power cords are connected to a grounded electrical outlet and the power switches located on the back of the power supplies are on. If the problem persists, contact your Fujitsu Customer Support representative to arrange for service (see "Support and Help" on page 11).

One power supply of the server is not functioning.

Determine which power supply has failed by observing which power supply indicator glows green. Change the power supply as described in Chapter "Removal and Replacement Proce-dures for CRUs" or contact your Fujitsu Customer Support representative to arrange for service (see "Support and Help" on page 11).

Both power supplies of the server are not functioning.

Contact your Fujitsu Customer Support representative to arrange for service (see "Support and Help" on page 11).

A power supply of a storage component is not functioning.


One fan is not operating. Determine which fan has failed by reading the service ticket generated by the system. Contact your Fujitsu Customer Support representative to arrange for service (see "Support and Help" on page 11).

Multiple fans are not operating.

W WARNING!Turn the system off immediately! The system will overheat with multiple fans not operating.



214 U41840-J-Z125-1-76

Table 39: Hardware Problems

A hard drive of the server is not responding

Determine which drive has failed by observing the orange fault LED on the drive carrier. Contact your Fujitsu Customer Support representative for a drive carrier replacement (see "Support and Help" on page 11).

A hard drive of a storage module is not responding

Determine which drive has failed by observing which LED related to a HDD glows orange. Change the HDD as described in Chapter "Removal and Replacement Procedures for CRUs" or contact your Fujitsu Customer Support representative for a drive carrier replacement (see "Support and Help" on page 11).

A SAS cable is removed during normal operation.

The system will shut down as soon as it recognizes the problem. There is a potential for data loss.

Power off the system, re-insert the SAS cable and restart system. Depending on the state of the system when the SAS cable was removed, a long-running, mandatory data verification may occur.


Troubleshooting via CS800 Web Pages Common Problems and Solutions

U41840-J-Z125-1-76 215

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:2

3.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\13

_Tr

oubl

esh

ootin

g.fm

Ethernet Network Problems

Table 40 describes corrective actions for problems occurring with the Ethernet network.

Table 40: Ethernet Network Problems


The Ethernet link light on the CS800 is not lit when a cable is connected to a hub or switch.

Check to make sure the Ethernet cable is not a cross-over cable. Use only “straight” CAT-6 Ethernet cables.

Port on the hub or switch is not active or damaged.

Port on the CS800 is damaged. Contact the Fujitsu Customer Support department (see "Support and Help" on page 11).

The Ethernet link light on the switch or hub is not lit when a cable is connected to CS800 system.

Check to make sure the Ethernet cable is not a cross-over cable. Use only “straight” CAT-6 Ethernet cables.

Port on the hub or switch is not active or damaged.

Port on the CS800 is damaged. Contact the Fujitsu Customer Support department (see "Support and Help" on page 11).

CS800 system is not visible on the Ethernet network.

Try to ping the CS800 system IP address from a host on the same network. If the ping reports round trip times, the CS800 system is active. If not, check the cables, switches, or hubs for damaged components. If everything checks out, contact the Fujitsu Customer Support department (see "Support and Help" on page 11).

CS800 remote management pages are not visible.

IF you cannot connect to the CS800 remote management pages, verify that the following network settings for the CS800 are correct:

● Hostname

● IP addresses

● Default gateway

● Subnet mask

● Domain name (optional)

An Ethernet cable is removed during normal operation.

The system will discontinue use of the associated Ethernet port. A Service ticket will be issued. The possibility of errors exist; data corruption will not occur.

Reconnect the cable as soon as possible. It is not necessary to power the system off. Depending on the state of the system when the Ethernet cable was removed, replication, system management, or ingest may need to be restarted.


216 U41840-J-Z125-1-76

Replication Problems

Table 41 describes corrective actions for problems occurring with the replication.

Table 41: Replication Problems

Temperature Problems

Temperature problems are generally caused by incorrect room temperature, poor air circu-lation inside the CS800 rack or components, or a malfunctioning cooling fan.

Use the following procedure if a temperature problem is reported:

Problem Explanation/Corrective Action

The replication was paused, but the repli-cation is still in process.

When you click Pause, the system will continue to replicate the current tag or block of information in process. The process of completing the current tag replication can take up to 15 minutes to complete. Once that tag has completed replication the system will pause and wait to resume.

The replication was paused and a Failure event was generated in the Replication Events page.

This is normal. When a replication is paused, a failure event is generated on the Replication Events page. They system will continue the replication when you click Resume.

Replication was disabled while a repli-cation was in process and the replication completed.

If you click Disable during a replication in process, the system will complete the entire replication and then disable replication on the system. The system will be unable to replicate until you click Enable.

Enabled replication on a NAS share and received the following Event: No destination host is specified for replication.

You must configure the target system prior to configuring the source. If the target system is not configured first, you will not be able to designate the replication target.

Able to enable and schedule replication for NAS even though no target IP configured.

It is possible to enable and schedule a replication when a target system has not been configured. The replication will not start until a target system is configured.

Troubleshooting via CS800 Web Pages Service Tickets

U41840-J-Z125-1-76 217

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:2

3.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\13

_Tr

oubl

esh

ootin

g.fm

1. Check the ambient temperature of the room containing the CS800 system to verify that the temperature falls within the specified range.

2. Inspect for adequate air circulation inside the rack. Some racks may provide additional fans to improve air circulations. Check the fan for proper operation. Clean or replace any air filter as necessary.

3. If a component reports a temperature problem, verify that the associated fan is operating correctly. If necessary, contact Fujitsu customer support to replace the fan (see "Support and Help" on page 11).

Service Tickets

The CS800 system can generate service tickets which can be used to resolve a problem.

Figure 107: Service Tickets Page

Service Tickets Troubleshooting via CS800 Web Pages

218 U41840-J-Z125-1-76

To access the Service Tickets page:

1. Access the CS800 remote management pages (see "Accessing CS800 Web Pages" on page 68), and log onto the system as an administrator.

2. From the Home page, click the Ticket button located at the top of the page.

The Service Tickets page displays (see Figure 107).Figure 108:

3. To view details for a ticket, click the ticket number.

The Ticket Details display at the bottom of the screen (see Figure 109).

Figure 109: Ticket Details

4. To see information about the actions you can to take to resolve the ticket, click the View Recommended Actions link.

The Recommended Actions window displays (Figure 110).

Ticket details

Troubleshooting via CS800 Web Pages Service Tickets

U41840-J-Z125-1-76 219

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:2

3.50

Pfa

d: P

:\allg

emei

n\C

S8

00\1

000

500_

FT

S-D

oku

\100

050

1_U

serG

uid

e\13

_Tr

oubl

esh

ootin

g.fm

Figure 110: Recommended Actions Window

5. Follow the instructions on the Recommended Actions window to resolve the problem.

Service Tickets Troubleshooting via CS800 Web Pages

220 U41840-J-Z125-1-76

U41840-J-Z125-1-76 221

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku\

1000

501

_Use

rGu

ide

\14_

Imp

lem

entin

g_D

ata

_Rep

licat

ion

_Pla

n.fm

Implementing a Data Replication PlanI The information in this section applies to NAS replication. OST optimized replication

using NetBackup is described separately (see Chapter "OST Optimized Replication").

The CS800 can be used as part of your disaster recovery plan through its built-in data repli-cation capability. Data replication is used to create another copy of your data on a remote CS800 system. In the event of a disaster where the original data was lost, the replicated data can be quickly recovered from the remote system allowing your business to resume normal operations.

The following sections provide information on setting up data replication and also recov-ering replicated data:

● "Setting Up Data Replication"

● "Recovering Replicated Data"

Setting Up Data Replication

Setting up data replication on the CS800 consists of the following steps:

1. "Setting Up the Target CS800 System"

2. "Setting Up the Source CS800 System"

3. "Enabling and Running Replication"

Then, files are replicated to the target CS800.

Setting Up the Target CS800 System

Before data can be replicated from a source system to a target system, the target must be authorized to receive data from a specific source. To authorize a target system to receive data from a source, you must add the source hostname or IP address to the Source Host List on the target system.

To add a source hostname or IP address on the target system:

Setting Up Data Replication Implementing a Data Replication Plan

222 U41840-J-Z125-1-76

1. Access the remote management pages on the target system. For information on accessing the remote management pages, see Chapter "Accessing CS800 Web Pages".


The Target Role General page displays (see Figure 111).

Figure 111: Target Role General Page

3. Enter the hostname or IP address for the replication source and click Add. Up to 10 sources can be defined.

Entering the hostnames or IP addresses of the replication source systems on the target system allows the target to receive replicated data from these sources.

Setting Up the Source CS800 System

Once you have added the source system hostname or IP address to the target system, you must add the target system hostname or IP address to the source system. The source system can only replicate data to one target.

Implementing a Data Replication Plan Setting Up Data Replication

U41840-J-Z125-1-76 223

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku\

1000

501

_Use

rGu

ide

\14_

Imp

lem

entin

g_D

ata

_Rep

licat

ion

_Pla

n.fm

I You must configure the target system prior to configuring the source. If the target system is not configured first, you will not be able to designate the replication target.

1. Access the remote management pages on the source system. For information on accessing the remote management pages, see Chapter "Accessing CS800 Web Pages".

2. From the Replication page, click the Source Role tab.

The Source Role General page displays (see Figure 112).

Figure 112: Source Role General Page

3. Enter the hostname or IP address for the replication target and click Apply.

The source system can now replicate data to a target system.

Enabling and Running Replication

Now that both the target and source systems are setup for replication, you can enable repli-cation and either schedule the replication process or manually replicate a share.

I For optimization purposes, the underlying data is continuously updated. The data will become available when the replication is either run manually or using a scheduled replication.

Setting Up Data Replication Implementing a Data Replication Plan

224 U41840-J-Z125-1-76

To enable replication and replicate a NAS share:

1. Access the remote management pages on the source system. For information on accessing the remote management pages, see Chapter "Accessing CS800 Web Pages".

2. From the Source Role page, click the NAS tab.

The Source Role NAS page displays (see Figure 113).

Figure 113: Source Role NAS Page

The Source Role NAS page displays the available NAS shares that have been dedupli-cated. The page also displays the current replication status for the share and infor-mation on the most recent replication that was run.

3. Select the NAS share to replicate and click Edit.

The Source Role NAS Settings page displays (see Figure 114).

Implementing a Data Replication Plan Recovering Replicated Data

U41840-J-Z125-1-76 225

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku\

1000

501

_Use

rGu

ide

\14_

Imp

lem

entin

g_D

ata

_Rep

licat

ion

_Pla

n.fm

Figure 114: Source Role NAS Settings Page

4. Select Enable Replication to enable replication.

5. To schedule a replication time, select Enable scheduled replication and enter the date and time to run the replication process.

I Replication should be scheduled to run after backups are complete.

6. Click Apply. The Source Role NAS page displays (see Figure 113).

7. To manually run the replication process, select the NAS share and click Replicate/Abort and then Replicate Now.

The NAS share is replicated from the source system to the target system. To pause or resume the replication process, click the Actions tab on the Source Role page and proceed as described in "Source Role Actions" on page 189.

Recovering Replicated Data

There are two ways to recover replicated data:

● "Data Recovery"

● "Data Failback"

Recovering Replicated Data Implementing a Data Replication Plan

226 U41840-J-Z125-1-76

Data Recovery

In the event that a NAS share has been destroyed or corrupted on the original source system, the data recovery option recreates the share on a target system that contained the replicated data. Once recovered, the share is available for use on the target system.

Major steps for recovering a NAS share, done on the target CS800 system are:

● Select the NAS share to recover.

● Enter a name for the recovered NAS share.

More in detail, proceed as follows to recover a NAS share:







Implementing a Data Replication Plan Recovering Replicated Data

U41840-J-Z125-1-76 227

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

ärz

201

0 S

tan

d 19

:23.

50P

fad:

P:\a

llgem

ein

\CS

800\

1000

500

_FT

S-D

oku\

1000

501

_Use

rGu

ide

\14_

Imp

lem

entin

g_D

ata

_Rep

licat

ion

_Pla

n.fm

4. To recover a NAS share, select the NAS share and click Recover.

5. The system prompts you to enter a name for the recovered NAS share. This name must be unique on the target system.

The NAS share is recreated on the target system and is ready for use.

I If the source share is an NFS share, then the target NFS share must be restored as an NFS share. If the source share is a CIFS share, then the target CIFS share must be restored as a CIFS share.

Data Failback

In the event that a NAS share has been destroyed or corrupted on the original source system, the data failback option copies the replicated share from the target system to the source system. Once the replicated share is copied to the source system, it can be recovered on the source system and returned to normal operation.

Major steps for failing back a NAS share are:

● On the target CS800 system:

1. Select the NAS share to „Failback“.

2. Enter the hostname or IP address of the system where you want a NAS share to „Failback“.

● Afterwards, on the source CS800 system, recover the „Failback“ NAS share.

More in detail, proceed as follows to failback a NAS share:





Recovering Replicated Data Implementing a Data Replication Plan

228 U41840-J-Z125-1-76



4. To failback a NAS share, select the share and click Failback.

The system prompts you for a hostname or IP address of the source system.

I A hostname is allowed ONLY if DNS is configured with valid system names. If DNS is not configured with valid system names, use the IP address of the source system.

5. Enter the hostname or IP address for the source system where you want the replicated share to failback and click Apply.

6. Open a new Web browser window and access the remote management pages on the source system.

7. From the Data Services menu, click the Replication tab.


9. On the source system, select the recovered NAS share from the replicated share list and click Recover.

The NAS share is recreated on the source system.

U41840-J-Z125-1-76 229

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10 S

tand

19:

23.5

0P

fad:

P:\

allg

em

ein

\CS

800

\100

0500

_F

TS

-Dok

u\10

005

01_

Use

rGu

ide\

13_C

RU

_Rem

oval

_R

epl

acem

ent

_Pro

cedu

res.

fm

Removal and Replacement Procedures for CRUsThis chapter describes how to handle Customer Replaceable Units (CRUs) and how to identify defective CRUs and replace them yourself. Other units may not be replaced by the customer.

The CRUs are hot-plug components which can be expanded or replaced during operation. The hot-plug procedure increases the availability of system operation and guarantees a high degree of data integrity and failsafe performance.

I Please note that unauthorized interference with the system will void the warranty and exempt the manufacturer from all liability.

V CAUTION!Follow the safety instructions in the chapter "Important Information" on page 13.

ETERNUS CS800 Server

Hot-Plug Power Supply Units

I A redundant power supply can be created by installing a second hot-pluggable power supply unit (optional). If one power supply unit fails, the other unit ensures operation can continue. The defective power supply unit can be replaced without interrupting operation.

Removing dummy module

The slot for the second hot-plug power supply unit contains a dummy module. This dummy module must be removed before installing a second power supply unit.

1. Remove the dummy module from the second power supply unit slot.

V CAUTION!

Keep the dummy module for future use. If the power supply unit is removed and not replaced with a new unit, the dummy module must be reinstalled due to cooling, to comply with applicable EMC regulations (regulations on electromagnetic compati-bility) and to protect against fire.

ETERNUS CS800 Server Removal and Replacement Procedures for CRUs

230 U41840-J-Z125-1-76

Adding a hot-plug power supply unit

1. Slide the second power supply unit into the empty slot until it locks into place (see "Replacing the hot-plug power supply unit" on page 230) and connect it up (see "Connecting the power cord" on page 231).

Replacing the hot-plug power supply unit

Figure 117: Unlocking and Removing the Power Supply Unit

V CAUTION!

Before replacing a non defective power supply unit in a non-redundant configu-ration (only one power supply unit present) the server must be switched OFF.

1. Remove the cable from the installed power supply unit.

2. Push the green catch in the direction of the arrow (1) while pulling the power supply unit out of its mounting location (2) by the handle.

3. Slide the new power supply unit into the empty slot until it clicks into place.

I Make sure that the power supply unit engages correctly in the slot and is locked in position.

This is the only way to prevent the power supply unit from sliding out of its mountings and being damaged during transportation.

1

2

Removal and Replacement Procedures for CRUs ETERNUS CS800 Server

U41840-J-Z125-1-76 231

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10 S

tand

19:

23.5

0P

fad:

P:\

allg

em

ein

\CS

800

\100

0500

_F

TS

-Dok

u\10

005

01_

Use

rGu

ide\

13_C

RU

_Rem

oval

_R

epl

acem

ent

_Pro

cedu

res.

fm

4. Connect the newly installed power supply unit.

Connecting the power cord

V CAUTION!

The installed power supply units automatically set themselves to a voltage in the range of 100 V – 240 V. Make sure that your local mains voltage is within the correct range.

Figure 118: Connecting the Server to the Mains

1. Connect the power cable with the insulated connector to the power supply unit of the server, and plug the power plug into a grounded outlet on the mains socket strip on the rack (see Technical Manual of the rack).

I A phase redundancy in the power supply of the server can be set up if two hot-plug power supply units are installed. In this case, the two power supply units are connected to two different phases.


232 U41840-J-Z125-1-76

ETERNUS CS800 Storage

Front cover installing / removal

V CAUTION!Be careful not to damage the panel during removal/installation of the front cover.

Removing

1. Open the front door of the rack.

2. Put a hand on the front cover, pull forward and remove the front cover.

Figure 119: Removing the Front Cover

Installing

V CAUTION!Make sure that the front cover does not touch the power switch ( ) of the panel when installing the front cover slot.

1. Attach the front cover to the front slot of the left end of the controller enclosure/drive enclosure (see Figure 120).

Figure 120: Attaching the Front Cover


U41840-J-Z125-1-76 233

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10 S

tand

19:

23.5

0P

fad:

P:\

allg

em

ein

\CS

800

\100

0500

_F

TS

-Dok

u\10

005

01_

Use

rGu

ide\

13_C

RU

_Rem

oval

_R

epl

acem

ent

_Pro

cedu

res.

fm

2. Insert the right side to the guide hole (see Figure 121)

Figure 121: Inserting the Front Cover

3. Close the front door of the rack.

Hard Disk Drive removal and installation

The Hard Disk Drive (HDD) used in the storage modules is a 3.5’’ HDD (NL-SAS, 1 TB, 7200 rpm).

V CAUTION!In order to avoid giving damages to the device by the static electricity of human body, be sure to wear a wrist strap during the maintenance work.

Hot Maintenance work should be finished within 5 minutes (for preventing temper-ature rise).

I This component can be replaced, during operation of the system (Hot Maintenance). The component cannot be replaced when the system is powered off.

When replacing the HDD unit, it is possible that the error log will display multiple errors, due to a temporaray disarray of the transmission route within the separation/connection of the HDD unit. This is not a problem/error of the HDD unit or the device.

Removing

1. Remove the front cover from the relevant device.

2. Confirm that the LED of the relevant part glows amber.

3. Press the latch of the HDD unit and open the lock lever (see Figure 122).


234 U41840-J-Z125-1-76

Figure 122: Removing/Installing the HDD Unit

4. Hold the lock lever and pull it partway.

V CAUTION!Do not pick up a HDD unit only by holding the lock lever. Doing so may cause damage.

5. Pull out the HDD unit (see Figure 123).

Figure 123: Pulling out the HDD Unit


U41840-J-Z125-1-76 235

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10 S

tand

19:

23.5

0P

fad:

P:\

allg

em

ein

\CS

800

\100

0500

_F

TS

-Dok

u\10

005

01_

Use

rGu

ide\

13_C

RU

_Rem

oval

_R

epl

acem

ent

_Pro

cedu

res.

fm

Installing

1. Installing shall be done in the reverse order of removing.

I Notes on Installing the HDD unit:

a) Check the type of HDD unit.

b) External view: There should not be inside distortion or bent pins.

c) Press the latch of the HDD unit and open the lock lever.

d) Air-clean the HDD unit and the connector part of the main device. Blow air for 2 to 3 seconds while keeping 30 cm between the blower tip and the part. After the cleaning, install quickly.

e) When installing multiple HDD units, check that the previous HDD unit’s disk status turned on in green, and then install the next HDD unit.

I Do not pick up a HDD unit only by holding the lock lever. Doing so may cause damage.

During insertion of the HDD unit, hold it firmly with both hands in order not to cause any vibration or shock.

2. Insert the replacement HDD unit in the HDD slot with the lever of the HDD unit opened (see Figure 124).

Figure 124: Inserting the HDD Unit

3. Insert the HDD unit fully into the HDD slot and return the lock lever. A clicking sound from the lock lever indicates that it is locked.

4. Confirm that the LED related to the HDD unit is glowing green or blinking green.

I It is possible, that it takes up top 1 minute to transition to normal or maintenance status.


236 U41840-J-Z125-1-76

U41840-J-Z125-1-76 237

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mä

rz 2

010

Sta

nd

19:2

3.50

Pfa

d: P

:\allg

eme

in\C

S8

00\1

000

500

_FT

S-D

oku

\100

050

1_U

serG

uide

\16_

Exp

ansi

on.fm

ExpansionAn existing CS800 system with less than 9 DX80 storage expansion modules can be expanded with further DX80 expansion modules (until the limit of 9 DX80 expansion modules is reached). These additional DX80 storage expansion modules are pre-configu-rated and their positions in the stack of DX80 storage expansion modules are determined.

For example, the existing CS800 system already has 2 DX80 storage expansion modules, numbered by 1 and 2 which means that number 1 is directly connected to the DX80 basic storage module and that number 2 is connected to number 1. If 3 further DX80 storage expansion modules are ordered, then these additional modules get the numbers 3, 4 and 5 indicated by labels on the rear. Number 3 has to be connected to number 2, number 4 to number 3 and number 5 to number 4.

Procedure for Installing and Commisioning New Expansion Modules

Proceed as described below in order to install and commission additional DX80 expansion modules (it is assumed that there is a rack with enough empty space):

I Make sure that you have the Getting Started manual at hand which provides you with details about installation tasks and cabling.

1. Shutdown the CS800 system as described in Chapter "Turning On and Shutting Down the System".

2. Install the additional DX80 expansion modules in the rack according to the numbering of the modules (e.g. number 4 between number 3 and number 5); for details see the Getting Started manual.The sequence of the modules should be: Server – Basic Storage Module – Expansion Module 1 – Expansion Module 2 – ...which can be realized top-down (server on the top) or bottom up (server on bottom).

I If you have to rearrange the existing CS800 components in the rack in order to get enough space below/above the last already existing storage module, remove the existing cable connections, then install all existing and new components in the rack and do the cabling as described in the Getting Started manual, then proceed with Step 5.

3. Connect a power cable to each power supply of the new DX80 expansion modules.

I It is recommended that you connect each expansion module power cord (two per module) to a separate AC circuit to ensure system availability in case of a power failure.

Expansion

238 U41840-J-Z125-1-76

4. Connect the new DX80 expansion modules with each other and with the last of the existing DX80 storage modules according to the numbering of the modules. This cabling between between two storage modules comprises two miniSAS cables (IN/OUT). Figure 125 shows the cabling for the top-down arrangement of the CS800 components; for more information, see the Getting Started Guide.

V Failure to connect the SAS cables to the correct ports will result in data corruption and/or potential data loss.

5. Turn on the system as described in Chapter "Turning On and Shutting Down the System".A „background initialize“ procedure is started. The new components are automatically integrated into the system and put into service. No further actions are required.

Figure 125: Cabling of the Storage Modules (1: power supply, 2: miniSAS cabling)

System Specifications System Specifications

U41840-J-Z125-1-76 239

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10 S

tand

19:

23.5

0P

fad:

P:\

allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

A1_

Sys

tem

_Spe

cific

atio

ns.

fm

System SpecificationsThis chapter lists characteristics and specifications of the ETERNUS CS800. The charac-teristics and specifications are categorized as follows:

● "System Specifications"

● "Additional Server Specifications"

● "Additional Storage Module Specifications"

System Specifications

The following tables provide characteristics of the ETERNUS CS800 system:

● Table 42 – "General Characteristics"

● Table 43 – "Software Capabilities"

● Table 44 – "Interfaces"

● Table 45 – "Mechanical Characteristics"

● Table 46 – "Power Requirements"

● Table 47 – "Environmental"

● Table 48 – "Compliance with Standards"

Table 42: General Characteristics

General Characteristics

NAS backup target NFS and/or CIFS mount point

128 shares maximum

OpenStorage (OST) Symantec Storage Servers and Logical Storage Units (LSUs)

100 storage servers maximum

Capacity (usable) 8 TB up to 80 TB (0 up to 9 expansion modules with 8 TB)

Performance In-line adaptive operation up to 2.0 TB/h

Standard Software Included

Deduplication, replication

OST support for application-aware replication

Optional Path-to-Tape Direct tape creation without using media server or backup SAN

OST support of direct tape creation


240 U41840-J-Z125-1-76

Table 43: Software Capabilities

Table 44: Interfaces

Table 45: Mechanical Characteristics

Table 46: Power Requirements

Software Capabilities

Policy Based Data Deduplication Options

● Adaptive In-line Data Deduplication: Data is deduplicated on ingestion.

● Deferred Processing Data Deduplication: Data is ingested to disk first, then deduplicated in a separate process at a time set by the user.

I Both methods may be enabled for different data sets in the same CS800.

Replication Support for remote replication.

Replication is asynchronous, one-to-one or multiple-to-one configurations; shares in the same unit act as replication source or target; units with shares acting as replication targets can also support local backup.

Interfaces NAS Basic Variant NAS Performance Variant

Host Ethernet (to Customer LAN)

7 × 1 GbE 3 × 1 GbE plus 2 × 10 GbE

Optional Path-to-Tape Fibre Channel

2 × 4 Gb 2 × 4 Gb

Physical Characteristics

Height 4 HU – 22 HU (0 – 9 expansion modules, each with 2 HU; 2 HU = 3.5’’)

Width (side to side) 484 mm

Depth (front to back) 770 mm

Weight (stand alone) 95 – 375 kg

Power Requirements

Voltage AC 100 – 120 V / 200 – 240 V

Frequency 50 Hz / 60 Hz

Power Consumption Min 1570 W / max 5850 W

Power Phases Dual


U41840-J-Z125-1-76 241

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10 S

tand

19:

23.5

0P

fad:

P:\

allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

A1_

Sys

tem

_Spe

cific

atio

ns.

fm

Table 47: Environmental

Table 48: Compliance with Standards

Climatic Environment

Temperature 10°C to 35°C (50°F to 95°F)

Relative Humidity 20% to 80% (non-condensing)

Heat Emission Min 5654 kJ/h, max 21 062 kJ/h (Min 5360 BTU/h, max 19 968 BTU/h)

Noise Emission

Sound Pressure 49 – 53 dB(A)

Compliance with Standards

Product Safety UL60950-1, CSA6090-1, EN60950-1, IEC60950-1, GOST

Electromagnetic Compat-ibility

FCC Part-15 Class A, ICES-003 Class A, EN55022 Class A, VCCI Class A, AS/NZS CISPR22 Class A, CNS13438(C6357) Class A, C-Tick, BSMI

Electromagnetic Immunity

EN 55024

CE Certification Electromagnetic Compatibility Directive 2004/108/EC, Low Voltage Directive 2006/95/EC

Environmental Compliance

RoHS-compliant (Restriction of hazardous substances), WEEE-compliant (Waste electrical and electronically equipment)

Compliance Notes There is general compliance with the safety requirements of all European countries and North America. National approvals required in order to satisfy statutory regulations or for other reasons can be applied for on request.

Compliance Link https://sp.ts.fujitsu.com/sites/certificates/default.aspx

Additional Server Specifications System Specifications

242 U41840-J-Z125-1-76

Additional Server Specifications

Table 49: Selected Server Specifications

Table 50: Characteristics of the 2.5’’ SAS hard disks

Additional Storage Module Specifications

Table 51: Selected DX80 Specifications

Selected Server Specifications

Weight Approx. 25 kg

Storage Units 11 × 2.5’’ 300 GB SAS disks (10 active, 1 hot spare)

Interface to Basic Storage Module

4 × Fibre Channel with 4 Gb/s each

Service Port 1 × 1 GbE

iRMC Port (Console Device)

100 MbE

Internal RAID Controller LSI 1078 – SAS 3G

RAID Level RAID 1 (1 + 1) for Operating System

RAID 1 (1 + 1) for StorNext and Block pool metadata

Service Port 1 × 1 GbE

Characteristics of the 2.5’’ Nearline SAS hard disk

Width x Depth x Hight 70 × 100 × 15 (mm)

Weight 220 g

Drive Interface Serial Attached SCSI (3 Gb/s)

Capacity 300 GB

Speed 10 000 rounds per minute

Selected Storage Module Specifications

Weight Approx. 35 kg

Storage Units 12 × 3.5’’ 1 TB Nearline SAS hard disk

Interface to Server (from Basic Storage Module)

4 × Fibre Channel with 8 Gb/s each

RAID Level 2 x RAID 6 (4 + 2)

System Specifications Additional Storage Module Specifications

U41840-J-Z125-1-76 243

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10 S

tand

19:

23.5

0P

fad:

P:\

allg

em

ein\

CS

800

\100

050

0_F

TS

-Dok

u\1

0005

01_

Use

rGui

de\

A1_

Sys

tem

_Spe

cific

atio

ns.

fm

Table 52: Characteristics of the 3.5’’ SAS hard disks

Characteristics of the 3.5’’ Nearline SAS hard disk

Width x Depth x Hight 109 × 196 × 27 (mm)

Weight 1 kg

Drive Interface Serial Attached SCSI (3 Gb/s)

Capacity 1 TB

Speed 7200 rounds per minute

Additional Storage Module Specifications System Specifications

244 U41840-J-Z125-1-76

U41840-J-Z125-1-76 245

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\A

2_G

loss

ary

.fm

Glossary

A

Adaptive In-line Data Deduplication

When you select Enable Data Deduplication for the NAS share, data deduplication is running all of the time and cannot be disabled. Backup data is sent to the ETERNUS CS800 and data deduplication is performed on data as it is ingested. Data deduplication begins when the backup begins. The advantage of selecting adaptive in-line data deduplication is that disk space is saved immediately.

B

Block Pool

A pool of all unique data blocks that were captured during the data deduplication cycle. When backup jobs occur, the data deduplication engine searches for new data entering the CS800 and uses a variable length compression type algorithm to compare this to existing data in the block pool. Unique blocks are added to the block pool and all known blocks are indexed.

Byte

The basic unit of computer memory which is large enough to hold one character.

C

Compress

A process of removing fine-grained redundancy from data prior to storing or transmitting it. The granularity may vary, but generally compression deals with redundancy in grains of a few bytes.

Glossary

246 U41840-J-Z125-1-76

D

Data Deduplication

A process of removing coarse-grained redundancy from data prior to storing or transmitting it. The granularity may vary, but generally data deduplication deals with redundancy in grains of several kilobytes.

Deferred Processing Data Deduplication

When you select Enable Backup Window for the NAS share, data deduplication is disabled for a specific time period allowing better throughput performance during this period of time. All of the backup data is sent to the CS800 immediately in its raw form without data deduplication. After the backup window is closed and data deduplication is re-enabled, the data that was moved during the backup windows is now deduplicated on the CS800. The advantage of deferred processing data deduplication is that backups will complete faster with system resources dedicated for incoming backup data.

Disk

A fixed set of sectors with sequential numbers starting from zero, directly and independently accessible and mutable by those numbers without affecting any other sector.

F

Filesystem

An abstraction layered over storage devices (typically disks) obscuring the physical details of the storage devices it supports n favor of a presentation oriented at storing and organizing files.

H

Host

The device or devices to which the system is connected.

I

Ingest

The throughput performance of data writes to the system.

Glossary

U41840-J-Z125-1-76 247

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31.

Mär

z 20

10

Sta

nd 1

9:23

.50

Pfa

d: P

:\al

lge

mei

n\C

S80

0\1

0005

00_

FT

S-D

oku

\100

050

1_U

serG

uid

e\A

2_G

loss

ary

.fm

L

LSU

Logical Storage Unit

N

NAS

Network Attached Storage is file-level computer data storage connected to a computer network providing data access to network clients.

NDMP

Network Data Management Protocol is a protocol meant to transport data between NAS devices, also known as filers, and backup devices. This removes the need for transporting the data through the backup server itself, thus enhancing speed and removing load from the backup server.

O

OST

Open Storage Technology

R

RAID

Redundant Array of Independent Disks is a technology through which several physical storage disks are grouped into an array that appears to an operating system as one or more physical devices.

S

SNFS

StorNext® File System

Glossary

248 U41840-J-Z125-1-76

SNMP

Short for Simple Network Management Protocol, a set of protocols for managing complex networks.

T

Terabyte

A unit of measure for digital data equal to approximately 1,000 gigabytes, or 1,099,511,627,776 bytes.

Truncation

As long as free disk space is available, the CS800 retains native format data on disk to provide accelerated reads from cache. As disk space is required, the native format data is truncated and reads come from the data deduplication blockpool.

U41840-J-Z125-1-76 249

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

arch

201

0 S

tan

d 19

:23.

50P

fad

: P:\a

llgem

ein

\CS

800

\10

0050

0_F

TS

-Do

ku\1

000

501

_Use

rGui

de\0

_CS

800

_Use

r_G

uid

eIX

.fm

Index

Aaction/alerts

admin alerts 169service tickets 171

adaptive in-line data deduplication 54admin alerts 169advanced settings 98

opportunistic locking 98alerts 169

Bbrowsers 63

supported 68

Cclass A compliance statement 19common problems and solutions 212compression 25configuration

accessing 75date and time 116NAS 75network 105security 117

consumables 21contacts 131

company 131primary/secondary 132

contents section 70CRU 15CS800

configurations 28, 29problem reporting 209shutting down 51turning on 50

CS800 remote management pages 63CS800 system

rebooting 207CS800 web pages

alerts 169configuring the network 105configuring the security options 117using 70

customer replaceable unit 15

Ddata deduplication

adaptive in-line 54deferred processing 55

data reduced by section 71data replication 180data services

data replication 180space reclamation 177

date and timeconfiguring 116

deferred processing data deduplication 55displayed frames 70disposal, devices 22DVD drive activity indicator 35

Ee-mail, sending service tickets 175electrostatic-sensitive devices (ESD) 17email

configuration 122server 125

environmental protection 21ESD

electrostatic-sensitive devices) 17

Index

250 U41840-J-Z125-1-76

ETERNUS CS800configurations 28, 29

FFCC statement 19firmware

uploading 199frames, displayed 70

Ggeneral 177

Hhardware

details 158status 157summary 158

home pagecontents section 70data reduced by section 71nas data services section 72quick status section 71system details section 72system status buttons 73

hot-plugpower supply unit 229

IID button 34ID indicator 34indicators

DVD drive activity 35ID 34

internet browsers 63

Llabels 21laser information 16light emitting diode (LED) 16lithium battery 17login type

administrator 69monitor 69

NNAS

advanced settings 98CIFS 30configuration 75NFS 31shares 76windows domain 89

nas data services section 72network configuration

fields 79, 81, 84, 88, 97viewing/editing 105

network performance monitor 206NMI button 34

Oopportunistic locking 98

Ppackaging 21ports

USB 34, 35power supply unit

adding 230dummy module 229hot-plug 229replacing 230

problem reporting 209problems

Ethernet 215hardware 213replication 216start-up 212temperature 216

protocolCIFS 30NFS 31

Qquick status section 71

RRAID 5

definition 31

Index

U41840-J-Z125-1-76 251

Dok

usch

ablo

nen

qua

19x

24 V

ersi

on 1

.1us

für

Fra

me

Mak

er V

7.x

vom

25.

03.2

010

© c

ogn

itas

Gm

bH

20

01-2

010

31. M

arch

201

0 S

tan

d 19

:23.

50P

fad

: P:\a

llgem

ein

\CS

800

\10

0050

0_F

TS

-Do

ku\1

000

501

_Use

rGui

de\0

_CS

800

_Use

r_G

uid

eIX

.fm

rebooting 207recycling devices 22replication

data transmission 183disable 190enable 190namespace 183pause 190problems 216replication set transmission and

accounting 183requirements 182resume 190target role 190, 196

reset button 34, 35return of devices 22

Ssafety instructions 13saving energy 21screens, User Interface

Send Ticket Information 175Ticket Analysis 175

securityconfiguration 117passwords 117SSL 119

security options 117Send Ticket Information screen 175server

hot-plug power supply unit 229NMI button 34transport 20

service tickets 171, 217closing 175modifying 174sending by e-mail 175viewing 171

sharesNAS 76

SNMPcommunity 129community management 129configuration 127destinations 127test 130traps 128

source roleactions 189NAS 185

space managementgeneral 177schedule 179

space reclamation 177SSL 119

configuration 120status

hardware 157system 160

status pagessystem status 172

supported internet browsers 63supported web browsers 68system

CPU 161data deduplication 164disk usage 166Ethernet 163RAID 162status 160

system details section 72system status buttons 73system status page 172

Ttarget role 190, 196Ticket Analysis screen 175tickets

closing service 175modifying service 174sending service by e-mail 175viewing service 171

transporting the server 20

Index

252 U41840-J-Z125-1-76

UUSB port 34, 35utilities 199

firmware 199

Wwindows domain 89

joining a domain using a domain user credential 92

joining a windows domain 91joining a windows workgroup 90troubleshooting ADS join issues 94