Restorer Operating System User Guide

Transcription

Restorer Operating System
User Guide
Software Version 4.1.0
Disclaimer
The information contained in this publication is subject to change without notice. Data Domain,
Incorporated makes no warranty of any kind with regard to this manual, including, but not limited
to, the implied warranties of merchantability and fitness for a particular purpose. Data Domain,
Incorporated shall not be liable for errors contained herein or for incidental or consequential
damages in connection with the furnishing, performance, or use of this manual.
Notices
NOTE: Data Domain hardware has been tested and found to comply with the limits for a Class A
digital device, pursuant to Part 15 of the FCC Rules.
This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NMB-0003 du Canada.
These limits are designed to provide reasonable protection against harmful interference when the
equipment is operated in a commercial environment. This equipment generates, uses, and can
radiate radio frequency energy and, if not installed and used in accordance with the instruction
manual, may cause harmful interference to radio communications. Operation of this equipment in a
residential area is likely to cause harmful interference in which case the user will be required to
correct the interference at his own expense.
Changes or modifications not expressly approved by Data Domain can void the user's authority to
operate the equipment.
Data Domain Patents
Data Domain products are covered by one or more of the following patents issued to Data Domain.
U.S. Patents: 6928526, 7007141, 7065619. Data Domain has other patents pending.
Copyright
Copyright © 2005 - 2007 Data Domain, Incorporated. All rights reserved. Data Domain, the Data
Domain logo, Restorer Operating System, Data Domain OS, Global Compression, Data
Invulnerability Architecture, and all other Data Domain product names and slogans are trademarks
or registered trademarks of Data Domain, Incorporated in the USA and/or other countries.
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in
the United States and/or other countries. Portions of this product are software covered by the GNU
General Public License Copyright © 1989, 1991 by Free Software Foundation, Inc. Portions of this
product are software covered by the GNU Library General Public License Copyright © 1991 by
Free Software Foundation, Inc. Portions of this product are software covered by the GNU Lesser
General Public License Copyright © 1991, 1999 by Free Software Foundation, Inc. Portions of this
product are software covered by the GNU Free Documentation License Copyright © 2000, 2001,
2002, by Free Software Foundation, Inc. Portions of this product are software covered by the GNU
Free Documentation License Copyright © 2000, 2001, 2002 by Free Software Foundation, Inc.
Portions of this product aresoftware Copyright © 1999 - 2003, by The OpenLDAP Foundation.
Portions of this product are software developed by the OpenSSL Project for use in the OpenSSL
Toolkit (http://www.openssl.org/), Copyright © 1998-2005 The OpenSSL Project, all rights
reserved. Portions Copyright © 1999-2003 Apple Computer, Inc. All rights Reserved. Portions of
this product are Copyright © 1995 - 1998 Eric Young ([email protected]) All rights reserved.
Portions of this product are Copyright © Ian F. Darwin 1986-1995. All rights reserved. Portions of
this product are Copyright © Mark Lord 1994-2004. All rights reserved. Portions of this product
are Copyright © 1989-1997 Larry Wall All rights reserved. Portions of this product are Copyright
© Mike Glover 1995, 1996, 1997, 1998, 1999. All rights reserved. Portions of this product are
Copyright © 1992 by Panagiotis Tsirigotis. All rights reserved. Portions of this product are
Copyright © 2000-2002 Japan Network Information Center. All rights reserved. Portions of this
product are Copyright © 1988-2003 by Bram Moolenaar. All rights reserved. Portions of this
product are Copyright © 1994-2006 Lua.org, PUC-Rio. Portions of this product are Copyright ©
1990-2005 Info-ZIP. All rights reserved. Portions of this product are under the Boost Software
License - Version 1.0 - August 17th, 2003. All rights reserved. Portions of this product are
Copyright © 1994 Purdue Research Foundation. All rights reserved. This product includes
cryptographic software written by Eric Young ([email protected]). Portions of this product are
Berkeley Software Distribution software, Copyright © 1988 - 2004 by the Regents of the
University of California, University of California, Berkeley. Portions of this product are software
Copyright © 1990 - 1999 by Sleepycat Software. Portions of this product are software Copyright ©
1985-2004 by the Massachusetts Institute of Technology. All rights reserved. Portions of this
product are Copyright © 1999, 2000, 2001, 2002 The Board of Trustees of the University of
Illinois. All rights reserved. Portions of this product are LILO program code, Copyright © 1992 1998 Werner Almesberger. All rights reserved. Portions of this product are software Copyright ©
1999 - 2004 The Apache Software Foundation, licensed under the Apache License, Version 2.0
(http://www.apache.org/licenses /LICENSE-2.0). Portions of this product are derived from
software Copyright © 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002 by Cold Spring
Harbor Laboratory. Funded under Grant P41-RR02188 by the National Institutes of Health.
Portions of this product are derived from software Copyright © 1996, 1997, 1998, 1999, 2000,
2001, 2002 byBoutell.Com, Inc. Portions of this product relating to GD2 format are derived from
software Copyright © 1999, 2000, 2001, 2002 Philip Warner. Portions of this product relating to
PNG are derived from software Copyright © 1999, 2000, 2001, 2002 Greg Roelofs. Portions of this
product relating to gdttf.c are derived from software Copyright © 1999, 2000, 2001, 2002 John
Ellson ([email protected]). Portions of this product relating to gdft.c are derived from software
Copyright © 2001, 2002 John Ellson ([email protected]). Portions of this product relating to
JPEG and to color quantization are derived from software Copyright © 2000,2001, 2002, Doug
Becker and copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, Thomas G. Lane.
This software is based in part on the work of the Independent JPEG Group. Portions of this product
relating to WBMP are derived from software Copyright © 2000, 2001, 2002 Maurice Szmurlo and
Johan Van den Brande. Other product names and/or slogans mentioned herein may be trademarks
or registered trademarks of their respective companies.
Data Domain, Incorporated
2300 Central Expressway
Santa Clara, CA 95050
USA
Phone 408-980-4800 Direct
866-933-3837 Toll-free
Fax 408-980-8620
www.datadomain.com
Data Domain Software Release 4.1.0.1
December 20, 2006
Part number: 760-0401-0001 Rev. B
Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Contacting Data Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Safety Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi
Product Disposal Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi
Qualified Personnel Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Circuit Breaker (15A) Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii
Grounded Equipment Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix
Ground Conductor Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
Wrist Strap Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii
Faceplates and Cover Panel Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxiii
Jewelry Removal Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxv
Class 1 Laser Product Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvii
Invisible Laser Radiation Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii
Regulatory Standards Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix
EMC Environmental Conditions for Product to be Installed in the European Union . . xxxix
(FCC) Class A Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xl
Canada Class A Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xl
Japan (VCCI) Class A Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xl
Taiwan (BSMI) Class A Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xli
Hazardous Substance Regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xli
v
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Restorer Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Applications that Send Data to a Restorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Data Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Data Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Restore Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Data Domain Replicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Restorer Hardware Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Initial System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Hardware System-Level Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Back Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Power Supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Hardware Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
System Card Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Chapter 2: Disk Space and System Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Space Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Estimate Use of Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Manage File System Use of Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Display the Space Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Monitor Multiple Restorers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Reclaim Data Storage Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Maximum Number of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
vi
Chapter 3: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Restorer Site Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Expansion Shelf Site Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Restorer Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Backup Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
CIFS Backup Server Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Login and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Additional Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Administering a Restorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Data Domain Enterprise Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Chapter 4: ES20 Expansion Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
RAID groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Disk Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Add a First Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Add a Second Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Disk Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Look for New Disks, LUNs, and Expansion Shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Add an Expansion Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Display Disk Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Shelf (enclosure) Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
List Enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Identify an Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Display Fan Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Display Component Temperatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Display Port Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Display All Hardware Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Display Power Supply Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Volume Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Contents
vii
Chapter 5: Gateway Restorers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Command Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Procedure: Adding a LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Chapter 6: Virtual Tape Library (VTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Compatibility Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Data Domain VTL with a SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Enable VTLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Disable VTLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Create a VTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Create New Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Import Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Export Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Remove Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Insert a Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Eject a Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Delete a VTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Set a Private-Loop Hard Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Reset a Private-Loop Hard Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Display the Private-Loop Hard Address Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Display VTL Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Display VTL Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Display All Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Display a Summary of All Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Display Tapes by VTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Display All Tapes in the Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Display Tapes by Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Display VTL Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Procedure: Retrieve a Replicated Tape from a Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
viii
LUN Masking (for VTL Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
The vtl initiator Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Add an Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Delete an Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Display Initiators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
The vtl lunmask Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Add a LUN Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Delete a LUN Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Display LUN Masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Procedure: Create a LUN Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Add a Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Delete a Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Display Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Chapter 7: Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
The config Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Change Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Save and Return a Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Reset the Location Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Reset the Mail Server to a Null Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Reset the Time Zone to the Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Set an Administrative Email Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Set an Administrative Host Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Change the System Location Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Change the Mail Server Hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Set a Time Zone for the System Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Display the Administrative Email Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Display the Administrative Host Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Display the System Location Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Contents
ix
Display the Mail Server Hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Display the Time Zone for the System Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
The license Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Add a License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Remove All Feature Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Remove a License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Display Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Set Up the Migration Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Start Migration from the Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Create an End Point for Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Display Migration Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Stop the Migration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Display Migration Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Display Migration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Procedure: Migrate between Source and Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Procedure: Migrate with Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Chapter 8: Access Control for Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Add a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Remove a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Enable a Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Disable a Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Reset System Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Add an Authorized SSH Public Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Remove an SSH Key File Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Remove the SSH Key File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Create a New HTTPS Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Display the SSH Key File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Display Hosts and Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Procedure: Return Command Output to a Remote machine . . . . . . . . . . . . . . . . . . . . . . . . . 107
x
Chapter 9: User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Add a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Remove a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Change a Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Reset to the Default User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Change a Privilege Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Display Current Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Display All Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Chapter 10: Alerts and System Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Add to the Email List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Test the Email List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Remove from the Email List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Reset the Email List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Display Current Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Display the Alerts History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Display the Email List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Display Current Alerts and Recent History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Display the Email List and Administrator Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Autosupport Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Add to the Email List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Test the Autosupport Report Email List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Send an Autosupport Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Remove from the Email List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Reset the Email List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Run the Autosupport Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Email Command Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Set the Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Reset the Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Reset the Schedule and the List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Contents
xi
Display all Autosupport Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Display the Autosupport Email List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Display the Autosupport Report Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Display the Autosupport History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Hourly System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Collect and Send Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Chapter 11: File System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Statistics and Basic Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Start the Restorer File System Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Stop the Restorer File System Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Stop and Start the Restorer File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Delete All Data in the File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Display File System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Display File System Uptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Display File System Space Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Display Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Clean Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Start Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Stop Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Change the Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Set the Schedule or Throttle to the Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Set Network Bandwidth Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Update Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Display All Clean Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Display the Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Display the Throttle Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Display the Clean Operation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Monitor the Clean Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
xii
Compression Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Local Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Set Local Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Reset Local Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Display the Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Global Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Set Global Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Reset Global Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Display the Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Replicator Destination Read/Write Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Report as Read/Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Report as Read-Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Return to the Default Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Display the Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Tape Marker Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Set a Marker Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Reset to the Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Display the Marker Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Chapter 12: Disk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Add a LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Fail a Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Unfail a Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Check All Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Look for New Disks, LUNs, and Expansion Shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Identify a Physical Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Add an Expansion Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Reset Disk Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Display Disk Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Display Disk Type and Capacity Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Display RAID Status for Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Contents
xiii
Display the History of Disk Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Display Detailed RAID Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Display Disk Performance Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Display Disk Reliability Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Chapter 13: System Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
The system Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Shut down the Restorer Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Reboot the Restorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Upgrade the Restorer Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
To upgrade using HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
To upgrade using FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Set the Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Create a Login Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Reset the Login Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Display the Login Banner Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Display the Restorer Serial Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Display System Uptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Display System Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Display Detailed System Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Display System Statistics Graphically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Display System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Display the Restorer Model Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Display Data Transfer Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Display the Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Display NVRAM Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Display Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Display the Data Domain OS Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Display All System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
xiv
The alias Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Add an Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Remove an Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Reset Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Display Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Time Servers and the NTP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Enable NTP Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Disable NTP Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Add a Time Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Delete a Time Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Reset the List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Reset All NTP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Display NTP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Display NTP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Chapter 14: Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
The net Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Enable an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Disable an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Enable DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Disable DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Change an Interface Netmask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Change an Interface Transfer Unit Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Add or Change DNS servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Ping a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Change the Restorer Hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Change an Interface IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Change the Domain Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Add a Hostname/IP Address to the /etc/hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Reset Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Set Interface Duplex Line Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Contents
xv
Set Interface Line Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Set Autonegotiate for an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Delete a Hostname/IP address from the /etc/hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Delete all Hostname/IP addresses from the /etc/hosts File . . . . . . . . . . . . . . . . . . . . . . . 172
Display Hostname/IP addresses from the /etc/hosts File . . . . . . . . . . . . . . . . . . . . . . . . . 172
Display an Ethernet Interface Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Display Interface Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Display Ethernet Hardware Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Display the Restorer Hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Display the Domain Name Used for Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Display DNS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Display Network Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Display All Networking Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
The route Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Add a Routing Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Remove a Routing Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Change the Routing Default Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Reset the Default Routing Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Display a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Display the Configured Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Display the Kernel IP Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Display the Default Routing Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Chapter 15: NFS Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Add NFS Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Remove Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Enable Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Disable Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Reset Clients to the Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Clear the NFS Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Display Active Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
xvi
Display Allowed Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Display Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Display Detailed Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Display Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Display Timing for NFS Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Chapter 16: CIFS Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
CIFS Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Add a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Add a Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
CIFS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Enable Client Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Disable Client Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Add a Backup Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Add an Administrative Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Remove a Backup Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Remove an Administrative Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Remove All CIFS Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Set a NetBIOS Hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Remove the NetBIOS Hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Set the Authentication Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Remove All IP Address/NetBIOS hostname Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Add an IP Address/NetBIOS hostname Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Remove an IP Address/NetBIOS hostname Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Resolve a NetBIOS Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Identify a WINS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Remove the WINS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Set CIFS Logging Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Increase Memory to Allow More User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Reset CIFS Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Display CIFS Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Contents
xvii
Display Active Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Display All Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Display the CIFS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Display CIFS Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Display Detailed CIFS Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Display CIFS Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Display All IP Address/NetBIOS hostname Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Procedure: Time Servers and Active Directory Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Synchronizing from an NTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Synchronizing from a Windows Domain Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Chapter 17: Replicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Using “Context” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Configure Replicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
VTL Pools Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Start Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Suspend Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Resume Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Remove Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Reset Authentication between the Restorers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Move Data to a New Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Change a Source or Destination Hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Connect with a Network Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Change the Port on a Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Add a Scheduled Throttle Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Set a Temporary Throttle Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Delete a Scheduled Throttle Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Set an Override Throttle Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Reset Throttle Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Set Replication Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Set Replication Network Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
xviii
Reset Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Repair a Broken Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Display Throttle settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Display Bandwidth and Delay Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Display Replicator Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Display Replication for Current Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Display Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Display Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Hostname Shorthand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Procedure: Set Up and Start Directory Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Procedure: Set Up and Start Collection Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Procedure: Set Up and Start Bidirectional Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Procedure: Set Up and Start Many-to-One Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Procedure: Replace a Directory Source - New Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Procedure: Replace a Collection Source - Same Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Procedure: Convert from Collection to Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Procedure: Seeding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
One-to-One . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Bidirectional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Many-to-One . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Chapter 18: Backup/Restore Using NDMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Add a Filer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Remove a Filer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Backup from a Filer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Restore to a Filer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Remove Filer Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Stop an NDMP Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Stop All NDMP Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Check for a Filer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Contents
xix
Display Known Filers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Display NDMP Process Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Chapter 19: SNMP Management and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Enable SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Disable SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Set the System Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Reset the System Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Set a System Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Reset a System Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Add a Trap Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Delete a Trap Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Delete All Trap Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Add a Community String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Delete a Community String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Delete All Community Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Reset All SNMP Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Display SNMP Agent status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Display Trap Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Display All Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Display the System Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Display the System Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Display Community Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Display the MIB and Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Chapter 20: Log File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Scroll New Log Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Send Log Messages to Another System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Add a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Remove a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Enable Sending Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
xx
Disable Sending Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Reset to Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Display the List and State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Display a Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
List Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Procedure: Archive Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Chapter 21: Hardware Servicing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Customer Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Replace Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Replace Power Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Trained Service Personnel Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Remove/Replace the Top Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Replace Fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Replace Disk Fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Replace Back Panel Fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Replace the Motherboard Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Appendix A Time Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Contents
xxi
xxii
About This Guide
This guide explains the use of Data Domain® DD400/DD500 backup and recovery restorers.
•
The “Introduction” chapter explains what the Data Domain restorers are and how they work,
details features, lists hardware and software requirements, and gives overviews of installation
and configuration tasks, the default configuration, and user interface commands.
•
The “Disk Space and System Monitoring” chapter gives guidelines for managing disk space on
Data Domain restorers and for setting up backup servers to get the best performance.
•
The “Installation” chapter gives all installation steps and information for setting up backup
software to use a restorer.
The next set of chapters detail the use of all user interface commands and operations. Each chapter
has headings that are a task-oriented list of the operations detailed in that chapter. For any task that
you want to perform, look in the table of contents for the heading that describes the task.
•
The “Gateway Restorers” chapter gives installation steps and other information specific to
restorers that use outside disk arrays instead of internal disks or external shelves.
•
The “Virtual Tape Library (VTL)” chapter explains the use of the virtual tape library feature.
•
The “Configuration Management” chapter describes how to examine and modify configuration
parameters.
•
The “Access Control for Administration” chapter describes how to give HTTP, FTP, TELNET,
and SSH access from remote hosts.
•
The “User Administration” chapter explains how to deal with users and passwords.
•
The “Alerts and System Reports” chapter details messages that the Data Domain Operating
System (DDOS) sends when monitoring components and details the daily system report.
•
The “File System Management” chapter gives details about file system statistics and capacity.
•
The “Disk Management” chapter explains how to monitor and manage disks on a restorer.
•
The “System Maintenance” chapter describes how to manage the background maintenance
task that continually checks the integrity of backup images, how to connect to time servers, and
how to set up alias commands.
•
The “Network Management” chapter describes how to manage network tasks such as routing
rules, the use of DHCP and DNS, and the setting IP addresses.
xxiii
Conventions
•
The “NFS Management” chapter describes how to deal with NFS clients and status.
•
The “CIFS Management” chapter details the use of Windows backup servers with a restorer.
•
The “Replicator” chapter details use of the Data Domain Replicator product for replication of
data from one restorer to another.
•
The “Backup/Restore Using NDMP” chapter explains how to do direct backup and restore
operations between a restorer and an NDMP-type filer.
•
The “SNMP Management and Monitoring” chapter details the use of SNMP operations
between a restorer and remote machines.
•
The “Log File Management” chapter explains how to view, archive, and clear the log file.
The final chapter, “Hardware Servicing,” explains how to replace disks, fans, power supply units,
and other hardware. The appendix lists all time zones from around the world.
Conventions
The following table describes the typographic conventions used in this guide.
xxiv
Typeface
Usage
Examples
Monospace
Commands, computer output, file contents,
files, directories, software elements such as
command options, and parameters
Find the log file under /var/log.
Italic
New terms, book titles, variables, and labels
of boxes and windows as seen on a monitor
The name is a path for the device...
Monospace
bold
User input; the “#” symbol indicates a
command prompt.
# config setup
Symbol
Usage
Examples
#
Administrative user prompt
[]
In a command synopsis, brackets indicate an
optional argument
log view [filename]
|
In a command synopsis, a vertical bar
separates mutually exclusive arguments
net dhcp [true | false]
{}
In a command synopsis, curly brackets
indicate that one of the exclusive arguments
is required.
adminhost add
{ftp | telnet | ssh}
See the net help page for more
information.
Audience
Audience
This guide is for system administrators who are familiar with standard backup software packages
and with general backup administration.
Contacting Data Domain
For comments or problems with Data Domain products, contact Data Domain Technical Support:
•
24 hours a day, 7 days a week at 877-207-DATA (3282) (toll free) or 408-980-4900 (direct)
•
email: [email protected]
For sales and license information:
•
877-622-2587
•
email: [email protected]
•
Fax: 408-980-8620
Data Domain, Incorporated
2300 Central Expressway
Santa Clara, CA 95050
USA
Phone 408-980-4800 Direct
866-933-3837 Toll-free
Fax 408-980-8620
About This Guide
xxv
Safety Warnings
Safety Warnings
Product Disposal Warning
Warning Ultimate disposal of this product should be handled according to all national laws
and regulations.
Waarschuwing
Het uiteindelijke wegruimen van dit product dient te geschieden in
overeenstemming met alle nationale wetten en reglementen.
Varoitus
Tämä tuote on hävitettävä kansallisten lakien ja määräysten mukaisesti.
Attention
La mise au rebut ou le recyclage de ce produit sont généralement soumis à des lois et/ou
directives de respect de l'environnement. Renseignez-vous auprès de l'organisme
compétent.
Warnung
Die Entsorgung dieses Produkts sollte gemäß allen Bestimmungen und Gesetzen des
Landes erfolgen.
Lo smaltimento di questo prodotto deve essere eseguito secondo le leggi e regolazioni
locali.
Avvertenza
Advarsel
Aviso
Endelig kassering av dette produktet skal være i henhold til alle relevante nasjonale lover
og bestemmelser.
Deitar fora este produto em conformidade com todas as leis e regulamentos nacionais.
¡Advertencia!
xxvi
Al deshacerse por completo de este producto debe seguir todas las leyes y
reglamentos nacionales.
Safety Warnings
Vid deponering hanteras produkten enligt gällande lagar och bestämmelser.
Varning!
Qualified Personnel Warning
Warning Only trained and qualified personnel should be allowed to install or replace this
equipment.
Waarschuwing
Ainoastaan koulutettu ja pätevä henkilökunta saa asentaa tai vaihtaa tämän laitteen.
Varoitus
Avertissement
Avvertenza
Aviso
About This Guide
Tout installation ou remplacement de l'appareil doit être réalisé par du personnel
qualifié et compétent.
Gerät nur von geschultem, qualifiziertem Personal installieren oder auswechseln lassen.
Achtung
Advarsel
Installatie en reparaties mogen uitsluitend door getraind en bevoegd personeel
uitgevoerd worden.
Solo personale addestrato e qualificato deve essere autorizzato ad installare o sostituire
questo apparecchio.
Kun kvalifisert personell med riktig opplæring bør montere eller bytte ut dette utstyret.
Este equipamento deverá ser instalado ou substituído apenas por pessoal devidamente treinado e
qualificado.
xxvii
Safety Warnings
¡Atención!
Varning
Estos equipos deben ser instalados y reemplazados exclusivamente por personal técnico
adecuadamente preparado y capacitado.
Denna utrustning ska endast installeras och bytas ut av utbildad och kvalificerad personal.
Circuit Breaker (15A) Warning
Warning This product relies on the building's installation for short-circuit (overcurrent)
protection. Ensure that a fuse or circuit breaker no larger than 120 VAC, 15A U.S. (240
VAC, 10A international) is used on the phase conductors (all current-carrying conductors).
Waarschuwing
Dit produkt is afhankelijk van de installatie van het gebouw voor kortsluit(overstroom) beveiliging. Controleer of er een zekering of stroomverbreker van
niet meer dan 120 Volt wisselstroom, 15 A voor de V.S. (240 Volt wisselstroom,
10 A internationaal) gebruikt wordt op de fasegeleiders (alle geleiders die stroom
voeren).
Varoitus
Tämä tuote on riippuvainen rakennukseen asennetusta oikosulkusuojauksesta
(ylivirtasuojauksesta). Varmista, että vaihevirtajohtimissa (kaikissa virroitetuissa
johtimissa) käytetään Yhdysvalloissa alle 120 voltin, 15 ampeerin ja monissa muissa
maissa 240 voltin, 10 ampeerin sulaketta tai suojakytkintä.
Attention
Pour ce qui est de la protection contre les courts-circuits (surtension), ce produit dépend
de l'installation électrique du local. Vérifier qu'un fusible ou qu'un disjoncteur de 120 V
alt., 15 A U.S. maximum (240 V alt., 10 A international) est utilisé sur les conducteurs de
phase (conducteurs de charge).
Warnung
Dieses Produkt ist darauf angewiesen, daß im Gebäude ein Kurzschluß- bzw.
Überstromschutz installiert ist. Stellen Sie sicher, daß eine Sicherung oder ein Unterbrecher
von nicht mehr als 240 V Wechselstrom, 10 A (bzw. in den USA 120 V Wechselstrom, 15
A) an den Phasenleitern (allen stromführenden Leitern) verwendet wird.
xxviii
Safety Warnings
Questo prodotto dipende dall'installazione dell'edificio per quanto riguarda la protezione
contro cortocircuiti (sovracorrente). Verificare che un fusibile o interruttore automatico,
non superiore a 120 VCA, 15 A U.S. (240 VCA, 10 A internazionale) sia stato usato nei
fili di fase (tutti i conduttori portatori di corrente).
Avvertenza
Advarsel
Aviso
Dette produktet er avhengig av bygningens installasjoner av kortslutningsbeskyttelse
(overstrøm). Kontroller at det brukes en sikring eller strømbryter som ikke er større enn
120 VAC, 15 A (USA) (240 VAC, 10 A internasjonalt) på faselederne (alle strømførende
ledere).
Este produto depende das instalações existentes para protecção contra curto-circuito
(sobrecarga). Assegure-se de que um fusível ou disjuntor não superior a 240 VAC, 10A é
utilizado nos condutores de fase (todos os condutores de transporte de corrente).
¡Advertencia!
Varning!
Este equipo utiliza el sistema de protección contra cortocircuitos (o sobrecorrientes)
deló propio edificio. Asegurarse de que se utiliza un fusible o interruptor
automático de no más de 240 voltios en corriente alterna (VAC), 10 amperios del
estándar internacional (120 VAC, 15 amperios del estándar USA) en los hilos de
fase (todos aquéllos portadores de corriente).
Denna produkt är beroende av i byggnaden installerat kortslutningsskydd
(överströmsskydd). Kontrollera att säkring eller överspänningsskydd används på fasledarna
(samtliga strömförande ledare) för internationellt bruk max. 240 V växelström, 10 A (i
USA max. 120 V växelström, 15 A).
Grounded Equipment Warning
Warning This equipment is intended to be grounded. Ensure that the host is connected to
earth ground during normal use.
About This Guide
xxix
Safety Warnings
Waarschuwing
Tämä laitteisto on tarkoitettu maadoitettavaksi. Varmista, että isäntälaite on yhdistetty
maahan normaalikäytön aikana.
Varoitus
Attention
Warnung
Cet équipement doit être relié à la terre. S'assurer que l'appareil hôte est relié à la terre
lors de l'utilisation normale.
Dieses Gerät muß geerdet werden. Stellen Sie sicher, daß das Host-Gerät während des
normalen Betriebs an Erde gelegt ist.
Questa apparecchiatura deve essere collegata a massa. Accertarsi che il dispositivo host
sia collegato alla massa di terra durante il normale utilizzo.
Avvertenza
Advarsel
Aviso
Dette utstyret skal jordes. Forviss deg om vertsterminalen er jordet ved normalt bruk.
Este equipamento deverá estar ligado à terra. Certifique-se que o host se encontra ligado à terra
durante a sua utilização normal.
¡Advertencia!
Varning!
xxx
Deze apparatuur hoort geaard te worden Zorg dat de host-computer tijdens
normaal gebruik met aarde is verbonden.
Este equipo debe conectarse a tierra. Asegurarse de que el equipo principal esté
conectado a tierra durante el uso normal.
Denna utrustning är avsedd att jordas. Se till att värdenheten är jordad vid normal
användning.
Safety Warnings
Ground Conductor Warning
Warning Never defeat the ground conductor or operate the equipment in the absence of a
suitably installed ground conductor. Contact the appropriate electrical inspection authority
or an electrician if you are uncertain that suitable grounding is available.
Waarschuwing
De aardingsleiding mag nooit buiten werking gesteld worden en de apparatuur mag
nooit bediend worden zonder dat er een op de juiste wijze geïnstalleerde
aardingsleiding aanwezig is. Neem contact op met de bevoegde instantie voor
elektrische inspecties of met een elektricien als u er niet zeker van bent dat er voor
passende aarding gezorgd is.
Varoitus
Älä koskaan ohita maajohdinta tai käytä laitteita ilman oikein asennettua maajohdinta. Ota
yhteyttä asianmukaiseen sähkötarkastusviranomaiseen tai sähköasentajaan, jos olet
epävarma maadoituksen sopivuudesta.
Attention
Ne jamais rendre inopérant le conducteur de masse ni utiliser l'équipement sans un
conducteur de masse adéquatement installé. En cas de doute sur la mise à la masse
appropriée disponible, s'adresser à l'organisme responsable de la sécurité électrique ou à un
électricien.
Warnung
Auf keinen Fall den Erdungsleiter unwirksam machen oder das Gerät ohne einen
sachgerecht installierten Erdungsleiter verwenden. Wenn Sie sich nicht sicher sind, ob eine
sachgerechte Erdung vorhanden ist, wenden Sie sich an den zuständigen elektrischen
Fachmann oder einen Elektriker.
Avvertenza
Advarsel
About This Guide
Non escludere mai il conduttore di protezione né usare l'apparecchiatura in assenza di un
conduttore di protezione installato in modo corretto. Se non si sa con certezza che è
disponibile un collegamento di messa a terra adeguato, esaminare le Norme CEI
pertinenti o rivolgersi a un elettricista qualificato.
Omgå aldri jordingslederen og bruk aldri utstyret uten riktig montert jordingsleder. Ta
kontakt med det riktige organet for elektrisk inspeksjon eller en elektriker hvis du er usikker
på om det finnes velegnet jording.
xxxi
Safety Warnings
Aviso
Nunca anule o condutor à terra nem opere o equipamento sem ter um condutor à terra
adequadamente instalado. Em caso de dúvida em relação ao sistema de ligação à terra, contacte
os serviços locais de inspecção eléctrica ou um electricista qualificado.
¡Advertencia!
Varning!
No inhabilitar nunca el conductor de tierra ni hacer funcionar el equipo si no existe un
conductor de tierra instalado correctamente. Póngase en contacto con una autoridad
apropiada de inspección eléctrica o con un electricista competente si no está seguro de
que hay una conexión a tierra adecuada.
Koppla aldrig från jordledningen och använd aldrig utrustningen utan en på lämpligt sätt
installerad jordledning. Om det föreligger osäkerhet huruvida lämplig jordning finns skall
elektrisk besiktningsauktoritet eller elektriker kontaktas.
Wrist Strap Warning
Warning During this procedure, wear grounding wrist straps to avoid ESD damage to the
card. Do not directly touch the backplane with your hand or any metal tool, or you could
shock yourself.
Waarschuwing
Varoitus
Attention
xxxii
Draag tijdens deze procedure aardingspolsbanden om te vermijden dat de kaart
beschadigd wordt door elektrostatische ontlading. Raak het achterbord niet
rechtstreeks aan met uw hand of met een metalen werktuig, omdat u anders een
elektrische schok zou kunnen oplopen.
Käytä tämän toimenpiteen aikana maadoitettuja rannesuojia estääksesi kortin vaurioitumisen
sähköstaattisen purkauksen vuoksi. Älä kosketa taustalevyä suoraan kädelläsi tai metallisella
työkalulla sähköiskuvaaran takia.
Lors de cette procédure, toujours porter des bracelets antistatiques pour éviter que des
décharges électriques n'endommagent la carte. Pour éviter l'électrocution, ne pas toucher le
fond de panier directement avec la main ni avec un outil métallique.
Safety Warnings
Warnung
Zur Vermeidung einer Beschädigung der Karte durch elektrostatische Entladung während
dieses Verfahrens ein Erdungsband am Handgelenk tragen. Bei Berührung der Rückwand
mit der Hand oder einem metallenen Werkzeug besteht Elektroschockgefahr.
Durante questa procedura, indossare bracciali antistatici per evitare danni alla scheda
causati da un'eventuale scarica elettrostatica. Non toccare direttamente il pannello delle
connessioni, né con le mani né con un qualsiasi utensile metallico, perché esiste il
pericolo di folgorazione.
Avvertenza
Advarsel
Aviso
Bruk jordingsarmbånd under prosedyren for å unngå ESD-skader på kortet. Unngå direkte
berøring av bakplanet med hånden eller metallverktøy, slik at di ikke får elektrisk støt.
Durante este procedimento e para evitar danos ESD causados à placa, use fitas de ligação à terra
para os pulsos. Para evitar o risco de choque eléctrico, não toque directamente na parte posterior
com a mão ou com qualquer ferramenta metálica.
¡Advertencia!
Varning!
Usartiras conectadas a tierra en las muñecas durante este procedimiento para evitar
daños en la tarjeta causados por descargas electrostáticas. No tocar el plano posterior
con las manos ni con ninguna herramienta metálica, ya que podría producir un choque
eléctrico.
Använd jordade armbandsremmar under denna procedur för att förhindra elektrostatisk skada
på kortet. Rör inte vid baksidan med handen eller metallverktyg då detta kan orsaka elektrisk
stöt.
Faceplates and Cover Panel Requirement
Warning Blank faceplates and cover panels serve three important functions: they prevent
exposure to hazardous voltages and currents inside the chassis; they contain
electromagnetic interference (EMI) that might disrupt other equipment; and they direct the
flow of cooling air through the chassis. Do not operate the system unless all cards,
faceplates, front covers, and rear covers are in place.
About This Guide
xxxiii
Safety Warnings
Waarschuwing
Varoitus
Lege vlakplaten en afdekpanelen vervullen drie belangrijke functies: ze voorkomen
blootstelling aan gevaarlijke voltages en stroom binnenin het frame, ze bevatten
elektromagnetische storing (EMI) hetgeen andere apparaten kan verstoren en ze
leiden de stroom van koellucht door het frame. Het systeem niet bedienen tenzij alle
kaarten, vlakplaten en afdekkingen aan de voor- en achterkant zich op hun plaats
bevinden.
Tyhjillä tasolaikoilla ja suojapaneeleilla on kolme tärkeää käyttötarkoitusta: Ne suojaavat
asennuspohjan sisäisille vaarallisille jännitteille ja sähkövirralle altistumiselta; ne pitävät
sisällään elektromagneettisen häiriön (EMI), joka voi häiritä muita laitteita; ja ne suuntaavat
tuuletusilman asennuspohjan läpi. Järjestelmää ei saa käyttää, elleivät kaikki tasolaikat,
etukannet ja takakannet ole kunnolla paikoillaan.
Attention
Ne jamais faire fonctionner le système sans que l'intégralité des cartes, des plaques
métalliques et des panneaux avant et arrière ne soient fixés à leur emplacement. Ceux-ci
remplissent trois fonctions essentielles : ils évitent tout risque de contact avec des tensions
et des courants dangereux à l'intérieur du châssis, ils évitent toute diffusion d'interférences
électromagnétiques qui pourraient perturber le fonctionnement des autres équipements, et
ils canalisent le flux d'air de refroidissement dans le châssis.
Warnung
Blanke Faceplates und Abdeckungen haben drei wichtigen Funktionen: (1) Sie schützen
vor gefährlichen Spannungen und Strom innerhalb des Chassis; (2) sie halten
elektromagnetische Interferenzen (EMI) zurück, die andere Geräte stören könnten; (3) sie
lenken den kühlenden Luftstrom durch das Chassis. Das System darf nur betrieben werden,
wenn alle Karten, Faceplates, Voder- und Rückabdeckungen an Ort und Stelle sind.
Avvertenza
xxxiv
Le piattaforme bianche e i panelli di protezione hanno tre funzioni importanti: Evitano
l'esposizione a voltaggi e correnti elettriche pericolose nello chassis, trattengono le
interferenze elettromagnetiche (EMI) che potrebbero scombussolare altri apparati e
dirigono il flusso di aria per il raffreddamento attraverso lo chassis. Non mettete in
funzione il sistema se le schede, le piattaforme, i panelli frontali e posteriori non sono in
posizione.
Safety Warnings
Advarsel
Aviso
Blanke ytterplater og deksler sørger for tre viktige funksjoner: de forhindrer utsettelse for
farlig spenning og strøm inni kabinettet; de inneholder elektromagnetisk forstyrrelse (EMI)
som kan avbryte annet utstyr, og de dirigerer luftavkjølingsstrømmen gjennom kabinettet.
Betjen ikke systemet med mindre alle kort, ytterplater, frontdeksler og bakdeksler sitter på
plass.
As faces furadas e os painéis de protecção desempenham três importantes funções: previnem
contra uma exposição perigosa a voltagens e correntes existentes no interior do chassis; previnem
contra interferência electromagnética (EMI) que poderá danificar outro equipamento; e
canalizam o fluxo do ar de refrigeração através do chassis. Não deverá operar o sistema sem que
todas as placas, faces, protecções anteriores e posteriores estejam nos seus lugares.
¡Advertencia!
Varning!
Las placas frontales y los paneles de relleno cumplen tres funciones importantes:
evitan la exposición a niveles peligrosos de voltaje y corriente dentro del chasis;
reducen la interferencia electromagnética (EMI) que podría perturbar la operación de
otros equipos y dirigen el flujo de aire de enfriamiento a través del chasis. No haga
funcionar el sistema a menos que todas las tarjetas, placas frontales, cubiertas
frontales y cubiertas traseras estén en su lugar.
Tomma framplattor och skyddspaneler har tre viktiga funktioner: de förhindrar att personer
utsätts för farlig spänning och ström som finns inuti chassit; de innehåller elektromagnetisk
interferens (EMI) som kan störa annan utrustning; och de styr riktningen på kylluftsflödet
genom chassit. Använd inte systemet om inte alla kort, framplattor, fram- och bakskydd är
på plats.
Jewelry Removal Warning
Warning Before working on equipment that is connected to power lines, remove jewelry
(including rings, necklaces, and watches). Metal objects will heat up when connected to
power and ground and can cause serious burns or weld the metal object to the terminals.
About This Guide
xxxv
Safety Warnings
Waarschuwing
Alvorens aan apparatuur te werken die met elektrische leidingen is verbonden,
sieraden (inclusief ringen, kettingen en horloges) verwijderen. Metalen
voorwerpen worden warm wanneer ze met stroom en aarde zijn verbonden, en
kunnen ernstige brandwonden veroorzaken of het metalen voorwerp aan de
aansluitklemmen lassen.
Ennen kuin työskentelet voimavirtajohtoihin kytkettyjen laitteiden parissa, ota pois kaikki
korut (sormukset, kaulakorut ja kellot mukaan lukien). Metalliesineet kuumenevat, kun ne
ovat yhteydessä sähkövirran ja maan kanssa, ja ne voivat aiheuttaa vakavia palovammoja tai
hitsata metalliesineet kiinni liitäntänapoihin.
Varoitus
Attention
Avant d'accéder à cet équipement connecté aux lignes électriques, ôter tout bijou (anneaux,
colliers et montres compris). Lorsqu'ils sont branchés à l'alimentation et reliés à la terre, les
objets métalliques chauffent, ce qui peut provoquer des blessures graves ou souder l'objet
métallique aux bornes.
Warnung
Vor der Arbeit an Geräten, die an das Netz angeschlossen sind, jeglichen Schmuck
(einschließlich Ringe, Ketten und Uhren) abnehmen. Metallgegenstände erhitzen sich,
wenn sie an das Netz und die Erde angeschlossen werden, und können schwere
Verbrennungen verursachen oder an die Anschlußklemmen angeschweißt werden.
Avvertenza
Advarsel
Aviso
xxxvi
Prima di intervenire su apparecchiature collegate alle linee di alimentazione, togliersi
qualsiasi monile (inclusi anelli, collane, braccialetti ed orologi). Gli oggetti metallici si
riscaldano quando sono collegati tra punti di alimentazione e massa: possono causare
ustioni gravi oppure il metallo può saldarsi ai terminali.
Fjern alle smykker (inkludert ringer, halskjeder og klokker) før du skal arbeide på utstyr som
er koblet til kraftledninger. Metallgjenstander som er koblet til kraftledninger og jord blir
svært varme og kan forårsake alvorlige brannskader eller smelte fast til polene.
Antes de trabalhar em equipamento que esteja ligado a linhas de corrente, retire todas as jóias
que estiver a usar (incluindo anéis, fios e relógios). Os objectos metálicos aquecerão em contacto
com a corrente e em contacto com a ligação à terra, podendo causar queimaduras graves ou
ficarem soldados aos terminais.
Safety Warnings
¡Advertencia!
Varning!
Antes de operar sobre equipos conectados a líneas de alimentación, quitarse las joyas
(incluidos anillos, collares y relojes). Los objetos de metal se calientan cuando se
conectan a la alimentación y a tierra, lo que puede ocasionar quemaduras graves o
que los objetos metálicos queden soldados a los bornes.
Tag av alla smycken (inklusive ringar, halsband och armbandsur) innan du arbetar på
utrustning som är kopplad till kraftledningar. Metallobjekt hettas upp när de kopplas ihop
med ström och jord och kan förorsaka allvarliga brännskador; metallobjekt kan också
sammansvetsas med kontakterna.
Class 1 Laser Product Warning
Warning Class 1 laser product.
Waarschuwing
Varoitus
Luokan 1 lasertuote.
Attention
Produit laser de classe 1.
Warnung
Laserprodukt der Klasse 1.
Avvertenza
Advarsel
About This Guide
Klasse-1 laser produkt.
Prodotto laser di Classe 1.
Laserprodukt av klasse 1.
xxxvii
Safety Warnings
Produto laser de classe 1.
Aviso
¡Advertencia!
Varning!
Producto láser Clase I.
Laserprodukt av klass 1.
Invisible Laser Radiation Warning
Warning Because invisible laser radiation may be emitted from the aperture of the port
when no cable is connected, avoid exposure to laser radiation and do not stare into open
apertures.
Waarschuwing
Varoitus
Omdat er onzichtbare laserstraling uit de opening van de poort geëmitteerd kan
worden wanneer er geen kabel aangesloten is, dient men om blootstelling aan
laserstraling te vermijden niet in de open openingen te kijken.
Kun porttiin ei ole kytketty kaapelia, portin aukosta voi vuotaa näkymätöntä lasersäteilyä.
Älä katso avoimiin aukkoihin, jotta et altistu säteilylle.
Attention
Etant donné qu'un rayonnement laser invisible peut être émis par l'ouverture du port quand
aucun câble n'est connecté, ne pas regarder dans les ouvertures béantes afin d'éviter tout
risque d'exposition au rayonnement laser.
Warnung
Aus der Öffnung des Ports kann unsichtbare Laserstrahlung austreten, wenn kein Kabel
angeschlossen ist. Kontakt mit Laserstrahlung vermeiden und nicht in offene Öffnungen
blicken.
xxxviii
Regulatory Standards Compliance
Poiché quando nessun cavo è collegato alla porta, da quest'ultima potrebbe essere emessa
radiazione laser invisibile, evitare l'esposizione a tale radiazione e non fissare con gli
occhi porte a cui non siano collegati cavi.
Avvertenza
Usynlige laserstråler kan sendes ut fra åpningen på utgangen når ingen kabel er tilkoblet.
Unngå utsettelse for laserstråling og se ikke inn i åpninger som ikke er tildekket.
Advarsel
Evite uma exposição à radiação laser e não olhe através de aberturas expostas, porque poderá
ocorrer emissão de radiação laser invisível a partir da abertura da porta, quando não estiver
qualquer cabo conectado.
Aviso
¡Advertencia!
Varning!
Cuando no esté conectado ningún cable, pueden emitirse radiaciones láser invisibles
por el orificio del puerto. Evitar la exposición a radiaciones láser y no mirar fijamente
los orificios abiertos.
Osynliga laserstrålar kan sändas ut från öppningen i porten när ingen kabel är ansluten.
Undvik exponering för laserstrålning och titta inte in i ej täckta öppningar.
Safety
IEC60950, UL/CSA60950, EN60950
EMC Environmental Conditions for Product to be Installed in
the European Union
This equipment is intended to operate under the following environmental conditions with respect to
EMC:
1. A separate defined location under user's control.
2. Earthing and bonding shall meet the requirements of ETS 300 253 or CCITT K27.
About This Guide
xxxix
3. Where applicable, AC power distribution shall be one of the following types: TN-S and TN-C
[as defined in IEC 364-3]
In addition, if equipment is operated in a domestic environment, interference may occur.
(FCC) Class A Warning
Modifying the equipment without authorization from Data Domain may result in the equipment no
longer complying with FCC requirements for Class A or Class B digital devices. In that event, your
right to use the equipment may be limited by FCC regulations, and you may be required to correct
any interference to radio or television communications at your own expense.
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. These limits are designed to provide reasonable
protection against harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the instruction manual, may cause harmful interference to
radio communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at his own expense.
Canada Class A Warning
This Class 'A' digital apparatus complies with Canadian ICES-003.
Cet appareil numerique de la classe 'A' est conforme á la norme NMB-003 de Canada.
Japan (VCCI) Class A Warning
Translation
This is a Class A product based on the standard of the Voluntary Control Council for Interference
by Information Technology Equipment (VCCI). If this equipment is used in a domestic
environment, radio disturbance may arise. When such trouble occurs, the user may be required to
take corrective actions.
xl
Taiwan (BSMI) Class A Warning
Translation
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.
Hazardous Substance Regulations
Complies with the Restriction of Hazardaous Substances (ROHS) directive 2002/95/EC.
About This Guide
xli
xlii
1
Introduction
Data Domain restorers are disk-based recovery appliances. A restorer makes backup data available
with the performance and reliability of disks at a cost competitive with tape-based storage. Data
integrity is assured with multiple levels of data checking and repair.
A restorer works seamlessly with your existing backup software. To a backup server, the restorer
appears as a file server supporting NFS or CIFS over Gigabit Ethernet, or as a virtual tape library
(VTL) over a Fibre Channel connection. Add a restorer to your site as a disk storage device, as
defined by your backup software, or as a tape library. Multiple backup servers can share one
restorer, and one restorer can handle multiple simultaneous backup and restore operations. For
additional throughput and capacity, you can attach multiple restorers to one or more backup
servers. Figure 1 shows a restorer in a basic backup configuration.
SCSI/
Fibre Channel
Backup
Server
Ethernet from
primary storage
Gigabit Ethernet or
Fibre Channel
NFS/CIFS/VTL
Tape
System
Management
Data Verification
Restorer File System
Global Compression
RAID
Restorer
Figure 1: A restorer as a file server
1
Restorer Models
Referring to Figure 1 on page 1, data flows to a restorer through an Ethernet or Fibre Channel
connection. Immediately, data verification processes begin that follow the data for as long as it is
on the restorer. In the file system, DD OS Global Compression™ algorithms prepare the data for
storage. Data is then sent to the disk RAID subsystem. The algorithms constantly adjust the use of
storage as the restorer receives new data from backup servers. Restore operations flow back from
storage, through decompression algorithms and verification consistency checks, and then through
the Ethernet connection to the backup servers.
Restorer Models
From a high-level viewpoint, the differences between Data Domain restorers are the number of
disks and the amount of data storage capacity. The gateway systems have no internal disks, instead
storing data on outside disk arrays through a fiber channel connection. An expansion shelf
increases storage space for and is managed by a restorer.
Table 1: Restorer capacities
Restorers
Disks
CPU
Raw storage
(Base 10
calculation)
Data storage
space (Base 2
calculation)
Data storage
space (Base 10
calculation)
DD560*
15 by 500 GB
2 by 3.6 GHz
7.5 TB
4.7 TiB
5.15 TB
DD460*
15 by 400 GB
2 by 3.2 GHz
6.0 TB
3.9 TiB
4.3 TB
DD430
8 by 400 GB
1 by 3.2 GHz
3.2 TB
1.9 TiB
2.1 TB
DD410
8 by 160 GB
1 by 3.0 GHz
1.3 TB
0.7 TiB
0.8 TB
DD560g*
N/A
2 by 3.6 GHz
17.3 TB
(external)
14.9 TiB
16.37TB
DD460g*
N/A
2 by 3.2 GHz
N/A
4.2 TiB
4.6 TB
16 by 500 GB
N/A
8 TB
5.08 TIB
5.58 TB
Gateways
Expansion
Shelf
ES20
* Marked platforms are available as controllers in the DDX array.
2
Applications that Send Data to a Restorer
Note All restorer commands that display the use of disk space or the amount of data on disks
compute and display amounts using base 2 calculations. For example, a command that
displays 1 GB of disk space used is reporting: 230 bytes = 1,073,741,824 bytes.
Applications that Send Data to a Restorer
The Data Domain operating system (DD OS) is designed specifically for storing relatively large
streams of sequential data from backup software and is optimized for high throughput, continuous
data verification, and high compression. A restorer makes optimum use of its disk space and
compression algorithms when it backs up file systems of at least 10 MB.
Restorer performance when storing data from applications that are not specifically backup software
is best when:
•
Data is sent to the restorer as sequential writes (no overwrites).
•
Small files are prepackaged with tar (on UNIX-based systems) into units of at least 10 MB in
size.
•
No compression or encryption is used before sending the data to the restorer.
Data Integrity
The DD OS Data Invulnerability Architecture™ protects against data loss from hardware and
software failures.
•
When writing to disk, the DD OS creates and stores self-describing metadata for all data
received. After writing the data to disk, the DD OS then creates metadata from the data on the
disk and compares it to the original metadata.
•
An append-only write policy guards against overwriting valid data.
•
After a backup completes, a validation process looks at what was written to disk to see that all
file segments are logically correct within the file system and that the data is the same on the
disk as it was before being written to disk.
•
In the background, the Online Verify operation continuously checks that data on the disks is
still correct and that nothing has changed since the earlier validation process.
•
Storage in a restorer is set up in a double parity RAID 6 configuration (two parity drives) with
a hot spare in 15-disk systems. Eight-disk systems have no hot spare. Each parity stripe has
block checksums to ensure that data is correct. The checksums are constantly used during the
online verify operation and when data is read from the restorer. With double parity, the system
can fix simultaneous errors on up to two disks.
Chapter 1: Introduction
3
Data Compression
•
To keep data synchronized during a hardware or power failure, the restorer uses NVRAM
(non-volatile RAM) to track outstanding I/O operations. An NVRAM card with fully-charged
batteries (the typical state) can retain data for a minimum of 48 hours.
•
When reading data back for a restore operation, the DD OS uses multiple layers of consistency
checks to verify that restored data is correct.
Data Compression
The DD OS compression algorithms:
•
store only unique data. Through Global Compression, a restorer pools redundant data from
each backup image. Any duplicated data or repeated patterns from multiple backups are stored
only once. The storage of unique data is invisible to backup software, which sees the entire
virtual file system.
•
are independent of data format. Data can be structured, such as databases, or unstructured, such
as text files. Data can be from file systems or raw volumes. All forms are compressed.
Typical compression ratios are 20:1 on average over many weeks assuming weekly full and daily
incremental backups. A backup that includes many duplicate or similar files (files copied several
times with minor changes) benefits the most from compression.
Depending on backup volume, size, retention period, and rate of change, the amount of
compression can vary. The best compression happens with backup volume sizes of at least 10 MB.
See “Display File System Space Utilization” on page 127 for details on displaying the amount of
user data stored and the amount of space available.
Global Compression functions within a single restorer. To take full advantage of multiple restorers,
a site that has more than one restorer should consistently backup the same client system or set of
data to the same restorer. For example, if a full backup of all sales data goes to restorerA, the
incremental backups and future full backups for sales data should also go to restorerA.
Restore Operations
With disk backup through the restorer, incremental backups are always reliable and access time for
files is measured in milliseconds. Furthermore, with a restorer, you can perform full backups more
frequently without the penalty of storing redundant data. With tape backups, a restore operation
may rely on multiple tapes holding incremental backups. Unfortunately, the more incremental
backups a site has on multiple tapes, the more time-consuming and risky the restore process. One
bad tape can kill the restore.
From a restorer, file restores go quickly and create little contention with backup or other restore
operations. Unlike tape drives, multiple processes can access a restorer simultaneously. A restorer
allows your site to offer safe, user-driven, single-file restore operations.
4
Data Domain Replicator
Data Domain Replicator
The Data Domain Replicator product sets up and manages the replication of backup data between
two restorers. After replication is started, the source restorer automatically sends any new backup
data to the destination restorer.
A Replicator pair deals with either a complete data set or a directory from a source restorer that is
sent to a destination restorer. An individual restorer can be a part of multiple directory pairs and can
serve as a source for one or more pairs and a destination for one or more pairs.
Restorer Hardware Interfaces
You can configure and administer a restorer using a directly-connected serial console, an Ethernet
connection from another system, or a monitor and keyboard. All hardware interfaces are on the
back panel of the restorer. See Figure 5 on page 13 and Figure 7 on page 15 for interface locations.
Licensing
The licensed features on a restorer are:
•
Data Domain Replicator, which sets up and manages the replication of data between two
restorers.
•
Data Domain Virtual Tape Library (VTL), which allows backup software to see a restorer as a
tape library.
The license command allows you to add new licenses, delete current licenses, or display current
licenses. See “The license Command” on page 94 for command details. Contact your Data
Domain representative to purchase licensed features.
User Interfaces
A restorer has a complete command set available to users in a command line interface. Commands
allow initial system configuration, changes to individual system settings, and give displays of
system states and the state of system operations. The command line interface is available through a
serial console or keyboard and monitor attached directly to the restorer, or through Ethernet
connections.
A web-based graphical user interface, the Data Domain Enterprise Manager, is available through
Ethernet connections. Using a Data Domain Enterprise Manager, you can do the initial system
configuration, make some configuration updates after initial configuration, and display system
states and the state of system operations.
5
Related Documentation
Related Documentation
•
See the Data Domain Quick Start folder for a simplified list of installation tasks.
•
See the Data Domain Command Reference for restorer command summaries.
•
See the Release Notes for a specific Data Domain software release for late changes and fixes.
Initial System Settings
A restorer as delivered and installed needs very little configuration. When you first log in through
the command line interface, the restorer automatically starts the config setup command. From
the Data Domain Enterprise Manager, you can open the Configuration Wizard for initial system
configuration. After configuration, the following parameters are set in the restorer:
6
•
If using DNS, one to three DNS servers are identified for IP address resolution.
•
DHCP is enabled or not enabled for each Ethernet interface, as you choose during installation.
•
Each active interface has an IP address.
•
The restorer hostname is set (for use by the network).
•
The IP addresses are set for the backup servers, SMTP server, and administrative hosts.
•
An SMTP (mail) server is identified.
•
For NFS clients, the restorer is set up to export the /backup and /ddvar directories using
NFSv3 over TCP. For CIFS clients, the restorer has shares set up for /backup and /ddvar.
The directories under /ddvar are:
-
core — The default destination for core files created by the system.
-
log — The destination for all system log files. See “Log File Management” on page 241
for details.
-
releases — The default destination for operating system upgrades that are downloaded
from the Data Domain Support web site.
-
snmp — The location of the SNMP MIB (management information base).
-
traces — The destination for execution traces used in debugging performance issues.
•
One or more backup servers are identified as restorer NFS or CIFS clients.
•
A host is identified for restorer administration. Administrative users have access to the
partition /ddvar. The partition is small and data in the partition is not compressed.
•
The time zone you select is set.
•
The initial user for the system is sysadmin with the password that you give during setup. The
user command allows you to later add administrative and non-administrative users later.
Command Line Interface
•
The SSH service is enabled and the HTTP, FTP, TELNET, and SNMP services are disabled.
Use the adminaccess command to enable and disable services.
•
The user lists for TELNET and FTP are empty, SNMP is not configured, and the protocols are
disabled, meaning that no users can connect through TELNET, FTP, or SNMP.
•
A system report runs automatically every day at 3 a.m. The report goes to a Data Domain email
address and an address that you give during set up. You can add addresses to the email list
using the autosupport command.
•
An email list for system alerts that are automatically generated has a Data Domain email
address and a local address that you enter during set up. You can add addresses to the email list
using the alerts command
•
The clean operation is scheduled for Tuesday at 6:00 a.m. To review or change the schedule,
use the filesys clean commands.
•
The background verification operation that continuously checks backup images is enabled.
A restorer is administered through a command line interface. Use the SSH or TELNET (if enabled)
utilities to access the command prompt. The majority of this manual gives details for using the
commands to accomplish specific administration tasks. Each command also has a help page that
gives the complete command syntax. Help pages are available through the restorer help command
and in an appendix at the back of this manual.
•
To list restorer commands, enter a question mark (?) at the prompt.
•
To list the options for a particular command, enter the command with no options at the prompt.
•
To find a keyword used in a command option when you do not remember which command to
use, enter a question mark (?) or the help command followed by the keyword. For example,
the question mark followed by the keyword password displays all restorer command options
that include password. If the keyword matches a command, such as net, then the command
explanation appears.
•
To display a detailed explanation of a particular command, enter the help command followed
by a command name.
•
Use the up and down arrow keys to move through a displayed command. Use the q key to exit.
Enter a slash character (/) and a pattern to search for and highlight lines of particular interest.
•
The Tab key completes a command entry when that entry is unique. Tab completion works for
the first three levels of command components. For example, entering syst(tab) sh(tab)
st(tab) displays the command system show stats.
•
Any restorer command that accepts a list, such as a list of IP addresses, accepts entries as
comma-separated, space-separated, or both.
7
•
Commands that display the use of disk space or the amount of data on disks compute amounts
using the following definitions:
1 KB = 210 bytes = 1024 bytes
1 MB = 220 bytes = 1,048,576 bytes
1 GB = 230 bytes = 1,073,741,824 bytes
1 TB = 240 bytes = 1,099,511,627,776 bytes
Note The one exception to displays in powers of 2 is the system show performance
command, in which the Read, Write, and Replicate values are calculated in powers of 10
(1KB = 1000).
The commands are:
adminaccess Manages the HTTP, FTP, TELNET, and SSH services. See “Access Control for
Administration” on page 103.
alerts Creates alerts for system problems. Alerts are emailed to Data Domain and to a
user-configurable list. See “Alerts” on page 114.
alias Creates aliases for restorer commands See “The alias Command” on page 162.
autosupport Generates a system status and health report. Reports are emailed to Data Domain
and to a user-configurable list. See “Autosupport Reports” on page 118.
cifs Manages Common Internet File System backups and restores on a restorer and displays
CIFS status and statistics for a restorer. See “CIFS Management” on page 187.
config Shows, resets, copies, and saves restorer configuration settings. See “Configuration
Management” on page 89.
disk Displays disk statistics, status, usage, reliability indicators, and RAID layout and usage.
See “Disk Management” on page 139.
filesys Displays filesystem status and statistics. See “Statistics and Basic Operations” on
page 125 for details. Manages the clean feature that reclaims physical disk space held by
deleted data. See “Clean Operations” on page 130 for details.
help Displays a list of all restorer commands and detailed explanations for each command.
license Displays current licensed features and allows adding or deleting licenses.
log Displays and administers the restorer log file. See “Log File Management” on page 241.
ndmp Manages direct backup and restore operations between a Network Appliance™ filer and
a restorer using the Network Data Management Protocol Version 2. See “Backup/Restore
Using NDMP” on page 231.
net Displays network status and set up information. See “Network Management” on page 167.
nfs Displays NFS status and statistics. See “NFS Management” on page 181 for details.
8
Graphical User Interface
ntp Manages restorer access to one or more time servers. The default setting is multicast. See
“Time Servers and the NTP Command” on page 164.
replication Manages the Replicator for replication of backup data from one restorer to another.
See “Replicator” on page 199.
route Manages restorer network routing rules. See “The route Command” on page 177.
snmp Enables or disables SNMP access to a restorer, adds community strings, and gives
contact and location information. See “SNMP Management and Monitoring” on page 235.
support Send log files to Data Domain Technical Support. See “Collect and Send Log Files”
on page 122.
system Displays restorer status, faults, and statistics, enables, disables, halts, and reboots a
restorer. See “The system Command” on page 149. Also sets and displays the system clock
and calendar and allows the restorer to synchronize the clock with an external time server. See
“Set the Date and Time” on page 152.
user Administers user accounts for the restorer. See “User Administration” on page 109.
Through the browser-based Data Domain Enterprise Manager graphical user interface, you can do
the initial system configuration, make a limited set of configuration changes, and display system
status, statistics, and settings. The supported browsers for web-based access are Netscape 7 and
above, Microsoft® Internet Explorer 6.0 and above, FireFox 0.9.1 and above, Mozilla 1.6 and
above, and Safari 1.2.4.
The console first asks for a login and then displays the Restorer Summary page (see Figure 2 on
page 10). Some of the individual displays on various pages have a Help link to the right of the
display title. Click on the link to bring up detailed online help about the display.
To bring up the interface:
1. Open a web browser.
2. Enter a path such as http://rstr01/ for restorer rstr01 on a local network.
3. Enter a login name and password.
9
rstr01.yourcompany.com
Figure 2: Summary screen
On the Restorer Summary screen:
10
•
The bar at the top displays the restorer host name.
•
The grey bar immediately below the host name displays the file system status, the number of
current alerts, and the system uptime.
•
The Current Status and Space Graph tabs toggle the display. Figure 2 shows Current Status.
See “Display the Space Graph” on page 20 for the Space Graph display and explanation.
•
The left panel lists the pages available in the interface. Click on a link to display a page.
•
Below the list, find the current login, a logout button, and a link to Data Domain Support.
•
The main panel shows current alerts and the space used by restorer file system components.
•
A line at the bottom of the page displays the restorer software release and the current date.
The page links in the left panel display the output from restorer commands that are detailed
throughout this manual.
Configuration Wizard gives the same system configuration choices as the config setup
command. See “Login and Configuration” on page 36.
System Stats Opens a new window and displays continuously updated graphs showing system
usage of various resources. See “Display Detailed System Statistics” on page 155.
Group Manager Opens a window that allows basic system monitoring for multiple restorers. See
“Monitor Multiple Restorers” on page 23.
Autosupport shows current alerts, the email lists for alerts and autosupport messages, and a history
of alerts. See “Display Current Alerts” on page 115, “Display the Email List” on page 116,
“Display the Autosupport Email List” on page 121, and “Display the Alerts History” on page 116.
Admin Access lists every access service available on a restorer, whether or not the service is
enabled, and lists every hostname allowed access through each service that uses a list. See “Display
Hosts and Status” on page 107.
CIFS displays CIFS configuration choices and the CIFS client list.
Disks shows statistics for disk reliability and performance and lists disk hardware information. See
“Display Disk Reliability Details” on page 147, “Display Disk Performance Details” on page 146,
and “Display Disk Type and Capacity Information” on page 142.
File System displays the amount of space used by restorer file system components. See “Display
File System Space Utilization” on page 127.
Licenses shows the current licenses active on the restorer. See “Display Licenses” on page 95.
Log Files displays information about each system log file.
Network displays settings for the restorer Ethernet ports. See “Display Interface Settings” on
page 173 and “Display Ethernet Hardware Information” on page 174.
NFS lists client machines that can access the restorer. See “Display Allowed Clients” on page 184.
SNMP displays the status of the local SNMP client and SNMP configuration information.
Support allows you to create a support bundle of log files and lists existing bundles. See “Collect
and Send Log Files” on page 122.
System shows system hardware information and status.
Replication lists configured replication pairs and replication statistics.
Users lists the users currently logged in and all users that are allowed access to the system. See
“Display Current Users” on page 111 and “Display All Users” on page 112.
11
Hardware System-Level Interfaces
The front and back panels of a restorer have a number of LEDs and hardware interfaces.
Front Panel
The upper right corner of the front panel has all of the front-panel interfaces (except for the disk
activity LEDs). See Figure 3.
System power on/off
Reboot the system
Power supply alarm cutoff
Power on/off indicator
Network activity indicator
Rack screw
Extreme temperature indicator
Power supply failure indicator
Figure 3: Front panel operations functions and indicators
12
•
At the top is the system power on/off button. Press and hold the button for several seconds to
power off the system.
•
Below the power button is a very small button labelled Reset. The button immediately reboots
the system. Do not press the button unless instructed to by Data Domain Technical Support.
•
The next button down is labelled Mute and turns off the power supply alarm that buzzes when
one or more power supplies is not working.
•
The top LED is the power on/off indicator that glows green when power is on.
•
The second LED is the network activity indicator that flashes green with network activity
through the Ethernet port, eth0. See “Hardware Interface” on page 14 to identify the port.
•
The third LED indicates extreme high temperature for either CPU inside the chassis.
•
The last LED glows red when any one or more of the power supplies fails.
•
The rack screw is to keep the chassis from sliding forward and back when in a rack with slide
rails. Use a 10-32 nut to secure the rack screw to the rack. The rack screws cannot support
the weight of the chassis in a rack. Use the rack screws only in combination with the slide
rails that are included in the shipping crate with the restorer.
Each disk has two LEDs at the bottom of the disk carrier. See Figure 4. The right LED on each disk
flashes green whenever the system accesses the disk. The left LED glows red when the disk has
failed. Both LEDs are dark on the disk that is available as a spare.
Disk LEDs
Figure 4: Disk activity LEDs
Back Panel
The back panel has three major functional areas: the power supply units, a hardware interface
panel, and a system card interface area. See Figure 5.
Power
supply
units
Hardware interface panel
System card interfaces
Figure 5: Back panel
13
Power Supply LEDs
A restorer has three power supply units. Each power unit has an LED (see Figure 6) that glows
green when the unit is functional. The LED glows amber if the unit has failed, but still has power.
The LED also glows amber when the restorer is turned off but the unit is still plugged in to a live
power source. The LED is dark if the unit has no power. Also, when a unit fails, the power supply
failure LED on the front panel of the system glows red (see Figure 3 on page 12).
LED locations
Figure 6: Power unit LEDs
Hardware Interface
The hardware interface panel is where you connect to a restorer with a serial console, a monitor and
keyboard, or through an Ethernet connection. See Figure 7 on page 15. The Ethernet interfaces eth0
and eth1 are for data transfer to the restorer or for administrative access over a network. Both
Ethernet interfaces are 1000 Base-T Gigabit copper ports that can accept 10/100 Base-T or Gigabit
connections.
Each Ethernet connection has two LEDs, one on each side. When the LED on the left side is dark,
the port has no live connection. When the LED on the left is green, the connection speed is 10/100
Base-T. When the LED on the left is amber, the connection speed is 1000 Base-T Gigabit. The LED
on the right flashes amber when the connection is active with network traffic.
14
Keyboard
port
Console port
Monitor
(VGA) port
eth0
eth1
Figure 7: Hardware interface panel
System Card Interface
The system card interface area has the NVRAM card LEDs and gives access to an optional
Ethernet card, with ports eth2 and eth3, or an optional single-channel Fibre Channel HBA card for
the VTL feature. The Ethernet ports are either 1000 Base-T copper or Gigabit fiber depending on
the option chosen. Figure 8 shows copper ports. Ethernet fiber ports are installed in the same
vertical slot, but are somewhat higher in the slot than the copper ports shown. A system can have
either an Ethernet card or a VTL Fibre Channel HBA card, but not both as both cards use the same
slot.
Remove indicator
Fault - bad NVRAM card battery
indicator
Power on/off indicator
Test LED switch
eth2 (or the VTL Fibre Channel port)
eth3
Figure 8: System card interfaces
15
The fiber Ethernet ports each have an LED that glows steadily when the connection is live. The
copper Ethernet ports each have an upper LED that flashes green when the connection is active and
a lower LED that glows green when the connection is 10/100 Base-T or amber when the connection
is Gigabit.
The NVRAM interfaces from the bottom to the top are:
•
A Test LED switch that lights the three NVRAM LEDs to test their functionality.
•
A power on/off indicator that glows green when powered on.
•
A fault indicator for the two batteries on the NVRAM card. If either battery is below
specifications or not working, the indicator glows amber.
•
The LED labeled Remove is not used at this time.
Caution Do not remove the NVRAM card from the system. Only a trained service person should
replace the card. The NVRAM card contains two lithium batteries which can cause fire
or explosion if handled incorrectly. Do not remove either battery from the NVRAM
card. Do not place the NVRAM card on a metal surface. Do not dispose of the NVRAM
card in fire as the batteries explode.
16
Disk Space and System Monitoring
2
This chapter:
•
Gives general guidelines for predicting how much disk space your site may use over time.
•
Explains how to deal with restorer components that run out of disk space.
•
Describes Data Domain Space Usage graphs.
•
Gives background information on how to reclaim restorer disk space.
Note Data Domain offers guidance on setting up backup software and backup servers for use with
a restorer. Because such information tends to change often, it is available on the Data
Domain Support web site (http://support.datadomain.com/). See the Technical Notes section
on the web site.
Space Management
A restorer is designed as a very reliable online cache for backups. As new backups are added to the
system, old backups are removed. Such removals are normally done under the control of backup
software (on the backup server) based on the configured retention period. The process with a
restorer is very similar to tape policies where older backups are retired and the tapes are reused for
new backups.
When backup software removes an old backup from a restorer, the space on the restorer becomes
available only after the restorer internal clean function reclaims disk space. A good way to manage
space on a restorer is to retain as many online backups as possible with some empty space (about
20% of total space available) to allow for data growth over time.
Data growth on a restorer is primarily affected by:
•
The size and compressibility of the primary storage that you are backing up.
•
The retention period that you specify with the backup software.
If you backup volumes that in total size are near the space available for data storage on a restorer
(for example 4 TB on a model DD460, which has 3.9 TB space available, see the table on page 2)
or the retention time for volumes that do not compress well is greater than four months, backups
may fill space on a restorer more quickly than expected.
17
Estimate Use of Disk Space
Also, bypassing backup software by copying files directly to a restorer (using xcopy, for example)
leads to poor compression and is not supported by Data Domain. A file system cleaning operation
can restore normal compression ratios for such data.
Estimate Use of Disk Space
The restorer’s use of compression when storing data means that you can look at the use of disk
space in two ways: physical and virtual. (See “Data Compression” on page 4 for details about
compression.) Physical space is the actual disk space used on the restorer. Virtual space is the
amount of space needed if all data and multiple backup images were uncompressed.
•
Through the restorer, the filesys show space command (or the alias of df) shows both
physical and virtual space. See “Manage File System Use of Disk Space” on page 19.
•
Directly from clients that mount a restorer, use your usual tools for displaying a file system’s
physical use of space.
The restorer generates log messages as the file system approaches its maximum size. The following
information about data compression gives guidelines for disk use over time.
The amount of disk space used over time by a restorer depends on:
•
The size of the initial full backup.
•
The number of additional backups (incremental and full) over time.
•
The rate of growth for data in the backups.
For data sets with average rates of change and growth, data compression generally matches the
following guidelines:
18
•
For the first full backup to a restorer, the compression factor is about 3:1. Disk space used on
the restorer is about one-third the size of the data before the backup.
•
Each incremental backup to the initial full backup has a compression factor of about 6:1.
•
The next full backup has a compression factor of about 60:1. All data that was new or changed
in the incremental backups is already in storage.
•
Over time, with a schedule of weekly full and daily incremental backups, the aggregate
compression factor for all the data is about 20:1. The compression factor is lower for
incremental-only data or for backups without much duplicate data. Compression is higher with
only full backups.
Manage File System Use of Disk Space
Manage File System Use of Disk Space
The restorer command filesys show space (or the alias command df) displays the amount
of disk space used for data storage and for restorer components.
# filesys show space
Resource
Size GB
Used GB
Avail GB
Use%
----------------------------------------/ddvar
29.5
16.7
12.8
57%
Pre-compression
6146.3
Data
2870.6
881.5
1989.0
31%
If 100% cleaned*
Meta-data
19.7
0.1
19.6
0%
Index
120.0
8.7
111.2
7%
----------------------------------------Estimated compression factor: 6.9x = 6146.3/(881.5+0.1+8.7
Estimate based on 2004/11/22 cleaning
•
The /ddvar line gives a rough idea of the amount of space used by and available to the log and
core files. Remove old logs and core files to free space in this area.
•
The Pre-compression line shows the amount of virtual data stored on the restorer. Virtual data
is the amount of data sent to the restorer from backup servers.
•
The Data line shows the actual physical space used by and available for data storage. Warning
messages go to the system log and an email alert is generated when the Use% figure reaches
90%, 95%, and 100%. At 100%, the restorer accepts no more data from backup servers. You
must run a filesys clean operation to reclaim disk space.
If Use% is always high, use the filesys clean show-schedule command to see how
often the operation runs automatically, then use filesys clean schedule to run the
operation more often. Also consider reducing the data retention period or splitting off a portion
of the backup data to another restorer.
The Avail GB and Use% columns change when the Index line Use% column reaches 80% and
the index is expanded.
•
The If 100% cleaned line is an estimate of actual physical space used, and physical space
available for data storage if you run the filesys clean start operation multiple times
to clean 100% of the file system. The estimate is based on the most recent clean operation.
On a destination, no estimate appears.
•
The Meta Data line tracks space used for the internal file descriptions that the restorer creates
for all stored files. The space for Meta Data allows for the storage of about 5 million files on a
restorer. Warning messages go to the system log and an email alert is generated when the
Use% figure reaches 90%, 95%, and 100%. At 100%, the restorer accepts no more data from
backup servers. From the backup server, you must expire or purge backup images (backup
server files, not user files) to create free space for meta data.
Chapter 2: Disk Space and System Monitoring
19
Display the Space Graph
•
The Index line tracks space used for internal restorer operations. When the Use% column
reaches approximately 80%, the space allocated for the index automatically increases by a set
amount and the Use% column adjusts to the new size. At the same time, the Data line Avail GB
and Use% columns also change to reflect the space taken for the index.
•
The Estimated compression factor line gives a rough idea of data compression efficiency. The
estimate is based on the most recent clean operation and changes if the compressibility of
data sent to the restorer changes. Note that the compression algorithm includes the metadata
and index space as part of the total storage space. On a destination, no estimate appears.
The value may be different on a replication destination than on a replication source. Multiple
replications of a file do not send all of the file data to the destination every time, but do
increase the number of bytes of pre-compression data used in the compression calculation.
•
The Estimate based on line displays the date for the most recent clean operation. The date is in
the format YYYY/MM/DD.
The Data Domain Enterprise Manager displays a graph of data from the spacelog file.
•
Data Collection The total amount of disk storage in use on the restorer. Look at the left vertical
axis of the graph.
•
Data Collection Limit The total amount of disk storage available for data on the restorer. Look
at the left vertical axis of the graph.
•
Pre-compression The total amount of data sent to the restorer by backup servers.
Pre-compressed data on a restorer is what a backup server sees as the total un-compressed data
held by a restorer-as-storage-unit. Look at the left vertical axis of the graph.
•
Compression factor The amount of compression the restorer has done with all of the data
received. Look at the right vertical axis of the graph for the compression ratio.
Two activity boxes below the graph allow you to change the data displayed on the graph. The
vertical axis and horizontal axis change as you change the data set.
20
•
The activity box on the left below the graph allows you to choose which data shows on the
graph. Click the check boxes for Data Collection, Data Collection Limit, Pre-compression, or
Compression factor to remove or add data.
•
The activity box on the right below the graph allows you to change the number of days of data
shown on the graph.
Display
When first logging in to the Data Domain Enterprise Manager or when you click on the Home link
in the left panel of the Data Domain Enterprise Manager, the Space Graph tab is on the far right of
the right panel. Click the words Space Graph to display the graph. Figure 9 shows an example of
the display with all four types of data included. In the example, the Data Collection and Data
Collection Limit values show as constants because of the relatively large scale needed for
Pre-compression on the left axis.
Pre-compression
Compression Factor
Data Collection and
Data Collection Limit
DD5601234567890
Figure 9: Space graph
21
Removing one or more types of data can give useful information as the axis scales change. For
example, Figure 10 shows the graph for the same restorer and the same data collection as in
Figure 9 on page 21. The difference is that the Pre-compression check box in the left-side activity
box at the bottom of the display was clicked to remove pre-compression data from the graph.
Data Collection Limit
Data Collection
Compression factor
DD5601234567890
Figure 10: Graph without pre-compression data
22
Monitor Multiple Restorers
The left axis scale in Figure 10 on page 22 is such that the Data Collection and Data Collection
Limit give useful information. Also, comparing each of the three lines with the other two lines gives
information. Data Collection (the amount of disk space used) at one point goes nearly to the Data
Collection Limit, which means that the system was running out of disk space. A file system
cleaning operation on about May 30 (see the scale along the bottom of the graph) cleared enough
disk space for operations to continue.
The Data Collection line rises with new data written to the restorer and falls steeply with every file
system clean operation. Note that the Compression factor line falls with new data and rises with
clean operations.
The graph also displays a vertical grey bar for each time the system runs a file system cleaning
process. The minimum width of the bar on the X axis is six hours. If the cleaning process runs for
more than six hours, the width increases to show the total time used by the process.
The Group Manager feature of the Data Domain Enterprise Manager displays information for
multiple restorers. In the left panel of the Data Domain Enterprise Manager, click on Group
Manager. See Figure 11.
Link
Figure 11: Group Manager link
The Group Manager display gives information about multiple restorers. Figure 12 on page 24 is an
example. See Figure 13 on page 25 for adding systems to the display.
23
rstr01.company.com
rstr02.company.com
rstr03.company.com
rstr04.company.com
rstr05.company.com
Figure 12: Multi-monitor window
24
•
Manage Hosts Click to bring up a screen that allows adding restorers to or deleting restorers
from the display. See Figure 13 on page 25 for details.
•
The Total Pre-compression and Total Data amounts are the combined amounts of data for all
displayed systems (five restorers in the example).
•
Update Now Click to update the main table of information and the status for each restorer
displayed.
•
Status Displays OK in green or the number of alerts in red for each restorer.
•
Restorer Displays the name of each restorer monitored. Click on a name to see more
information about a restorer. See Figure 14 on page 26 for an example.
•
Pre-compression GB The amount of data sent to the restorer by backup software.
•
Data GB The amount of disk space used on the restorer.
•
% Used A bar graph of the amount of disk space used for compressed data.
•
Compression The amount of compression achieved for all data on the restorer.
Figure 13 shows the Manage Hosts window for adding and deleting systems from the main display.
Enter either hostnames or IP addresses for the restorers that you want to monitor.
•
Click the Save button to save changes.
•
Click the Cancel button to return to the main display with no changes.
Figure 13: Add to or delete from the display
25
Reclaim Data Storage Disk Space
Figure 14 shows the display after clicking on a name in the Restorer column. Connect to GUI
brings up the login screen for the monitored system if the GUI is enabled on the monitored system.
Whichever protocol the current GUI (the one hosting the display) is using, HTTP or HTTPS, is also
used to connect to the GUI on the monitored system.
rstr01.company.com
rstr02.company.com
rstr03.company.com
rstr04.company.com
rstr05.company.com
Figure 14: System details
Reclaim Data Storage Disk Space
When your backup application (such as NetBackup or NetWorker) expires data, the data is marked
by the restorer for deletion. However, the data is not deleted immediately. The restorer clean
operation deletes expired data from the restorer disks.
•
During the clean operation, the restorer file system is available for backup (write) and restore
(read) operations.
•
Although cleaning uses a noticeable amount of system resources, cleaning is self-throttling and
gives up system resources in the presence of user traffic.
•
Data Domain recommends running a clean operation after the first full backup to a restorer.
The initial local compression on a full backup is generally a factor of 1.5 to 2.5. An immediate
clean operation gives additional compression by another factor of 1.15 to 1.2 and reclaims a
corresponding amount of disk space.
A default schedule runs the clean operation every Tuesday at 6 a.m. (tue 0600). The operation can
clean a maximum of about 34% of the total space available for data on a DD460 or DD560, about
65% of the total space on a DD430, and 100% on a DD410. You can change the schedule or you
can run the operation manually with the filesys clean commands. If you want to increase file
system availability and if the restorer is not short on disk space, consider changing the schedule to
clean less often. See “Clean Operations” on page 130 for details on changing the schedule.
26
Maximum Number of Files
You can have the clean operation run for a set number of hours or until a set number of gigabytes
are available on the restorer. The default (and maximum allowed in one operation) is 34% of total
space available for data (on a DD460 or DD560), which takes from three to four hours on a system
that is at least 34% full and that is not otherwise busy. When the operation finishes, it sends a
message to the system log giving the percentage of storage space that was cleaned.
A full DD560 or DD460 restorer would need three clean operations to clean 100% of the file
system (about 34% for each operation). Depending on the type of data stored, such as when using
markers for specific backup software (filesys option set marker-type ... ), the file
system may never report 100% cleaned. The total space cleaned may always be a few percentage
points less than 100.
The disk space set aside for the meta data that describes each file on a restorer allows for the
storage of about 5 million files. However, the number of files in a single directory under /backup,
such as /backup/dir2, can affect performance of commands such as ls -l from a system
that mounts the restorer file system.
Data Domain recommends a maximum of 5,000 files under one directory if you have performance
considerations. A maximum of 2,000 files under one directory gives uniform performance across
all directories. Displays from commands such as ls -l become noticeably slower when
directories have between 2,000 files and 5,000 files. The number of files that can be under a single
directory is limited only by the space set aside for meta data (5 million files).
27
28
Installation
3
Installation and site configuration for a restorer consist of the tasks listed below. After
configuration, the restorer is fully functional and ready for backups. For site hardware and backup
software requirements, see “Restorer Hardware Interfaces” on page 5.
Note Installation and configuration for a Gateway restorer (using outside storage systems) is
explained in the chapter “Gateway Restorers.”
•
Check the site and backup software requirements.
•
To use DHCP with Ethernet interfaces, configure the DHCP server with the appropriate
restorer information. To configure a restorer using an Ethernet interface, DHCP information is
required for at least one interface. The alternative is to use a serial console or a keyboard and
monitor.
•
Set up the restorer hardware.
•
Set up a serial console or a monitor and keyboard if you are not using an Ethernet interface for
configuration.
•
Login to the restorer as sysadmin using a serial console, monitor and keyboard, SSH and an
Ethernet interface, or the Data Domain Enterprise Manager through a web browser.
•
Answer questions asked by the configuration process. The process starts automatically when
sysadmin first logs in through the command line interface. To start configuration in the Data
Domain Enterprise Manager, click on Configuration Wizard. The process requests all of the
basic information needed to use the restorer.
•
Optionally, after completing the initial configuration, follow the steps in “Additional
Configuration” on page 46 to add to the configuration.
•
Configure the backup software and servers. See the Data Domain Support web site
(https://support.datadomain.com), Technical Notes section for details about configuring a
restorer with specific backup servers and software.
To upgrade Data Domain OS software to a new release, see “Upgrade the Restorer Software” on
page 150.
29
Restorer Site Requirements
Note The Data Domain OS is pre-installed on the restorer. You do not need to install software. In
emergency situations, such as when a restorer fails to boot up by itself, call Data Domain
Technical Support for step-by-step instructions.
Restorer Site Requirements
To install a restorer at your site, you need:
•
30
A 3U space in a standard 19 inch rack. A restorer in a rack has the following requirements:
-
Air conditioning that can cope with a maximum thermal rating of 1570 BTUs an hour for
DD460 and DD560 systems and 1370 BTUs an hour for DD430 and DD410 systems.
-
Ambient air temperature range of from 5° C to 35° C at the front panel of the chassis.
-
Adequate temperature control with a gradient (change) not to exceed 20° C in an hour.
-
Ventilation and air flow through the front and back panels of the restorer is critical. The
restorer requires six inches (16 cm.) of unobstructed clearance for both the front panel and
the back panel. Do not block or cover the openings in the front and back panels.
-
In a closed or multi-unit rack, ensure that the unit has adequate airflow and that the
ambient air temperature requirements are met.
•
For configuration and administrative tasks, either a serial console, an Ethernet connection, or a
keyboard and monitor.
•
An Ethernet connection to a restorer interface for data transfer to and from backup servers.
-
You can configure different network interfaces on a restorer to different subnets. However,
multiple interfaces must not be linked to the same LAN or VLAN in the network.
-
If the restorer uses Fiber Gigabit Ethernet interfaces, the cables and connecting ports on
the other end must be SX compatible.
•
Three grounded power outlets. The restorer is shipped with grounding type (three wire) power
cords. To reduce the risk of electric shock, always use the cords with grounded power outlets.
•
Three single phase AC power outlets with an earth ground conductor (safety ground). A safe
electrical earth connection must be provided to each power cord.
-
Frequency: 50 to 60 Hz.
-
Normal operating current 115VAC/230VAC
DD410/DD430: 3.0/1.5A
DD460/DD560: 3.5/1.8A
-
Maximum current at power up 115VAC/230VAC
DD410/DD430: 4.5/2.3A
DD460/DD560: 5.0/2.5A
Expansion Shelf Site Requirements
•
Ensure that the circuit used for the restorer is not overloaded. Look for the power ratings on the
nameplates of all equipment on the circuit. The total load on the circuit should not exceed the
maximum circuit rating. Note that the restorer requires about 650W during the first six seconds
after power-on and about 300W during normal operation.
•
If a restorer is installed in a rack with limited space above the restorer, use cables that are long
enough to allow sliding the restorer out on the slide rails for servicing.
Expansion Shelf Site Requirements
A fully-populated expansion shelf weighs 77 lbs/35 kg. See the slide rail and installation
documentation in the external shelf packaging for installing the shelf in a rack.
Each installed expansion shelf needs:
•
A 3U space in a standard 19 inch rack.
•
A shelf requires:
•
-
One inch (2.54 cm.) of unobstructed clearance for the front panel/bezel.
-
Five inches (12.7 cm.) of unobstructed clearance for the back panel.
-
Back pressure by rack doors and obstacles not to exceed 5 pascals (0.5 mm. water gauge
pressure or 0.9997 psi).
Two single phase AC power outlets with an earth ground conductor (safety ground). A safe
electrical earth connection must be provided to each power cord.
-
Voltage: 100-120 VAC or 200-240 VAC.
-
Frequency: 50 to 60 Hz.
-
Power consumption: 420 watts.
-
Input current: 3.5 / 2.0 @ 120 / 230 VAC
•
Ambient temperature range: 41F/5C to 104F/40C
•
Air conditioning that can cope with a maximum thermal rating of 2800 BTUs an hour.
•
Humidity: 20% to 80% non-condensing
•
Height: 130mm / 5.12 inches, width: 482.6mm / 19.0 inches, depth: 551mm / 21.7 inches.
•
Acoustic noise: Maximum 58 dB LpA average measured at the bystander positions.
Chapter 3: Installation
31
Restorer Installation
Caution The two side brackets on the restorer’s front faceplate (see Figure 18 on page 34) cannot
support the weight of the restorer in a rack. Support the system with the slide rails that
are delivered with the restorer.
•
Mount the restorer in a 3U space in a 19-inch, four-post rack using the slide rails provided by
Data Domain. Any other means of mounting the restorer must be rated for at least 100 pounds
(45 kilograms).
-
Open the slide rails package that ships with the restorer.
-
Using the slide rail instruction and rack template documents that are included with other
system documentation, mount the inner rails onto the restorer.
Note The slide rails can accommodate a front-to-back rail depth of 28 inches (710 mm) to 33.67
inches (855 mm).
•
-
Mount the outer rails onto the rack.
-
Slide the restorer into the rails that are in the rack.
-
Remove the thin, clear plastic wrap that covers the top panel of the system and the clear
plastic tape that covers the top and bottom surfaces of the trim around the front of the
chassis.
-
Slide the restorer all the way into the rack.
Determine whether your configuration and ongoing administration access for the restorer is to
be through an Ethernet connection, a serial console, or a monitor and keyboard.
-
For an Ethernet connection, attach an Ethernet cable to one of the Ethernet interfaces,
eth0, eth1, eth2, or eth3 on the back panel. See Figure 19 on page 36 for Ethernet interface
locations.
Eth0 and eth1 each have two leds, one on each side of the port. When the LED on the left
side is dark, the port has no active connection. When the LED on the left is green, the
connection speed is 10/100 Base-T. When the LED on the left is amber, the connection
speed is 1000 Base-T gigabit. The LED on the right flashes amber when the connection is
active with network traffic.
32
-
For a serial console, attach an RS232 null modem cable to the DB9 port (labeled “Console
Port”) on the back panel. See Figure 15. Use the console communication settings of: 9600
baud, 8 data bits, no parity, 1 stop bit.
-
For a monitor and keyboard, attach the monitor to the port labeled VGA and the keyboard
to the port nearest the keyboard icon. See Figure 15 for locations.
Keyboard port
Console port Monitor (VGA) port
Figure 15: Access points
•
Attach at least one Ethernet cable to an Ethernet interface on the back panel for backup and
restore communications between the restorer and your backup servers. See for Ethernet
interface locations.
•
Attach the power cords to the three power supplies. See Figure 16.
eth0
Power cord slots
eth1
eth2 eth3
Figure 16: Power cord plug-in slots
•
For each power cord, slide a power cord retainer bracket over the cord.
33
•
Pinch the two “wings” on the bracket and slide the bracket down over the power cord plug and
flush with the back of the power unit so that the wings secure the plug by clicking into the
power unit handle brackets. See Figure 17.
Power unit handle brackets
Retainer
bracket
wings
Figure 17: Power cord retainer bracket
•
Plug in the three power cords to a power source.
•
Start the Restorer. Push the power button (the top button) on the right-side control panel on the
front of the system. See Figure 18 for the location.
Power
button
Power-on LED
Power unit
failure
indicator
Side bracket
Figure 18: Restorer front panel
•
34
After the restorer starts, the power-on LED glows green. See Figure 18 for the location.
Backup Software Requirements
Backup Software Requirements
A restorer accepts data from many combinations of backup software and servers. See the Data
Domain Support web site (https://support.datadomain.com), Compatibility Matrix section for the
latest updates on supported backup software and server combinations.
Note See the Data Domain Support web site, Technical Notes section for configuration details for
using specific backup software and server types with a restorer.
CIFS Backup Server Timeout
Internal activities on a Data Domain restorer can take longer than a default CIFS timeout, leading to
an error message from the media server. The message is similar to: Network name no longer
existed. On all CIFS backup servers using a restorer, change the SESSTIMEOUT value from the
default of 45 (seconds) to decimal 3600 (five minutes).
•
If you want detailed background information, see the following web page:
http://support.microsoft.com/default.aspx?scid=http://support.m
icrosoft.com:80/support/kb/articles/Q102/0/67.asp&NoWebContent=
1
•
Open REGEDT32 and navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\
LANMANWORKSTATION\PARAMTERS
•
If the SESSTIMEOUT key does not exist, click in the right panel and select New and DWORD
value. Create a new key, SESSTIMEOUT. Note that the registry is case sensitive. Use all caps
for the new key name.
•
Double click on the new (or existing) key and set to the decimal value of 3600.
DHCP Server
If one or more of the restorer Ethernet interfaces are to use DHCP, the DHCP server needs MAC
addresses for the interfaces and a hostname for the restorer. Data Domain recommends configuring
infinite lease IP addresses for the restorer interfaces. All of the interfaces do not need to use DHCP.
If you set an interface to use DHCP and DHCP is not yet available to the interface, the restorer
attempts to set up the interface without DHCP until DHCP is available. Use the net show
settings command to display which interfaces are configured for DHCP.
35
Login and Configuration
Each Ethernet interface on the back of the restorer is labeled with its MAC address. See Figure 19.
Eth0 and eth1 are copper 1000 Base-T gigabit interfaces. The optional eth2 and eth3 are for
additional Fiber or copper Ethernet interfaces. The MAC addresses for eth0 and eth1 are vertical
labels just to the right of each port. The MAC addresses for eth2 and eth3 are vertical labels just
above eth2. The label on the left is for eth2 and the label on the right is for eth3.
eth0 eth1
eth2
eth3
Figure 19: Ethernet interfaces
After the hardware is installed and running, configure the system with the config setup
command through the command line interface or use the Data Domain Enterprise Manager. The
config setup command starts automatically the first time sysadmin logs in through the
command line interface. The command reappears at each login until configuration is complete.
To bring up the Data Domain Enterprise Manager and start the configuration:
1. Open a web browser.
2. Enter a path to the restorer. For example: http://rstr01/ for a restorer named rstr01 on a
local network.
3. Enter a login name and password. The default password for the sysadmin login is the serial
number that appears on the rear panel of the restorer. Note that all characters in a serial number
are numeric except for the third and fourth characters. Other than the third and fourth
characters, all “0” characters are zeros. See Figure 22 on page 38 for the location. The Restorer
Summary screen appears.
4. Click on the Configuration Wizard link as shown in Figure 20 on page 37.
36
Configuration link
Figure 20: Configuration Wizard link
Note Most of the installation procedure in this chapter uses the command line interface as an
example. However, the Configuration Wizard of the Data Domain Enterprise Manager has
the same configuration groups and sets the same configuration parameters. With the Data
Domain Enterprise Manager, click on links and fill in boxes that correspond to the command
line examples that follow. To return to the list of configuration sections from within one of
the sections, click on the Wizard List link in the top left corner of the Configuration Wizard
screen.
If you earlier set up DHCP for one or more restorer Ethernet interfaces, a number of the config
setup prompts display the values given to the restorer from a DHCP server. DHCP servers
normally supply values for a number of networking parameters. Press Return during the installation
to accept DHCP values. If you do not use DHCP for an interface, determine what you will use for
the following values before starting the configuration:
•
Interface IP addresses.
•
Interface netmasks.
•
Routing gateway.
•
DNS server list (if using DNS).
•
A site domain name, such as yourcompany.com.
•
A fully-qualified hostname for the restorer, such as rstr01.yourcompany.com.
You can configure different network interfaces on a restorer to different subnets. However, multiple
interfaces must not be linked to the same LAN or VLAN in the network.
When configuring restorer software:
•
At any prompt, enter a question mark (?) for detailed information about the prompt.
•
Press Return to accept a displayed value.
•
Enter either hostnames or IP addresses where ever a prompt mentions a host. Hostnames must
be fully qualified, such as srvr22.yourcompany.com.
37
•
For any entry that accepts a list, the entries in the list can be comma-separated, spaceseparated, or both.
•
When configuration is complete, the system is ready to accept backup data. For NFS clients,
the restorer is set up to export the /backup and /ddvar directories using NFSv3 over TCP.
For CIFS clients, the restorer has shares set up for /backup and /ddvar.
The configuration utility has five sections: Licenses, Network, NFS, CIFS, and System. You can
configure or skip any section. The command line interface automatically moves from one section to
the next. With the Data Domain Enterprise Manager, click on the sections as shown in Figure 21.
Configuration
sections (wizards)
Figure 21: Configuration sections
1. The first login to the restorer can be from a serial console, keyboard and monitor, through an
Ethernet connection, or through a web browser. Log in as user sysadmin. The default password
is the serial number from the rear panel of the restorer. See Figure 22 for the location.
Serial number
Figure 22: Serial number location
38
-
From a serial console or keyboard and monitor, log in to the restorer at the login prompt.
-
From a remote machine over an Ethernet connection, give the following command (with
the hostname you chose for the restorer) and then give the default password.
# ssh -l sysadmin host-name
sysadmin@host-name’s password:
-
From a web browser, enter a path to the restorer. For example: http://rstr01/ for a
restorer named rstr01 on a local network.
2. When using the command line interface, the first prompt after login gives the opportunity to
change the sysadmin password. The prompt appears only once, at the first login to a new
system. You can change the sysadmin password immediately at the prompt or later with the
user change password command.
To improve security, Data Domain recommends that you change the
'sysadmin' password before continuing with the system
configuration.
Change the 'sysadmin' password at this time? (yes|no) [yes]:
3. When using the command line interface, the restorer command config setup starts next.
4. The first configuration section is for licensing. Licenses that you ordered with the restorer are
already installed. At the first prompt, enter yes to configure or view licenses.
-
Enter the license characters, including dashes, for each license category.
-
Make no entry and press Enter for categories that you have not licensed.
LICENSES Configuration
Configure LICENSES at this time (yes|no) [no]: yes
VTL License Code
Enter your VTL license code []:
REPLICATION License Code
Enter your REPLICATION license code []:
-
A listing of your choices appears. You can accept the settings (Save), reject the settings
and go to the next section (Cancel), or return to the beginning of the current section and
change settings (Retry). A Retry shows your previous choice for each prompt. Press
Return to accept the displayed value or enter a new value.
Pending License Settings.
NFS License:
ABCD-ABCD-ABCD-ABCD
CIFS License:
ABCD-ABCD-ABCD-ABCD
REPLICATION License: ABCD-ABCD-ABCD-ABCD
VTL License:
ABCD-ABCD-ABCD-ABCD
Do you want to save these settings (Save|Cancel|Retry):
39
5. The second section is for network configuration. At the first prompt, enter yes to configure
network parameters.
NETWORK Configuration
Configure NETWORK parameters at this time (yes|no) [no]:
Note After configuring the restorer to use DNS, the restorer must be rebooted. Also, if DHCP is
disabled for all interfaces and then later enabled for one or more interfaces, the restorer must
be rebooted.
a. The first prompt is for a restorer machine name. Enter a fully-qualified name that includes
the domain name. For example: rstr01.yourcompany.com. Note: With CIFS using domain
mode authentication, the first component of the name is also used as the netBIOS name,
which cannot be over 15 characters. If you use domain mode and the hostname is over 15
characters, use the cifs set nb-hostname command for a shorter netBIOS name.
Hostname
Enter the hostname for this system (fully-qualified
domain name)[]:
b. Supply a domain name, such as yourcompany.com, for use by restorer utilities, or accept
the display of the domain name used in the hostname.
Domainname
Enter your DNS domainname []:
c. Configure each Ethernet interface that has an active Ethernet connection. If you earlier set
up DHCP for an interface, the IP address and netmask prompts do not appear. You can
accept or not accept DHCP for each interface.
-
If you enter yes for DHCP and DHCP is not yet available to the interface, the restorer
attempts to set up the interface with DHCP until DHCP is available. Use the net
show settings command to display which interfaces are configured for DHCP.
-
If you are on an Ethernet interface and you choose to not use DHCP for the interface,
the connection is lost when you complete the configuration.
-
At the last prompt, entering Cancel deletes all new values and goes to the next
section.
-
Each interface is a Gigabit Ethernet connection. The same set of prompts appears for
each interface.
Ethernet port eth0:
Enable Ethernet port (yes|no) [ ]:
Use DHCP on Ethernet port eth0 (yes|no) [ ]:
Enter the IP address for eth0 [ ]:
Enter the netmask for eth0 [ ]:
40
-
When not using DHCP on any Ethernet port, you must specify an IP address for a
default routing gateway.
Default Gateway
Enter the default gateway IP address[]:
-
When not using DHCP on any Ethernet port, you can enter up to three DNS servers
for a restorer to use for resolving hostnames into IP addresses. Use a commaseparated or space-separated list. Enter a space for no DNS servers. With no DNS
servers, you can use the net hosts commands to inform the restorer of IP
addresses for relevant hostnames.
DNS Servers
Enter the DNS Server list (zero, one, two or three IP
addresses)[]:
d. A listing of your choices appears. You can accept the settings (Save), reject the settings
Pending Network Settings.
------------------------------------Hostname:
srvr26.yourcompany.com
Domainname:
yourcompany.com
Default Gateway
DNS Server List
DNS Server List
------------------Cable Port Enabled DHCP IP Address
Netmask
----- ---- ------- ---- ---------------------------eth0 yes
yes
(dhcp-supplied)
(dhcp-supplied)
eth1 yes
yes
(dhcp-supplied)
(dhcp-supplied)
eth2 no
n/a
n/a
n/a
***
eth3 yes
yes
(dhcp-supplied)
(dhcp-supplied)
----- ---- ------- ---- ---------------------------*** No connection on indicated Ethernet port
Note An information box also appears in the recap if any interface is set up to use DHCP, but does
not have a live Ethernet connection. After troubleshooting and completing the Ethernet
connection, wait for up to two minutes for the restorer to update the interface. The Cable
column of the net show hardware command displays whether or not the Ethernet
connection is live for each interface.
6. The third section is for CIFS (Common Internet File System) configuration. At the first
prompt, enter yes to configure CIFS parameters. The default authentication mode is Active
Directory.
41
Note When configuring a destination restorer as part of a Replicator pair, configure the
authentication mode, WINS server (if needed) and other entries as with the originator in the
pair. The exceptions are that a destination does not need a backup user and will probably
have a different backup server list (all machines that can access data that is on the
destination).
CIFS Configuration
Configure CIFS at this time (yes|no) [no]: yes
a. Select a user-authentication method for the CIFS user accounts that connect to the
/backup and /ddvar shares on the restorer.
CIFS Authentication
Which authentication method will this system use
(Workgroup|Domain|Active-Directory) [Active Directory]:
The Workgroup method has the following prompts. Enter a workgroup, the name of a
CIFS workgroup account that will send backups to the restorer, a password for the
workgroup account, a WINS server name, and backup server names.
Workgroup Name
Enter the workgroup name for this system
[ ]:
Do you want to add a backup user yes|no) [no]:
Backup User
Enter backup user name:
Backup User Password
Enter backup user password:
Enter the WINS server for the restorer to use:
WINS Server
Enter the IP address for the WINS server for this system
[]:
Enter one or more backup servers as restorer clients.
Backup Servers
Enter the Backup Server list (CIFS clients of /backup)
[]:
42
The Domain method brings the following prompts. Enter a domain name, the name of a
CIFS domain account that will send backups to the restorer and optionally, one or more
domain controller IP addresses, a WINS server name, and backup server names. Press
Enter with no entry to break out of the prompts for domain controllers.
Domain Name
Enter the name of the Windows domain for this system
[ ]:
Do you want to add a backup user? (yes|no) [no]:
Backup user
Domain Controller
Enter the IP address of domain controller 1 for this
system
[ ]:
WINS Server
[]:
Enter one or more backup servers as restorer clients.
Backup Servers
[]:
The Active-Directory method brings the following prompts. Enter a fully-qualified realm
name, the name of a CIFS backup account, a WINS server name, and backup server
names. Data Domain recommends not specifying a domain controller. When not
specifying a domain controller, be sure to specify a WINS server. The restorer must meet
all active-directory requirements, such as a clock time that is no more than five minutes
different than the domain controller. Press Enter with no entry to break out of the prompts
for domain controllers.
Active-Directory Realm
Enter the name of the Active-Directory Realm for this
system [ ]:
Do you want to add a backup user? (yes|no) [no]:
Backup user
Domain Controllers
Enter list of domain controllers for this system [ ]:
43
WINS Server
[]:
Enter one or more backup servers as restorer clients. An asterisk (*) is allowed as a wild
card only when used alone to mean “all.”
Backup Server List
[]:
b. A listing of your choices appears. You can accept the settings (Save), reject the settings
The following example is with an authentication mode of Active-Directory.
Pending CIFS Settings
---------------------
-----------------
Auth Method
Active-Directory
Domain
domain1
Realm
domain1.local
Backup User
dsmith
Domain Controllers
WINS Server
192.168.1.10
Backup Server List
*
-------------------------------------Do you want to save these settings (Save|Cancel|Retry):
7. The fourth section is for NFS configuration. At the first prompt, enter yes to configure NFS
parameters.
NFS Configuration
Configure NFS at this time (yes|no) [no]: yes
a. Add backup servers that will access the restorer through NFS. You can enter a list that is
comma-separated, space-separated, or both. An asterisk (*) opens the list to all clients.
The default NFS options are: rw, no_root_squash, no_all_squash, and secure. You can
later use adminaccess add and nfs add /backup to add backup servers.
Backup Servers
Enter the Backup Server list (NFS clients of /backup)[]:
44
b. A listing of your choices appears. You can accept the settings (Save), reject the settings
Pending NFS Settings.
Backup Server List:
8. The fifth section is for system parameters. At the first prompt, enter yes to configure system
parameters.
SYSTEM Configuration
Configure SYSTEM Parameters at this time (yes|no) [no]:
a. Add a client host from which you will administer the restorer. The default NFS options
are: rw, no_root_squash, no_all_squash, and secure. You can later use the commands
adminaccess add and nfs add /ddvar to add other administrative hosts.
Admin host
Enter the administrative host []:
b. You can add an email address so that someone at your site receives email for system alerts
and autosupport reports. For example, [email protected]. By default, the restorer
email lists include an address for the Data Domain support group. You can later use the
restorer commands alerts and autosupport to add more addresses.
Admin email
Enter an email address for alerts and support emails[]:
c. You can enter a location description for ease of identifying the physical machine. For
example, Bldg4-rack10. The alerts and autosupport reports display the location.
System Location
Enter a physical location, to better identify this
system[]:
d. Enter the name of a local SMTP (mail) server for restorer emails. If the server is an
Exchange server, be sure that SMTP is enabled.
SMTP Server
Enter the hostname of a mail server to relay email
alerts[]:
e. The default time zone for each restorer is the factory time zone. For a complete list of time
zones, see “Time Zones” on page 265.
Timezone Name
Enter your timezone name:[US/Pacific]:
45
Additional Configuration
f.
To allow the restorer to use one or more Network Time Service (NTP) servers, you can
enter IP addresses or server names. The default is to enable NTP and to use multicast.
Configure NTP
Enable Network Time Service? (yes|no)|? [yes]:
Use multicast for NTP? (yes|no|?) [no]:
Enter the NTP Server list [ ]:
g. A listing of your choices appears. Accept the settings (Save), reject the settings and go to
the next section (Cancel), or return to the beginning of the current section and change
settings (Retry). A Retry shows your previous choice for each prompt. Press Return to
accept the displayed value or enter a new value.
Pending System Settings
------------------------------Admin host
[email protected]
System Location
Server Room 52327
SMTP Server
mail.yourcompany.com
Timezone name
US/Pacific
NTP Servers
123.456.789.33
---------------------------------Do you want to save these settings (Save|Cancel|Retry):
Note For Tivoli Storage Manager on an AIX backup server to access a restorer, you must re-add
the backup server to the restorer after completing the original configuration setup. On the
restorer, run the following command with the server-name of the AIX backup server:
# nfs add /backup server-name insecure
h. Configure the backup servers. For the most up-to-date information about setting up
backup servers for use with a restorer, go to the Data Domain Support web site
(http://support.datadomain.com/). See the Technical Notes section.
Additional Configuration
The following are common changes to the restorer configuration that users make after the
installation. Changes to the initial configuration settings are all made through the command line
interface. Each change describes the general task and the command used to accomplish the task.
•
Add email addresses to the alerts list and the autosupport list. See “Add to the Email List” on
page 118 for details.
alerts add addr1[,addr2,...]
46
Administering a Restorer
•
Give access to additional backup servers. See “NFS Management” on page 181 for details.
nfs add /backup srvr1[,srvr2,...]
•
From a remote machine, add an authorized SSH public key to the restorer. See “Add an
Authorized SSH Public Key” on page 105 for details.
ssh-keygen -d
ssh -l sysadmin rstr01 “adminaccess add ssh-keys” \
< ~/.ssh/id_dsa.pub
•
Add remote hosts that can use FTP or TELNET on the restorer. See “Add a Host” on page 103
for details.
adminaccess add {ftp | telnet}{all | host1[,host2,...]}
•
Enable HTTP, HTTPS, FTP or TELNET. The SSH, HTTP, and HTTPS services are enabled by
default. See “Enable a Protocol” on page 104 for details.
adminaccess enable {http | https | ftp | telnet | ssh | all}
•
Add a standard user. See “User Administration” on page 109 for details.
user add username
•
Change a user password. See “User Administration” on page 109 for details.
user change password username
To administer a restorer, use either the command line interface or the Data Domain Enterprise
Manager graphical user interface.
The command line interface gives complete access to a restorer for the initial system configuration,
for making changes to individual system settings, and to display of system states and the state of
system operations. The remaining chapters in this book detail the use of all restorer commands and
operations. The headings in each chapter are a task-oriented list of operations performed by the
featured commands. To find the command for any task that you want to perform, do either of the
following:
•
Look in the table of contents at the beginning of this guide for the heading that describes the
task.
•
List the restorer commands and operations. To see a list of commands, log in to the restorer
using SSH (or TELNET if that is enabled) and enter a question mark (?) at the prompt. To see
a list of operations available for a particular command, enter the command name. To display a
47
detailed help page for a command, use the help command with the name of the target
command. Use the up and down arrow keys to move through a displayed command. Use the q
key to exit. Enter a slash character (/) and a pattern to search for and highlight lines of
particular interest.
Data Domain Enterprise Manager
The web-based graphical user interface, the Data Domain Enterprise Manager, is available through
Ethernet connections to a restorer. With the Data Domain Enterprise Manager, you can do the
initial system configuration, make some configuration updates after initial configuration, and
display system states and the state of system operations. From the left panel of the Data Domain
Enterprise Manager, select the Configuration Wizard to change configuration values or select an
area such as File System to display system information. See Figure 23.
rstr01.company.com
Selections
on the
left panel
Figure 23: Data Domain Enterprise Manager selections
For a complete explanation of the default Data Domain Enterprise Manager screen, see “Graphical
User Interface” on page 9.
48
ES20 Expansion Shelf
4
A Data Domain ES20 expansion shelf is a 3U chassis that has 16 disks for increasing the storage
capacity of a Data Domain restorer. The Data Domain OS Data Invulnerability Architecture™ and
all other restorer data integrity features that protect against data loss from hardware and software
failures also apply to the ES20 expansion shelf. All restorer data compression technology also
applies as does the Data Domain Replicator feature that sets up and manages replication of backup
data between two restorers. The Replicator sees data on an expansion shelf as part of the volume
that resides on the managing restorer.
•
In related restorer commands, the restorer and each expansion shelf is called an enclosure.
•
A restorer sees all data storage (restorer and attached shelves) as part of a single volume.
•
A new restorer installed along with one or two expansion shelves finds the shelves when
booted up. Follow the instructions in this chapter to add shelves to the volume and create
RAID groups.
•
After adding a shelf to a restorer with an existing, active file system, a percentage of new data
is sent to the new shelf. An algorithm takes into account the amount of space available in the
restorer file system, in the file system on a previously installed shelf (if one exists), and the
probable impact of location on read/write times. Over time, data is spread evenly over all
enclosures.
Warning After adding a shelf to a volume, the volume must always include the shelf to maintain
file system integrity. Do not add a shelf and then later remove it, unless you are prepared
to lose all data in the volume. If a shelf is disconnected, the volume’s file system is
immediately disabled. Re-connect the shelf or transfer the shelf disks to another shelf
chassis and connect the new chassis to re-enable the file system. If the data on a shelf is
not available to the volume, the volume cannot be recovered.
All administrative access to an ES20 shelf is done through the controlling restorer command line
interface and graphical user interface. Initial configuration tasks, changes to the configuration, and
displaying disk usage in a shelf are all done with standard restorer commands as explained in this
chapter.
49
RAID groups
RAID groups
The single volume that includes all disks in a restorer and one or two shelves also includes multiple
RAID 6 groups. Each shelf is one RAID group and the restorer is one RAID group for a maximum
of three RAID groups.
•
The restorer has a RAID group of 12 data disks, two parity disks, and one spare.
•
Each shelf has a RAID group with 12 data disks, two parity disks, and two spares.
•
A RAID group is created on a new shelf with the disk add enclosure command.
Disk Failures
A restorer and two expansion shelves (three enclosures) have a total of five spare disks. If the
number of spare disks needed by an enclosure exceeds the number of spares in that enclosure, the
RAID group for that enclosure takes an available spare disk from another enclosure.
Warning If no spare disks are available from any enclosure, a shelf can have up to two more failed
disks and still maintain the RAID group of 12 data disks. However, if one more disk in a
shelf fails (leaving only 11 data disks), the data volume (made up of all the enclosures)
fails and cannot be recovered. Always replace any failed disk in any enclosure as
soon as possible.
Add a First Shelf
Physically install the first shelf by following the installation instructions received with the shelf.
After installing the shelf and starting the restorer:
1. On the restorer, use the enclosure show summary command to verify that the shelf is
recognized.
# enclosure show summary
2. Enter the disk rescan command to make the disks in the new shelf visible to other disk
commands. If existing RAID groups need spare disks and have none of their own, the disk
rescan command immediately makes disks in the new shelf available as spares for the other
RAID groups. See “Volume Expansion” on page 58 for details. Data Domain recommends
replacing all failed disks in a restorer and in an existing shelf before adding a new shelf.
# disk rescan
50
DD500 Series Restorer User Guide
Add a First Shelf
3. The new disks are not yet part of a RAID group or part of the restorer volume. Use the disk
add enclosure command to add the disks to the volume:
# disk add enclosure 2
4. Use the disk show raid-info command to display the RAID groups. The shelf should
show two disks with a State of spare. If two disks are labeled as unused and none are labeled
spare, use the disk unfail command for each unused disk. For example, if the two disks
are 2.15 and 2.16, use the following two commands:
# disk unfail 2.15
# disk unfail 2.16
5. Shutdown the restorer.
6. Shut down the shelf.
7. Power-up the shelf and wait for the SAS state LEDs to go off. See Figure 24 for the SAS state
LED locations on the back of the shelf.
HOST
SAS state LEDs (8)
EXP’N
Figure 24: SAS state LEDs on the disk controller module
8. Power-up the restorer.
9. Check the file system status:
# filesys status
The filesystem is enabled and running
Chapter 4: ES20 Expansion Shelf
51
Add a Second Shelf
Add a Second Shelf
Physically install the second shelf by following the installation instructions received with the shelf.
After installing the shelf and starting the restorer:
1. On the restorer, use the enclosure show summary command to verify that the shelf is
recognized.
2. On the restorer, enter the disk rescan command to make the disks in the new shelf visible
to other disk commands. If existing RAID groups need spare disks and have none of their own,
the disk rescan command immediately makes disks in the new shelf available as spares.
See “Volume Expansion” on page 58 for details. Data Domain recommends replacing all failed
disks in a restorer and in an existing shelf before adding a new shelf.
3. The new disks are not yet part of a RAID group or part of the restorer volume. Use the disk
add enclosure command to add the disks to the volume.
4. Use the disk show raid-info command to display the RAID groups. The shelf should
show two disks with a State of spare. If two disks are labeled as unused and none are labeled
spare, use the disk unfail command for each unused disk. For example, if the two disks
are 2.15 and 2.16, use the following two commands:
# disk unfail 2.15
# disk unfail 2.16
5. Shutdown the restorer.
6. Shut down the shelf.
7. Power-up the shelf and wait for the SAS state LEDs to go off. See Figure 24 on page 51 for the
SAS state LED locations on the back of the shelf.
8. Power-up the restorer.
9. Check the file system status:
# filesys status
52
Disk Commands
Disk Commands
With DD OS 4.1.0.0 and later releases, all disk commands that take a disk-id variable must
use the format enclosure-id.disk-id to identify a single disk. Both parts of the ID are a
decimal number. A restorer with no shelves must also use the same format for disks on the restorer.
A restorer always has the enclosure-id of 1 (one). For example, to check that disk 12 in a restorer
(with or without shelves) is recognized by the DD OS and hardware, use the following command:
# disk beacon 1.12
In DD OS releases previous to 4.1.0.0, output from disk commands listed individual disks with
the word disk and a number. For example:
# disk
Disk
-----disk1
disk2
show hardware
Manufacturer/Model
------------------HDS725050KLA360
HDS725050KLA360
Firmware Serial No.
-------- -------------K2A0A51A
KRFS06RAG9VYGC
K2AOA51A
KRFS06RAG9TYYC
Capacity
--------465.76 GB
465.76 GB
Output now shows the enclosure (Enc) number, a dot, and the disk (Slot) number:
# disk show hardware
Disk
Manufacturer/Model
(Enc.Slot)
--------- ------------------1.1
HDS725050KLA360
1.2
HDS725050KLA360
Firmware Serial No.
Capacity
-------- -------------- -------K2AOA51A KRFS06RAG9VYGC 465.76 GB
K2AOA51A KRFS06RAG9TYYC 465.76 GB
Command output for a restorer that has one or more expansion shelves includes entries for all
enclosures, disk slots, and RAID Groups.
Note All restorer commands that display the use of disk space or the amount of data on disks
compute and display amounts using base 2 calculations. For example, a command that
displays 1 GB of disk space as used is reporting: 230 bytes = 1,073,741,824 bytes.
1 KB = 210 bytes = 1024 bytes
1 MB = 220 bytes = 1,048,576 bytes
1 GB = 230 bytes = 1,073,741,824 bytes
1 TB = 240 bytes = 1,099,511,627,776 bytes
Look for New Disks, LUNs, and Expansion Shelves
To check for new disks or LUNs with gateway systems or when adding an expansion shelf, use the
disk rescan operation. Administrative users only.
disk rescan
53
Disk Commands
Add an Expansion Shelf
To add an expansion shelft, use the disk add enclosure command. The enclosure-id is
always 2 for the first added shelf and 3 for the second. The restorer always has the enclosure-id of 1
(one).
disk add enclosure enclosure-id
For example, to add a first enclosure:
Display Disk Status
The disk status operation displays the number of disks in use and failed, the number of spare
disks available, and whether a RAID disk group reconstruction is underway. Note that the RAID
portion of the display could show one or more disks as “failed” while the Operational portion of
the display could show all drives as “operating normally.” A disk can be physically functional and
available, but not currently in use by RAID, possibly because of operator intervention.
disk status
The display for a restorer with two expansion shelves is similar to the following. Note that the disks
in a new expansion shelf recognized with the disk rescan command show a status of
“unknown.” Use the disk add enclosure command to change the status to “in use.”
# disk status
Configuration:
RAID:
RAID:
RAID:
RAID:
RAID:
RAID:
RAID:
RAID:
RAID:
Operational:
Performance:
54
47 drives present.
47 drives are "in use"
0 drives are undergoing "reconstruction"
0 drives are undergoing "resynch"
5 drives are "spare"
0 drives are "absent"
0 drives have "failed"
0 drives are "foreign"
0 drives are "unknown"
0 drives are "not in use"
47 drives operating normally..
Cumulative 114.954 MB/s, 7 % busy
Shelf (enclosure) Commands
Use the restorer enclosure command to identify and display information about expansion
shelves.
List Enclosures
To list known enclosures, model numbers, serial numbers, and capacity (number of disks in the
enclosure), use the enclosure show summary command. The serial number displayed for an
expansion shelf is actually the enclosure’s world-wide name (WWN). See Figure 25 for the WWN
label’s physical location on the back panel of the shelf.
enclosure show summary
For example:
# enclosure show summary
Enclosure
Model No.
--------- --------------------1
Data Domain DD560
2
Data Domain ES20
3
Data Domain ES20
--------- --------------------3 enclosures present.
Serial No.
----------------00:00:18:76:72:c8
50050CC100123456
50050CC100123457
-----------------
Capacity
-------15 Slots
16 Slots
16 Slots
--------
World-wide
name label
Figure 25: World-wide name location
55
Identify an Enclosure
To check that the Data Domain OS and hardware recognize an enclosure, use the enclosure
beacon operation. The operation causes the green (activity) LED on each disk in an enclosure to
flash green. Use the (Control) c key sequence to turn off the operation. Administrative users only.
enclosure beacon enclosure-id
Display Fan Status
To display the current status of fans in all enclosures or in a specific enclosure, use the
enclosure show fans command:
enclosure show fans [enclosure-id]
To show the status of all fans for a restorer with one expansion shelf:
# enclosure
Enclosure
--------1
2
---------
show fans
Description
------------------Crossbar fan #1
Crossbar fan #2
Crossbar fan #3
Crossbar fan #4
Rear fan #1
Rear fan #2
Power module #1 fan
Power module #2 fan
-------------------
Level
------High
High
Medium
Medium
Medium
Medium
Low
Low
-------
Status
-----OK
OK
OK
OK
OK
OK
OK
OK
------
Enclosure starts with the restorer as enclosure 1 (one).
Description for a shelf lists one fan for each power/cooling unit.
Level is the fan speed and depends on the internal temperature and amount of cooling needed.
Status is either OK or Failed.
Display Component Temperatures
To display the internal and CPU temperatures for a restorer and the internal temperature for
expansion shelves, use the enclosure show temperature-sensors command.
enclosure show temperature-sensors [enclosure-id]
56
For example:
# enclosure
Enclosure
--------1
2
---------
show temperature-sensors
Description
C/F
Status
--------------------Chassis
45/113
OK
CPU 0
51/124
OK
CPU 1
50/122
OK
Internal
45/113
OK
----------------------
Display Port Connections
To list the order of shelves connected to a restorer, use the enclosure show ports command.
enclosure show ports
For example:
# enclosure show ports
Port Connection Connected
Type
Enclosures
---- ---------- ------------1
SAS
2, 3
---- ---------- -------------
Status
-----online
------
Port refers to the SAS HBA expansion port on the restorer.
Connected Enclosures shows each shelf by number that is recognized by the restorer. The order in
which shelf numbers are shown is not important.
Status can be either online or offline. Offline means that the connection between shelves and the
restorer is not functional.
Display All Hardware Status
To display temperatures and the status of all fans and power supplies, use the enclosure show
all command:
enclosure show all [enclosure-id]
Display Power Supply Status
To display the status of power supplies in all enclosures or in a specific enclosure, use the
enclosure show powersupply command:
enclosure show powersupply [enclosure-id]
57
Volume Expansion
For example:
# enclosure
Enclosure
--------1
2
---------
show powersupply
Description
--------------Power Module #1
Power Module #2
Power Module #3
Power Module #1
Power Module #2
---------------
Status
-----OK
OK
OK
OK
OK
------
Volume Expansion
Creating a RAID group on a new shelf automatically expands a restorer’s existing volume. In most
cases, creating a RAID group is simple: run the following command on the restorer with an
enclosure-id of 2 for the first shelf or 3 for the second shelf.
The unusual case is when the restorer or a previously installed shelf or both need spare disks and
have none available. Disks from the new shelf are automatically allocated after a disk rescan
command makes the disks visible to the RAID processes. If three disks are allocated from the new
shelf to existing RAID groups, a RAID group cannot be created on the new shelf and the disk
add enclosure command fails. The procedure below allows a recovery from such a situation.
Note The most efficient strategy is to replace all failed disks in existing enclosures before adding
a new shelf.
To create a RAID group on a new shelf that has lost three or more disks to existing RAID groups:
1. Use the disk show raid-info command to identify which RAID group is using disks in
the new shelf. Also note which disk(s) a RAID group is using
2. In the enclosure for the RAID group that is using one or more disks in the new shelf, replace
the bad disks that created the need for a spare outside of the enclosure.
3. In the new shelf, fail a disk used by the enclosure that now has a replacement spare disk. The
RAID group should immediately start to rebuild using the new spare in its own enclosure.
After the rebuild, fail other disks in the new shelf as needed to move data to other replacement
spares in other enclosures.
4. Unfail the disk or disks in the new shelf that were used by the other RAID group(s).
5. Run disk add enclosure for the new shelf.
58
Gateway Restorers
5
Gateway restorers store data in and restore data from outside mounted disk arrays through Fibre
Channel connections. Currently, the gateway restorers support the following types of connectivity:
•
Fibre Channel direct-attached connectivity to a storage array using a 1 or 2 Gb/sec Fibre
Channel interface. The FC-AL loop mode is required.
•
Fibre Channel SAN-attached connectivity to a storage array using a 1 or 2 Gb/sec Fibre
Channel interface.
See the Gateway Compatibility Matrix on the Data Domain Support web site for the latest updates
of certified storage arrays, storage firmware, and SAN topology.
A gateway system has the same chassis and CPUs as a DD460 or DD560 restorer, but no disks.
Other points to be aware of with a gateway system are:
•
The system supports a single volume with a single data collection. A data collection is all the
files stored in a single restorer.
•
When using a SAN-attached gateway restorer, the SAN must be zoned before the restorer is
booted.
•
The storage array can have single or multiple controllers and each controller can have multiple
ports.
•
A single storage controller port is needed for direct connect to the gateway. Multiple storage
controller ports (with different LUNs) can be used for a SAN attached gateway. Port and
controller failover on the storage array must be disabled.
•
The storage array port used for gateway connectivity cannot be shared with other
SAN-connected hosts that access the array.
•
Multiple gateway systems can access storage on a single storage array.
•
The outside physical disks that provide storage to the gateway should be dedicated to the
gateway an not shared with other hosts.
•
Outside storage is configured into one or more LUNs that are exported to the gateway.
•
All LUNs presented to the gateway are used automatically when the gateway is booted. Use
the restorer commands disk rescan and disk add to see newly added LUNs.
59
60
•
A volume may use any of the disk types supported on the disk array. However, only one disk
type can be used for all LUNs in the volume to assure equal performance for all LUNs.
•
All disks in the LUNs must be like drives in identical RAID configurations.
•
Multiple storage array RAID configurations can be used; however, you should select RAID
configurations that provide the fastest possible sequential data access for the type of disks
used.
•
A gateway restorer supports one volume composed of 1 to 16 LUNs. LUN numbers must start
at 0 (zero) and be contiguous.
•
The total amount of storage in a volume can be no more than 17.3 TB/15.8 TiB for the
DD560g and 4.2 TiB for the DD460g. A smaller volume can be expanded by adding additional
LUNs.
•
LUNs should be provisioned across the maximum number of spindles available. Vendorspecific provisioning best practices should be used and, if available, vendor-specific tools
should be used to create a virtual- or meta-LUN that spans multiple LUNs. If virtual- or
meta-LUNs are used, they must follow the configuration parameters defined in this chapter.
•
For replication between a gateway restorer and other model Data Domain restorers, the total
amount of storage on the originator must not exceed the total amount of storage on the
destination.
•
Replication between gateway restorers must use storage arrays with similar performance
characteristics. The size of destination storage must be equal to or greater than the size of
source storage. Configurations do not need to be identical.
•
Power supplies are the only hardware in a gateway restorer that a customer would replace.
•
A restorer does not support temporary Fibre Channel disconnection while the restorer is active.
Removing the fiber cable that connects the restorer and the storage array can lead to
unrecoverable errors at any time that the restorer has I/O activity. Data Domain recommends
shutting down the restorer before removing the cable.
•
A restorer does not support Fibre Channel multipathing (also known as failover) Be sure that
the storage array is not configured as if multipathing is enabled.
•
The maximum data size for a LUN that a gateway restorer can access is 2 TiB.
•
The minimum data size for a LUN that a gateway restorer can access is 400 GiB. To use the
maximum amount of space on a restorer, create multiple LUNs and adjust the LUN sizes so
that the smallest is at least 400 GiB.
•
The maximum total size of all LUNs accessed by a DD460g restorer is 4.2 TiB. The maximum
for a DD560g is 15.3 TiB. A smaller volume can be expanded by adding LUNs.
Command Changes
•
A Fibre Channel host bus adapter card (QLogic 2 gigabit class) in the restorer communicates
with the outside disk array. See Figure 26 for a schematic of the peripheral cards in a gateway
restorer.
Back panel
Restorer
front panel
Figure 26: Peripheral card slots
Command Changes
The following disk commands are not valid for a gateway restorer using outside storage. All other
commands in the Data Domain command set are available.
disk
disk
disk
disk
disk
beacon
fail
unfail
show failure-history
show reliability-data
The following additional commands are available only with the gateway restorer. See “Procedure:
Adding a LUN” on page 67 for details about using the commands.
disk add disk-id Expand the outside storage seen by the restorer to include a new
LUN.
disk rescan Search outside storage for new or removed LUNs.
Chapter 5: Gateway Restorers
61
Command Changes
The following disk commands report activity and information only at the LUN level, not for
individual disks in a LUN. Each disk entry represents a LUN in output from the following
commands.
•
disk show raid-info The following example shows two LUNs available to the restorer.
After the drives are “in use” line, the remainder of the drives lines are not valid.
system12# disk show raid-info
Disk
State
Additional Status
-------------------------------disk1
in use (dg0)
disk2
in use (dg0)
-------------------------------2 drives are "in use"
0 drives are "hot spare(s)"
0 drives are "missing/absent"
•
disk show performance Displays information similar to the following for each LUN.
system12# disk show performance
Disk
Read
Write
Cumul.
sects/s
sects/s
MBytes/s
-----------------------disk1
46
109
0.075
disk2
0
0
0.000
-----------------------Cumulative
0.075 MB/s, 7 % busy
•
Busy
---14 %
0 %
----
disk show detailed-raid-info Displays information similar to the following for
each LUN:
system12# disk show detailed-raid-info
Disk Group (dg0) - Status: normal
Raid Group (ext3):(raid-0)(61.01 GB) - Status: normal
Raid Group (ext3_1):(raid-100)(68.64 GB) - Status:
normal
Slot
Disk
State
Additional Status
----------------------------------1
disk1
in use (dg0)
-----------------------------------
62
Command Changes
Raid Group (ppart):(raid-0)(3.04 TB) - Status: normal
Raid Group (ppart_1):(raid-100)(3.04 TB) - Status:
normal
Slot
Disk
State
Additional Status
----------------------------------1
disk1
in use (dg0)
2
disk2
in use (dg0)
----------------------------------Spare Disks
None
Unused Disks
None
•
disk show hardware Displays information similar to the following for each LUN.
-
LUN is the LUN number used by the outside storage system.
-
Port WWN is the world-wide number of the port on the outside storage system through
which data is sent to the restorer.
-
Manufacturer/Model includes a label that identifies the manufacturer. The display may
include a model ID or RAID type or other information depending on the vendor string sent
by the outside storage system.
-
Firmware is the firmware level used by the outside storage controller.
-
Serial No. is the serial number of the outside storage system.
-
Capacity is the amount of data in a volume sent to the restorer.
system12# disk show hardware
Disk
LUN
Port WWN
----------------------------disk1
0
50:06:01:60:30:20:e2:12
disk2
4
50:06:01:60:30:20:e2:12
----------------------------Firmware
Serial No.
--------------------0216
APM00045001866
0216
APM00045001866
--------------------2 drives present.
Manufacturer/Model
-----------------DGC RAID 3
DGC RAID 3
------------------
Capacity
-------1.56 TB
1.56 TB
--------
63
Installation
•
disk status Displays information similar to the following. After drives are “in use”, the
remainder of the drives lines are not valid.
system12# disk
Configuration:
RAID:
RAID:
RAID:
RAID:
RAID:
RAID:
RAID:
Performance:
status
2 drives present.
Cumulative
0.075 MB/s, 7 % busy
Installation
A restorer using outside storage must first connect with the outside storage and then configure the
use of the storage.
1. For hardware setup (setting up the restorer chassis), see “Restorer Installation” on page 32.
2. On the outside disk array system, create the LUNs for use by the restorer.
3. On the outside disk array system, configure LUN masking so that the restorer can see only
those LUNs that should be available to the restorer. The restorer writes to every LUN that is
available.
4. Connect the Fiber Channel cable from the Fiber-Channel Arbitrated Loop (FC-AL) to the
Fiber Channel HBA card ports on the back of the restorer. The cable and the outside storage
must also be connected to the FC-AL.
5. Connect a serial terminal to the restorer. A VGA console does not display the menu mentioned
in the next step of this procedure.
64
Installation
6. Press the Power button on the front of the restorer. During the initial system start, the restorer
does not know of the available LUNs. The following menu appears with the Do a New Install
entry selected:
New Install
1. Do a New Install
2. Show Configuration
3. Reboot
7. Check that the LUNs available from the connected array system are correct. Use the
down-arrow key, select Show Configuration, and press Enter. The configuration menu appears
with Show Storage Information selected:
System Configuration
(Before Installation)
1.
2.
3.
4.
5.
Show Storage Information
Show Head Information
Go to Previous Menu
Go to Rescue Menu
Reboot
8. Press Enter to display storage information. Each LUN that is available from the array system
appears as a one line entry in the List of SCSI Disks/LUNs. The Valid RAID DiskGroup UUID
List section shows no disk groups until after installation. Use the arrow keys to move up and
down in the display.
Storage Details
Software Version: 3.1.0.0-19112
Valid RAID DiskGroup UUID List:
ID
DiskGroup UUID Last Attached Serialno
------------------------------------------------- No diskgroup uuids were found -List of SCSI Disks/LUNs:
(Press ctrl+m for disk size information)
ID
UUID tgt lun loop
wwpn
comments
--------------------------------------------------------------1
No UUID
0
0
0 500601603020e212
2
No UUID
0
4
0 500601603020e212
Number of Flash disks: 1
---------------------------------------Errors Encountered:
----------------------------------------- No errors to report
65
Troubleshooting
9. Press Enter to return to the New Install menu.
10. Use the up-arrow key to select Do a New Install.
11. Press Enter to start the installation. The system automatically configures the use of all LUNs
available from the array.
12. Press Enter to accept the Yes selection in the New Install? Are you sure? display. No other user
input is required.
A number of displays appear during the reboot. Each one automatically times-out with the
displayed information and the reboot continues.
13. When the reboot completes, the login prompt appears. Login and configure the restorer as
explained in the Installation chapter of this manual beginning with step 2 on page 39.
Troubleshooting
Problems during installation or loss of access to a configured LUN causes the following menu to
appear. Use the arrow keys to navigate the menu and press Enter to display the next level of
information.
System Misconfigured
(The system has 0 disks/LUNs!)
1.
2.
3.
4.
5.
6.
•
66
Show Storage Information
Show Head Information
Show Head Swap Menu
Show New Install Menu
Go to Rescue Menu
Reboot
Show Storage Information displays the LUNs that are currently available to the restorer. If the
Comments column of the List of SCSI Disks/LUNs section includes an Incomplete, one or more
LUNs configured for the restorer is not available.
Procedure: Adding a LUN
•
Show Head Information displays informative error messages in the Errors Encountered
section. For example, the version number of the software on the restorer is also stored in a file
on the outside storage. If the version number on the restorer does not match the version number
stored on outside storage, an error message appears.
Head Details
Software Version: 4.0.0.0-26902
Model Type: DD500G
Serial Number xxxx
Has Flash: YES
Previously Saved RAID DiskGroup UUID List:
ID
DiskGroup UUID
--------------------------------------------1
1302c2433dec8025
--------------------------------------------Errors Encountered:
----------------------------------------------Version numbers do not match
•
Go to Rescue Menu allows you to display the system log.
Rescue Options
1. View Log
2. Go to Previous Menu
3. Reboot
After installing a gateway restorer to use LUNs on outside storage, you can expand the volume by
adding LUNs (all LUNs are seen as a single volume by the restorer).
Caution Once a LUN is added to the volume used by the restorer, you cannot remove the LUN.
The only way to reduce the volume size is to re-install the restorer operating system and
reconfigure the restorer.
If a LUN used by a restorer is removed from the outside storage, the restorer file system
is immediately compromised and returns an error condition.
1. On the outside storage, create the new LUN. Make sure that masking for the new LUN allows
the restorer to see the LUN.
67
2. On the restorer, enter the disk rescan command to find the new LUN.
# disk rescan
NEW: Host: scsi0 Channel: 00 Id: 00 Lun: 03
Vendor: NEXSAN
Model: ATAbea(C0A80B0C) Rev: 8035
Type:
Direct-Access
ANSI SCSI revision: 04
1 new device(s) found.
The disk show raid-info command then shows all of the previously configured LUNs
(as disk1, disk2, and so on) and the new LUN as not in use - foreign. Also, the new LUN is
referenced in the line 1 drive is “not in use”.
# disk show raid-info
Disk
State
Additional Status
---------------------------------------disk1
in use (dg0)
disk2
in use (dg0)
disk3
not in use - foreign
---------------------------------------2 drives are "in use"
1 drive is "not in use"
Note At this point, the new LUN can be removed from outside storage with no damage to the
restorer file system. The disk rescan command then shows the LUN as removed. After
using the disk add command (the next step), you cannot safely remove the LUN.
3. Use the disk add disk-id command to add the new LUN to the restorer volume. The
disk-id is given in the output from the disk show raid-info command.
# disk add disk3
The 'disk add' command adds a disk to the filesystem. Once the
disk is added, it cannot be removed from the filesystem without
re-installing the restorer.
Are you sure? (yes|no|?) [no]: yes
Output from the disk show raid-info command should now show the new disk (LUN) as in
use. Output from the filesys show space command should include the new space in the
Data section.
68
Virtual Tape Library (VTL)
6
The Data Domain VTL feature allows backup applications to connect to and manage a restorer as if
the restorer is a stand-alone tape library. All of the functionality supported with tape is available
with a restorer. Also, as with a physical stand-alone tape library, the movement of data from a
restorer VTL to a physical tape must be managed by backup software, not by the restorer.
Virtual tape drives are accessible to backup software in the same fashion as physical tape devices.
Devices appear to backup software as SCSI tape drives. A virtual tape library appears to software
as a SCSI robotic device accessed through standard driver interfaces.
The VTL feature:
•
Communicates between a backup server and a restorer through a Fibre Channel interface. The
restorer must have a Fibre Channel interface card in the PCI card array.
•
Is compatible with all Data Domain DD400 and DD500 series restorers.
•
Supports the tape drive model IBM LTO-1.
•
Supports the tape library personalities StorageTek L180 and RESTORER-L180. Data Domain
recommends using RESTORER-L180 with NetBackup.
Note Use tape and library drivers that are supplied by your backup software vendor and that
support the IBM LTO-1 drive and StorageTek L180 library. The RESTORER-L180 works
with the same drivers as the StorageTek L180.
•
Allows 16 virtual tape drive instances to be active concurrently.
•
Supports 8 tape library instances.Access to VTLs and tape drives can be managed with the
LUN masking feature. See “LUN Masking (for VTL Only)” on page 82.
•
Supports up to 100,000 tapes (cartridges) of up to 800 GB for an individual tape.
•
Includes a pool feature for replication of tapes by defined pools. See “Pools” on page 86 and
the VTL command output examples in this chapter. See “VTL Pools Replication” on page 201
for replication details.
•
Includes internal restorer data structures for each virtual data cartridge. The structures have a
fixed amount of space that is optimized for records of 16KB or larger. Smaller records use the
space at the same rate per record as larger records, leading to a virtual cartridge marked as full
when the amount of data is less than the defined size of the cartridge.
69
Compatibility Matrix
•
Supports replication between Data Domain restorers. A source restorer exports received virtual
tapes (each tape is seen as a file) into a virtual vault and leaves the tapes in the vault. On the
destination, each tape (file) is always in a virtual vault.
•
Does not protect virtual tapes from a restorer filesys destroy command. The command
deletes all virtual tapes.
•
Handles data received by a restorer during a power loss so that backup software sees the data in
the same way as with tape drives in a power loss situation. The strategy your backup software
uses to protect data during a loss of power to tape drives gives the same results with a loss of
power to a Data Domain restorer.
•
Responds to the mtx status command from an outside system in the same way as would a
tape library. If the restorer virtual library has registered any change since the last contact from
the outside system, the first use of the mtx status command returns incorrect results. Use
the command a second time for valid results.
•
Supports simultaneous use of tape library and file system (NFS/CIFS) interfaces.
•
VTL is a licensed feature for a Data Domain restorer. Contact your Data Domain
representative for licensing details.
Compatibility Matrix
For specific backup software and hardware configurations tested and supported by Data Domain,
see the VTL Certification Summary matrix. Find the matrix at:
https://support.datadomain.com/compat_matrix.php
Data Domain VTL with a SAN
Data Domain recommends single initiator zoning when using the VTL feature in a SAN (storage
area network) environment to simplify management and avoid possible host configuration issues.
Single initiator zoning puts the Data Domain VTL HBA (host bus adapter) card and a single
initiator, such as a backup server host, in a single zone. To allow additional hosts access to restorer
VTL devices, use LUN masking and define a new zone for each unique initiator and VTL HBA
pair.
For example, for backup serverA and backup serverB to access a restorer HBA in a SAN
environment, define two zones, one for each server, and create one LUN mask for each server. For
LUN masking details, see “LUN Masking (for VTL Only)” on page 82.
70
Enable VTLs
Enable VTLs
To start the VTL process and enable all libraries and drives, use the vtl enable option.
vtl enable
Disable VTLs
To disable all VTL libraries and drives and shutdown the VTL process, use the vtl disable
option.
vtl disable
Create a VTL
To create a virtual tape library, use the vtl add operation. The VTL process must be enabled (use
the vtl enable command) to create a library. Administrative users only.
vtl add vtl_name model model [drives num_drives]
[slots num_slots]
If incorrect values are entered for any of the command variables, a list of valid values is displayed.
•
vtl_name A name of your choice.
•
model Is a tape library model name. The current supported model names are L180 and
RESTORER-L180. Data Domain recommends using RESTORER-L180 with NetBackup.
•
num_drives The number of tape drives in the library. The maximum number of drives for
all VTLs on a restorer is 48 minus one for each VTL. A restorer with three VTLs could have a
maximum of 45 drives. The default is four drives.
•
num_slots The number of slots in the library. The number of slots must be equal to or
greater than the number of drives. The maximum number of slots for all VTLs on a restorer is
10000. The default is 20 slots.
For example, to create a VTL with 5 drives and 25 slots:
# vtl add VTL1 model L180 drives 5 slots 25
Chapter 6: Virtual Tape Library (VTL)
71
Create New Tapes
Create New Tapes
To create new tapes, use the vtl tape add option. All new tapes go into the virtual vault.
Note On a destination restorer, manually creating a tape is not permitted.
vtl tape add barcode [capacity capacity][count count]
[pool pool]
•
barcode The barcode must begin with six upper-case alpha-numeric characters. Of the six
characters, the number of numeric characters reading from the right determines the total
possible number of tapes that can be created (the number given for count). The last characters
in the barcode are a two-character tag of L1, LA, LB, or LC. L1 represents a tape of 100 GB
capacity; LA represents a tape of 50 GB capacity; LB represents a tape of 30 GB capacity; LC
represents a tape of 10 GB capacity. For example, a barcode of ABC000L1 creates tapes of 100
GB capacity and can accept a count of up to 1,000 tapes (from 000 to 999). A bar code of
AB0000LA creates tapes of 50 GB capacity and can accept a count of up to 100,000 tapes.
The numeric characters from the right also set the number for the first tape created. For
example, a barcode of ABC100L1 starts numbering the tapes at 100.
Data Domain recommends only creating tapes with unique bar codes. Duplicate bar codes in
the same tape pool create an error. Although no error is created for duplicate bar codes in
different pools, duplicate bar codes may cause unpredictable behavior in backup applications
and can lead to operator confusion.
•
capacity The number of gigabytes of size for each tape (overrides the barcode capacity
designation). The upper limit is 800. For the efficient reuse of restorer disk space after data is
obsolete, Data Domain recommends setting capacity to 100 or less.
•
count The number of tapes to create. The default is 1 (one).
•
pool Put the tapes into a pool. The pool is Default if none is given. A named pool must already
exist to use this option. Use the vtl pool add command to create a pool.
For example, to create 5 tapes starting with a barcode of TST010L1:
# vtl tape add TST010L1 count 5
72
Import Tapes
Import Tapes
To move existing tapes from the vault to a library, use the vtl import option. If a tape is in a
pool, you must use the pool option to identify the tape. You can import only as many tapes as the
VTL has available slots. Use the vtl tape show vtl-name command to display the
currently in-use slots. Use the vtl tape show vault command to display barcodes for all
tapes in the vault. Use backup software commands from the backup server to move library tapes
into virtual drives. Also, when a tape is in a library, you cannot manually insert the tape into a drive
with the vtl tape insert command.
vtl import vtl_name barcode barcode [pool pool] [count count]
For example, to import 5 tapes starting with a barcode of TST010L1 into the library VTL1:
# vtl import VTL1 barcode TST010L1 count 5
Export Tapes
Remove tapes from a VTL. Use the vtl tape show vtl-name command to match slots and
barcodes. The removed tapes revert to the vault.
vtl export vtl_name slot slot [count count]
For example, to export 5 tapes starting from slot 11 from the library VTL1:
# vtl export VTL1 slot 11 count 5
Remove Tapes
To remove one or more tapes from the vault and delete all of the data in the tapes, use the vtl
tape del option. The tapes must be in the vault, not in a VTL. Use the vtl tape show
vault command to display barcodes. If count is used, remove that number of tapes in sequence
starting at barcode.
•
If a tape is in a pool, you must use the pool option to identify the tape.
•
If count is used, remove that number of tapes in sequence starting at barcode.
•
After a tape is removed, the physical disk space used for the tape is not reclaimed until after a
file system clean operation.
Note On a destination restorer, manually removing a tape is not permitted.
vtl tape del barcode [pool pool] [count count]
73
Insert a Tape
For example, to remove 5 tapes starting with a barcode of TST010L1:
# vtl tape del TST010L1 count 5
Insert a Tape
To directly insert a tape into a drive without media changer intervention, use the vtl tape
insert option. The option is useful for disaster recovery as configuration information for the
media changer must be recovered from tape. Use the vtl tape show vtl-name command to
display which drives are available. Drives that already have tapes inserted appear as the first lines
in the vtl tape show vtl-name output.
•
The tape must already exist in the virtual vault and must not be in any drive.
•
If a tape is already imported into a VTL, the operation fails.
•
If a tape is in a pool, you must use the pool option to identify the tape.
vtl tape insert vtl_name drive drive barcode barcode [pool
pool]
Eject a Tape
To directly remove a tape from a drive without media changer intervention, use the vtl tape
eject option. Use the vtl tape show vtl-name command to display which drives are in
use. Drives with tapes inserted appear as the first lines in the vtl tape show vtl-name
output. A tape that is in a library (and in the drive through backup software commands) cannot be
ejected with this command. An ejected tape goes directly into the virtual vault.
vtl tape eject vtl_name drive drive
For example, to manually eject a tape, the following commands display drives in use for libr01,
then eject a tape from a drive:
# vtl tape show libr01
Barcode
Location
-------- -------------ABC100L1 libr01 drive 1
Type
----LTO-1
Size ...
---- ...
100.0 GB
# vtl tape eject libr01 drive 1
74
Delete a VTL
Delete a VTL
To remove a previously created virtual tape library, use the vtl del option. If the library name is
not valid, a list of valid library names is displayed.
vtl del vtl_name
Set a Private-Loop Hard Address
Some backup software requires all private-loop targets to have a hard address (loop ID) that does
not conflict with another node. Use the vtl option set loop-id command to set a hard
address for a restorer. The range for value is 0 - 125. For a new value to take effect, disable and
enable VTL or reboot the restorer.
vtl option set loop-id value
For example, to set a value of 5 and have the value take effect:
# vtl option set loop-id 5
# vtl disable
# vtl enable
Reset a Private-Loop Hard Address
To reset the private-loop hard address to the restorer default of 1 (One), use the vtl option
reset loop-id command.
vtl option reset loop-id
Display the Private-Loop Hard Address Setting
To display the most recent setting of the loop ID value (which may or may not be the current in-use
value), use the vtl option show loop-id command.
vtl option show loop-id
75
Display VTL Status
Display VTL Status
To display the status of the VTL process, use the vtl status option.
vtl status
The display is similar to the following:
# vtl status
VTL admin_state: enabled, process_state: running
VTL admin_state Can be enabled or disabled.
process_state Can be:
-
running The system is enabled and active.
-
starting The vtl enable command is bringing up the VTL process.
-
stopping The vtl disable command is shutting down the VTL process.
-
stopped The VTL process is disabled.
-
timing out The VTL process crashed and is attempting an automatic restart.
-
stuck After a number of VTL process automatic restarts failed, the process was not able to
shut down normally and attempts to kill the process failed.
Display VTL Configurations
To display configuration details for all or a single virtual tape library, use the vtl show config
option.
vtl show config [vtl_name]
# vtl show config
Library Name
Library Model
-----------------------VTL1
10001
------------------------
76
Drive Model
----------1
-----------
Slots
----120
-----
Drives
-----4
------
Display All Tapes
Display All Tapes
To display information about all tapes created on a restorer, use the vtl tape show all
option. The Size and Used columns show the amount of data sent to the tape by the backup client,
not the amount of actual disk space used by compressed data.
vtl tape show all
# vtl tape show all
... processed 6 tapes...
Barcode Pool
Location
-------- ------- -------A00000L1 Default VTL1
A00001L1 Default VTL1
A00002L1 Default vault
Type
----LTO-1
LTO-1
LTO-1
LTO-1
LTO-1
LTO-1
Size
-------100.0 GB
100.0 GB
100.0 GB
100.0 GB
100.0 GB
100.0 GB
Used
Compression
-------- ----------100.0 GB
10x
100.0 GB
10x
0.0 GB
0x
0.0 GB
0x
0.0 GB
0x
0.0 GB
0x
-
The Pool column displays which pool holds the tape. The Default pool holds all tapes that
are not assigned to a user-created pool.
-
The Location column displays whether tapes are in a user-created library or in the virtual
vault.
-
The Size column displays the configured data capacity of the tape.
-
The Used column displays the amount of data sent to the tape (before compression).
-
The Compression column displays the amount of compression done to the data on a tape.
Display a Summary of All Tapes
To display a summary of all tapes on a restorer, use the vtl tape show summary option.
vtl tape show summary
The display for the summary option gives the following types of information with values
appropriate for your system:
# vtl tape show summary
VTL Tape Summary
---------------Total number of tapes:
Total pools:
6
1
77
Display Tapes by VTL
Total size of tapes:
600.0 GB
Total space used by tapes: 200.0 GB
Average Compression:
15.0x
-
Total number of tapes is the number of tapes configured on the restorer.
-
Total pools is the number of default and user-defined tape pools. A restorer always has one
default tape pool.
-
Total size of tapes is the total capacity of all configured tapes.
-
Total space used by tapes is the amount of data sent to all tapes (before compression).
-
Average compression is the average of the compression value for all tapes that hold data.
If data is stored elsewhere on the restorer and then identical data is stored on tapes, the
tape compression value can be very high as the data on the virtual tapes takes up no new
disk space.
Display Tapes by VTL
To display information about all tapes in a VTL, use the vtl tape show vtl_name option.
vtl tape show vtl_name
The display for the vtl-name option includes a slot number in the Location column. The Size and
Used columns show the amount of data sent to the tape by the backup client, not the amount of
actual disk space used by compressed data.
# vtl tape show VTL1
Barcode Pool
Location
-------- ------- -----------A00000L1 Default VTL1 drive 1
A00004L1 Default VTL1 drive 2
A00001L1 Default VTL1 slot 2
A00003L1 Default VTL1 slot 3
78
Type
----LTO-1
LTO-1
LTO-1
LTO-1
Size
-------100.0 GB
100.0 GB
100.0 GB
100.0 GB
Used
Compression
-------- ----------100.0 GB
20x
0.0 GB
0x
100.0 GB
10x
0.0 GB
0x
-
-
The Location column displays whether tapes are in a drive or a library slot. A tape is
inserted into a drive either by backup software or manually with the vtl tape insert
command. Tapes in a drive are moved to the beginning of the command output.
-
-
-
Display All Tapes in the Vault
Display All Tapes in the Vault
To display all tapes that are in the virtual vault, use the vtl tape show vault option.
vtl tape show vault
In the following example, only two tapes of the six used in previous examples are still in the vault:
# vtl tape show vault
Barcode Pool
Location
-------- ------- -------A00002L1 Default vault
Type
----LTO-1
LTO-1
Size
Used
Compression
-------- -------- ----------100.0 GB
0.0 GB
0x
100.0 GB
0.0 GB
0x
-
-
The Location column displays whether tapes are in a user-created library or in the virtual
vault.
-
-
-
Display Tapes by Pools
To display information about tapes in pools, use the vtl tape show pool name option.
vtl tape show pool name
# vtl tape show pool pl22
Barcode Pool
Location
-------- ------- -------A00000L1 pl22
VTL1
A00004L1 pl22
VTL1
A00001L1 pl22
VTL1
A00003L1 pl22
VTL1
Type
----LTO-1
LTO-1
LTO-1
LTO-1
Size
-------100.0 GB
100.0 GB
100.0 GB
100.0 GB
Used
Compression
-------- ----------100.0 GB
20x
0.0 GB
0x
100.0 GB
10x
0.0 GB
0x
-
The Pool column displays which pool holds the tape.
-
The Location column displays whether tapes are in a drive or a library slot. A tape is
inserted into a drive either by backup software or manually with the vtl tape insert
command. Tapes in a drive are moved to the beginning of the command output.
-
79
Display VTL Statistics
-
-
Display VTL Statistics
To display statistics for all or a single virtual tape library, use the vtl show stats option. The
statistics are updated every two seconds. Use the <Ctrl> c key combination to stop the
command. The vtl_name variable is case sensitive.
vtl show stats vtl_name
# vtl show stats VTL1
Read KB/s Write KB/s
--------- ---------80
40
79
42
80
41
Procedure: Retrieve a Replicated Tape from a Destination
Replicating tapes from a source to a destination requires a replication license on the both the source
and destination restorers. Visualize the retrieving of a replicated tape from a destination restorer as
physically removing the tape from the source restorer VTL and moving the tape to the destination
restorer VTL. One tape physically cannot be in two places at the same time from the point of view
of backup software.
Backup application behavior for handling replicated tapes varies. To minimize unexpected
behavior or error conditions, virtual tapes should remain imported in the destination libraries only
for as long as needed. After importing a replicated tape at the destination, follow your backup
application’s procedures to utilize the replicated tape and then export the tape from the destination
library. The objective is to ensure that at any time, only one instance of a replicated tape is visible to
the backup application.
The following generic procedure allows you to configure a VTL for replication and retrieve data
from a virtual tape that was replicated to a destination restorer. See “VTL Pools Replication” on
page 201 for further replication detail and consult your backup application documentation for
specific backup procedures.
1. On the source restorer, create the VTL and tapes. Use the vtl add command.
2. Perform and verify one or more backups to the source restorer.
80
Procedure: Retrieve a Replicated Tape from a Destination
3. Configure replication for the pool to be replicated (for example: /backup/vtc/Default
or /backup/vtc/pool-name) using the replication add command.
4. Verify that any tapes targeted for replication from the destination reside in the vault and not in
a library. Use the vtl tape show command.
5. Initialize replication for the targeted pool using the replication initialize
command. Wait for initialization to complete.
6. As required, perform additional backups to the source. Wait for outstanding backups to
complete.
7. Identify the tapes that you need to retrieve from the destination restorer and have the list
available at the destination location.
8. On the source, enter the command replication sync for the target pool to ensure that the
source tape and destination tape are consistent. Wait for the command to complete.
9. If the replicated tapes to be retrieved at the destination are still accessible at the source, export
the tapes from the source restorer and, using the backup application, inventory the source VTL.
10. On the destination, create a VTL if one does not already exist. Use the vtl add command.
The destination VTL configuration does not have to match the library on the source restorer.
11. Import the tape or tapes to the library using the vtl import command. The replicated tapes
should now reside in the destination VTL. From the backup application, inventory the
destination VTL. For some configurations or backup application versions, you may need to
import the catalog (the backup application database) to use replicated tapes.
12. Read the tapes from the destination restorer VTL in the same way that you would read tapes
from a library on the source and perform required backup application operations such as
cloning to physical tape.
13. After using the replicated tapes, export the tapes from the destination using the vtl export
command.
14. If necessary, import the replicated tapes from the source restorer using the vtl import
command. The replicated tapes should now reside in the source restorer VTL.
15. From the backup application, inventory the destination VTL.
81
LUN Masking (for VTL Only)
The Data Domain VTL LUN masking feature allows clients to access only selected LUNs (devices,
which are media changers or virtual tape drives) on a restorer.
•
All restorer clients are automatically in a VTL access pool named default and can access all
VTL devices.
•
A client that is set up for LUN masking is no longer in the default pool and can access only
devices masked for the client.
•
Clients that are not set up for LUN masking are still in the default pool and can access all
devices that are not part of another client’s LUN mask.
To use LUN masking:
•
Create a VTL on the restorer. See “Create a VTL” on page 71.
•
Enable the VTL with the vtl enable command.
•
Map a client as a LUN masking initiator (see below).
•
Create a LUN mask. See the commands in this section and “Procedure: Create a LUN Mask”
on page 85.
Note Avoid making LUN masking changes on a restorer during active backup or restore jobs. A
change may cause an active job to fail. The impact of changes during active jobs depends on
a combination of backup software and host configurations.
The vtl initiator Command
An initiator is any restorer client. Before adding a LUN mask for a client, create an initiator name
to map to the client’s world-wide port name (WWPN).
82
•
Adding a client as an initiator removes the client from the default access pool. Deleting the
initiator mapping from a client returns the client to the default pool.
•
After mapping a client as an initiator and before adding a LUN mask for the client, the client
cannot access any data on the restorer.
•
After adding a LUN mask for the initiator/client, the client can access only the devices in the
LUN mask. A client can have LUN masks for multiple devices.
•
A maximum of 128 initiators can be configured.
Add an Initiator
Use the vtl initiator add command to give a client an initiator name on a restorer.
vtl initiator add initiator-name wwpn wwpn
•
The initiator-name is a name that you create for LUN masking. The name can have up to 256
characters. Data Domain suggests using a simple, meaningful name.
•
The wwpn is the world-wide port name of the Fibre Channel port on the client system. Use the
vtl initiator show command on the restorer to list the restorer’s known clients and
WWPNs.
•
The wwpn must use colons ( : ).
For example:
# vtl initiator add client22 wwpn 21:00:00:e0:8c:11:33:04
Delete an Initiator
Use the vtl initiator del command to delete a client initiator mapping from the restorer.
The client returns to the default access pool. All LUN masks for the initiator must be deleted before
deleting the initiator.
vtl initiator del initiator-name
For example:
# vtl initiator del client22
Display Initiators
Use the vtl initiator show command to list one or all named initiators and their WWPNs.
vtl initiator show [initiator-name]
For example:
# vtl initiator show
Initiator
WWPN
------------------------------Default
00:00:00:00:00:00:00:00
client22
21:00:00:e0:8c:11:33:04
-------------------------------
83
The vtl lunmask Command
When setting up LUN masks on a restorer:
•
Each restorer device can have a maximum of 1 LUN mask. A device is a media changer or a
virtual tape drive.
•
Each initiator can have multiple LUN masks.
Add a LUN Mask
Use the vtl lunmask add command to create a LUN mask. Each instance of the command can
create a mask for one device. To mask multiple devices for a single initiator, use the command once
for each device.
vtl lunmask add vtl-name {all | changer | drive drive-name}
name initiator [lun lun]
The vtl-name is one of the libraries that you have created. Use the vtl show config command
to display all library names.
The all option adds all devices in the vtl-name.
The drive-name is a virtual tape drive as reported to an initiator. Use the vtl lunmask show
command on the restorer to list drive names (which include a space between the word drive and the
number). A drive that is not masked to any initiator displays default in the Initiator column.
The initiator is a restorer client that you have mapped as an initiator on the restorer. Use the vtl
initiator show command to list known initiators.
The optional lun is the LUN number that the restorer returns to the initiator.
-
The maximum LUN number accepted when creating a LUN mask is 255.
-
A LUN number can be used only once for an individual initiator. The same LUN number
can be used with multiple initiators.
For example, the following two commands add masks for the initiator client22 for drive 3 and
drive 4 (note the space in each name) with a LUN number of 22 for drive 4.
# vtl lunmask add vtl01 drive drive 3 name client22
# vtl lunmask add vtl01 drive drive 4 name client22 lun 22
Delete a LUN Mask
Use the vtl lunmask del command to delete one or all LUN masks for an individual initiator.
vtl lunmask del vtl-name {all | changer | drive drive-name}
name initiator
84
The vtl-name is one of the libraries that you have created. Use the vtl show config command
to display all library names.
The all option deletes all devices in the vtl-name that are masked for the initiator.
The drive-name is a virtual tape drive as reported to an initiator. Use the vtl lunmask show
command on the restorer to list drive names and the initiators masked to each drive.
The initiator is a restorer client that you have mapped as an initiator on the restorer. Use the vtl
initiator show command to list known initiators.
Display LUN Masks
Use the vtl lunmask show command to display configured LUN masks. The optional
vtl-name variable limits the display to a single VTL.
vtl lunmask show [vtl-name]
The following example shows a VTL with client22 masks for drive 3 and drive 4. Multiple masks
for the same device appear in the order in which they were configured.
# vtl lunmask show vtl02
Device
Initiator
--------------------vtl02 changer
default
vtl02 drive 1
default
vtl02 drive 2
default
vtl02 drive 3
client22
vtl02 drive 4
client22
vtl02 drive 5
default
LUN
--0
1
2
3
22
5
Procedure: Create a LUN Mask
1. Use the vtl initiator show command to list the restorer’s known clients and
world-wide port names (WWPNs). The WWPN is for the Fibre Channel port on the client
system.
For example:
# vtl initiator show
Initiator
WWPN
------------------------------Default
00:00:00:00:00:00:00:00
client22
21:00:00:e0:8c:11:33:04
-------------------------------
85
Pools
2. Add a client as an initiator for the VTL feature. Use the client WWPN from the vtl
initiator show command.
# vtl initiator add client22 wwpn 21:00:00:e0:8c:11:33:04
3. Use the vtl lunmask show command to display VTLs and device numbers.
Device
Initiator
--------------------vtl02 changer
default
vtl02 drive 1
default
vtl02 drive 2
default
vtl02 drive 3
default
vtl02 drive 4
default
vtl02 drive 5
default
LUN
--0
1
2
3
4
5
4. Add a LUN mask. The following example adds a LUN mask that makes drive 3 available to
client22.
# vtl lunmask add vtl01 drive drive 3 name client22
5. With no LUN number specified, the default LUN number is used.
Device
Initiator
--------------------vtl02 changer
default
vtl02 drive 1
default
vtl02 drive 2
default
vtl02 drive 3
client22
vtl02 drive 4
default
vtl02 drive 5
default
LUN
--0
1
2
3
4
5
Pools
The Data Domain pool feature for VTL allows replication by groups of VTL virtual tapes. The
feature also allows for the replication of VTL virtual tapes from multiple replication originators to a
single replication destination. For replication details, see “VTL Pools Replication” on page 201.
86
•
A pool name can be a maximum of 32 characters.
•
A pool name with the restricted names Default, all, vault, or summary cannot be created or
deleted.
•
A pool named Default always exists. All tapes not assigned to user-created pools are assigned
to Default.
Pools
•
A pool can be replicated no matter where individual tapes are located. Tapes can be in the
vault, a library, or a drive.
•
You cannot move a tape from one pool to another.
•
Two tapes in different pools on one restorer can have the same name.
•
A pool sent to a replication destination must have a pool name that is unique on the destination.
•
Restorer pools are not accessible by backup software.
•
No VTL configuration or license is needed on a replication destination when replicating pools.
•
Data Domain recommends only creating tapes with unique bar codes. Duplicate bar codes in
the same tape pool create an error. Although no error is created for duplicate bar codes in
different pools, duplicate bar codes may cause unpredictable behavior in backup applications
and can lead to operator confusion.
Add a Pool
Use the vtl pool add command to create a pool. The pool-name cannot be Default, all, vault,
or summary. Max of 32 characters.
vtl pool add pool-name
Delete a Pool
Use the vtl pool del command to delete a pool. The pool must be empty before the deletion.
Use the vtl tape del command to empty the pool.
vtl pool del pool-name
Display Pools
Use the vtl pool show command to display pools.
vtl pool show {all | pool-name}
For example, to display the tapes in pl22:
# vtl pool show pl22
Barcode Pool
Location
-------- ------- -------A00000L1 pl22
VTL1
A00004L1 pl22
VTL1
A00001L1 pl22
VTL1
A00003L1 pl22
VTL1
Type
----LTO-1
LTO-1
LTO-1
LTO-1
Size
-------100.0 GB
100.0 GB
100.0 GB
100.0 GB
Used
Compression
-------- ----------100.0 GB
20x
0.0 GB
0x
100.0 GB
10x
0.0 GB
0x
87
Pools
88
Configuration Management
7
The restorer config command allows you to examine and modify all of the configuration
parameters that are set in the initial system configuration. The license command allows you to
add, delete, and display feature licenses. The migration command copies all data from one
restorer to another. The command is usually used when upgrading from a smaller restorer to a
larger restorer.
The config Command
The config setup command brings up the same prompts as the initial system configuration.
You can change any of the configuration parameters as detailed in the section “Login and
Configuration” on page 36. All of the config operations are available only to administrative
users.
You can also use other restorer commands to change individual configuration settings. Most of the
remaining chapters of this manual detail using individual commands. An example of an individual
command that sets only one of the config possibilities is nfs add to add NFS clients.
Change Configuration Settings
To change multiple configuration settings with one command, use the config setup operation.
The operation displays the current value for each setting. Press the Return key to retain the current
value for a setting. Administrative users only.
config setup
See “Login and Configuration” on page 36 for details about using config setup. Enter the
command from a command prompt to change values after the initial setup.
Many other restorer commands change configuration settings. For example, the user command
adds another user account each time a user is added.
89
The config Command
Note You can also use the Data Domain Enterprise Manager graphical user interface to change all
of the same parameters that are available through the config setup command. In the
Data Domain Enterprise Manager, select Configuration Wizard in the top section of the left
panel.
Save and Return a Configuration
Using SSH, you can direct output from the restorer config dump command, which returns all
restorer configuration settings, into a file on a remote host from which you do restorer
administration. You can later use SSH to return the file to the restorer, which immediately
recognizes the settings as a configuration and accepts the settings as the current configuration.
For example, the following command connects with the restorer dd10 as user sysadmin, asks for the
password, returns output from the command config dump that is run on the restorer, and stores
the output in the local file (remote from the restorer) /tmp/config12:
# ssh -l sysadmin dd10 config dump > /tmp/config12
sysadmin@dd10’s password:
reg set config.aliases.default_set.root = '1'
reg set config.aliases.default_set.sysadmin = '1'
reg set config.aliases.sysadmin.df = 'filesys show space'
reg set config.aliases.sysadmin.halt = 'system poweroff'
.
.
.
The following command returns the configuration settings from the file /tmp/config12 to the
restorer. The settings immediately become the current configuration for the restorer.
# ssh -l sysadmin dd10 < /tmp/config12
Reloading configuration: (CHECKED)
Security access lists (from adminaccess) updated
Bringing up DHCP client daemon for eth0...
Bringing up DHCP client daemon for eth2...
Reset the Location Description
To reset the location description to the system default of a null entry, use the config reset
location command. Administrative users only.
config reset location
90
The config Command
Reset the Mail Server to a Null Entry
To reset the mail server used by the restorer to the system default of a null entry, use the config
reset mailserver command. Administrative users only.
config reset mailserver
Reset the Time Zone to the Default
To reset the time zone used by the restorer to the system default of US/Pacific, use the config
reset timezone command. Administrative users only.
config reset timezone
Set an Administrative Email Address
To give an address to which the restorer sends alerts and autosupport messages, use the config
set admin-email command. The system needs only one administrative email address. Use the
autosupport and alerts commands to add other email addresses. Administrative users only.
config set admin-email email-address
For example:
# config set admin-email [email protected]
The Admin email is: [email protected]
To check the operation, use the config show admin-email command.
Set an Administrative Host Name
To change the machine from which you can log into the restorer to see system logs and use system
commands, use the config set admin-host host operation. The host name can be a
simple host name, a host name with a fully-qualified domain name, or an IP address.
Administrative users only.
config set admin-host host
For example, to set the administrative host to admin12.yourcompany.com:
# config set admin-host admin12.yourcompany.com
To check the operation, use the config show admin-host command.
Chapter 7: Configuration Management
91
The config Command
Change the System Location Description
To change the description of a restorer location, use the config set location
“location” operation. A description of a physical location helps identify the machine when
viewing alerts and autosupport emails. If the description contains one or more spaces, the
description must be in double quotes. Administrative users only.
config set location ”location”
For example, to set the location description to row2-num4-room221:
# config set location “row2-num4-room221”
To check the operation, use the config show location command.
Change the Mail Server Hostname
To change the SMTP mail server used by the restorer, use the config set mailserver
host operation. Administrative users only.
config set mailserver host
For example, to set the mail server to mail.yourcompany.com:
# config set mailserver mail.yourcompany.com
To check the operation, use the config show mailserver command.
Set a Time Zone for the System Clock
To set the system clock to a specific time zone, use the config set timezone operation. The
default setting is US/Pacific. See the appendix: “Time Zones” on page 265 for a complete list of
time zones. For the change to take effect for all currently running processes, you must reboot the
restorer. The operation is available to administrative users only.
config set timezone zone
For example, to set the system clock to the time zone that includes Los Angeles, California, USA:
# config set timezone Los_Angeles
To display time zones, enter a category or a partial zone name. The categories are: Africa, America,
Asia, Atlantic, Australia, Brazil, Canada, Chile, Europe, Indian, Mexico, Mideast, Pacific, and US.
The following examples show the use of a category and the use of a partial zone name:
# config set timezone us
US/Alaska
US/Aleutian
US/Eastern US/East-Indiana
US/Michigan US/Mountain
92
US/Arizona
US/Hawaii
US/Pacific
US/Central
US/Indiana-Starke
US/Samoa
The config Command
# config set timezone new
Ambiguous timezone name, matching ...
America/New_York
Canada/Newfoundland
Display the Administrative Email Address
To display the administrative email address that the restorer uses for email from the alerts and
autosupport utilities, use the config show admin-email operation.
config show admin-email
# config show admin-email
The Admin Email is: [email protected]
Display the Administrative Host Name
To display the administrative host from which you can log into the restorer to see system logs and
use system commands, use the config show admin-host operation.
config show admin-host
# config show admin-host
The Admin Host is: admin12.yourcompany.com
Display the System Location Description
To display the restorer location description, if you gave one, use the config show location
operation. Administrative users only.
config show location
# config show location
The System Location is: bldg12 rm 120 rack8
Display the Mail Server Hostname
To display the name of the mail server that the restorer uses to send email, use the config show
mailserver operation.
config show mailserver
93
The license Command
# config show mailserver
The Mail (SMTP) server is: mail.yourcompany.com
Display the Time Zone for the System Clock
To display the time zone used by the system clock, use the config show timezone operation.
config show timezone
# config show timezone
The Timezone name is: US/Pacific
The license Command
The license command manages licensed features on a restorer.
Add a License
To add a feature license, use the license add operation. The code for each license is a string of
16 letters with dashes. Include the dashes when entering the license code. Administrative users
only.
The licensed features are:
•
REPLICATION
Use the Data Domain Replicator for replication of data from one restorer to another.
•
VTL
Use a restorer as a virtual tape library.
license add license-code
For example:
# license add ABCD-BCDA-CDAB-DABC
License “ABCE-BCDA-CDAB-DABC” added.
94
The license Command
Remove All Feature Licenses
To remove all licenses use the license reset operation. The system then behave as though it
has the single default license of CAPACITY-FULLSIZE. Administrative users only.
license reset
Remove a License
To remove a current license, use the license del operation. Enter the license feature name or
code (as shown with the license show command). Administrative users only.
license del {license-feature | license-code}
For example:
# license del replication
The REPLICATION license is removed.
Display Licenses
The license display shows only those features licensed on the restorer. Administrative users only.
## is the license number of the feature.
License Key is the characters of a valid license key.
Feature is the name of the licensed feature. Current licensed features are Replicator for replication
from one restorer to another, and the virtual tape library (VTL) feature.
Display
To display current licenses and default features, use the license show operation. Each line
shows the license code.
license show
For example:
# license show
## License Key
-- ------------------1 DEFA-EFCD-FCDE-CDEF
2 EFCD-FCDE-CDEF-DEFA
-- ------------------
Feature
----------------REPLICATION
VTL
----------------
95
Migration
Migration
The migration command copies all data from one restorer to another and may also copy
replication contexts (configurations). Use the command when upgrading to a larger capacity
restorer. Migration is usually done in a LAN environment. See the procedures at the end of this
section for using migration with a restorer that is part of a replication pair.
•
All data under /backup is always migrated and exists on both systems after migration.
•
After migrating replication contexts, the migrated contexts still exist on the migration source.
After migrating a context, break replication for that context on the migration source.
•
Do not run backup operations to a migration source during a migration operation.
•
A migration destination does not need a replication license unless the system will use
replication.
•
The migration destination must have a capacity that is the same size as or larger than the
migration source.
•
The migration destination must have an empty file system.
•
Any setting of the system’s replication throttle feature also applies to migration. If the
migration source has throttle settings, use the replication throttle set override
command to set the throttle to the maximum (unlimited) before starting migration.
Set Up the Migration Destination
To prepare a restorer to be a migration destination, use the migration receive operation.
Administrative users only. Use the operation:
•
Only on the migration destination.
•
Before entering the migration send command on the migration source.
•
Only on a destination system that has no data in the file system. Run a filesys destroy
operation first if needed to clear the file system.
The command syntax is:
migration receive source-host src-hostname
For example, to prepare a destination for migration from a migration source named hostA:
# migration receive source-host hostA
96
Migration
Start Migration from the Source
To start migration, use the migration send operation on the migration source. Administrative
users only. Use the operation:
•
Only on the migration source.
•
Only when no backup data is being sent to the migration source.
•
After entering the migration receive command on the migration destination.
migration send obj-spec-list destination-host dest-hostname
The obj-spec-list is /backup for systems that do not have a replication license. With replication,
the obj-spec-list is one or more contexts from the migration source. After migrating a context, all
data from the context is still on the source system, but the context configuration is only on the
migration destination. A context in the obj-spec-list can be:
•
The destination string as defined when setting up replication. Examples are:
dir://hostB/backup/dir2
col://hostB
pool://hostB/pool2
•
The context number as shown in output from the replication status command. For
example:
rctx://2
•
The keyword all, which migrates all contexts from the migration source to the destination.
Backup jobs to the restorer should be stopped during the first migration phase as write access is
blocked during the first phase. Backup jobs can be resumed during the second phase. The first
phase takes a maximum of 30 minutes for a restorer with a full /backup file system. Use the
migration watch command to track the first migration phase.
New data written to the source is marked for migration until you enter the migration commit
command. New data written to the source after a migration commit command is not
migrated. Note that write access to the source is blocked from the time a migration commit
command is given until the migration process finishes.
The migration send command stays open until a migration commit command is
entered.
97
Migration
In the following examples, remember that all data on the migration source is always migrated, even
when a single directory replication context is specified in the command.
•
To start migration of data only (no replication contexts, even if replication contexts are
configured) to a migration destination named hostC, use a command similar to the following:
# migration send /backup destination-host hostC
•
To start a migration that includes a collection replication context (replication destination
string) of col://hostB:
# migration send col://hostB destination-host hostC
•
To start migration with a directory replication context of dir://hostB/backup/dir2:
# migration send dir://hostB/backup/dir2 destination-host hostC
•
To start migration with two replication contexts using context numbers 2 and 3:
# migration send rctx://2 rctx://3 destination-host hostC
•
To migrate all replication contexts:
# migration send all destination-host hostC
Create an End Point for Data Migration
The migration commit command limits migration to data received by the source at the time
the command is entered. You can enter the command and limit the migration of new data at any
time after entering the migration send command. All data on the source restorer at the time of
the commit command (including data newly written since the migration started) is migrated to the
destination restorer. Data Domain recommends entering the commit command after all backup jobs
for the context being migrated are finished.
Write access to the source is blocked after entering the migration commit command and
during the time needed to complete migration. After the migration process finishes, the source is
opened for write access, but new data is no longer migrated to the destination. After the commit,
new data for the contexts migrated to the destination should be sent only to the destination.
migration commit
Display Migration Progress
To track the initial phase of migration (when write access is blocked), use the migration
watch operation. The command output shows the percent completed.
migration watch
98
Migration
Stop the Migration Process
To kill a migration that is in progress, use the migration abort operation. The operation stops
the migration process and returns the restorer to its previous state. If the migration source restorer is
part of a replication pair, replication is re-started. Run the command on the migration source and
the migration destination. Administrative users only.
migration abort
Display Migration Statistics
To display migration statistics during the migration process, use the migration show stats
operation.
migration show stats
Migration statistics have the following columns:
Bytes Sent The total number of bytes sent from the migration source. The value includes backup
data, overhead, and network overhead. On the destination, the value includes overhead and network
overhead. Use the value (and the next value, Bytes received) to estimate network traffic generated
by migration.
Bytes Received The total number of bytes received at the destination. On the destination, the value
includes data, overhead, and network overhead. On the source, the value includes overhead and
network overhead. Use the value (and the previous value) to estimate network traffic generated by
migration.
Received Time The date and time of the most recent records received.
Processed Time The date and time of the most recent records processed.
For example:
# migration show stats
Destination
Bytes Sent
----------hostB
-----------
-----------153687473704
------------
Bytes
Received
---------1974621040
----------
Received
Time
---------------Fri Jan 13 09:37
----------------
Processed
Time
---------------Fri Jan 13 09:37
----------------
99
Migration
Display Migration Status
To display the current status of migration, use the migration status operation.
migration status
For example:
# migration status
CTX:
Mode:
Destination:
Enabled:
Local file system status
Connection
State:
Error:
Destination lag:
Current throttle:
Contexts under migration:
0
migration source
hostB
yes
enabled
connected since Tue Jul 17 15:20:09
migrating 3/3 60%
no error
0
unlimited
dir://hostA/backup/dir2
Procedure: Migrate between Source and Destination
To migrate data from a source, hostA, to a destination, hostB (ignoring replication contexts):
1. On hostB (the migration destination):
2. On hostA (the source), run the following command:
# migration send /backup destination-host hostB
3. On either host, run the following command to display migration progress:
# migration watch
4. At the appropriate time for your site, create a migration end point. The three phases of
migration may take many hours. During that time, new data sent to the source is also marked
for migration. To allow backups with the least disruption, use the following command after the
three migration phases finish. On hostA:
# migration commit
100
Migration
Procedure: Migrate with Replication
To migrate data and a context from a source, hostA, to a destination, hostC, when hostA is also a
directory replication source for hostB:
1. On hostC (the migration destination), run the following command. Note that the command also
disables the file system.
2. On hostA (the migration and replication source), run the following command. Note that the
command also disables the file system.
# migration send dir://hostB/backup/dir2 destination-host hostC
3. On the source migration host, run the following command to display migration progress:
# migration watch
4. First on hostA and then on hostC, run the following command. Note that the command also
disables the file system.
# migration commit
5. on hostB (the replication destination), run commands similar to the following to change the
replication source to hostC:
# filesys disable
# replication modify dir://hostB/backup/dir2
source-host hostC
# filesys enable
101
Migration
102
8
Access Control for Administration
The restorer adminaccess command allows remote hosts to use the FTP, TELNET, and SSH
administrative protocols on the restorer. The command is available only to restorer administrative
users.
The FTP and TELNET protocols have host-machine access lists that limit access. The SSH
protocol is open to the default user sysadmin and to all restorer users added with the user add
command. By default, only the SSH protocol is enabled.
Add a Host
To add a host (IP address or hostname) to the FTP or TELNET protocol access lists, use the
adminaccess add operation. You can enter a list that is comma-separated, space-separated, or
both. To give access to all hosts, the host-list can be an asterisk (*). Administrative users only.
adminaccess add {ftp | telnet} host-list
The host-list can contain class-C IP addresses, IP addresses with either netmasks or length,
hostnames, or an asterisk (*) followed by a domain name, such as *.yourcompany.com.
For example, to add srvr24 and srvr25 to the list of hosts that can use TELNET on the restorer:
# adminaccess add telnet srvr24,srvr25
Netmasks, as in the following examples, are supported:
# adminaccess add ftp 192.168.1.02/24
# adminaccess add ftp 192.168.1.02/255.255.255.0
103
Remove a Host
Remove a Host
To remove hosts (IP addresses, hostnames, or asterisk (*)) from the FTP or TELNET access lists,
use the adminaccess del operation. You can enter a list that is comma-separated,
space-separated, or both. Administrative users only.
adminaccess del {ftp | telnet} host-list
For example, to remove srvr24 from the list of hosts that can use TELNET on the restorer:
# adminaccess del telnet srvr24
Enable a Protocol
By default, the SSH, HTTP, and HTTPS services are enabled. FTP and TELNET are disabled.
HTTP and HTTPS allow users to log in through the web-based graphical user interface. The
adminaccess enable operation enables a protocol on the restorer. Note that to use FTP and
TELNET, you must also add host machines to the access lists. Administrative users only.
adminaccess enable {http | https | ftp | telnet | ssh | all}
For example, to enable the FTP service:
# adminaccess enable ftp
Disable a Protocol
To disable a service on the restorer, use the adminaccess disable operation. Disabling FTP
or TELNET does not affect entries in the access lists. If all services are disabled, the restorer is
accessible only through a serial console or keyboard and monitor. Administrative users only.
adminaccess disable {http | https | ftp | telnet | ssh | all}
For example, to disable the FTP service:
# adminaccess disable ftp
104
Reset System Access
Reset System Access
By default, FTP and TELNET are disabled and have no entries in their access lists. SSH is enabled.
No one is able to use FTP or TELNET unless the appropriate access list has one or more host
entries. The adminaccess reset operation returns the FTP and TELNET protocols to the
default state of disabled with no entries and sets SSH to enabled. Administrative users only.
adminaccess reset {ftp | telnet | ssh | all}
For example, to reset the FTP list to an empty list and reset FTP to disabled:
# adminaccess reset ftp
Add an Authorized SSH Public Key
Adding an authorized SSH public key to the SSH key file on a restorer is done from a machine that
will access the restorer. Adding a key allows a user to log in from the remote machine to the
restorer without entering a password. After creating a key on the remote machine, use the
adminaccess add ssh-keys operation. Administrative users only.
adminaccess add ssh-keys
For example, the following steps create a key and then write the key to a restorer:
1. On the remote machine, create the public and private SSH keys.
jsmith > ssh-keygen -d
Generating public/private dsa key pair.
Enter file in which to save the key (/home/jsmith/.ssh/id_dsa):
.
.
2. Press Enter to accept the file location and other defaults. The public key created under
/home/jsmith/.ssh (in this example) is id_dsa.pub.
3. On the remote machine, write the public key to the restorer, dd10 in this example. The restorer
asks for the sysadmin password before accepting the key:
jsmith > ssh -l sysadmin dd10 “adminaccess add ssh-keys” \
< ~/.ssh/id_dsa.pub
Chapter 8: Access Control for Administration
105
Remove an SSH Key File Entry
Remove an SSH Key File Entry
To remove one entry from the SSH key file, use the adminaccess del ssh_keys lineno
operation. The lineno variable is the line number as displayed by the adminaccess show
ssh-keys command. Available only to administrative users.
adminaccess del ssh-keys lineno
For example, to remove the third entry in the SSH key file:
# adminaccess del ssh-keys 3
Remove the SSH Key File
To remove the entire SSH key file, use the adminaccess reset ssh-keys operation.
Available only to administrative users.
adminaccess reset ssh-keys
Create a New HTTPS Certificate
To generate a new HTTPS certificate for the restorer, use the adminaccess https
generate certificate command. Available only to administrative users.
adminaccess https generate certificate
Display the SSH Key File
To display all entries in the SSH key file, use the adminaccess show ssh-keys operation.
The output gives a line number to each entry. Available only to administrative users.
adminaccess show ssh-keys
106
Display Hosts and Status
Display Hosts and Status
The display shows every access service available on a restorer, whether or not the service is
enabled, and a list of hostnames that are allowed access through each service that uses a list. An
N/A in the Allowed Hosts column means that the service does not use a list. A - (dash) means that
the service can have a list, but currently has no hosts in the list. Administrative users only.
Display
To display protocol access lists and status, use the adminaccess show operation or click Admin
Access in the left panel of the Data Domain Enterprise Manager.
adminaccess show
For example, to show the status and lists for all services:
# adminaccess show
Service
Enabled
-------- -------ssh
yes
telnet
no
ftp
yes
http
https
--------
yes
no
--------
Allowed Hosts
-----------------------N/A
admin10.yourcompany.com
admin22.yourcompany.com
N/A
N/A
------------------------
Procedure: Return Command Output to a Remote machine
Using SSH, you can have output from restorer commands return to a remote machine at login and
then automatically log out. Available only to the user sysadmin. For example, the following
command connects with the machine dd10 as user sysadmin, asks for the password, and returns
output from the command filesys status.
# ssh -l sysadmin dd10 filesys status
The filesystem is enabled
You can create a file with a number of restorer commands, with one command on a line, and then
use the file as input to the login. Output from all the commands is returned. For example, a file
named cmds11 could contain the following commands:
filesys status
system show uptime
nfs status
Chapter 8: Access Control for Administration
107
Procedure: Return Command Output to a Remote machine
The login and the returned data look similar to the following:
# ssh -l sysadmin dd10 < cmds11
The filesystem is enabled
3:00 pm up 14 days 10 hours 15 minutes 1 user, load average:
0.00, 0.00, 0.00
Filesystem has been up 14 days 10:13
The NFS system is currently active and running
Total number of NFS requests handled = 314576
To use scripts that return output from a restorer, see “Add an Authorized SSH Public Key” on
page 105 to eliminate the need for a password.
108
User Administration
9
The restorer command user adds, removes, and displays users and changes user passwords. A
restorer has two classes of user accounts. The user class is for standard users who have access to a
limited number of commands. Most of the user commands display information. The admin class is
administrative users who have access to all restorer commands. The default administrative account
is sysadmin. You can change the sysadmin password, but cannot delete the account.
Throughout this manual, command explanations include text similar to the following for
commands or operations that standard users cannot access: Available to administrative users only.
Add a User
To add a restorer user, use the user add user-name operation. The operation asks for a
password and confirmation or you can include the password as part of the command. Each user has
a privilege level of either admin or user. Admin is the default. The only way to change a user’s
privilege level is to delete the user and then add the user with the other privilege level. Available to
administrative users only. A user name must start with an alpha character.
user add user-name [password password][priv {admin | user}]
Note The user names root and test are default existing names on every restorer and are not
available for general use. Use the existing sysadmin user account for administrative tasks.
For example, to add a user with a login name of jsmith, a password of usr256, and administrative
privilege:
# user add jsmith password usr256 priv
Remove a User
To remove a user from a restorer, use the user del user-name operation. Available to
administrative users only.
user del user-name
109
Change a Password
For example, to remove a user with a login name of jsmith:
# user del jsmith
user jsmith removed
Change a Password
To change a user password, including the password for the sysadmin user, use the user change
password user-name operation. The operation asks for the new password and then asks you
to re-enter the password as a confirmation. Without the user-name component, the command
changes the password for the current user. Available to sysadmin to change any user password and
available to all users to change only their own password.
user change password [user-name]
For example, to change the password for a user with a login name of jsmith:
# user change password jsmith
Enter new password:
Re-enter new password:
Passwords matched
Reset to the Default User
To reset the user list to the one factory default user, sysadmin, use the user reset operation.
Available to administrative users only.
user reset
The response looks similar to the following, which lists all removed users:
# user reset
Removing user jsmith
Removing user bjones
Can not remove user sysadmin
Change a Privilege Level
To change a user privilege level, use the user change user-name operation with a key word
of admin or user. Available to users who currently have the admin privilege.
user change user-name {admin | user}
110
Display Current Users
For example, to change the privilege level from admin to user for the login name of jsmith:
# user change jsmith user
Display Current Users
The display of users currently logged in to a restorer shows:
Name is the user’s login name.
Idle is the amount of time logged in with no actions from the user.
Login Time is the date and time when the user logged in.
Login From shows the address from which the user logged in.
tty is the hardware or network port through which the user is logged in or GUI for the users logged
in through the Data Domain Enterprise Manager web-based interface.
Session is the user session number.
Display
Use the user show active operation or click Users in the left panel of the Data Domain
Enterprise Manager and look at Logged in Users.
user show active
The display looks similar to the following:
# user show active
Name
Idle Login Time
-------- ---- ---------------jsmith
18h
Thu Nov 11 15:46
sysadmin 0s
Fri Nov 12 09:44
-------- ---- ----------------
Login From
-----------------jsmith.company.com
------------------
tty
----GUI
pts/0
-----
Session
-----3262
26772
------
Chapter 9: User Administration
111
Display All Users
Display All Users
The display of all users known to the restorer is available to administrative users only. The
information given is:
Name is the user’s login name.
Class is the user’s access level of an administrator or a user who can see most information displays.
Last login from shows the address from which the user logged in.
Last login time is the date and time when the user last logged in.
Display
Use the user show all operation or click Users in the left panel of the Data Domain Enterprise
Manager and look at All Users.
user show list
# user show list
Name
Class Last login from
-------- ----- -----------------sysadmin admin user24.company.com
rjones
user user25.company.com
jsmith
user user26.company.com
-------- ----- ---------------------3 users found.
112
Last login time
-----------------------Fri Nov 12 14:55:47 2004
Fri Nov 12 12:36:30 2004
(never)
------------------------
Alerts and System Reports
10
A restorer uses multiple methods to inform administrators about the status of the Data Domain OS
and hardware. The restorer alerts, autosupport, and AM email features send messages and reports
to user-configurable lists of email addresses. The lists include an email address for Data Domain
support staff who monitor the status of all restorers and contact your company when problems are
reported. The messages also go to the system log.
•
The alerts feature sends an email whenever a critical component in the system fails or is
known, through monitoring, to be out of an acceptable range. Consider adding pager email
addresses to the alerts email list so that someone is informed immediately about system
problems. For example, a single fan failure is not critical and does not generate an alert as the
system can continue normal operations; however, multiple fan failures can cause a system to
begin overheating, which generates an alerts email.
Each disk, fan, and CPU in the restorer is monitored. Temperature extremes are also
monitored.
•
The autosupport feature sends a daily report that shows system identification information and
consolidates the output from a number of restorer commands. See “Run the Autosupport
Report” on page 119 for details. Data Domain support staff use the report for troubleshooting.
•
Every morning at 8:00 a.m. (local time for your system), the restorer sends an AM email to the
autosupport email list. The purpose is to highlight hardware or other failures that are not
critical, but that should be dealt with soon. An example would be a fan failure. A failed fan
should be replaced as soon as is reasonably possible, but the system can continue operations.
The AM email is a copy of output from alerts show current (see “Display Current
Alerts” on page 115) and alerts show history (see “Display the Alerts History” on
page 116) messages about non-critical hardware situations, and some disk space usage
numbers.
•
Non-critical hardware problems generate email messages to the autosupport list. An example
is a failed power supply when the other two power supplies are still fine. If the situation is not
fixed, the message also appears in the AM email.
•
Every hour, the restorer logs a short system status message. See “Hourly System Status” on
page 122 for details.
•
The support command sends multiple log files to the Data Domain Support organization.
113
Alerts
Alerts
Use the alerts command to administer the alerts feature.
Add to the Email List
To add an email address to the alerts list, use the alerts add operation. By default, the list
includes an address for Data Domain support staff. The email-list is a list of addresses that are
comma- separated or space-separated or both. After adding to the list, always use the alerts
test operation to test for mailer problems. Administrative users only.
alerts add email-list
For example, to add an email address to the alerts list:
# alerts add [email protected]
Test the Email List
To test the alerts list, use the alerts test operation, which sends an alerts email to each
address on the list or to a specific address. After adding addresses to the list, always use this
operation to test for mailer problems.
alerts test [email-addr]
For example, to test for the address [email protected]:
# alerts test [email protected]
Remove from the Email List
To remove an email address from the alerts list, use the alerts del operation. The operation is
for administrative users only. The email-list is a list of addresses that are comma-separated or
space-separated or both. Administrative users only.
alerts del email-list
For example, to remove an email address from the alerts list:
# alerts del [email protected]
114
Alerts
Reset the Email List
By default, the alerts list includes an address for Data Domain support personnel. The alerts
reset operation returns the list to the default address. Available only to administrative users.
alerts reset
Display Current Alerts
The list of current alerts includes all alerts that are not corrected. An alert is removed from the
display when the underlying situation is corrected. For example, an alert about a fan failure is
removed when the fan is replaced with a working unit.
Each type of alert maintains only one message in the current alerts list. For example, the display
reports the most recent date of a system reboot, not every reboot. Look in the system log files for
current and previous messages.
Display
To display current alerts, use the alerts show current operation or click Autosupport in the
left panel of the Data Domain Enterprise Manager and look at Current Alerts.
alerts show current
The command returns entries similar to the following:
# alerts show current
Alert Time
Description
---------------- -------------------------------------Fri Nov 12 18:54 Rear fan #1 failure: Current RPM is 0,
nominal is 8000
Fri Nov 12 16:22 Reboot reported. System rebooted
---------------- -------------------------------------There are 2 active alerts.
Chapter 10: Alerts and System Reports
115
Alerts
Display the Alerts History
The alerts history lists alerts messages from all of the existing messages system log files, which
hold messages for up to ten weeks.
Display
To display the history of alerts messages, use the alerts show history operation or click
Autosupport in the left panel of the Data Domain Enterprise Manager and look at Alert History. Use
the up and down arrow keys to move through the display. Use the q key to exit. Enter a slash
character (/) and a pattern to search for and highlight lines of particular interest.
alerts show history
# alerts show history
Alert Time
Description
----------------------------------------------------------Nov 11 18:54:51
Rear fan #1 failure: Current RPM is 0,
nominal is 8000
Nov 11 18:54:53
System rebooted
Nov 12 18:54:58
Rear fan #2 failure: Current RPM is 0,
nominal is 8000
-----------------------------------------------------------
Display the Email List
The alerts email list includes an address for Data Domain support. Addresses that you add to the list
appear as local or fully-qualified addresses exactly as you enter them.
Display
To display all email addresses in the alerts list, use the alerts show alerts-list operation
or click Autosupport in the left panel of the Data Domain Enterprise Manager and look at Mailing
Lists, Alert Email List.
alerts show alerts-list
# alerts show alerts-list
Alert email list
[email protected]
admin12
[email protected]
116
Alerts
Display Current Alerts and Recent History
To display the current alerts and the alerts history over the last 24 hours, use the alerts show
daily operation.
alerts show daily
# alerts show daily
Current Alert
------------Alert Time
Description
----------------------------------------------------------Nov 12 18:54
Rear fan #1 failure: Current RPM is 0, nominal
is 8000
----------------------------------------------------------There is 1 active alert.
Recent Alerts and Log Messages
-----------------------------Nov 5 20:56:43 localhost sysmon: EMS: Rear fan #2 failure:
Current RPM is 960, nominal is 8000
Display the Email List and Administrator Email
To display all email addresses in the alerts list and the system administrator email address, use the
alerts show all operation.
alerts show all
The display is similar to the following. The administrator address appears twice:
# alerts show all
Alerts email
[email protected]
[email protected]
admin12
[email protected]
117
Autosupport Reports
Autosupport Reports
The autosupport feature automatically generates reports detailing the state of the system.
The first section of an autosupport report gives system identification and uptime information. The
next sections display output from numerous restorer commands and entries from various log files.
At the end of the report, extensive and detailed internal statistics and information are included to
aid Data Domain in debugging system problems.
Add to the Email List
To add an email address to the autosupport report list, use the autosupport add operation. By
default, the list includes an address for Data Domain support staff. The email-list is a list of
addresses that are comma-separated or space-separated or both. After adding to the list, always use
the autosupport test operation to test the address. Administrative users only.
autosupport add email-list
For example, to add a an email address to the list:
# autosupport add [email protected]
Test the Autosupport Report Email List
To create an autosupport report and send it to all addresses in the email list or to a specific address,
use the autosupport send operation. After adding addresses to the list, always use this
operation to test the address.
autosupport test [email-addr]
For example, after adding the email address [email protected] to the list, the test for that
address would be:
# autosupport test [email protected]
Send an Autosupport Report
To send an autosupport report to all addresses in the email list or to a specific address, use the
autosupport send operation.
autosupport send [email-addr]
For example, to send an autosupport to [email protected]:
# autosupport send [email protected]
118
Autosupport Reports
Remove from the Email List
To remove an email address from the autosupport report list, use the autosupport del
operation. The operation is available only to administrative users. The email-list is a list of
addresses that are comma-separated or space-separated or both. Administrative users only.
autosupport del email-list
For example, to remove an email address from the list:
# autosupport del [email protected]
Reset the Email List
By default, the list includes an address for Data Domain support personnel. The autosupport
reset operation returns the list to the default address. The operation is available only to
administrative users.
autosupport reset support-list
Run the Autosupport Report
To manually run and immediately display the autosupport report, use the autosupport show
report operation. Use the up and down arrow keys to move through the display. Use the q key to
exit. Enter a slash character (/) and a pattern to search for and highlight lines of particular interest.
autosupport show report
The display is similar to the following. The first section gives system identification and uptime
information:
# autosupport show report
========== GENERAL INFO ==========
GENERATED_ON=Wed Sept 7 13:17:48 UTC 2005
VERSION=Data Domain OS 3.1.0.0-19019
SYSTEM_ID=Serial number: 22BM030026
MODEL_NO=DD560
HOSTNAME=dd10.yourcompany.com
LOCATION=Bldg12 room221 rack6
[email protected]
UPTIME= 1:17pm up 124 days, 14:31, 2 users,
0.00, 0.00, 0.00
load average:
The next sections display output from numerous restorer commands and entries from various log
files. At the end of the report, extensive and detailed internal statistics and information appear to
aid Data Domain in debugging system problems.
119
Autosupport Reports
Email Command Output
To send the display output from any restorer command to an email address, use the
autosupport send operation. Enclose the command that is to generate output in double
quotes. With a command and no address, the output is sent to the autosupport list.
autosupport send [email-addr] [cmd "command"]
For example, to email the log file messages.1 to Data Domain Support:
# autosupport send [email protected] cmd "log view
messages.1"
Set the Schedule
To change the date and time when a restorer automatically runs a verbose autosupport report, use
the set schedule operation. The default time is daily at 3 a.m. (daily 0300). The operation
is available only to administrative users.
•
A time is required. 2400 is not a valid time. An entry of 0000 is midnight at the beginning of
a day.
•
The never option turns off the report. Set a schedule using any of the other options to turn on
the report.
autosupport set schedule [daily | never day1[,day2,...]] time
For example, the following command runs the report automatically every Tuesday at 4 a.m.:
# autosupport set schedule tue 0400
The most recent invocation of the scheduling operation cancels the previous setting.
Reset the Schedule
To reset the autosupport report to run at the default time, use the autosupport reset
schedule operation. The default time is Sunday at 3 a.m. The operation is available only to
autosupport reset schedule
Reset the Schedule and the List
To reset the autosupport schedule and email list to defaults, use the autosupport reset
all operation. The operation is available only to administrative users.
autosupport reset all
120
Autosupport Reports
Display all Autosupport Parameters
To display all autosupport parameters, use the autosupport show all operation.
autosupport show all
The display is similar to the following. The default display includes only the Data Domain support
address and the system administrator address (as given in the initial system configuration). Any
additional addresses that you add to the list also appear.
# autosupport show all
The Autosupport email list is :
[email protected]
[email protected]
Autosupport is scheduled to run “Sun” at “0300”
Display the Autosupport Email List
The autosupport email list includes an address for Data Domain support. Addresses that you add to
the list appear as local or fully-qualified addresses exactly as you enter them.
Display
To display all email addresses in the alerts list, use the autosupport show support-list
operation or click Autosupport in the left panel of the Data Domain Enterprise Manager and look at
Mailing Lists, Autosupport Email List.
autosupport show support-list
The default display is similar to the following:
# autosupport show support-list
Autosupport Email List
[email protected]
[email protected]
Display the Autosupport Report Schedule
Display the date and time when the autosupport report runs with the autosupport
show schedule operation.
autosupport show schedule
# autosupport show schedule
Autosupport is scheduled to run “Sun” at “0300”
121
Hourly System Status
Display the Autosupport History
To display all autosupport messages, use the autosupport show history operation. Use
the J key to scroll down through the file, the K key to scroll up, and the Q key to exit. The operation
displays entries from all of the messages system logs, which hold messages for up to ten weeks.
autosupport show history
# autosupport show history
Nov 10 03:00:19 scheduled autosupport
Hourly System Status
The restorer automatically generates a brief system status message every hour. The message is sent
to the system log and to a serial console if one is attached. To see the hourly message, use the log
view command. The message reports system uptime, the amount of data stored, the number of
NFS operations, and the amount of disk space used for data storage (as a percentage).
For example:
# log view
Nov 12 13:00:00 localhost logger: at 1:00pm up 3 days, 3:42, 52324 NFS ops, 84763 GB data
col. (1%)
Nov 12 14:00:00 localhost logger: at 2:00pm up 3 days, 4:42, 59411 NFS ops, 84840 GB data
col. (1%)
Collect and Send Log Files
When troubleshooting problems, Data Domain Technical Support may ask for a support bundle,
which is a tar-gzipped selection of log files with a README file that includes identifying
autosupport headers. To create a support bundle in the Data Domain Enterprise Manager, click on
the Support link in the left panel, and then click on the here link under the title Generate a support
bundle. The browser opens a dialog window. Select the Save option and save the file on the local
system. You can then send the file to Data Domain Technical Support.
The new file immediately appears in the Data Domain Enterprise Manager Support bundles list.
Left click on the file name to bring up the dialog window if you want to open the zip file or save the
file to another location.
122
The support upload operations create bundles of log files (with a README file) and
automatically send the results to Data Domain Technical Support.
support upload {bundle | traces}
The bundle operation sends various restorer log files that are often needed by the Support staff.
The traces operation sends multiple perf.log (performance log) files.
123
124
File System Management
11
The filesys command allows you to display statistics, capacity, status, and utilization of the
restorer file system. The command also allows you to clear the statistics file and to start and stop
the file system processes. The clean operations of the filesys command reclaim physical
storage within the restorer file system.
Statistics and Basic Operations
The following operations manage file system statistics and status displays and start and stop file
system processes.
Start the Restorer File System Process
To start the restorer file system, allowing restorer operations to begin, use the filesys enable
filesys enable
Stop the Restorer File System Process
To stop the restorer file system, which stops restorer operations (including cleaning), use the
filesys disable operation. Administrative users only.
filesys disable
Stop and Start the Restorer File System
To disable and enable the restorer file system in one operation, use the filesys restart
command. Administrative users only.
filesys restart
125
Delete All Data in the File System
To delete all data in the restorer file system and re-initialize the file system, use the filesys
destroy operation. The operation also removes Replicator configuration settings. Deleted data is
not recoverable. The basic command takes about one minute. The and-zero option writes zeros
to all disks, which can take many hours. Administrative users only.
filesys destroy [and-zero]
The display includes a warning similar to the following:
# filesys destroy
The 'filesys destroy' command irrevocably destroys all data in
the '/backup' data collection, including all virtual tapes, and
creates a newly initialized (empty) file system.
The 'filesys destroy' operation will take about a minute.
File access is disabled during this process.
Are you sure? (yes|no|?) [no]:
Display File System Status
To display the state of the file system process, use the filesys status operation. The display
gives a basic status of enabled or disabled with more detailed information for each basic status.
filesys status
# filesys status
If the file system was shut down with a restorer command, such as filesys disable, the
display includes the command. For example:
# filesys status
The filesystem is disabled and shutdown. [filesys disable]
Display File System Uptime
To display the amount of time that has passed since the file system was last enabled, use the
filesys show uptime operation. The display is in days and hours and minutes.
filesys show uptime
# filesys show uptime
Filesys has been up 47 days, 23:28
126
Display File System Space Utilization
The display shows the amount of space available for and used by restorer file system components.
•
The /ddvar line gives a rough idea of the amount of space used by and available to the log and
core files. Remove old logs and core files to free space in this area.
•
The Pre-compression line shows the amount of virtual data stored on the restorer. Virtual data
is the amount of data sent to the restorer from backup servers. Do not expect the amount shown
in the Pre-compression line to be the same as the amount displayed with the filesys show
compression command, Original Bytes line, which includes system overhead.
•
The Data line shows the actual physical space used by and available for data storage. Warning
messages go to the system log and an email alert is generated when the Use% figure reaches
90%, 95%, and 100%. At 100%, the restorer accepts no more data from backup servers. You
must run a filesys clean operation to reclaim disk space.
If Use% is always high, use the filesys clean show-schedule command to see how
often the operation runs automatically, then use filesys clean schedule to run the
operation more often. Also consider reducing the data retention period or splitting off a portion
of the backup data to another restorer.
The Avail GB and Use% columns change when the Index line Use% column reaches 80% and
the index is expanded.
•
The If 100% cleaned line is an estimate of actual physical space used, and physical space
available for data storage if you run the filesys clean start operation multiple times
to clean 100% of the file system. The estimate is based on the most recent clean operation.
On a destination, no estimate appears.
•
The Meta-data line tracks space used for the internal file descriptions that the restorer creates
for all stored files. The amount of space used for the descriptions may not be enough to register
in the Meta-data line until several thousand files are stored, leaving the Meta-data value at
zero. Warning messages go to the system log and an email alert is generated when the Use%
figure reaches 90%, 95%, and 100%. At 100%, the restorer accepts no more data from backup
servers. From the backup server, you must expire or purge backup images to create free space
for meta data. Do not expect the amount shown in the Meta-data line to be the same as the
amount displayed with the filesys show compression command, Meta-data line,
which includes an estimate of data in the index.
•
The Index line tracks space used for internal restorer operations. When the Use% column
reaches approximately 80%, the space allocated for the index automatically increases by a set
amount and the Use% column adjusts to the new size. At the same time, the Data line Avail GB
and Use% columns also change to reflect the space taken for the index.
•
The Estimated compression factor line gives a rough idea of data compression efficiency. The
estimate is based on the most recent clean operation and changes if the compressibility of
data sent to the restorer changes. Note that the compression calculation includes the metadata
and index space as part of the total storage space.
Chapter 11: File System Management
127
The value may be different on a replication destination than on a replication source. Multiple
replications of a file do not send all of the file data to the destination every time, but do
increase the number of bytes of pre-compression data used in the compression calculation.
•
On the destination, internal handling of replicated meta-data and unwritten regions in files
causes the difference
•
The Estimate based on line displays the date for the most recent clean operation. The date is in
the format YYYY/MM/DD.
Display
To display the space available to and used by file system components, use the filesys show
space operation or click File System in the left panel of the Data Domain Enterprise Manager.
Values are in gigabytes to one decimal place.
filesys show space
# filesys show space
Resource
Size GB
Used GB
Avail GB
Use%
----------------------------------------/ddvar
29.5
0.2
29.3
1%
Pre-compression
56.9
Data
3982.0
44.5
3937.5
1%
If 100% cleaned*
3982.0
41.8
3940.2
1%
Meta-data
19.7
0.0
19.7
0%
Index
60.0
0.6
59.4
1%
----------------------------------------Estimated compression factor*: 1.3x = 56.9/(41.8+0.0+0.6)
* Estimate based on 2004/11/22 cleaning
Display Compression
To display the amount of compression for a single file, multiple files, or a file system, use the
filesys show compression command. Optionally, display compression for a given number
of hours or days. In general, the more often a backup is done for a particular file or file system, the
higher the compression. Note that the display on a busy system may not return for one to two hours.
Other factors may also influence the display. Call Data Domain Technical Support to analyze
displays that seem incorrect.
filesys show compression [path] [last {n hours | n days}]
128
•
In the display, the value for bytes/storage_used is the compression ratio after all compression
of data (global and then local) plus the overhead space needed for meta data. In the Original
bytes line, (which includes system overhead) do not expect the amount shown to be the same
as the amount displayed with the filesys show space command, Pre-compression line,
which does not include system overhead.
•
The Original Bytes value may be different on a replication destination than on a replication
source for the same files or file system. On the destination, internal handling of replicated
meta-data and unwritten regions in files lead to the difference.
•
The value for Meta-data includes an estimate for data that is in the restorer internal index and
is not updated when the amount of data on the restorer decreases after a file system clean
operation. Because of the index estimate, the amount shown is not the same as the amount
displayed with the filesys show space command, Meta-data line.
# filesys show compression /backup/usr
Total files: 6,018; bytes/storage_used: 10.7
Original Bytes:
6,599,567,913,746
Globally Compressed:
992,690,774,605
Locally Compressed:
608,225,239,283
Meta-data:
7,329,091,080
Using an asterisk (*) as a wild card to display compression for more than one file returns the same
information as above for each file, but in a single line for each file. The g_comp and l_comp in each
line is short for global and local compression. The display ends with a summary that has the same
format for total figures as with a file system. For example:
# filesys show compression /backup/*.tar
/backup/usr.tar: mtime: 1127172717, bytes: 3,930,583,040,
g_comp: 53,484,389, l_comp: 29,214,049, meta-data: 27,439,680,
bytes/storage_used: 69.4
/backup/var.tar: mtime: 1127142658, bytes: 2,733,137,920,
g_comp: 1,941,043,800, l_comp: 1,103,938,251, meta-data:
31,147,968, bytes/storage_used: 2.4
Total files: 2, bytes/storage_used: 5.6
Original Bytes:
6,663,720,960
Globally Compressed (g_comp):
1,994,528,189
Locally Compressed (l_comp):
1,133,152,300
Meta-data:
58,587,648
129
Clean Operations
Clean Operations
The filesys clean operation reclaims physical storage used by deleted objects in the Data
Domain file system. Use the clean operations of the filesys command to manually start a
clean operation, change the schedule that automatically runs the operation, or check the status of
the operation.
The default settings for clean operations are:
•
A run time of Tuesday at 6 a.m. (tue 0600).
•
34% of a DD560 or DD460 restorer’s total data capacity, about 65% of total capacity for a
DD430, and 100% for a DD410.
Note Any operation that shuts down the restorer file system, such as the filesys disable
command, or that shuts down the restorer, such as a system power-off or reboot, stops the
clean operation. The clean does not restart when the system and file system restart.
Either manually restart the clean or wait until the next scheduled start.
Note Cleaning 34% of the space available for data on a restorer that is not busy with other tasks
generally takes three to four hours when the cleaning throttle is set to 100. Different types of
data, a busy system, and throttle settings below 100 all can extend the time needed. During
cleaning, the speed of backup and restore operations may be affected.
The clean operation does not run on a destination restorer.
A full DD560 or DD460 restorer would need three clean operations to clean 100% of the file
system (about 34% for each operation). Depending on the type of data stored, such as when using
markers for specific backup software, the file system may never report 100% cleaned. The total
space cleaned may always be a few percentage points less than 100.
The operation has six phases:
130
•
Phase one makes a preliminary selection of data. Phase one on average takes 10 to 40 minutes.
•
Phase two goes through all of the files on the system and determines what should remain and
what should be removed. Phase two can take up to three hours.
•
Phase three writes any pending index-metadata to disk. Phase three on average takes two to
four minutes.
•
Phase four removes any duplicate data segments that may be left behind when a clean process
is interrupted. Phase four on average takes 15 to 45 minutes.
•
Phase five makes clean copies of all files that hold live data and creates new indexes. Phase
five on average take 40 to 60 minutes.
•
Phase six regenerates internal restorer data structures. Phase six on average takes about 90
minutes.
Clean Operations
Start Cleaning
To manually start the clean process, use the filesys clean start operation. The
operation uses the current setting for the scheduled automatic clean operation and cleans up to
34% of the total space available for data on a DD560 or DD460 system. If the system is less than
34% full, the operation cleans all data. Administrative users only.
filesys clean start
For example, the following command runs the clean operation and reminds you of the monitoring
command:
# filesys clean start
Cleaning started. Use ‘filesys clean watch’ to monitor
progress.
When the operation finishes, a message goes to the system log giving the amount of free space
available.
Stop Cleaning
To stop the clean process, use the clean stop operation. Stopping the process during the first
four phases means that all work done so far is lost. Starting the process again means starting over at
the beginning. If the clean process is slowing down the rest of the system, consider using the
filesys clean set throttle operation to reset the amount of system resources used by
the clean process. The change in the use of system resources takes place immediately.
filesys clean stop
Change the Schedule
To change the date and time when clean runs automatically, use the clean set schedule
operation. The default time is Tuesday at 6 a.m. (tue 0600). The operation is available only to
•
Daily runs the operation every day at the given time.
•
Monthly starts on a given day or days (from 1 to 31) at the given time.
•
Never turns off the clean process and does not take a qualifier.
•
With the day-name qualifier, the operation runs on the given day(s) at the given time. A
day-name is three letters (such as mon for Monday). Use a dash (-) between days for a range of
days. For example: tue-fri.
•
Time is 24-hour military time. 2400 is not a valid time. mon 0000 is midnight between
Sunday night and Monday morning.
131
Clean Operations
•
The most recent invocation of the scheduling operation cancels the previous setting.
filesys clean set schedule daily time
filesys clean set schedule monthly day-numeric-1
[,day-numeric-2,...]time
filesys clean set schedule never
filesys clean set schedule day-name-1[,day-name-2,...]time
For example, the following command runs the operation automatically every Tuesday at 4 p.m.:
# filesys clean set schedule tue 1600
To run the operation more than once in a month, set multiple days in one command. For example, to
run the operation on the first and fifteenth of the month at 4 p.m.:
# filesys clean set schedule monthly 1,15 1600
Set the Schedule or Throttle to the Default
To set the clean schedule to the default of Tuesday at 6 a.m. (tue 0600), the default throttle of
50%, or both, use the filesys clean reset operation. The operation is available only to
filesys clean reset {schedule | throttle | all}
Set Network Bandwidth Used
To set clean operations to use a lower level of system resources when the restorer is busy, use the
filesys set throttle operation. At a percentage of 0 (zero), cleaning runs very slowly or
not at all when the system is busy. A percentage of 100 allows cleaning to use system resources in
the usual way. The default is 50. When the restorer is not busy with backup or restore operations,
cleaning always runs at 100% (uses resources as would any other process). Administrative users
only.
filesys clean set throttle percent
For example, to set the clean operation to run at 30% of its possible speed:
# filesys clean set throttle 30
132
Clean Operations
Update Statistics
To update the If 100% cleaned numbers that show in the output from filesys show space,
use the filesys clean update-stats operation. With a full file system, the update
operation can take up to 12 hours. Administrative users only.
filesys clean update-stats
Display All Clean Parameters
To display all of the settings for the clean operation, use the filesys clean show config
operation.
filesys clean show config
The display is similar to the following.:
# filesys clean show config
50 Percent Throttle
Filesystem cleaning is scheduled to run "Tue" at "0600".
Display the Schedule
To display the current date and time for the clean operation, use the filesys clean show
schedule operation.
filesys clean show schedule
# filesys clean show schedule
Filesystem cleaning is scheduled to run “Tue” at “0600”
Display the Throttle Setting
To display the throttle setting for cleaning operations, use the filesys clean show
throttle operation.
filesys clean show throttle
# filesys clean show throttle
100 Percent Throttle
133
Compression Options
Display the Clean Operation Status
To display the active/inactive status of the clean operation, use the filesys clean status
operation. When the clean operation is running, the command displays progress.
filesys clean status
# filesys clean status
cleaning progress:
phase 5 of 6, 64.6% complete, 2496 GB available
total time elapsed 8:53:21, remaining 4:15:45
Monitor the Clean Operation
To monitor an ongoing clean operation, use the filesys clean watch operation. The
output is the same as output from the filesys clean status command, but continuously
updates. Enter a <CTRL> C to stop monitoring the progress of a clean operation. The operation
continues, but the reporting stops. Use the filesys clean start command to restart
monitoring.
filesys clean watch
Compression Options
A restorer compresses data at two levels: global and local. Global compression compares received
data to data already stored on disks. Data that is new is then locally compressed before being
written to disk. Command options allow changes at both compression levels.
Local Compression
A restorer uses a local compression algorithm developed specifically to maximize throughput as
data is written to disk. The default algorithm allows shorter backup windows for backup jobs, but
uses more space. Local compression options allow you to choose slower performance that uses less
space, or you can set the system for no local compression.
134
•
Changing the algorithm affects only new data and data that is accessed as part of the filesys
clean process. Current data remains as is until a clean operation checks the data.
•
To enable the new setting, use the filesys disable and filesys enable commands.
Compression Options
Set Local Compression
To set the compression algorithm, use the filesys option set local-compressiontype operation. The setting is for all data received by the system.
filesys option set local-compression-type {none | lz | gzfast |
gz}
•
lz The default algorithm that gives the best throughput. Data Domain recommends the lz
option.
•
gzfast A zip-style compression that uses less space for compressed data, but more CPU
cycles. Gzfast is the recommended alternative for sites that want more comrpession at the
cost of lower performance.
•
gz A zip-style compression that uses the least amount of space for data storage (10% to 20%
less than lz), but also uses the most CPU cycles (up to twice as many as lz).
•
none Do no data compession.
Reset Local Compression
To reset the compression algorithm to the default of lz, use the filesys option reset
local-compression-type operation.
filesys option reset local-compression-type
Display the Algorithm
To display the current algorithm, use the filesys option show local-compressiontype operation.
filesys option show local-compression-type
Global Compression
DD OS 4.0 and later releases use a global compression algorithm called type 9 as the default.
Earlier releases use an algorithm called type 1 (one) as the default.
•
A restorer using type 1 global compression continues to use type 1 when upgraded to a new
release. A restorer using type 9 global compression continues to use type 9 when upgraded to a
new release.
•
A DD OS 4.0.3.0 or later restorer can be changed from one type to another if the file system is
less than 40% full.
•
Directory replication pairs must use the same global compression type.
135
Replicator Destination Read/Write Option
Set Global Compression
To change the global compression setting, use the filesys option set globalcompression-type command.
filesys option set global-compression-type {1 | 9}
To change the setting (to type 1, for example) and activate the change, use the following
commands:
# filesys option set global-compression-type 1
# filesys disable
# filesys enable
Reset Global Compression
To remove a manually set gobal compression type, use the filesys option reset
global-compression-type command. The file system continues to use the current type.
Only when a filesys destroy command is entered does the type used change to the default of
type 9.
filesys option reset global-compression-type
Display the Type
To display the current global compression type, use the filesys option show
global-compression-type command.
filesys option show global-compression-type
Replicator Destination Read/Write Option
The read/write setting of the file system on a Replicator destination restorer is read-only. With
some backup software, the file system must be reported as writable for restoring or vaulting data
from the destination restorer. The commands in this section change and display the reported setting
of the destination file system. The actual state of the file system remains as read-only.
136
•
Before changing the reported setting, use the filesys disable command. After changing
the setting, use the filesys enable command.
•
When using CIFS on the restorer, use the cifs disable command before changing the
reported state and use the cifs enable command after changing the reported state.
Tape Marker Handling
Report as Read/Write
Use the filesys option enable report-replica-as-writable command on the
destination restorer to report the file system as writable.
filesys option enable report-replica-as-writable
Report as Read-Only
Use the filesys option disable report-replica-as-writable command on the
destination restorer to report the file system as read-only.
filesys option disable report-replica-as-writable
Return to the Default Setting
Use the filesys option reset report-replica-as-writable command on the
destination restorer to reset reporting to the default of the file system as read-only.
filesys option reset report-replica-as-writable
Display the Setting
Use the filesys option show report-replica-as-writable command on the
destination restorer to display the current reported setting.
filesys option show report-replica-as-writable
Backup software from some vendors inserts markers (tape markers, tag headers, or other names are
used) in all data streams (both file system and VTL backups) sent to a restorer. Markers can
significantly degrade data compression on a restorer. The filesys option ...
marker-type commands allow a restorer to handle specific marker types while maintaining
compression at expected levels.
137
Set a Marker Type
Use the filesys option set marker-type command to have a restorer deal with markers
inserted into backup data by some backup software.
•
The setting is system-wide and applies to all data received by a restorer.
•
If a restorer is set for a marker type and data is received that has no markers, compression and
system performance are not affected.
•
If a restorer is set for a marker type and data is received with markers of a different type,
compression is degraded for the data with different markers.
filesys option set marker-type {nw1 | cv1 | tsm1 | none}
The options are:
•
nw1 for Legato NetWorker
•
cv1 for CommVault Galaxy
•
tsm1 for IBM Tivoli Storage Manager
•
none for data with no markers (none is also the default setting)
After changing the setting, enter the following two commands to enable the new setting:
# filesys disable
# filesys enable
Reset to the Default
Use the filesys option reset marker-type command to return the marker setting to
the default of none.
filesys option reset marker-type
Display the Marker Setting
Use the filesys option show marker-type command to display the current marker
setting.
filesys option show marker-type
138
Disk Management
12
The restorer disk command manages disks and displays disk locations, logical (RAID) layout,
usage, and reliability statistics. Command output examples in this chapter show systems with 15
disk drives. Each restorer model reports on the number of disks actually in the system. With a
DD560 that has one or more Data Domain external disk shelves, commands also include entries for
all enclosures, disks, and RAID groups. See the Data Domain publication ES20 Expansion Shelf
User Guide for details about disks in external shelves.
Each disk in a restorer has two LEDs at the bottom of the disk carrier. The LED on the right is
green. The LED glows steadily when the disk has power and is functioning normally and flashes
when the disk is accessed or when the disk is the target of a beacon operation. The LED on the left
is red and glows steadily when the disk has failed.
Each disk in an external shelf has two LEDs at the right edge of the disk carrier. The top LED is
green and flashes when the disk is accessed or when the disk is the target of a beacon operation.
The bottom LED is amber and glows steadily when the disk has failed.
The disk-identifying variable used in disk commands (except gateway-specific commands) is in
the format enclosure-id.disk-id. An enclosure is a restorer or an external disk shelf. A
restorer is always enclosure 1 (one). For example, disk 12 in a restorer is 1.12. Disk 12 in the first
external shelf is 2.12.
On gateway restorers (that use outside disk arrays other than Data Domain external disk shelves),
the following command options are not valid:
disk
disk
disk
disk
disk
beacon
fail
unfail
show failure-history
show reliability-data
With gateway storage, output from all other disk commands returns information about the LUNs
and volumes accessed by the restorer.
139
Add a LUN
Add a LUN
For gateway systems only. Add a new LUN to the current volume. To get the disk-ID, use the disk
rescan command and then use the disk show raid-info command. The disk-ID format is
the word disk and the number as seen in output from the disk show raid-info command.
For example: disk2. See “Procedure: Adding a LUN” on page 67 for details.
disk add disk-ID
Fail a Disk
To set a disk to the failed state, use the disk fail enclosure-id.disk-id operation. The
command asks for a confirmation before carrying out the operation. Available to administrative
users only.
disk fail enclosure-id.disk-id
A failed disk is automatically removed from a RAID disk group and is replaced by a spare disk
(when the spare is available). The disk use changes from spare to in use and the status becomes
reconstructing. See “Display RAID Status for Disks” on page 143 to list the available spares.
Note A restorer can run with a maximum of two failed disks. Always replace a failed disk as soon
as possible. Spare disks are supplied in a carrier for a restorer or a carrier for an expansion
shelf. DO NOT move a disk from one carrier to another.
Unfail a Disk
To change a disk status from failed to available, use the disk unfail
enclosure-id.disk-id command. Use the command when replacing a failed disk. The new
disk in the “failed” slot is seen as failed until the disk is unfailed.
disk unfail enclosure-id.disk-id
Check All Disks
To check that the Data Domain OS and hardware recognize all disks, use the disk beacon all
operation. The operation causes the green LED (that signals normal operation) on all disks to flash
green. Use the (Control) c key sequence to turn off the operation. Administrative users only.
disk beacon all
140
To check for new disks or LUNs with gateway systems or when adding an expansion shelf, use the
disk rescan operation. Administrative users only.
disk rescan
Identify a Physical Disk
The disk beacon enclosure-id.disk-id operation causes the green LED (that signals
normal operation) on the target disk to flash. Use the (Control) c key sequence to turn off the
disk beacon enclosure-id.disk-id
For example, to flash the LED for disk3 in a restorer:
# disk beacon 1.3
Add an Expansion Shelf
To add a Data Domain expansion shelf disk storage unit, use the disk add enclosure
command. The enclosure-id is always 2 for the first added shelf and 3 for the second. The restorer
always has the enclosure-id of 1 (one).
Reset Disk Performance Statistics
To reset disk performance statistics to zero, use the disk reset performance operation. See
“Display Disk Performance Details” on page 146 for displaying disk statistics.
disk reset performance
Display Disk Status
The disk status operation displays the number of disks in use and failed, the number of spare
disks available, and whether a RAID disk group reconstruction is underway. Note that the RAID
portion of the display could show one or more disks as failed while the Operational portion of the
display could show all drives as “operating nominally.” A disk can be physically functional and
available, but not currently in use by RAID, possibly because of operator intervention.
disk status
Chapter 12: Disk Management
141
Display Disk Type and Capacity Information
On a gateway restorer, the display shows only the number and state of the LUNs accessed by the
restorer. The remainder of the display is not valid for a gateway system.
The display for a restorer with two expansion shelves is similar to the following. Note that the disks
in a new expansion shelf recognized with the disk rescan command show a status of unknown.
Use the disk add enclosure command to change the status to in use.
# disk status
Configuration:
RAID:
RAID:
RAID:
RAID:
RAID:
RAID:
RAID:
RAID:
RAID:
Operational:
Performance:
47 drives present.
5 drives are "spare"
0 drives are "absent"
0 drives are "foreign"
0 drives are "unknown"
47 drives operating normally..
Cumulative 114.954 MB/s, 7 % busy
Display Disk Type and Capacity Information
The display of disk information for a restorer has the columns:
•
Disk (Enc.Slot) is the enclosure and disk numbers.
•
Manufacturer/Model shows the manufacturer’s model designation.
•
Firmware is the firmware revision on each disk.
•
Serial No. is the manufacturer’s serial number for the disk.
•
Capacity is the data storage capacity of the disk when used in a restorer. The Data Domain
convention for computing disk space defines one gigabyte as 230 bytes, giving a different disk
capacity than the manufacturer’s rating.
The display for a gateway restorer has the columns:
142
•
Disk displays each LUN accessed by the restorer as a disk.
•
LUN is the LUN number given to a LUN on the outside storage system.
•
Port WWN is the world-wide number of the port on the storage array through which data is sent
to the restorer.
•
Manufacturer/Model includes a label that identifies the manufacturer. The display may include
a model ID or RAID type or other information depending on the vendor string sent by the
storage array.
Display RAID Status for Disks
•
Firmware is the firmware level used by the outside storage controller.
•
Serial No. is the serial number from the outside storage system for a volume that is sent to the
restorer.
•
Capacity is the amount of data in a volume sent to the restorer.
Display
Use the disk show hardware operation or click Disks in the left panel of the Data Domain
Enterprise Manager to display disk information.
disk show hardware
The display for disks in a restorer is similar to the following:
# disk show hardware
Disk
Manufacturer/Model
(Enc.Slot)
--------- -----------------1.1
HDS724040KLSA80
1.2
HDS724040KLSA80
1.3
HDS724040KLSA80
1.4
HDS724040KLSA80
1.5
HDS724040KLSA80
1.6
HDS724040KLSA80
1.7
HDS724040KLSA80
1.8
HDS724040KLSA80
1.9
HDS724040KLSA80
1.10
HDS724040KLSA80
1.11
HDS724040KLSA80
1.12
HDS724040KLSA80
1.13
HDS724040KLSA80
1.14
HDS724040KLSA80
1.15
HDS724040KLSA80
--------- -----------------15 drives present.
Firmware Serial No.
Capacity
-------KFAOA32A
KFAOA32A
KFAOA32A
KFAOA32A
KFAOA32A
KFAOA32A
KFAOA32A
KFAOA32A
KFAOA32A
KFAOA32A
KFAOA32A
KFAOA32A
KFAOA32A
KFAOA32A
KFAOA32A
--------
--------372.61 GB
372.61 GB
372.61 GB
372.61 GB
372.61 GB
372.61 GB
372.61 GB
372.61 GB
372.61 GB
372.61 GB
372.61 GB
372.61 GB
372.61 GB
372.61 GB
372.61 GB
---------
-------------KRFS06RAG9VYGC
KRFS06RAG9TYYC
KRFS06RAG99EVC
KRFS06RAGA002C
KRFS06RAG9SGMC
KRFS06RAG9VX7C
KRFS06RAG9SEKC
KRFS06RAG9U27C
KRFS06RAG9SHXC
KRFS06RAG9SJWC
KRFS06RAG9SHRC
KRFS06RAG9SK2C
KRFS06RAG9WYVC
KRFS06RAG9SJDC
KRFS06RAG9SKBC
--------------
Display RAID Status for Disks
To display the RAID status and use of disks, which disks have failed from a RAID point of view,
spare disks available for RAID, and the progress of a disk group reconstruction operation, use the
disk show raid-info operation.
disk show raid-info
143
Display the History of Disk Failures
When a spare disk is available, the restorer file system automatically replaces a failed disk with a
spare and begins the reconstruction process to integrate the spare into the RAID disk group. The
disk use changes from spare to in use and the status becomes reconstructing. In the sample display
below, disk 8 is a spare disk.
The display for a gateway restorer shows only as many Disk and drives are “in use” entries as
LUNs accessed by the restorer. All other lines in the drives section of the display are always zero
for gateway displays.
The display for disks in a restorer is similar to the following:
Disk
State
Additional Status
(Enc.Slot)
---------- ------------- --------------------------1.1
in use (dg0)
1.2
in use (dg0)
1.3
in use (dg0)
1.4
in use (dg0)
1.5
in use (dg0)
1.6
in use (dg0)
1.7
in use (dg0)
1.8
spare
1.9
in use (dg0)
1.10
in use (dg0)
1.11
in use (dg0)
1.12
in use (dg0)
1.13
in use (dg0)
1.14
in use (dg0)
1.15
in use (dg0)
------------------ --------------------------14 drives are “in use”
1 drive is “spare(s)”
0 drives are undergoing “reconstruction”
0 drives are “not in use”
0 drives are “missing/absent”
Display the History of Disk Failures
The disk show failure-history operation displays a list of serial numbers for all disks
that have ever been failed in the restorer. Use the disk show hardware command to display
the serial numbers of current disks. Administrative users only.
disk show failure-history
144
Display Detailed RAID Information
Display Detailed RAID Information
To display RAID disk groups and the status of disks within each group, use the disk show
detailed-raid-info operation.
disk show detailed-raid-info
The Slot column in the Disk Group section shows the logical slot for each disk in a RAID subgroup.
In the example below, the RAID group name is ext3 with subgroups of ext3_1 through ext3_4 (only
subgroups ext_1 and ext_2 are shown). The number of Gigabytes allocated for the RAID group and
for each subgroup is shown just after the group or subgroup name. The Raid Group section shows
the logical slot and actual disks for the whole group.
On a gateway restorer, the display does not include information about individual disks.
# disk show detailed-raid-info
Disk Group (dg0) - Status: normal
Raid Group (ext3):(raid-0)(61.6 GB) - Status: normal
Raid Group (ext3_1):(raid-6)(15.26 GB) - Status: normal
Slot
Disk
State
Additional Status
-----------------------------------0
1.10
in use (dg0)
1
1.11
in use (dg0)
2
1.12
in use (dg0)
-----------------------------------Raid Group (ext3_2):(raid-6)(15.26 GB) - Status: normal
Slot
Disk
State
Additional Status
-----------------------------------0
1.13
in use (dg0)
1
1.14
in use (dg0)
2
1.15
in use (dg0)
-----------------------------------Raid Group (ppart):(raid-6)(2.47 TB) - Status: normal
Slot
Disk
State
Additional Status
---------------------------------0
1.16
in use (dg0)
1
1.11
in use (dg0)
2
1.12
in use (dg0)
3
1.13
in use (dg0)
4
1.14
in use (dg0)
5
1.15
in use (dg0)
6
1.6
in use (dg0)
7
1.9
in use (dg0)
8
1.10
in use (dg0)
9
1.1
in use (dg0)
10
1.2
in use (dg0)
145
Display Disk Performance Details
11
1.3
in use (dg0)
12
1.4
in use (dg0)
13
1.5
in use (dg0)
14
1.7
in use (dg0)
--------- -----------Spare Disks
Disk
State
(Enc.Slot)
-----------------1.8
spare
-----------------Unused Disks
None
-----------------
Display Disk Performance Details
The display of disk performance shows statistics for each disk. Each column displays statistics
averaged over time since the last disk reset performance command. See “Reset Disk
Performance Statistics” on page 141 for reset details.
Command output from a gateway restorer lists each LUN accessed by the restorer as a disk.
Disk (Enc.Slot) is the enclosure and disk numbers.
Read sects/s is the average number of sectors per second read from each disk.
Write sect/s is the average number of sectors per second written to each disk.
Cumul. MBytes/s is the average number of megabytes per second written to each disk.
Busy is the average percent of time that each disk has at least one command queued.
Display
Use the disk show performance operation or click Disks in the left panel of the Data
Domain Enterprise Manager to see disk performance statistics.
disk show performance
# disk show
Disk
(Enc.Slot)
---------1.1
1.2
1.3
146
performance
Read
Write
sects/s sects/s
-------- -------378
426
0
0
346
432
Cumul.
MBytes/s
-------0.392
0.000
0.379
Busy
-----11 %
0 %
10 %
Display Disk Reliability Details
1.4
0
0
1.5
410
439
1.6
397
427
1.7
360
439
1.8
(spare) (spare)
1.9
358
430
1.10
390
429
1.11
412
430
1.12
379
429
1.13
392
426
1.14
373
427
1.15
424
432
---------------- -------Cumulative 5.583 MB/s, 11 % busy
0.000
0.414
0.402
0.389
(spare)
0.384
0.399
0.411
0.394
0.399
0.390
0.417
--------
0 %
11 %
11 %
11 %
(spare)
10 %
11 %
11 %
11 %
11 %
12 %
12 %
------
Disk reliability information details the hardware state of each disk. The information is generally for
the use of Data Domain support staff when troubleshooting.
Disk is the enclosure.disk-id disk identifier.
The ATA Bus CRC Err column shows uncorrected raw UDMA CRC errors.
Reallocated Sectors indicates the end of the useful disk lifetime when the number of reallocated
sectors approaches the vendor-specific limit. The limit is 2000 for Western digital disks and 2000
for Hitachi disks. Use the disk show hardware command to display the disk vendor.
Temperature shows the current temperature of each disk in Celsius and Fahrenheit. The allowable
temperature range for disks is from 5 degrees centigrade to 45 degrees centigrade.
Display
Use the disk show reliability data operation or click Disks in the left panel of the Data
Domain Enterprise Manager to see the reliability statistics.
disk show reliability-data
# disk show reliability-data
Disk
ATA Bus
Reallocated
(Encl.Slot)
CRC Err
---------- -------- ------1.1
0
0
1.2
0
0
1.3
0
0
Temperature
Sectors
----------33 C
91 F
33 C
91 F
32 C
90 F
147
1.4
0
0
33 C
91 F
1.5
0
0
34 C
93 F
1.6
0
0
34 C
93 F
1.7
0
0
33 C
91 F
1.8
0
0
33 C
91 F
1.9
0
0
34 C
93 F
1.10
0
0
34 C
93 F
1.11
0
0
35 C
95 F
1.12
0
0
33 C
91 F
1.13
0
0
34 C
93 F
1.14
0
0
34 C
93 F
1.15
0
0
56 C 133 F
---------- -------- ----------------14 drives operating normally.
1 drive reporting excessive temperatures.
148
System Maintenance
13
The restorer system, ntp, and alias commands allow you to take system-level actions.
Examples for the system command are shutting down or restarting the restorer, displaying system
problems and status, and setting the system date and time.
The alias command allows users to set up aliases for restorer commands.
The ntp command manages access to one or more time servers.
The support command sends multiple log files to the Data Domain Support organization.
Support staff may ask you to use the command when dealing with unusual situations. See “Collect
and Send Log Files” on page 122 for details.
The system Command
The system command manages system-level actions on the restorer.
Shut down the Restorer Hardware
To shut down power to the restorer, use the system poweroff operation. The operation
automatically does an orderly shut down of file system processes; however, always close the
Enterprise Manager graphical user interface before a poweroff operation to avoid a series of
harmless warning messages when rebooting. The operation is available to administrative users
only.
system poweroff
# system poweroff
The ‘system poweroff’ command shuts down the system and turns
off the power.
Continue? (yes|no|?) [no]:
149
The system Command
Reboot the Restorer
To shutdown and reboot a restorer, use the system reboot operation. The operation
automatically does an orderly shutdown of the file system process; however, always close the
Enterprise Manager graphical user interface before a reboot operation to avoid a series of harmless
warning messages when the system reboots. Administrative users only.
system reboot
# system reboot
The ‘system reboot’ command reboots the system. File access is
interrupted during the reboot.
Are you sure? (yes|no|?) [no]:
Upgrade the Restorer Software
You can upgrade restorer software either from the Data Domain Support web site or with FTP.
Upgrade points of interest:
•
The upgrade operation shuts down the restorer file system and reboots the restorer.
•
The upgrade operation may take over an hour, depending on the amount of data on the system.
•
After the upgrade completes and the system reboots, the /backup file system is disabled for
up to an hour for upgrade processing.
•
Stop any active CIFS client connections before starting an upgrade. Use the cifs show
active command on the restorer to check for CIFS activity. Disconnect any client that is
active. On the client, enter the command net use \\dd\backup /delete.
•
For systems that are already part of a replication pair:
•
150
-
Both sides of the pair must be upgraded to the same software release.
-
Do NOT disable replication on either system in the pair.
-
Upgrade the destination first.
-
Upgrade the originator after upgrading the destination.
Data Domain supports the following upgrades:
-
For 3.0.x releases, upgrade to version 3.1.2.4. The upgrade includes changes to the index
used by the file system. The upgrade can take a number of hours, depending on the
amount of data on the system. Do not halt the upgrade after the process starts.
-
From 3.1.x releases, upgrade to version 3.2.2.6.
-
From 3.2.x releases, upgrade to version 3.3.2.3 or a 3.3.3.x release.
The system Command
-
From version 3.3.2.3 (and versions of 3.3.3.x) to version 4.0.2 and above, see the 4.0.x
Release Notes for instructions that are unique to the upgrade.
Note Before starting an upgrade, always read the Release Notes for the new release. DD OS
changes in a release may require unusual, one-time operations to perform an upgrade.
To upgrade using HTTP
1. Log in to a restorer administrative host that mounts /ddvar from the restorer.
2. On the administrative host, open a browser and go to the Data Domain Support web site. Use
HTTP to connect to the web site. For example:
http://support.datadomain.com
3. Log in with the Data Domain login name and password that you use for access to the support
web page.
Note Some web browsers do not automatically ask for a login if a machine does not accept all
logins. In that case, add your user name and password. For example:
http://your-name:[email protected]
4. Click on Downloads. (If the web site has updated instructions, follow those instructions.)
5. Click on the Download button for the latest release.
6. Download the new release file to the restorer directory /ddvar/releases.
Note When using Internet Explorer to download a software upgrade image, the browser may add
bracket and numeric characters to the upgrade image name. Remove the added characters
before running the system upgrade command.
7. To start the upgrade, log in to the restorer as sysadmin and enter a command similar to the
following. Use the file name (not a path) received from Data Domain. (Always close the
Enterprise Manager graphical user interface before an upgrade operation to avoid a series of
harmless warning messages when rebooting.) For example:
# system upgrade 4.0.2.0-30094.rpm
Chapter 13: System Maintenance
151
The system Command
To upgrade using FTP
1. Log in to a restorer administrative host that mounts /ddvar from the restorer.
2. On the administrative host, use FTP to connect to the Data Domain support site. For example:
# ftp://support.datadomain.com/
3. Log in with the Data Domain login name and password that you use for access to the support
web page.
4. Download the release recommended by your Data Domain field representative. The file should
go to /ddvar/releases on the restorer.
Note When using Internet Explorer to download a software upgrade image, the browser may add
bracket and numeric characters to the upgrade image name. Remove the added characters
before running the system upgrade command.
5. To start the upgrade, log in to restorer as sysadmin and enter a command similar to the
following. Use the file name (not a path) received from Data Domain. (Always close the
Enterprise Manager graphical user interface before an upgrade operation to avoid a series of
harmless warning messages when rebooting.) For example:
# system upgrade 4.0.2.0-30094.rpm
Set the Date and Time
To set the system date and time, use the system set date operation. The entry is two places
for month (01 through 12), two places for day of the month (01 through 31), two places for hour (00
through 23), two places for minutes (00 through 59), and optionally, two places for century and two
places for year. The hour (hh) and minute (mm) entries are 24-hour military time with no colon
between hours and minutes. 2400 is not a valid entry. An entry of 0000 is midnight at the beginning
of a day. The operation is available to administrative users only.
system set date MMDDhhmm[[cc]yy]
For example, use either of the following commands to set the date and time to October 22 at 9:24
a.m. in the year 2004:
# system set date 1022092404
# system set date 102209242004
152
The system Command
Create a Login Banner
To create a message that appears whenever someone logs in, mount the restorer directory /ddvar
from another system. Create a text file with your login message as the text. To have the banner
appear, use the system option set login-banner command with the path and file name
of the file that you created:
system option set login-banner file
For example, to use the text from a file named banner:
# system option set login-banner /ddvar/banner
Reset the Login Banner
To reset the login banner to the default of no banner, use the system option reset
login-banner command:
system option reset login-banner
Display the Login Banner Location
To display the location of the file that contains the login banner text, use the system option
show command:
system option show
The command output shows the path and file name:
# system option show
Option
Value
----------------------------Login Banner File
/ddvar/banner
-----------------------------
Display the Restorer Serial Number
To display the system serial number, use the system show serialno operation.
system show serialno
# system show serialno
Serial number: 22BM030026
153
The system Command
Display System Uptime
To display the time that has passed since the last reboot and the file system uptime, use the
system show uptime operation.
system show uptime
The system display includes the current time, time since the last reboot (in days and hours), the
current number of users, and the average load for file system operations, disk operations, and the
idle time. The Filesystem line displays the time that has passed since the file system was last
started.
For example:
# system show uptime
12:57pm up 9 days, 18:55, 3 users, load average: 0.51, 0.42,
0.47
Filesystem has been up 9 days, 16:26
Display System Statistics
To display system statistics for CPUs, disks, Ethernet ports, and NFS, use the system show
stats operation. The time period covered is from the last reboot, except with interval and
count.
An interval, in seconds, runs the command every number of seconds (nsecs) for the number
of times in count. The first report covers the time period since the last reboot. Each subsequent
report is for activity in the last interval. The default interval is five seconds.
The interval and count labels are optional when giving both an interval and a count. To give
only an interval, you can enter a number for nsecs without the interval label. To give only a
count, you must enter the count label and a number for count.
The start and stop options return averages per second of statistics over the time between the
commands.
system show stats [start | stop | ([interval nsecs] [count
count])]
# system show stats
09/30/ 16:23:10
CPU
FS
FS
busy ops/s
proc
---- -------9%
624
0 %
154
Net kB/s
in
out
---- ---0
0
Disk kB/s
read write
----- ----40834 37245
Disk
busy
----10%
The system Command
NVRAM
kB/s
----0
Repl
kB/s
---0
Display Detailed System Statistics
The detailed system statistics cover the time period since the last reboot. The columns in the
display are:
CPUx busy The percentage of time that each CPU is busy.
State 'CDVMS' A single character shows whether any of the five following events is occurring.
Each event can affect performance.
C cleaning
D disk reconstruction (repair of a failed disk), or RAID is resyncing (after an improper
system shutdown and a restart), or RAID is degraded (a disk is missing and no
reconstruction is in progress)
V verify data (a background process that checks for data consistency)
M merging of the internal fingerprint index
S summary vector internal checkpoint process
NFS ops/s The number of NFS operations per second.
NFS proc The fraction of time that the file server is busy servicing requests.
NFS rcv The proportion of NFS-busy time spent waiting for data on the NFS socket.
NFS snd The proportion of NFS-busy time spent sending data out on the socket.
NFS idle The percentage of NFS idle time.
CIFS ops/s The number of CIFS (Common Internet File System) operations per second.
ethx kB/s The amount of data in kilobytes per second passing through each Ethernet
connection. One column appears for each Ethernet connection.
Disk kB/s The amount of data in kilobytes per second going to and from all disks in the
restorer.
Disk busy The percentage of time that all disks in the restorer are busy.
NVRAM kB/s The amount of data in kilobytes per second that are read from and written to the
NVRAM card.
Repl kB/s The amount of data in kilobytes per second being replicated between one restorer
and another. For directory replication, the value is the sum total of all in and out traffic for all
replication contexts.
155
The system Command
Display
To display detailed system statistics, use the system show detailed-stats operation or
click System Stats in the left panel of the Data Domain Enterprise Manager. The time period
covered is from the last reboot, except when using interval and count.
An interval, in seconds, runs the command every number of seconds (nsecs) for the number
of times in count. The first report covers the time period since the last reboot. Each subsequent
report is for activity in the last interval. The default interval is five seconds.
The interval and count labels are optional when giving both an interval and a count. To give
only an interval, you can enter a number for nsecs without the interval label. To give only a
count, you must enter the count label and a number for count.
The start and stop options return averages per second of statistics over the time between the
commands.
system show detailed-stats [start | stop | ([interval
int][count count])]
# system show detailed-stats
CPU0
busy
---0 %
CPU1 State
busy ‘CDVMS’
---- -----0 %
eth0 kB/s
in
out
------0
0
Disk
busy
---0
156
NFS
ops/s
----624
eth1 kB/s
in
out
----- ----0
0
NVRAM kB/s
read
write
-------0
0
NFS
proc
---0%
NFS
recv
---0%
eth2 kB/s
in
out
----- ----0
0
NFS
send
---0
NFS
idle
---0
eth3 kB/s
in
out
----- ----0
0
CIFS
ops/s
----------Disk kB/s
read
write
----- ----0
0
Repl kB/s
in
out
------0
0
The system Command
Display System Statistics Graphically
The graphical display of system statistics is taken from the partial output of multiple commands in
the command line interface. Six continuously updated graphs form the display. Each graph is
labeled in the lower left corner.
CPU The percentage of time that each CPU is busy.
Network The amount of data in kilobytes per second passing
through each Ethernet connection. One line appears for each
Ethernet connection.
NFS
recv % The proportion of NFS-busy time spent waiting for data on the NFS socket.
proc % The fraction of time that the file server is busy servicing requests.
send % The proportion of NFS-busy time spent sending data out on the socket.
Disk The amount of data in kilobytes per second going to and
from all disks in the restorer.
Replication Displays only if the Replicator feature is
licensed.
KB/s in The total number of kilobytes received by this side from the other side of the
Replicator pair. For the destination, the value includes backup data, replication overhead,
and network overhead. For the source, the value includes replication overhead and
network overhead.
KB/s out The total number of kilobytes sent by this side to the other side of the Replicator
pair. For the source, the value includes backup data, replication overhead, and network
overhead. For the destination, the value includes replication overhead and network
overhead.
FS ops File system operations per second.
NFS ops/s The number of NFS operations per second.
CIFS ops/s The number of CIFS operations per second.
Display
To display general system statistics, click System Stats in the left panel of the Data Domain
Enterprise Manager.
157
The system Command
Figure 27: Graphic display of system statistics
Display System Status
The system hardware status display includes information about fans, internal temperatures, and the
status of power supplies. Information is grouped by enclosure (restorer or expansion shelf).
•
•
Fans displays status for all the fans cooling each enclosure:
-
Description tells where the fan is located in the chassis.
-
Level gives the current operating speed range (low, medium, high) for each fan. The
operating speed changes depending on the temperature inside the chassis. See “Replace
Fans” on page 256 to identify fans in the restorer chassis by name and number. All of the
fans in an expansion shelf are located inside the power supply units.
-
Status is the system view of fan operations.
Temperature displays the temperature for each CPU and for the interior of the chassis. The C/F
column displays temperature in degrees Celsius and Fahrenheit. The Status column shows
whether or not the temperature is acceptable.
-
158
If the overall temperature for a restorer reaches 47 degrees centigrade, a warning message
is generated. If the temperature reaches 50 degrees centigrade, the restorer shuts down.
The system Command
-
•
If a restorer CPU temperature reaches 60 degrees centigrade, a warning message is
generated. If a restorer CPU temperature reaches 74 degrees centigrade, the restorer shuts
down.
Power Supply informs you that all power supplies are either operating normally or that one or
more are not operating normally. The message does not identify which power supply or
supplies are not functioning (except by enclosure). Look at the back panel of the enclosure and
check the LED for each power supply to identify those that need replacement.
Display
To display the current hardware status, use the system status operation.
system status
# system status
Enclosure 1
Fans
Description
--------------Crossbar fan #1
Crossbar fan #2
Crossbar fan #3
Crossbar fan #4
Rear fan #1
Rear fan #2
--------------Temperature
Description
--------------CPU 0 Actual
CPU 1 Actual
Chassis Ambient
--------------Power Supply
Status
-----OK
------
Level
-----medium
medium
medium
medium
medium
medium
------
Status
-----OK
OK
OK
OK
OK
OK
------
C/F
-----53/127
0/32
31/88
------
Status
-----OK
OK
OK
------
159
The system Command
Display the Restorer Model Number
To display the model number of the restorer, use the system show modelno command.
system show modelno
For example:
# system show modelno
Model number DD560
Display Data Transfer Performance
To display system performance figures for data transfer for an amount of time, use the system
show performance operation. You can set the duration and the interval of the display. Duration
is the hours, minutes, or seconds for the display to go back in time. Interval is the time between
each line in the display. The default is to show the last 24 hours in 10 minute intervals. You can set
duration only, but not interval only. The raw option displays unformatted statistics. The Read,
Write, and Replicate values are calculated in powers of 10 (1KB = 1000) instead of powers of 2
(1KB = 1024).
system show performance [raw][duration {hr | min | sec}
[interval {hr | min | sec}]]
The following example sets a duration of 30 minutes with an interval of 10 minutes:
# system show performance 30 min
Date
Time
Read
---------- -------- ---------2004/05/18 10:37:28 0.0 MB/s
2004/05/18 10:47:28 0.0 MB/s
recv
---0%
0%
send
---0%
0%
10 min
Write
---------0.0 MB/s
0.0 MB/s
Replicate
--------0.0 MB/s
0.0 MB/s
proc
---0%
0%
idle
---99%
99%
Display the Date and Time
To display the system date and time, use the system show date operation.
system show date
# system show date
Fri Nov 12 12:06:30 PDT 2004
160
The system Command
Display NVRAM Status
To display information about the NVRAM card, use the system show nvram operation.
•
The memory size, window size, and number batteries identify the type of NVRAM card.
•
The errors entry shows the operational state of the card. If the card has one or more PCI or
memory errors, an alerts email is sent and the daily AM-email includes an NVRAM entry.
•
Each battery entry should show 100% charged, enabled. The exceptions are for a new system
or for a replacement NVRAM card. In both cases, the charge may initially be below 100%. If
the charge does not reach 100% in three days (or if a battery is not enabled), the card should be
replaced.
Display Hardware
To display the PCI cards and other hardware in a restorer, use the system show hardware
operation. The display is useful for Data Domain Support when troubleshooting.
system show hardware
A few sample lines from the display follow:
# system show hardware
00:00.0 Host bridge: Intel Corp. E7520 Memory Controller Hub
(rev 0c)
00:00.1 Class ff00: Intel Corp. E7525/E7520 Error Reporting
Registers (rev 0c)
00:02.0 PCI bridge: Intel Corp. E7525/E7520/E7320 PCI Express
Port A (rev 0c)
00:04.0 PCI bridge: Intel Corp. E7525/E7520 PCI Express Port B
(rev 0c)
00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller (rev 02)
Display the Data Domain OS Version
To display the Data Domain OS version on your system, use the system show version
operation. The display gives the release number and a build identification number.
system show version
# system show version
Data Domain Release 3.0.0.0-12864
161
The alias Command
To display the versions of restorer components on your system, use the show
detailed-version operation. The display is useful for Data Domain support staff.
system show detailed-version
# system show detailed-version
Data Domain Release 3.0.0.0-12864
//prod/main/tools/ddr_dist/ddr_dist_files/...@12826
//prod/main/httpd/...@9826
//prod/main/app/...@12858
//tools/main/devtools/ddr/...@11444
//tools/main/devtools/README-DataDomain@10093
//tools/main/devtools/toolset.bom@3909
//prod/main/net-snmp/...@9320
//prod/main/os/lib/...@3799
.
.
.
Display All System Information
To display memory usage and the output from the commands: system show
detailed-version, system show fans, system show modelno, system show
serialno, system show uptime, and system show date, use the system show
all operation.
system show all
The alias Command
The alias command allows you to add, delete, or display command aliases and their definitions.
See “Display Aliases” on page 163 for the list of default aliases.
Add an Alias
To add an alias, use the alias add name “command” operation. Use double quotes around the
command if it has includes one or more spaces. A new alias is available only to the user who
creates the alias. A user can not create a working alias for a command that is outside of that user’s
permission level.
alias add name command
162
The alias Command
For example, to add an alias named rely for the restorer command that displays reliability statistics:
# alias add rely “disk show reliability-data”
Remove an Alias
To remove an alias, use the alias del name operation.
alias del name
For example, to remove an alias named rely:
# alias del rely
Reset Aliases
To return to the default alias list, use the alias reset operation. Administrative users only.
alias reset
Display Aliases
To display all aliases and their definitions, use the alias show operation.
alias show
The following example displays the default aliases:
# alias show
date -> system show date
df -> filesys show space
hostname -> net show hostname
ifconfig -> net config
iostat -> system show detailed-stats 2
netstat -> net show stats
nfsstat -> nfs show statistics
passwd -> user change password
ping -> net ping
poweroff -> system poweroff
reboot -> system reboot
sysstat -> system show stats
traceroute -> route trace
uname -> system show version
uptime -> system show uptime
who -> user show active
You have 16 aliases
163
Time Servers and the NTP Command
The sysstat alias can take an interval value for the number of seconds between each display of
statistics. The following example refreshes the display every 10 seconds:
# sysstat 10
The ntp command allows you to synchronize a restorer with an NTP time server, manage the NTP
service, or turn off the local (on the restorer) NTP server. The default system settings for NTP
service are enabled and multicast.
A restorer can use a time server supplied through the default multicast operation, received from
DHCP, or set manually with the restorer ntp add command.
•
Time servers set with the ntp add command override time servers from DHCP and from
multicast operations.
•
Time servers from DHCP override time servers from multicast operations.
•
The restorer ntp del and ntp reset commands act only on manually added time servers,
not on DHCP supplied time servers. You cannot delete DHCP time servers or reset to multicast
when DHCP time servers are supplied.
Enable NTP Service
To enable NTP service on a restorer, use the ntp enable operation. Available to administrative
users only.
ntp enable
Disable NTP Service
To disable NTP service on a restorer, use the ntp disable operation. Available to
ntp disable
Add a Time Server
To add a remote time server to NTP list, use the ntp add timeserver operation. Available to
ntp add timeserver server_name
164
For example, to add an NTP time server named srvr26.yourcompany.com to the list:
# ntp add timeserver srvr26.yourcompany.com
Delete a Time Server
To delete a manually added time server from the list, use the ntp del timeserver operation.
Available to administrative users only.
ntp del timeserver server_name
For example, to delete an NTP time server named srvr26.yourcompany.com from the list:
# ntp del timeserver srvr26.yourcompany.com
Reset the List
To reset the time server list from manually entered time servers to either DHCP time servers (if
supplied) or to the multicast mode (if no DHCP time servers supplied), use the ntp reset
timeservers operation. Available to administrative users only.
ntp reset timeservers
Reset All NTP Settings
To reset the local NTP server list to either DHCP time servers (if supplied) or to the multicast mode
(if no DHCP time servers supplied) and reset the service to enabled, use the ntp reset
operation. Available to administrative users only.
ntp reset
Display NTP Status
To display the local NTP service status, time, and synchronization information, use the ntp
status operation.
ntp status
The following example shows the information that is returned:
# ntp status
NTP Service is currently enabled.
Current Clock Time: Fri, Nov 12 2004 16:05:58.777
Clock last synchronized: Fri, Nov 12 2004 16:05:19.983
Clock last synchronized with time server: srvr26.company.com
165
Display NTP Settings
To display the NTP enabled/disabled setting and the time server list, use the ntp show config
operation.
ntp show config
The following example shows the information that is returned:
# ntp show config
NTP Service: enabled
The Remote Time Server List is:
srvr26.company.com, srvr28.company.com
166
Network Management
14
The net command manages the use of DHCP, DNS, and IP addresses, and displays network
information and status. The route command manages routing rules.
Note Changes to the ethernet interfaces made with the net command options flush the routing
table. All routing information is lost and any data movement currently using routing is
immediately cut off. Data Domain recommends making interface changes only during
scheduled maintenance down times. After making interface changes, you must reconfigure
any routing rules and gateways.
The net Command
Use the net command for the following operations.
Enable an Interface
To enable a disabled Ethernet interface on the restorer, use the net enable interface
net enable interface
For example, to enable the interface eth0:
# net enable eth0
Disable an Interface
To disable an Ethernet interface on the restorer, use the net disable interface operation.
net disable interface
For example, to disable the interface eth0:
# net disable eth0
167
The net Command
Enable DHCP
To set up an Ethernet interface to expect DHCP information, use the net config interface
dhcp yes operation. Changes take effect only after a system reboot. Administrative users only.
Note To activate DHCP for an interface when no other interface is using DHCP, the restorer must
be rebooted.
net config interface dhcp yes
For example, to set DHCP for the interface eth0:
# net config eth0 dhcp yes
To check the operation, use the net show configuration command. To check that the
Ethernet connection is live, use the net show hardware command.
Disable DHCP
To set an Ethernet interface to not use DHCP, use the net config interface dhcp no
operation. After the operation, you must set an IP address for the interface. All other DHCP settings
for the interface are retained. Administrative users only.
net config interface dhcp no
For example, to disable DHCP for the interface eth0:
# net config eth0 dhcp no
To check the operation, use the net show configuration command.
Change an Interface Netmask
To change the netmask used by an Ethernet interface, use the net config interface
netmask mask operation. Administrative users only.
net config interface netmask mask
For example, to set the netmask 255.255.255.0 for the interface eth0:
# net config eth0 netmask 255.255.255.0
168
The net Command
Change an Interface Transfer Unit Size
To change the maximum transfer unit size for an Ethernet interface, use the net config
interface mtu operation. Supported values are from 256 to 9180. For 100 Base-T and gigabit
networks, 1500 is the standard default. The default option returns the setting to the default
value. Make sure that all of your network components support the size set with this option.
net config interface mtu {size | default}
For example, to set a maximum transfer unit size of 9180 for the interface eth2:
# net config eth2 mtu 9180
Add or Change DNS servers
To add or change DNS servers for the restorer to use in resolving addresses, use the net set
dns ipaddr operation to give DNS server IP addresses. The operation writes over the current list
of DNS servers. Only the servers given in the latest command are available to a restorer. The list
can be comma-separated, space-separated, or both. Changes take effect only after a system reboot.
Note To activate a DNS change, the restorer must be rebooted.
net set dns ipaddr1[,ipaddr2[,ipaddr3]]
For example, to allow a restorer to use a DNS server with an IP address of 123.234.78.92:
# net set dns 123.234.78.92
To check the operation, use the net ping host-name command.
Ping a Host
To check that a restorer can communicate with a remote host, use the net ping operation with a
hostname or IP address.
net ping hostname [broadcast] [count n] [interface ifname]
broadcast Allows pinging a broadcast address.
count Gives the number of pings to issue.
interface Gives the interface to use: eth0 through eth3.
For example, to check that communication is possible with the host srvr24:
# net ping srvr24
Chapter 14: Network Management
169
The net Command
Change the Restorer Hostname
To change the name other systems use to access the restorer, use the net set hostname host
net set hostname host
For example, to set the restorer name to dd10:
# net set hostname dd10
To check the operation, use the net show hostname command.
Note If the restorer is using CIFS with active directory authentication, changing the hostname
causes the restorer to drop out of the domain. Use the cifs set authentication
command to rejoin the active directory domain.
Change an Interface IP Address
To change the IP address used by a restorer Ethernet interface, use the net config
interface ipaddr operation. If the interface is configured for DHCP, the command returns an
error. Use the net config interface dhcp disable command to turn off DHCP for an
interface. See “Disable DHCP” on page 168 for details. Administrative users only.
net config interface ipaddr
For example, to set the interface eth0 to the IP address of 192.168.1.1:
# net config eth0 192.168.1.1
Use the net show config command to check the operation.
Change the Domain Name
To change the domain name used by the restorer, use the net set domainname dm.name
net set domainname dm.name
For example, to set the domain name to yourcompany-ny.com:
# net set domainname yourcompany-ny.com
170
The net Command
Add a Hostname/IP Address to the /etc/hosts File
To associate an IP address with a hostname, use the net hosts add operation. The hostname is
a fully-qualified domain name or a hostname. In a list, separate each entry with a space and enclose
the list in double quotes. The entry is added to the /etc/hosts file. Administrative users only.
net hosts add ipaddr {host | “alias host”} ...
For example, to associate both the fully-qualified domain name bkup20.yourcompany.com and the
hostname of bkup20 with an IP address of 192.168.3.3:
# net hosts add 192.168.3.3 “bkup20 bkup20.yourcompany.com”
Reset Network Parameters
To reset the hostname, domain name, and DNS parameters to their default values (empty), use the
net reset operation. The command requires at least one parameter and accepts multiple
parameters. Changes take effect only after a system reboot. Administrative users only.
net reset {hostname | domainname | dns}
For example, to reset the system host name:
# net reset hostname
Set Interface Duplex Line Use
To manually set the line use for an interface to half-duplex or full-duplex, use the net config
interface duplex operation and set the speed at the same time. Half-duplex is not available
for any port set for a speed of 1000 (Gigabit). Administrative users only.
net config interface duplex {full|half} speed {10 | 100 | 1000}
For example, to set the line use to half-duplex for interface eth1:
# net config eth1 duplex half speed 100
Set Interface Line Speed
To manually set the line speed for an interface to 10 Base-T, 100 Base-T, or 1000 Base-T (Gigabit),
use the net config interface speed operation. A line speed of 1000 allows only a duplex
setting of full. Setting a port to a speed of 1000 and duplex of half leads to unpredictable results.
net config interface speed {10 | 100 | 1000}
171
The net Command
For example, to set the line speed to 100 Base-T for interface eth1:
# net config eth1 speed 100
Set Autonegotiate for an Interface
To allow the network interface card to autonegotiate the line speed and duplex setting for an
interface, use the net config interface autoneg operation. Administrative users only.
net config interface autoneg
For example, to set autonegotiation for interface eth1:
# net config eth1 autoneg
Delete a Hostname/IP address from the /etc/hosts File
To delete a hostname/IP address entry from the /etc/hosts file, use the net hosts del
net hosts del ipaddr
For example, to remove the hosts with an IP address of 192.168.3.3:
# net hosts del 192.168.3.3
Delete all Hostname/IP addresses from the /etc/hosts File
To delete all hostname/IP address entries from the /etc/hosts file, use the net hosts
reset operation. Administrative users only.
net hosts reset
Display Hostname/IP addresses from the /etc/hosts File
To display hostname/IP addresses from the /etc/hosts file, use the net hosts show
net hosts show
# net hosts show
Hostname Mappings:
192.168.3.3 -> bkup20 bkup20.yourcompany.com
172
The net Command
Display an Ethernet Interface Configuration
To display the current network driver settings for an Ethernet interface, use the net show
config operation. With no ifname, the command returns configuration information for all
Ethernet interfaces.
net show config [ifname]
A display for interface eth0 looks similar to the following:
# net show config eth0
eth0 Link encap:Ethernet HWaddr 00:02:B3:B0:8A:D2
inet addr:192.168.240.187 Bcast:123.456.78.255
Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500
Metric:1
RX packets:3081076 errors:0 dropped:0 overruns:0 frame:0
TX packets:1533783 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:100
RX bytes:3764464 (3.5 Mb) TX bytes:136647745 (130.3 Mb)
Interrupt:20 Base address:0xc000
Display Interface Settings
The display of Ethernet interface settings shows what you have configured, not the actual status of
each interface. For example, if an interface on the restorer does not have a live Ethernet connection,
the interface is not actually enabled.
Port lists each Ethernet interface by name.
Enabled shows whether or not the port is configured as enabled. To check the actual status of
interfaces, use the net show hardware command or see Network Hardware State in the Data
Domain Enterprise Manager. Both show a Cable column entry of yes for live Ethernet
connections.
DHCP shows whether or not port characteristics are supplied by DHCP. If a port uses DHCP for
configuration values, the display does not have values for the remaining columns.
IP address is the address used by the network to identify the port.
Netmask is the standard IP network mask.
173
The net Command
Display
Use the net show settings operation or click Network in the left panel of the Data Domain
Enterprise Manager and look at Network Settings.
net show settings
# net show settings
Ethernet settings:
port enabled DHCP
---- -----------eth0 yes
yes
eth1 no
n/a
eth2 yes
no
eth3 yes
yes
---- -----------
IP address
--------------(dhcp-supplied)
n/a
192.168.10.187
(dhcp-supplied)
---------------
netmask
--------------(dhcp-supplied)
n/a
255.255.255.0
(dhcp-supplied)
---------------
Display Ethernet Hardware Information
The display of the actual status of Ethernet connections has the columns:
Port is for the four Ethernet interfaces, eth0 through eth3. All Ethernet interfaces use the Gigabit
data transmission speed of 1000 Base-T.
Speed is the actual speed at which the port currently deals with data.
Duplex shows whether the port is using the full or half duplex protocol.
Supp. Speeds lists all the speeds that the port is capable of using.
Hardware Address is the MAC address.
Physical shows whether the port is Copper or Fiber.
Cable shows whether or not the port currently has a live Ethernet connection.
Display
Use the net show hardware operation or click Network in the left panel of the Data Domain
Enterprise Manager and look at Network Hardware State.
net show hardware
174
The net Command
The display looks similar to the following (each line wraps in the example here):
# net
Port
---eth0
eth1
eth2
eth3
show hardware
Speed
Duplex
-------- ------100Mb/s full
unknown unknown
1000Mb/s full
unknown unknown
Physical
-------Copper
Copper
Copper
Copper
Supp Speeds
----------10/100/1000
10/100/1000
10/100/1000
10/100/1000
Hardware Address
----------------00:02:b3:b0:8a:d2
00:02:b3:b0:80:3f
00:07:e9:0d:5a:1a
00:07:e9:0d:5a:1b
Cable
----yes
no
yes
no
Display the Restorer Hostname
To display the current hostname used by the restorer, use the net show hostname operation.
net show hostname
# net show hostname
The Hostname is: dd10.yourcompany.com
Display the Domain Name Used for Email
To display the domain name used for email sent by a restorer, use the net show domainname
operation.
net show domainname
# net show domainname
The Domainname is: yourcompany.com
175
The net Command
Display DNS Servers
To display the DNS servers used by a restorer, use the net show dns operation.
net show dns
The display looks similar to the following. The last line informs that the servers were configured
manually or by DHCP.
# net show dns
# Server
- ----------1 192.168.1.3
2 192.168.1.4
- ----------Showing DNS servers configured manually.
Display Network Statistics
To display network statistics, use the net show stats operation. The information returned
from all the options is used by Data Domain support staff for troubleshooting.
net show stats [all | interfaces | listening | route |
statistics]
all Display summaries of the other options.
interfaces Display the kernel interface table and a table of all network interfaces and their activity.
listening Display statistics about active internet connections from servers.
route Display the IP routing tables showing the destination, gateway, netmask, and other
information for each route.
statistics Display network statistics for protocols.
The display with no options is similar to the following, with statistics about live client connections.
# net show stats
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address
Foreign Address
State
tcp
0
20 123.234.78.90:21 123.234.78.11:512 ESTABLISHED
tcp
0
0
123.234.78.90:34 123.234.78.27:673 TIME_WAIT
176
The route Command
Display All Networking Information
To display the output from the commands net show config, net show settings, net
show domainname, net show hostname, net show hardware, net show dns, and
net show stats, use the net show hostname operation.
net show all
The route Command
Use the route command to manage routing between a restorer and backup hosts. An added
routing rule appears in the Kernel IP routing table and in the restorer Route Config list, a list of
static routes that are re-applied at each system boot. Use the route show config command to
display the Route Config list. Use the route show table command to display the Kernel IP
routing table.
Note Changes to the ethernet interfaces made with the net command options flush the routing
table. All routing information is lost and any data movement currently using routing is
immediately cut off. Data Domain recommends making interface changes only during
scheduled maintenance down times. After making interface changes, you must reconfigure
any routing rules and gateways.
Add a Routing Rule
To add a routing rule, use the route add -host or add -net operation. If the target being
added is a network, use the -net option. If the target is a host, use the -host option. The gateway
can be either an IP address or a hostname that is available to the restorer and that can be resolved to
an IP address. Administrative users only.
route add -host host-name gw gw-addr
route add -net ip-addr netmask mask gw gw-addr
To add a route for the host user24 with a gateway of srvr12:
# route add -host user24 gw srvr12
To add a route with a route specification of 192.168.1.x, a netmask, and a gateway of srvr12:
# route add -net 192.168.1.0 netmask 255.255.255.0 gw srvr12
The following example gives a default gateway of srvr14 for use when no other route matches:
# route set gateway srvr14
177
The route Command
Remove a Routing Rule
To remove a routing rule, use the route del -host or del -net operation. Use the same
form (-host or -net) to delete a rule as was used to create the rule. The route show
config command shows whether the entry is a host name or a net address. If neither -host or
-net is used, any matching lines in the Route Config list are deleted. Administrative users only.
route del -host host-name
route del -net ip-addr netmask mask
To remove a route for host user24:
# route del -host user24
To remove a route with a route specification of 192.168.1.x and a gateway of srvr12:
# route del -net 192.168.1.0 netmask 255.255.255.0 gw srvr12
Change the Routing Default Gateway
To change the routing default gateway, use the route set gateway ipaddr operation.
route set gateway ipaddr
For example, to set the default routing gateway to the IP address of 192.168.1.2:
# route set gateway 192.168.1.2
Reset the Default Routing Gateway
To reset the default routing gateway to the default value (empty), use the route reset
route reset gateway
Display a Route
To display a route used by a restorer to connect with a particular destination, use the route show
trace host operation.
route trace host
178
The route Command
For example, to trace the route to srvr24:
# route trace srvr24
Traceroute to srvr24.yourcompany.com (192.168.1.6), 30 hops
max, 38 byte packets
1 srvr24 (192.168.1.6) 0.163 ms 0.178 ms 0.147 ms
Display the Configured Static Routes
To display the configured static routes that are in the Route Config list, use the route show
config operation.
route show config
The display looks similar to the following (each line in the example wraps):
# route show config
The Route Config list is:
-host user24 gw srvr12
-net 192.168.1.0 netmask 255.255.255.0 gw srvr12
Display the Kernel IP Routing Table
To display all entries in the Kernel IP routing table, use the route show table operation.
route show table
The display looks similar to the following (each line in the example wraps):
# route show table
Kernel IP routing table
Destination
Gateway
192.168.1.0
0.0.0.0
127.0.0.0
0.0.0.0
0.0.0.0
192.168.1.2
Genmask
255.255.255.0
255.0.0.0
0.0.0.0
Flags
U
U
UG
Metric Ref
0
0
0
0
0
0
Use Iface
0 eth0
0 lo
0 eth0
179
The route Command
Display the Default Routing Gateway
To display the configured or DHCP-supplied routing gateways used by a restorer, use the route
show gateway operation.
route show gateway
# route show gateway
Default Gateways
192.168.1.2
192.168.3.4
180
NFS Management
15
The nfs command manages NFS clients and displays NFS statistics and status.
A restorer exports the directories /ddvar and /backup. /ddvar contains restorer log files and
core files. Add clients from which you will administer the restorer to /ddvar.
/backup is the target for data from your backup servers. The data is compressed before being
stored. Add backup servers as clients to /backup. If you choose to add a client to /backup and
to /ddvar, consider adding the client as read-only to /backup to guard against accidental
deletions of data.
Add NFS Clients
To add NFS clients that can access the restorer, use the nfs add export client-list
nfs-options operation. Add clients for administrative access to /ddvar. Add clients for
backup operations to /backup. A client added to a subdirectory under /backup has access only
to that subdirectory. The client-list can have a comma, a space, or both between list entries. To give
access to all clients, the client-list can be an asterisk (*).
nfs add {/ddvar | /backup[/subdir]} client-list [(nfs-options)]
The client-list can contain class-C IP addresses, IP addresses with either netmasks or length,
The nfs-options list can have a comma, a space, or both between entries. The default NFS
options for an NFS client are: rw, no_root_squash, no_all_squash, and secure. The list accepts the
following options:
ro Read only permission.
rw Read and write permissions.
root_squash Map requests from uid/gid 0 to the anonymous uid/gid.
no_root_squash Turn off root squashing.
all_squash Map all user requests to the anonymous uid/gid.
no_all_squash Turn off the mapping of all user requests to the anonymous uid/gid.
181
Remove Clients
secure Requires that requests originate on an Internet port that is less than IPPORT_RESERVED
(1024).
insecure Turn off the secure option
anonuid=id Set an explicit user-ID for the anonymous account. The id is an integer bounded from
-65635 to 65635.
anongid=id Set an explicit group-ID for the anonymous account. The id is an integer bounded from
-65635 to 65635.
For example, to add an NFS client with an IP address of 192.168.1.02 and read/write access to
/ddvar: with the secure option:
# nfs add /ddvar 192.168.1.02 (rw,secure)
# nfs add /ddvar 192.168.1.02/24 (rw,secure)
# nfs add /ddvar 192.168.1.02/255.255.255.0 (rw,secure)
Remove Clients
To remove NFS clients that can access the restorer, use the nfs del export client-list
operation. A client can be removed from access to /ddvar and still have access to /backup. The
client-list can contain IP addresses, hostnames, and an asterisk (*) and can be comma-separated,
space separated, or both.
nfs del {/ddvar | /backup[/subdir]} client-list
For example, to remove an NFS client with an IP address of 192.168.1.02 from /ddvar access:
# nfs del /ddvar 192.168.1.02
Enable Clients
To allow access for NFS clients to a restorer, use the nfs enable operation.
nfs enable
Disable Clients
To disable all NFS clients from accessing the restorer, use the nfs disable operation.
nfs disable
182
Reset Clients to the Default
Reset Clients to the Default
To return the list of NFS clients that can access the restorer to the factory default, use the nfs
reset clients operation. The factory default is an empty list. No NFS clients can access the
restorer when the list is empty. The operation is available to administrative users only.
nfs reset clients
Clear the NFS Statistics
To clear the NFS statistics counters and reset them to zero, use the nfs reset stats operation.
nfs reset stats
Display Active Clients
The list of active clients shows all clients that have been active in the past 15 minutes and the
mount path for each client.
Display
To display active NFS clients, use the nfs show active operation.
nfs show active
# nfs show active
NFS Active Clients
path
client
------- ---------------------/ddvar
jsmith.yourcompany.com
/backup djones.yourcompany.com
------- ----------------------
Chapter 15: NFS Management
183
Display Allowed Clients
Display Allowed Clients
The list of NFS clients allowed to access the restorer shows the mount path and the NFS options for
each client.
Display
To display all NFS clients, use the nfs show clients operation or click NFS in the left panel
of the Data Domain Enterprise Manager.
nfs show clients
# nfs show clients
NFS Client List
path
client
-------- --------/ddvar
jsmith
/backup djones
-------- ---------
options)
---------------------------------------(rw,root_squash,no_all_squash,secure)
(rw,no_root_squash,no_all_squash,secure)
----------------------------------------
Display Statistics
To display NFS statistics for a restorer, use the nfs show stats operation.
nfs show stats
The following example shows relevant entries, but not all possible entries:
# nfs show stats
NFS statistics:
NFSPROC3_NULL
NFSPROC3_GETATTR
NFSPROC3_SETATTR
NFSPROC3_LOOKUP
NFSPROC3_ACCESS
NFSPROC3_READLINK
NFSPROC3_READ
NFSPROC3_WRITE
NFSPROC3_CREATE
NFSPROC3_MKDIR
NFSPROC3_SYMLINK
NFSPROC3_MKNOD
NFSPROC3_REMOVE
NFSPROC3_RMDIR
184
:
:
:
:
:
:
:
:
:
:
:
:
:
:
0
327
30
66
455
0
0
6080507
10
0
0
0
0
0
[0]
[0]
[0]
[24]
[0]
[0]
[0]
[0]
[0]
[0]
[0]
[0]
[0]
[0]
Display Detailed Statistics
NFSPROC3_RENAME
NFSPROC3_LINK
NFSPROC3_READDIR
NFSPROC3_READDIRPLUS
NFSPROC3_FSSTAT
NFSPROC3_FSINFO
NFSPROC3_PATHCONF
NFSPROC3_COMMIT
:
:
:
:
:
:
:
:
11
0
0
0
0
0
0
0
Total Requests
:
6081406
[1]
[0]
[0]
[0]
[0]
[0]
[0]
[0]
FH statistics:
There are currently (2) exported filesystems.
Stats for export point [/backup]:
File System Type = SFS
Number of cached entries = 28
Number of file handle lookups = 6083544 (cache miss = 28)
Max allowed file cache size = 200, max streams = 64
Number of authentication failures = 0
Number of currently open file streams = 1
Stats for export point [/ddvar]:
File System Type = UNIX
Number of cached entries = 0
Number of file handle lookups = 0 (cache miss = 0)
Max allowed file cache size = 200, max streams = 64
Number of authentication failures = 0
Number of currently open file streams = 0
Display Detailed Statistics
The nfs show detailed-stats operation displays statistics used by Data Domain support
staff for troubleshooting.
nfs show detailed-stats
Chapter 15: NFS Management
185
Display Status
Display Status
To display NFS status for a restorer, use the nfs status operation.
nfs status
# nfs status
The NFS system is currently active and running
Total number of NFS requests handled = 6160900
Display Timing for NFS Operations
To display information about the time needed for NFS operations, use the nfs show
histogram operation. Administrative users only.
nfs show histogram
The column headers are:
Op The name of the NFS operation.
mean-ms The mathematical mean time for completion of the operations.
stddev The standard deviation for time to complete operations, derived from the mean time.
max-s The maximum time taken for a single operation.
<10ms The number of operations that took less than 10ms.
100ms The number of operations that took between 10ms and 100ms.
1s The number of operations that took between 1 second and 10 seconds.
10s The number of operations that took between 1 second and 10 seconds.
>10s The number of operations that took over 10 seconds.
186
CIFS Management
16
The cifs command manages CIFS (Common Internet File System) backups and restores from
and to Windows clients, and displays CIFS statistics and status.
CIFS system messages on the restorer go to a CIFS log directory. The location is:
/ddvar/log/windows
Note When configuring a destination restorer as part of a Replicator pair, configure the
authentication mode, WINS server (if needed), and other entries as with the originator in the
pair. The exceptions are that a destination does not need a backup user and will probably
have a different backup server list (all machines that can access data on the destination).
CIFS Access
A CIFS client can map to two shares on a restorer. Use the cifs add command (see “Add a
Client” on page 189) to make a share available to a client. A client is typically a Windows
workstation, not a user.
•
/ddvar is the share for administrative tasks, such as looking at a log file.
•
/backup is the share used by a Windows backup account for data storage and retrieval.
Any user that logs in to a restorer is put into one of two groups. The user group is limited to
commands that display statistics and status. The admin group can make configuration changes and
use the display commands.
•
If the restorer and a user account are in the same domain (or in an attached trusted domain), the
user can login to the restorer through a client that is known to the restorer.
-
If the user has no matching local account on the restorer, the user is part of the user group.
-
If the user has a matching local account on the restorer and the local account is part of the
admin group, the user is logged in as part of the admin group.
187
CIFS Access
•
If the restorer is in a workgroup, a user can login to the restorer through a client that is known
to the restorer.
-
The user must have a matching account (name and password) added to the restorer as a
local user account (see “Add a User” below).
-
The user is logged in as part of the group specified for the local account, user or admin.
For access to the restorer command line interface, use the SSH (or TELNET if enabled) utility to
log into the restorer or use a web-based browser to connect to the Data Domain Enterprise Manager
graphical user interface.
Note Permissions changes made to /backup or /ddvar from a CIFS administrative account
may cause unexpected limitations in access to the restorer and may not be reversible from
the CIFS account. By default, folders are created with permission bits of 755 and files with
permission bits of 744.
Add a User
To add a user, use the command user add user-name. The command asks for a password and
confirmation or you can include the password as part of the command. Users added to the restorer
can have a privilege level of admin or user. The default is user.
user add user-name [password password][priv admin | user]
All user accounts on a restorer act as CIFS local (built-in) accounts, which means that the user
name can access data in /backup on the restorer, and the user name can log in to the restorer and
use the restorer command set for managing the system. See the restorer command adminaccess
for the available access protocols.
For example, to add a user with a name of backup22, a password of usr256, and user privilege:
# user add backup22 password usr256
For a Windows client that needs file access to a restorer, enter a command similar to the following
from a command prompt on the Windows client (usually a Windows media server). The example
below maps /backup from restorer rstr02 to drive H on the Windows system and gives user
backup22 access to /backup:
> net use H: \\rstr02\backup /USER:rstr02\backup22
188
CIFS Commands
Add a Client
To add a Windows machine as a client that hosts a user account, use the cifs add /backup
command. To add a Windows machine that hosts an administrative user account as a client on the
restorer, use the cifs add /ddvar command. List entries can be comma-separated,
space-separated, or both. To give access to all clients, the client-list can be an asterisk (*).
cifs add /backup client-list
cifs add /ddvar client-list
The client-list can contain class-C IP addresses, IP addresses with either netmasks or length,
For example, to add a client named srvr24 that will do backups and restores with the restorer:
# cifs add /backup srvr24
# cifs add /backup 192.168.1.02/24
# cifs add /backup 192.168.1.02/255.255.255.0
CIFS Commands
The cifs command enables and disables access, sets the authentication mode, and displays status
and statistics. All cifs operations are available only to administrative users.
Enable Client Connections
To allow CIFS clients to connect to a restorer, use the cifs enable operation.
cifs enable
Disable Client Connections
To block CIFS clients from connecting to a restorer, use the cifs disable operation.
cifs disable
Chapter 16: CIFS Management
189
CIFS Commands
Add a Backup Client
Each Windows backup server that will do backup and restore operations with a restorer must be
added as a backup client. Use the cifs add /backup operation. List entries can be
cifs add /backup client-list
For example, to add a backup server named srvr24 as a backup client for a restorer:
# cifs add /backup srvr24
Add an Administrative Client
Each Windows machine that will host an administrative user for a restorer must be added as an
administrative client. Administrative clients use the /ddvar directory on a restorer. Use the cifs
add /ddvar operation. List entries can be comma-separated, space-separated, or both. To give
access to all clients, the client-list can be an asterisk (*).
cifs add /ddvar client-list
For example, to add an administrative client named srvr22:
# cifs add /ddvar srvr22
Remove a Backup Client
To remove a Windows backup client, use the cifs del /backup operation. List entries can be
cifs del /backup client-list
For example, to remove the backup client srvr24:
# cifs del /backup srvr24
Remove an Administrative Client
To remove a Windows administrative client, use the cifs del /ddvar operation. List entries
can be comma-separated, space-separated, or both.
cifs del /ddvar client-list
For example, to remove the administrative client srvr22:
# cifs del /ddvar srvr24
190
CIFS Commands
Remove All CIFS Clients
To remove all of the CIFS clients from a restorer, use the cifs reset clients operation.
cifs reset clients
Set a NetBIOS Hostname
To change the NetBIOS hostname of the restorer, use the cifs set nb-hostname operation.
The default NetBIOS name is the first component of the fully-qualified hostname used by the
restorer. If you are using domain authentication, the nb-name cannot be over 15 characters long.
Use the cifs show config command to see the current NetBIOS name.
cifs set nb-hostname nb-name
For example, to give a restorer the name of rstr12 for NetBIOS use:
# cifs set nb-hostname rstr12
Remove the NetBIOS Hostname
To remove the NetBIOS hostname of the restorer, use the reset nb-hostname operation.
cifs reset nb-hostname
Set the Authentication Mode
The restorer can use the authentication modes of: active-directory, domain, or workgroup. Use the
cifs set authentication operations to choose or change a mode. Each mode has a
separate syntax.
The active-directory mode joins a restorer to an active-directory-enabled domain. The realm must
be a fully-qualified name. Data Domain recommends not specifying a domain controller. When not
using a domain controller, first specify a WINS server. The restorer must meet all active-directory
requirements, such as a clock time that is no more than five minutes different than the domain
controller. See “Procedure: Time Servers and Active Directory Mode” on page 197 for information
about time servers. Optionally, include multiple domain controllers or all ( * ). The domain
controller list entries can be comma-separated, space-separated, or both.
cifs set authentication active-directory realm {[dc1[dc2 ...]]
| *}
The domain mode puts the restorer into an NT4 domain. Include a domain name and optionally, a
primary domain controller or backup and primary domain controllers or all ( * ).
cifs set authentication domain domain [[pdc [bdc]] | *]
191
CIFS Commands
The workgroup mode means that the restorer verifies user passwords.
cifs set authentication workgroup wg-name
Remove All IP Address/NetBIOS hostname Mappings
To remove all IP address/NetBIOS hostnames from the lmhosts file, use the cifs hosts
reset operation.
cifs hosts reset
Add an IP Address/NetBIOS hostname Mapping
To add an IP address/NetBIOS hostname mapping to the lmhosts file, use the cifs hosts
add ipaddr host-list operation. One IP address can have multiple host names.
cifs hosts add ipaddr host-list
For example, to add the IP address for the machine srvr22:
# cifs hosts add 192.168.10.25 srvr22
Added "srvr22" -> "192.168.10.25" mapping to hosts list.
Remove an IP Address/NetBIOS hostname Mapping
To remove an IP address/NetBIOS hostname mapping from the lmhosts file, use the cifs
hosts del ipaddr operation.
cifs hosts del ipaddr
For example, to remove the IP address 192.168.10.25:
# cifs hosts del 192.168.10.25
Removed mapping 192.168.10.25 -> srvr22.
Resolve a NetBIOS Name
To display the IP address used for any NetBIOS name on the WINS server, use the cifs
nb-lookup operation. The CIFS feature must already be enabled.
cifs nb-lookup net-bios-name
For example, to display the IP address for the machine srvr22:
# cifs nb-lookup srvr22
querying srvr22 on 192.168.1.255
192.168.1.14 morgan<00>
192
CIFS Commands
Identify a WINS server
To identify a WINS server for resolving NetBIOS names to IP addresses, use the cifs set
wins-server operation.
cifs set wins-server ipaddr
For example, to use a WINS server with the IP address of 192.168.1.12:
# cifs set wins-server 192.168.1.12
Remove the WINS server
To remove the WINS server IP address, use the reset wins-server operation.
cifs reset wins-server
Set CIFS Logging Levels
You can set the level of messages that go to the CIFS-related log files under
/ddvar/log/windows. Use the cifs option set command.
cifs option set loglevel value
The value is an integer from 0 (zero) to 10 (ten). Zero is the default system value that sends all
CIFS messages to the files. The lower the value, the fewer log messages go to the logs. As an
example:
# cifs option set loglevel 4
Set "loglevel" to "4"
Increase Memory to Allow More User Accounts
When using domain or active directory mode authentication on a restorer, adding 30,000 or more
user accounts may cause memory allocation errors. Use the cifs option set command to
increase memory available for user accounts.
cifs option set “dd winbindd mem limit” value
The recommended value of 104857600 doubles the available memory. For example:
# cifs option set “dd winbindd mem limit” 104857600
Set "dd winbindd mem limit" to "104857600"
193
CIFS Commands
Reset CIFS Options
To reset a CIFS option to the default, use the cifs option reset command.
cifs option reset name
For example:
# cifs option reset loglevel
Display CIFS Options
To display the CIFS options that are available from the cifs command, use the cifs option
show command.
cifs option show
Display Active Clients
To display Windows clients that are currently active, use the cifs show active operation.
cifs show active
The display is similar to the following and shows which shares are accessed from a client machine
and what data transfer may be happening (Locked files).
# cifs show active
PID
Username
Group
Machine
---------------------------------------------------------568
sysadmin
admin
srvr24
(192.168.1.5)
566
sysadmin
admin
srvr22
(192.168.1.6)
Service pid
machine
Connected at
--------------------------------------------------ddvar
566
srvr22
Tue Jan 13 12:11:03 2004
backup
568
srvr24
Tue Jan 13 12:09:44 2004
IPC$
566
srvr22
Tue Jan 13 12:10:55 2004
IPC$
568
srvr24
Tue Jan 13 12:09:36 2004
backup
566
srvr22
Tue Jan 13 12:10:59 2004
Locked files:
Pid DenyMode
Access
R/W
Oplock Name
------------------------------------------------------------566 DENY_WRITE 0x20089 RDONLY NONE
/loopback/setup.iso Tue
Jan 13 12:11:53 2004
566 DENY_ALL
0x30196 WRONLY NONE
/loopback/RH8/
psyche-i386-disc1.iso
Tue Jan 13 12:12:23 2004
194
CIFS Commands
Display All Clients
The display of all Windows clients that have access to a restorer lists the access path for each client.
Each Windows backup server that will do backup and restore operations has a path starting with
/backup. Each Windows client that will host an administrative user has the path of /ddvar.
Display
Use the cifs show clients operation or click CIFS in the left panel of the Data Domain
Enterprise Manager to see all clients.
cifs show clients
# cifs show clients
path
client
------- --------/backup all
/backup srvr24.yourcompany.com
/ddvar
srvr24.yourcompany.com
------- ---------
Display the CIFS Configuration
The CIFS configuration display begins with the authentication mode, gives details unique to each
mode, lists a WINS server if one is configured, and lists NetBIOS hostnames.
Display
Use the cifs show config operation or click CIFS in the left panel of the Data Domain
Enterprise Manager to display CIFS configuration details.
cifs show config
For example:
# cifs show config
-----------------Mode
Workgroup
WINS Server
NB Hostname
------------------
------------Workgroup
WORKGROUP
192.168.1.7
server26
-------------
195
CIFS Commands
Display CIFS Statistics
To display CIFS statistics for total operations, reads, and writes, use the cifs show stats
operation.
cifs show stats
For example:
# cifs show stats
SMB total ops :
SMB reads
:
SMB writes
:
31360
165
62
Display Detailed CIFS Statistics
To display statistics for each individual type of SMB operation, use the cifs show
detailed-stats operation.
cifs show detailed-stats
Display CIFS Status
To display the status of CIFS access to the restorer, use the cifs status operation.
cifs status
For example:
# cifs status
CIFS is enabled and running.
Display All IP Address/NetBIOS hostname Mappings
To display all IP address/NetBIOS hostname mappings in the lmhosts file, use the cifs
hosts show operation.
cifs hosts show
The command output is similar to the following:
# cifs hosts show
Hostname Mappings:
192.168.10.25 -> srvr22
196
Procedure: Time Servers and Active Directory Mode
When using active directory mode for CIFS access, the restorer clock time can be no more than five
minutes different than the domain controller. Use the restorer ntp command (see “Time Servers
and the NTP Command” on page 164) to synchronize the clock with a time server.
Note The ntp command cannot synchronize the restorer with a time server if the time difference
is greater than 1000 seconds. Before following either of the procedures below, manually set
the clock on the restorer to less than 1000 seconds difference.
Synchronizing from an NTP Server
When synchronizing directly from a standard NTP server, use the following commands on the
restorer. Substitute your ntp-server-name:
# ntp add timeserver ntp-server-name
# ntp enable
Synchronizing from a Windows Domain Controller
When synchronizing through a Windows domain controller:
•
The domain controller must get time from an external source.
•
NTP must be configured on the domain controller. To configure NTP, see the documentation
for the Windows software version and service pack that is running on your domain controller.
The following example is for Windows 2003 SP1 (use your ntp-server-name):
C:\>w32tm /config /syncfromflags:manual /manualpeerlist:
ntp-server-name
C:\>w32tm /config /update
C:\>w32tm /resync
•
After NTP is configured on the domain controller, run the following commands on the restorer
using your domain-controller-name:
# ntp add timeserver domain-controller-name
# ntp enable
197
198
Replicator
17
The replication command sets up and manages the Data Domain Replicator for replicating
data between restorers. The Replicator is a licensed product. Contact Data Domain for license keys.
Use the license add command to add one key to each restorer in the Replicator configuration.
Collection replication replicates the complete /backup directory from one restorer (a source that
receives data from backup systems) to another restorer (a destination). Each restorer is dedicated as
a source or a destination and each can be in only the one replication pair. The destination is a
read-only system except for receiving data from the source. With collection replication:
•
A destination restorer can be mounted as read-only for access from other systems.
•
A destination restorer must have a storage capacity that is equal to or greater than the source.
•
A destination restorer removed from a collection pair (with the replication break
command) cannot be brought back into the pair or be used as a destination for another source
until the file system is emptied with the filesys destroy command. Note that the
filesys destroy command erases all Replicator configuration settings.
•
A destination restorer removed from a collection pair becomes a stand-alone restorer that can
be used as a source for replication.
•
With collection replication, all user accounts and passwords are replicated from the source to
the destination. Any changes made manually on the destination are overwritten after the next
change is made on the source. Data Domain recommends making changes only on the source.
Directory replication provides replication at the level of individual directories. Each restorer can be
the source or the destination for multiple directories and can also be a source for some directories
and a destination for others. During directory replication, each restorer can also perform normal
backup and restore operations. Replication command options with directory replication may target
a single replication pair (source and destination directories) or may target all pairs that have a
source or destination on the restorer. Each replication pair configured on a restorer is called a
context. With directory replication:
•
The maximum number of contexts allowed on a restorer is twenty. Be sure that the destination
restorer has enough network bandwidth and disk space to handle all traffic from the
originators.
•
A destination restorer must have available storage capacity that is at least the size of the
expected maximum size of the source directory. The destination must have adequate space.
199
Using “Context”
•
Do not have a single destination restorer receive backups from both CIFS clients and NFS
clients. Data corruption may result. Set up separate destination restorers for CIFS clients and
for NFS clients.
•
Source or destination directories may not overlap.
•
A destination directory that does not already exist is created automatically when replication is
initialized.
•
After replication is initialized, ownership and permissions of the destination directory are
always identical to those of the source directory.
•
In the replication command options, a specific replication pair is always identified by the
destination.
Throttle options for limiting the bandwidth used by replication:
•
Apply to all replication pairs and all network interfaces on a system. Each throttle setting
affects all replication pairs and network interfaces equally.
•
Affect only outbound network traffic.
•
Govern the total replication bandwidth available for a given network interface.
Using “Context”
Except for the replication add operation, all replication commands that can use a destination
variable can take either the complete destination specification or a context number. Context
numbers appear in the output from a number of commands, such as replication status.
Look for the number in a command output’s first column that has the heading CTX. To use the
context number, preface the number with rctx://. For example, to display statistics for the
destination labeled as context 2, use the following command:
# replication show stats rctx://2
Configure Replicator
To configure a Replicator pair, use the replication add operation on both the source and
destination restorers. Administrative users only.
replication add source source destination destination
•
200
The source and destination host names must be exactly the same as the names returned by the
hostname command on the source and destination restorers.
VTL Pools Replication
•
For collection replication:
-
Enter the filesys disable command on both the source and destination.
-
Start the source and destination variables with col://. For example, enter a command
similar to the following on the source and destination restorers:
replication add source col://hostA destination col://hostB
•
Enter the filesys enable command on both the source and destination.
For directory replication:
-
The restorer file system must be enabled.
-
The source directory must exist.
-
The destination directory should be empty.
-
Start the source and destination variables with dir:// and include the directory that is
the replication target. For example, enter a command similar to the following on the
source and destination restorers:
replication add source dir://hostA/backup/dir2
destination dir://hostB/backup/hostA/dir2
•
When the host name for a source or destination does not correspond to the network name
through which the restorers will communicate, use the replication modify command
with the connection-host option on the other system to direct communications to the
correct network name.
•
After including a source directory in a replication add command, you cannot add new
sub-directories under the source directory or change sub-directory names.
VTL Pools Replication
•
Start the source and destination variables with pool:// and include the pool that is the
replication target. For example, enter a command similar to the following on the source and
destination restorers:
replication add source pool://hostA/pool2
destination pool://hostB/pool2
•
The pool name must be unique on the destination and the destination cannot include levels of
directories between the destination hostname and the pool name. For example, a destination of
pool://hostB/hostA/pool2 is not allowed.
•
Pool replication and directory replication are the same (except for the destination name
limitation above) when configuring replication and when using the replication command
set. Examples in this chapter that use dir:// are also valid for pool://.
Chapter 17: Replicator
201
Start Replication
•
Pool replication does not require the VTL license on the destination restorer.
Start Replication
To start replication between a source and destination, use the replication initialize
operation on the source. The command checks that the configuration and connections are correct
and returns error messages if any problems appear. If the source holds a lot of data, the initialize
operation can take many hours. Consider putting both restorers in the Replicator pair in the same
location with a direct link to cut down on initialization time. A destination variable is required.
replication initialize destination
For a successful initialization:
•
The source directory must exist.
•
The destination directory must be empty.
Suspend Replication
To temporarily halt the replication of data between source and destination, use the replication
disable operation on either the source or the destination. On the source, the operation stops the
sending of data to the destination. On the destination, the operation stops serving the active
connection from the source. If the file system is disabled on either restorer when replication is
disabled, replication remains disabled even after the file system is restarted. Administrative users
only.
replication disable {destination | all}
Resume Replication
To restart replication that is temporarily halted, use the replication enable operation on the
restorer that was temporarily halted. On the source, the operation resumes the sending of data to the
destination. On the destination, the operation resumes serving the active connection from the
source. If the file system is disabled on either restorer when replication is enabled, replication is
enabled when the file system is restarted. Administrative users only.
replication enable {destination | all}
202
Remove Replication
Remove Replication
To remove either the source or destination restorer from a Replicator pair or to remove all
Replicator configurations from a restorer, use the replication break operation. A
destination variable or all is required.
•
Always run the filesys disable command before the break operation and the filesys
enable command after.
•
With collection replication, a destination is left as a stand-alone read/write restorer that can
then be used as a source.
•
With collection replication, a destination cannot be brought back into the replication pair or
used as a destination for another source until the file system is emptied with the filesys
destroy command.
•
With directory replication, a destination directory must be empty to be used again with the
original source or with a different source.
replication break {destination | all}
Reset Authentication between the Restorers
To reset authentication between a source and destination, use the replication reauth
operation on both the source and the destination. Messages similar to “Authentication keys out of
sync,” or “Key out of sync” signal the need for a reset. Reauthorization is primarily used when
replacing a source restorer. See “Procedure: Replace a Directory Source - New Name” on
page 216. A destination variable is required. Administrative users only.
replication reauth destination
Move Data to a New Source
To move data from a surviving destination to a new source, use the replication recover
operation on the new source. With collection replication, first use the filesys destroy
operation on the source. With directory replication, the target directory on the source must be
empty. See “Procedure: Set Up and Start Many-to-One Replication” on page 216. Do not use the
operation on a destination. If the replication break command was run earlier, the
destination cannot be used to recover a source. A destination variable is required. Also see
“Procedure: Replace a Directory Source - New Name” on page 216 for an example of using the
recover option when replacing a source restorer. Administrative users only.
replication recover destination
203
Change a Source or Destination Hostname
Change a Source or Destination Hostname
When replacing a system and using a new name for the replacement system, use the
replication modify operation on the other side of the replication pair. The new-host-name
must be exactly the same as displayed by the hostname command on the system with the new
hostname. If the replication pair has a throttle setting, the setting applies with the new destination.
If you are changing the hostname on an existing source restorer, use the replication modify
operation on the destination. Do not use the command if you want to change the hostname on an
existing destination. Call Data Domain Technical Support before changing the hostname on an
existing destination.
When using the replication modify command, always run the filesys disable
command first and the filesys enable command after. Administrative users only.
replication modify destination {source-host | destination-host}
new-host-name
For example, if the local destination dest-orig.ca.company.com is moved from California to New
York, run a command similar to the following on both the source and destination:
# replication modify dir://ca.company.com/backup/dir2
destination-host dir://ny.company.com
Connect with a Network Name
A source restorer connects to the destination restorer using the destination name as returned by the
hostname command on the destination. If the destination host name does not resolve to the
correct IP address for the connection, use the modify connection-host option to give the
correct name to use for the connection. The connection-host name can also be a numeric IP address.
When specifying a connection-host, an optional port number can also be used. The connection-host
option may be required when connecting to an alternate interface on the destination or when a
connection passes through a firewall.
The option may be needed after adding a new source/destination pair or after renaming either a
source or a destination. The port option is valid only when used on a source and must match the
listen-port used by the destination. The default port is 2051.
replication modify destination connection-host new-host-name
[port port]
The following example is run on the source to inform the source that the destination host
dest-orig.ny.company.com has a network name of dest-orig-2.ny.company.com. Note that the
destination variable for the pair does not change and is still dest-orig.ny.company.com.
# replication modify dir://ny.company.com/backup/dir2
connection-host dir://ny2.company.com
204
Change the Port on a Destination
Change the Port on a Destination
To change the port from which the destination receives data from sources, use the replication
option set listen-port operation on the destination system. The default port is 2051. The
connection-host port used by the source must match the listen-port used by the destination.
replication option set listen-port port
Add a Scheduled Throttle Event
To change the rate of network bandwidth used by replication, use the throttle add operation.
The default network bandwidth use is unlimited.
replication throttle add sched-spec rate
The sched-spec must include:
•
One or more three-letter days of the week (such as mon, tue, or wed) or the word daily (to set
the schedule every day of the week).
•
A time of day in 24 hour military time.
The rate includes a number or the word unlimited. The number can include a tag for bits or
bytes per second. Do not use a space between the number and the bits or bytes specification. For
example, 2000KB. The default rate is bits per second. In the rate variable:
•
bps or b equals raw bits per second
•
Kbps, Kb, or K equals 1024 bits per second
•
Bps or B equals bytes per second
•
KBps or KB equals 1024 bytes per second
The rate can also be 0 (the zero character), disable, or disabled. Each stops replication until the
next rate change.
For example, the following command limits replication to 20 kilobytes per second starting on
Mondays and Thursdays at 6:00 a.m.
# replication throttle add mon thu 0600 20KB
Replication runs at the given rate until the next scheduled change or until new throttle commands
force a change. The default rate with no scheduled changes is to run as fast as possible at all times.
The add operation may change the current rate. For example, if on Monday at Noon, the current
rate is 20 KB, and the schedule that set the current rate started on mon 0600, a new schedule change
for Monday at 1100 at a rate of 30 KB (mon 1100 30KB) makes the change immediately.
Note The system enforces a minimum rate of 98,304 bits per second (12 KB).
205
Set a Temporary Throttle Rate
Set a Temporary Throttle Rate
To set a throttle rate until the next scheduled change or until a system reboot, use the throttle
set current operation. A temporary rate cannot be set if the replication throttle
set override command is in effect.
replication throttle set current rate
example, for 2000 kilobytes, use 2000KB. The default rate is bits per second. In the rate variable:
•
•
•
•
next rate change.
As an example, the following command sets the rate to 2000 kilobytes per second:
# replication throttle set current 2000KB
Delete a Scheduled Throttle Event
To remove one or more throttle schedule entries, use the throttle del operation.
replication throttle del sched-spec
The sched-spec must include:
•
One or more three-letter days of the week (such as mon, tue, or wed) or the word daily to delete
all entries for the given time.
•
A time of day in 24 hour military time.
For example, the following command removes an entry for Mondays at 1100:
# replication throttle del mon 1100
The command may change the current rate. For example, assume that on Monday at Noon, the
current rate is 30 KB, and the schedule that set the current rate started on mon 1100. If you now
delete the scheduled change for Monday at 1100 (mon 1100), the replication rate immediately
changes to the next previous scheduled change, such as mon 0600 20KB.
206
Set an Override Throttle Rate
Set an Override Throttle Rate
To set a throttle rate that overrides scheduled rate changes, use the throttle set override
operation. The rate stays at the override level until another override command is entered.
replication throttle set override rate
example, 2000KB. The default rate is bits per second. In the rate variable:
•
•
•
•
next rate change.
As an example, the following command sets the rate to 2000 kilobytes per second:
# replication throttle set override 2000KB
Reset Throttle Settings
To reset any or all of the throttle settings, use the throttle reset operation.
replication throttle reset {current | override | schedule |
all}
•
A reset of current removes the rate set by the replication throttle set
current command. The rate returns to a scheduled rate or to the default if no rate is
scheduled.
•
A reset of override removes the rate set by the replication throttle set
override command. The rate returns to a scheduled rate or to the default if no rate is
scheduled. The default network bandwidth use is unlimited.
•
The reset of schedule removes all scheduled change entries. The rate remains at a
current or override setting, if either is active, or returns to the default of unlimited.
•
The reset of all removes any current or override settings and removes all scheduled
change entries, returning the system to the default, which is unlimited.
207
Set Replication Bandwidth
Set Replication Bandwidth
To limit the bandwidth used by a system, use the replication option set bandwidth
operation.
replication option set bandwidth rate
•
The rate is an integer of bytes/second.
•
Use the replication disable command before changing the rate and use the
replication enable command after changing the rate.
Set Replication Network Delay
To set a network delay value for the system, use the replication option set delay
operation.
replication option set delay value
•
The value is an integer of milliseconds.
•
Use the replication disable command before changing the delay and use the
replication enable command after changing the delay.
Reset Options
To reset system bandwidth to the default of unlimited and delay or listen-port to the default of none,
use the replication option reset operation. Use the replication disable
command before making changes and use the replication enable command after making
changes.
replication option reset {bandwidth | delay | listen-port}
Repair a Broken Recovery
To re-synchronize source and destination restorers after a recovery operation is destroyed, use the
replication abort recover command. Enter the command on the destination to
synchronize the restorers and to restart the recovery operation. Running a filesys destroy
command on the source during a recovery operation is an example of destroying a recovery. A
break, such as a network connection down, does not destroy a recovery, which continues as
expected when the break is repaired.
replication abort recover destination
208
Display Throttle settings
Display Throttle settings
To display all scheduled throttle entries, rates, and the current rate, use the replication
throttle show operation.
replication throttle show [kb]
The kb option displays the rate in kilobytes per second. Without the option, the rate is displayed in
bits per second. The display is similar to the following:
# replication throttle show kb
Time
Sun
Mon
Tue
Wed
Thu
Fri
Sat
-----------------06:00
90
15:00
200
18:00
500
-----------------All units in KBps (1024 bytes (8192 bits) per second).
Active schedule: Mon, 06:00 at 90 KBps.
Display Bandwidth and Delay Settings
To display the current bandwidth and delay settings, use the replication option show
operation. If the current setting is the default of none, the operation returns to a command prompt
with no setting information.
replication option show {destination | all}
Display Replicator Configuration
To display the source and destination, the name of the other system in the Replicator pair, and the
state of replication, use the show config operation.
replication show config [destination | all]
The display with no destination variable or all option is similar to the following:
# replication show config
CTX Source
--- ----------------------------------1
dir://host2.company.com/backup/dir2
2
--- -----------------------------------
209
Display Replication for Current Data
Destination
----------------------------------dir://host3.company.com/backup/dir3
-----------------------------------
Connection Host
----------------host3.company.com
host3.company.com
-----------------
Enabled
------Yes
Yes
------The display with a destination variable is similar to the following. The all option returns a similar
display for each context.
# replication show
Source:
Destination:
Connection Host:
Enabled:
config dir://host3.company.com/backup/dir2
dir://host2.company.com/backup/host2
dir://host3.company.com/backup/host2
ccm34.datadomain.com
yes
Display Replication for Current Data
To display when data currently available for replication is completely replicated, use the
replication sync option on the source restorer.
replication sync
The output’s current value represents data on the source that is yet to be replicated to the
destination. The value represents only data available at the time the command is given. Data
received after the command begins is not added to the output. When the current value is equal to or
greater than the output’s sync_target value, replication is complete for all of the data that was
available for replication at the time the command began. For example:
# replication sync
0 files flushed.
current=2832642 sync_target=2941532 head=2841234
210
Display Status
Display Status
To display Replicator configuration information and the status of replication operations, use the
replication status operation.
replication status [destination | all]
With no option, the display is similar to the following:
# replication status
CTX Destination
--- ----------------------------------1
2
--- ----------------------------------Connected
----------------Thu Jan 12 17:06
disconnected
-----------------
Enabled
------yes
yes
-------
Lag
-----00:00
698:32
------
Enabled The enabled state (yes or no) of replication for each replication pair.
Connected The most recent connection date and time or connection state for a replication pair.
Lag The difference between the timestamp on the most recently executed record and the system
clock time on the destination. Lag is not the time needed to complete replication. Lag can
immediately drop from a high number to zero when the last record is processed. A generic message
of "Less than 5 minutes" appears if the destination is either nearly caught up with data from the
source or if the destination is caught up and synchronized and the source is not sending new data.
Output from the replication show stats command shows whether or not any data remains
to be sent from the source.
With a destination variable, the display is similar to the following. The all option returns a similar
display for each context. The displays include the information above plus:
# replication status dir://host2.company.com/backup/dir2
Mode:
source
Destination:
dir://ccm34.datadomain.com/backup/dir2
Enabled:
yes
Local filesystem status: enabled
Connection:
connected since Thu Jan 12 17:06:41
State:
normal
Error:
no error
Lag:
less than 5 minutes
Current throttle:
unlimited
Mode The role of the local system: source or destination.
211
Display Statistics
Local Filesystem Status The enabled/disabled status of he local file system.
Connected Includes both the state and the date and time of the last change in the connection state.
State The state of the replication process.
Error A listing of any errors in the replication process.
Current Throttle The current throttle setting.
Display Statistics
Replication statistics have the following columns:
Bytes Sent The total number of bytes sent by this side to the other side of the Replicator pair. For
the source, the value includes backup data, replication overhead, and network overhead. For the
destination, the value includes replication overhead and network overhead. Use the value (and the
next value, Bytes received) to estimate network traffic generated by replication.
Bytes Received The total number of bytes received by this side from the other side of the
Replicator pair. For the destination, the value includes backup data, replication overhead, and
network overhead. For the source, the value includes replication overhead and network overhead.
Use the value (and the previous value) to estimate network traffic generated by replication.
Virtual Bytes The total number of bytes of backup data (before compression) replicated since the
last time the restorer file system was enabled.
Received Time The date and time of the most recent records received.
Processed Time The date and time of the most recent records processed.
Source Records Remaining The number of file operations (such as open, close, delete) that have
happened on the source and that have not yet been sent to the destination. If a lot of content is being
sent for one file, a number of file operations (for deleted files, for example) may accrue while
waiting. As the operations are a relatively small amount of data, the number in this column can fall
quickly when the operations are sent to the destination.
Dest Records Remaining The number of file operations received by the destination and not yet
processed. With directory replication, the value is always 0 (zero).
Compressed data remaining New data on the source that is not yet sent to the destination.
Display
To display Replicator statistics for all replication pairs or for a specific destination pair, use the
replication show stats operation.
replication show stats [destination | all]
212
Display Statistics
The display with no destination or all option is similar to the following:
# replication show stats
CTX
Destination
------------------------------------1
2
------------------------------------Bytes
Received
---------1974621040
0
----------
Virtual
Bytes
-------------11115121593320
0
--------------
Source Records
Remaining
-------------0
0
--------------
Bytes Sent
-----------153687473704
0
------------
Received
Time
---------------Fri Jan 13 09:37
Wed Dec 31 16:00
----------------
Dest Records
Remaining
-----------0
0
------------
Processed
Time
---------------Fri Jan 13 09:37
Wed Dec 31 16:00
----------------
Compressed
Data Remaining
-------------0
0
--------------
With a destination variable, the display is similar to the following. The all option returns a similar
display for each context:
# replication show stats rctx://1
CTX:
1
Destination:
Bytes sent:
153687473704
Bytes received:
1974621040
Virtual bytes replicated:
11115121593320
Destination records remaining: 0
Source records remaining:
0
Compressed data remaining:
0
213
Hostname Shorthand
Hostname Shorthand
With all Replicator commands that use a hostname to identify the source or destination, the
hostname can be left out if the hostname refers to the local system. Use the same three slashes ( /// )
that would bracket the hostname if the hostname was included. For example, the replication
add command when given on the source restorer could be entered in either of the following ways:
destination dir://hostB/backup/dir2
replication add source dir:///backup/dir2
The same command given on the destination restorer could be done in either of the following ways:
destination dir:///backup/dir2
Use the same format with collection replication. Add a third slash, even though a third slash is not
otherwise used with collection replication. For example, the replication add command for
collection replication entered on the source could be done in either of the following ways:
replication add source col://hostA
destination col://hostB
replication add source col:///
destination col://hostB
Procedure: Set Up and Start Directory Replication
To set up directory replication using restorers hostA and hostB for a directory named dir2:
•
Run the following command on both the source and destination restorers:
•
Run the following command on the source. The command checks that both restorers in the pair
can communicate and starts all Replicator processes. If a problem appears, such as that
communication between the restorers is not possible, you do not need to re-initialize after
fixing the problem. Replication should begin as soon as the restorers can communicate.
replication initialize
214
Procedure: Set Up and Start Collection Replication
Procedure: Set Up and Start Collection Replication
To set up and start collection replication between two restorers, hostA and hostB:
•
filesys disable
•
If the destination holds any data, run the following command on the destination:
filesys destroy
•
Run the following command on both the source and destination restorers. See “Configure
Replicator” on page 200 for the details of using the command:
•
filesys enable
•
Run the following command on the source. The command checks that both restorers in the pair
can communicate and starts all Replicator processes. If a problem appears, such as that
communication between the restorers is not possible, you do not need to re-initialize after
fixing the problem. Replication should begin as soon as the restorers can communicate.
replication initialize
Procedure: Set Up and Start Bidirectional Replication
To set up and start directory replication for dir2 from hostA to hostB and for dir1 from hostB to
hostA:
•
Run both of the following commands on hostA and hostB:
replication add source dir://hostB/backup/dir1
destination dir://hostA/backup/dir1
•
Run the following command on hostA.
replication initialize dir://hostB/backup/dir2
•
Run the following command on hostB.
replication initialize dir://hostA/backup/dir1
215
Procedure: Set Up and Start Many-to-One Replication
Procedure: Set Up and Start Many-to-One Replication
To set up and start directory replication for directories from hostA and hostB to hostC:
•
Run the following command on hostA and hostC:
destination dir://hostC/backup/dir2
•
Run the following command on hostB and hostC:
replication add source dir://hostB/backup/dir1
destination dir://hostC/backup/dir1
•
Run the following command on hostA.
replication initialize dir://hostC/backup/dir2
•
Run the following command on hostB.
replication initialize dir://hostC/backup/dir1
Procedure: Replace a Directory Source - New Name
If the source (hostA) for directory replication is replaced or changed out, use the following
commands to integrate (with hostB) a new source that uses a new name (hostC).
•
If the new source has any data in the target directories, delete all data from the directories:
•
Run the following commands on the destination:
filesys disable
replication modify dir://hostB/backup/dir2 source-host hostC
replication reauth dir://hostB/backup/dir2
filesys enable
•
Run the following commands on the new source:
replication add source dir://hostC/backup/dir2
replication recover dir://hostB/backup/dir2
•
216
Use the following command to see when the recovery is complete. Note the State entry in the
output. State is normal when recovery is done and recovering while recovery is in progress.
Also, a messages log file entry, replication recovery completed is sent when the process is
complete. The byte count may be equal on both sides, but the recovery is not complete until
data integrity is verified. The recovering directory is read-only until recovery finishes.
Procedure: Replace a Collection Source - Same Name
# replication status dir://hostC/backup/dir2
CTX:
2
Mode:
source
Destination:
dir://hostC/backup/dir2
Enabled:
yes
Local filesystem status:
enabled
Connection:
connected since Sat Apr
State:
recovering
Error:
no error
Destination lag:
less than 5 minutes
Current throttle:
unlimited
8 23:38:11
Procedure: Replace a Collection Source - Same Name
If the source (hostA) for collection replication is replaced or changed out, use the following
commands to integrate (with hostB) a new source that uses the same name as the previous source.
•
If the new source was using the VTL feature, use the following command on the source:
vtl disable
•
If the new source has any data in its file system, run the following command on the source to
clear all data from the file system:
filesys destroy
•
Run the following commands on the destination:
filesys disable
replication reauth
filesys enable
•
Run the following commands on the new source:
replication recover
•
See the last bullet in the previous procedure for checking the progress of the recovery.
217
Procedure: Convert from Collection to Directory
Procedure: Convert from Collection to Directory
Convert a collection replication pair (source is hostA, destination is hostB) to directory replication:
•
Run the following commands on both of the collection replication systems:
filesys disable
replication break col://hostB
filesys enable
•
On the destination, hostB, move everything that is under /backup to /backup/old.
•
Run the following command on both systems:
replication add source dir://hostA/backup
destination dir://hostB/backup/hostA
•
Run the following command on the source system:
replication initialize dir://hostB/backup/hostA
•
After the initialization completes, remove /backup/old.
Procedure: Seeding
A restorer that already holds data in its file system can be used as a source restorer for replication.
Part of setting up replication with such a restorer is to transfer the current data on the source
restorer to the destination restorer. The procedure for the transfer is called seeding. As seeding over
a WAN may need large amounts of bandwidth and time, Data Domain provides alternate seeding
procedures for the following replication configurations:
218
•
One-to-one One source restorer replicates data to one destination restorer. Replication can be
collection or directory type.
•
Bidirectional A source restorer, such as ddr01, replicates data to the destination ddr02. At the
same time, ddr02 is a source for replication to ddr01. Each restorer is a source for its own data
and a destination for the other restorer’s data. Bidirectional replication can be directory
replication only.
•
Many-to-one More than one source restorer replicates data to a single destination restorer.
Many-to-one replication can be directory replication only.
Procedure: Seeding
One-to-One
For collection replication, the destination restorer file system must be empty. In the following
example, ddr01 is the source restorer and ddr02 is the destination.
1. Ship the destination restorer (ddr02) to the source restorer (ddr01) site.
2. Follow the standard Data Domain installation process to install the destination restorer.
3. Connect the restorers with a direct link to cut down on initialization time.
4. Boot up the destination restorer. (The source restorer should already be in service.)
5. Enter the following command on both restorers:
# filesys disable
6. Enter a command similar to the following on both restorers:
# replication add source col://ddr01.company.com
destination col://ddr02.company.com
7. Enter the following command on both restorers:
# filesys enable
8. On the source, enter a command similar to the following. If the source holds a lot of data, the
initialize operation can take many hours.
# replication initialize col://ddr02.company.com
9. Wait for initialization to complete. Output from the replication initialize
command details initialization progress.
10. On the destination, enter the following command:
# system poweroff
11. Move the destination restorer to its permanent location, company2.com in this example.
12. Boot up the destination restorer.
13. On the destination restorer, run the config setup command and make any needed
changes. For example, the system hostname is a fully-qualified domain name that may be
different in the new location.
219
Procedure: Seeding
14. On ddr02, enter commands similar to the following to change the replication destination host
to the new hostname:
# filesys disable
# replication modify col://ddr02.company.com
destination-host ddr02.company2.com
# filesys enable
15. :On ddr01, enter commands similar to the following to change the destination host to the new
hostname:
# filesys disable
# replication modify col://ddr02.company.com
# filesys enable
For directory replication, the source directory must exist and the destination directory must be
empty. In the following example, ddr01 is the source restorer and ddr02 is the destination.
1. Ship the destination restorer (ddr02) to the source restorer (ddr01) site, company.com in this
example.
2. Follow the standard Data Domain installation process to physically install ddr02.
3. Connect the restorers with a direct link to cut down on initialization time.
4. Boot up ddr02. (The source restorer should already be in service.)
5. Configure ddr02 using the standard Data Domain process.
6. Enter a command similar to the following on both restorers:
# replication add source dir://ddr01.company.com/backup/data01
destination dir://ddr02.company.com/backup/data01
7. On ddr01, enter a command similar to the following. If the source holds a lot of data, the
initialize operation can take many hours.
# replication initialize dir://ddr02.company.com/backup/data01
8. Wait for initialization to complete. Output from the replication initialize
command details initialization progress.
220
Procedure: Seeding
9. On ddr02, enter the following command:
# system poweroff
10. Move ddr02 to its permanent location, company2.com in this example.
11. Boot up the destination restorer.
12. On ddr02, run the config setup command and make any needed changes, such as
hostname, which is a fully-qualified domain name that may be different in the new location.
13. On ddr02, enter commands similar to the following to change the replication destination host
to the new hostname:
# filesys disable
# replication modify dir://ddr02.company.com/backup/data01
# filesys enable
14. On ddr01, enter commands similar to the following to change the destination host to the new
hostname:
# filesys disable
# replication modify dir://ddr02.company.com/backup/data01
# filesys enable
Bidirectional
With bidirectional replication, the seeding process uses three restorers: one permanent restorer at
each customer site and one temporary restorer that is physically moved from one site to another.
Bidirectional replication must use directory-type replication. For directory replication, the source
directory must exist and the destination directory must be empty.
The instructions below use the name ddr01 for the first permanent restorer that is replicated, ddr02
for the second permanent restorer that is replicated, and ddr-temp for the restorer that is moved
from one site to another.
Bidirectional replication is done in eight phases:
•
Copy source data from the first permanent restorer (ddr01) to the temporary restorer
(ddr-temp).
•
Move ddr-temp to the site of the second permanent restorer (ddr02).
•
Transfer the ddr01 source data from ddr-temp to ddr02.
221
Procedure: Seeding
•
Setup and start replication between ddr01 and ddr02 for ddr01 source data.
•
Copy the ddr02 source data to ddr-temp
•
Move ddr-temp back to the ddr01 site.
•
Transfer the ddr02 source data to ddr01.
•
Setup and start replication between ddr02 and ddr01 for ddr02 source data.
Copy source data from the first restorer (ddr01):
1. Ship the temporary restorer (ddr-temp) to the ddr01 site, company.com in this example.
2. Follow the standard Data Domain hardware installation process to physically setup ddr-temp.
3. Connect ddr01 and ddr-temp with a direct link to cut down on initialization time.
4. Boot up ddr-temp. (Ddr01 should already be in service.)
5. Configure ddr-temp using the standard Data Domain command config setup.
6. Enter a command similar to the following on both restorers. Note the use of an added temp
directory for the destination.
destination dir://ddr-temp.company.com/backup/temp/data01
7. On ddr01, enter a command similar to the following.
# replication initialize
dir://ddr-temp.company.com/backup/temp/data01
8. Wait for initialization to finish. If ddr01 holds a lot of data, the initialize operation can take
many hours. Output from the replication initialize command details initialization
progress.
9. On ddr01 and ddr-temp, enter commands similar to the following to break replication:
# filesys disable
# replication break
# filesys enable
10. On ddr-temp, enter the following command:
# system poweroff
222
Procedure: Seeding
Move the temporary restorer.
1. Move ddr-temp to the ddr02 site, company2.com in this example.
2. Follow the standard Data Domain hardware installation process to physically set up ddr-temp.
5. On ddr-temp, run the config setup command and make any needed changes, such as
1. Set up replication with ddr-temp as the source and ddr02 as the destination. Enter a command
similar to the following on both ddr-temp and ddr02. Note that the added temp directory is
used for both source and destination.
# replication add
source dir://ddr-temp.company2.com/backup/temp/data01
destination dir://ddr02.company2.com/backup/temp/data01
2. On ddr-temp, enter a command similar to the following to transfer data to ddr02:
dir://ddr02.company2.com/backup/temp/data01
3. Wait for initialization to finish. If ddr-temp holds a lot of data, the initialize operation can take
progress.
4. On ddr-temp and ddr02, enter commands similar to the following to break replication:
# filesys disable
# replication break dir://ddr02.company2.com/backup/temp/data01
# filesys enable
223
Procedure: Seeding
Setup and start replication between ddr01 and ddr02 for data from ddr01. Note that the temp
directory is NOT used for either the source or the destination.
1. Enter a command similar to the following on both ddr01 and ddr02 to set up replication:
# replication add
source dir://ddr01.company.com/backup/data01
destination dir://ddr02.company2.com/backup/data01
2. On ddr01, enter a command similar to the following to initialize replication. The initialization
process should take a short time as the process transfers only metadata and backup application
data that is new since data was transferred to ddr-temp. The metadata goes to the specified
location on ddr02, in this example: /backup/data01. Backup application data that was
transferred from ddr-temp to ddr02 remains on ddr02 and is not replicated again.
# replication initialize dir://ddr02.company2.com/backup/data01
3. Wait for initialization to finish. Output from the replication initialize command
details initialization progress.
4. If ddr-temp has space for the current ddr01 data and space for the ddr02 data, leave ddr-temp as
is. Take into account that any common data between the two data sets gets compressed on
ddr-temp, using less space.
If ddr-temp does not have enough space for both sets of data, mount or map the ddr-temp
directory /backup from another system and delete /temp.
Copy the ddr02 source data to ddr-temp. ddr-temp should still be installed at the ddr02 site and
communicating with ddr02.
1. Enter a command similar to the following on both restorers. Note the use of the added temp
directory for both the source and the destination.
# replication add
source dir://ddr02.company2.com/backup/temp/data02
destination dir://ddr-temp.company2.com/backup/temp/data02
dir://ddr-temp.company2.com/backup/temp/data02
3. Wait for initialization to finish. If ddr02 holds a lot of source data, the initialize operation can
take many hours. Output from the replication initialize command details
initialization progress.
224
Procedure: Seeding
# filesys disable
# replication break
# filesys enable
# system poweroff
Move the temporary restorer.
1. Move ddr-temp back to the ddr01 site.
hostname, which is a fully-qualified domain name that may be different in the current location.
1. Set up replication with ddr-temp as the source and ddr01 as the destination. Enter a command
similar to the following on both ddr-temp and ddr01. Note that the added temp directory is
used for both source and destination.
# replication add
source dir://ddr-temp.company.com/backup/temp/data02
destination dir://ddr01.company.com/backup/temp/data02
2. On ddr-temp, enter a command similar to the following to transfer the ddr02 source data to
ddr01:
dir://ddr01.company.com/backup/temp/data02
progress.
225
Procedure: Seeding
# filesys disable
# replication break dir://ddr01.company.com/backup/temp/data02
# filesys enable
Setup and start replication between ddr02 and ddr01 for data from ddr02. Note that the temp
directory is NOT used for either the source or the destination.
1. Enter a command similar to the following on both ddr02 and ddr01 to set up replication:
# replication add
source dir://ddr02.company2.com/backup/data02
destination dir://ddr01.company.com/backup/data02
location on ddr01, in this example: /backup/data02. Backup application data that was
transferred from ddr-temp to ddr01 remains on ddr01 and is not replicated again.
# replication initialize dir://ddr01.company.com/backup/data02
4. On ddr02, mount or map the directory /backup from another system and delete /temp.
5. On ddr01, mount or map the directory /backup from another system and delete /temp.
Many-to-One
With many-to-one replication, the seeding process uses a temporary restorer to receive data from
each source restorer site. The temporary restorer is physically moved from one source site to
another and then moved to the destination restorer site. Many-to-one replication must use
directory-type replication. For directory replication, the source directory must exist and the
destination directory must be empty.
The instructions below use the name ddr01 for the first restorer that is replicated, ddr02 for the
second restorer that is replicated, ddr-dest for the single destination restorer, and ddr-temp for the
restorer that is moved from site to site.
226
Procedure: Seeding
Many-to-one replication is done in six phases for the example in this section:
•
Copy source data from the first source restorer (ddr01) to the temporary restorer (ddr-temp).
•
Move ddr-temp to the second source restorer (ddr02) site.
•
Copy source data from ddr02 to ddr-temp.
•
Move ddr-temp to the site of the destination restorer (ddr-dest).
•
Transfer the ddr01 and ddr02 source data from ddr-temp to ddr-dest.
•
Setup and start replication between ddr01 and ddr-dest and between ddr02 and ddr-dest.
Copy source data from the first restorer (ddr01):
1. Ship the temporary restorer (ddr-temp) to the ddr01 site, company.com in this example.
5. Configure ddr-temp using the standard Data Domain command config setup.
6. Enter a command similar to the following on both restorers. Note the use of an added temp
directory for the destination.
destination dir://ddr-temp.company.com/backup/temp/data01
progress.
# filesys disable
# replication break
# filesys enable
227
Procedure: Seeding
# system poweroff
Move the temporary restorer to the second (ddr02) source site.
1. Move ddr-temp to the ddr02 site, company2.com in this example.
Copy source data from the second source restorer (ddr02):
1. Enter a command similar to the following on ddr-temp and ddr02. Note the use of an added
temp directory for the destination.
# replication add source dir://ddr02.company2.com/backup/data02
destination dir://ddr-temp.company2.com/backup/temp/data02
progress.
# filesys disable
# replication break
# filesys enable
# system poweroff
228
Procedure: Seeding
Move the temporary restorer to the destination (ddr-dest) site.
1. Move ddr-temp to the ddr-dest site, company3.com in this example.
3. Connect ddr-dest and ddr-temp with a direct link to cut down on initialization time.
4. Boot up ddr-temp. (Ddr-dest should already be in service.)
Transfer the ddr01 and ddr02 source data from ddr-temp to ddr-dest.
1. Set up a replication context with ddr-temp as the source and ddr-dest as the destination. Enter a
command similar to the following on both ddr-temp and ddr-dest. Note that the added temp
directory is used for both sources and destinations.
# replication add
source dir://ddr-temp.company3.com/backup/temp
destination dir://ddr-dest.company3.com/backup/temp
2. On ddr-temp, enter a command similar to the following to transfer the ddr01 and ddr02 source
data to ddr-dest:
dir://ddr-dest.company3.com/backup/temp
progress.
4. On ddr-dest and ddr-temp, enter commands similar to the following to break replication:
# filesys disable
# replication break
dir://ddr-dest.company3.com/backup/temp
# filesys enable
229
Procedure: Seeding
Setup and start replication between ddr01 and ddr-dest and between ddr02 and ddr-dest. Note that
the temp directory is NOT used for either the sources or the destinations.
1. Enter a command similar to the following on both ddr01 and ddr-dest to set up ddr01
replication:
# replication add
source dir://ddr01.company.com/backup/data01
destination dir://ddr-dest.company3.com/backup/data01
2. Enter a command similar to the following on both ddr02 and ddr-dest to set up ddr02
replication:
# replication add
source dir://ddr02.company2.com/backup/data02
destination dir://ddr-dest.company3.com/backup/data02
location on ddr-dest, in this example: /backup/data01. Backup application data that was
transferred from ddr-temp to ddr-dest remains on ddr-dest and is not replicated again.
dir://ddr-dest.company3.com/backup/data01
location on ddr-dest, in this example: /backup/data02. Backup application data that was
transferred from ddr-temp to ddr-dest remains on ddr-dest and is not replicated again.
dir://ddr-dest.company3.com/backup/data02
6. On ddr-dest, mount or map the directory /backup from another system and delete the
temporary directory.
230
Backup/Restore Using NDMP
18
The NDMP (Network Data Management Protocol) feature allows direct backup and restore
operations between an NDMP Version 2 data server (such as a Network Appliance™ filer with the
ndmpd daemon turned on), and a restorer. NDMP software on the restorer acts, through the
command line interface, to provide Data Management Application (DMA) and NDMP server
functionality for the filer. The ndmp command on the restorer manages NDMP operations.
Add a Filer
To add to the list of filers available to the restorer, use the ndmp add operation. The user name is
a user on the filer and is used by the restorer when contacting the filer. The password is for the user
name on the filer. With no password, the command returns a prompt for the password. Note that
any add operation for a filer name that already exists replaces the complete entry for that filer name.
A password can include any printable character. Administrative users only.
ndmp add filer_name user username [password password]
For example, to add a filer named toaster5 using a user name of back2 with a password of pw1212:
# ndmp add toaster5 user back2 password pw1212
Remove a Filer
To remove a filer from the list of servers available to the restorer, use the ndmp delete
ndmp delete filer_name
For example, to delete a filer named toaster5:
# ndmp delete toaster5
231
Backup from a Filer
Backup from a Filer
To backup data from a filer to a file on a restorer, use the ndmp get operation. Administrative
users only.
ndmp get [incremental level] filer_name:src_path dst_path
filer_name The name of the filer that holds the information for the backup operation.
src_path The directory to backup from the filer.
dst_path The destination file for the backup data on the restorer.
incremental level The numeric level for an incremental backup using a number between 0
(zero) and 9. Using any level greater than 0 backs up only changes since the latest previous backup
of the same src_path with a lower numbered level. Using the get operation without the
incremental option is the same as a level 0, or full, backup.
For example, the following command opens a connection to a filer named toaster5 and returns all
data under the directory /vol/vol0. The data is stored in a file located at
/backup/toaster5/week0 on the restorer.
# ndmp get toaster5:/vol/vol0 /backup/toaster5/week0
The following incremental backup backs up changes since the last full backup.
# ndmp get incremental 1 toaster5:/vol/vol0 \
/backup/toaster5/week0.day1
Restore to a Filer
To restore data from a restorer to a filer, use one of the ndmp put operations. Note that a filer may
report a successful restore even when one or more files failed restoration. For details, always
review the LOG messages sent by the filer. Administrative users only.
ndmp put src_file filer_name:dst_path
ndmp put partial src_file subdir filer_name:dst_path
partial Restore a particular directory or file from within a backup file on the restorer. Give the
path to the file or subdirectory.
src_file The file on the restorer from which to do a restore to a filer. The src_file argument
must always begin with /backup.
filer_name The NDMP server to which to send the restored data.
232
Remove Filer Passwords
dst_path The destination for the restored data on the NDMP server. Some filers require that
subdir be relative to the path used during the ndmp get that created the backup. For example, if
the get operation was for everything under the directory /a/b/c in a tree of /a/b/c/d/e, then
the put partial subdirectory argument should start with /d. On some filers, dst_path must end
with subdir.
The following command restores data from the restorer file /backup/toaster5/week0 to
/vol/vol0 on the filer toaster5.
# ndmp put /backup/toaster5/week0 toaster5:/vol/vol0
The following command restores the file .../jsmith/foo from the week0 backup.
# ndmp put partial jsmith/foo /backup/toaster5/week0
toaster5:/vol/vol0/jsmith/foo
Remove Filer Passwords
To remove all filer entries, including the associated user names and passwords stored on the
restorer, and to write zeros to the disk areas that held them, use the ndmp reset filers
ndmp reset filers
Stop an NDMP Process
To stop an NDMP process on the restorer, use the ndmp stop operation. The pid is the PID
(process ID) number shown for the process in the ndmp status display. A stopped process is
cancelled. To restart a process, begin the process again with the get or put commands.
ndmp stop pid
Stop All NDMP Processes
To stop all NDMP processes on a restorer, use the ndmp stop all operation. Administrative
users only.
ndmp stop all
Chapter 18: Backup/Restore Using NDMP
233
Check for a Filer
Check for a Filer
To check that a filer is known, use the ndmp test operation to display a filer authentication
token.
ndmp test filer
Display Known Filers
To display all filers available to the restorer, use the show filers operation. Administrative
users only.
ndmp show filers
For example:
# ndmp show filer
filer
name:password
------------------filer1
root:******
filer2
root:******
toaster
root:******
Display NDMP Process Status
To display the status of current NDMP processes on the restorer, use the ndmp status operation.
The operation labels each process with an identification number. Administrative users only.
ndmp status
The display looks similar to the following and shows the process ID, the command that is currently
running, and the total number of megabytes transferred. The following example shows the
command entered twice in a row. Note that MB Copied shows the progress of the operation.
# ndmp status
PID MB Copied
--- -------715 3267
Command
------------------------------------------------get filer1:/vol/vol0/etc /backup/filer1/dumpfile1
# ndmp status
PID MB Copied
--- --------715 4219
234
Command
------------------------------------------------get filer1:/vol/vol0/etc /backup/filer1/dumpfile1
SNMP Management and Monitoring
19
The SNMP (Simple Network Management Protocol) feature allows a restorer to respond to a set of
SNMP “get” operations from a remote machine. From an SNMP perspective, a restorer is a
read-only device with the following exceptions: A remote machine can set the SNMP location,
contact, and system name on a restorer. To configure community strings, hosts, and other SNMP
variables on the restorer, use the snmp command. With one or more trap hosts defined, a restorer
takes the additional action of sending alerts messages as SNMP traps, even when the SNMP agent
is disabled.
Note The SNMP sysLocation and sysContact variables are not the same as those set with the
config set location and config set admin-email commands. However, if
the SNMP variables are not set with the SNMP commands, the variables default to the
system values given with the config set commands.
Enable SNMP
To enable the SNMP agent on a restorer, use the snmp enable operation. The default port that is
opened when SNMP is enabled is port 161. Traps are sent to port 162. Administrative users only.
snmp enable
Disable SNMP
To disable the SNMP agent on a restorer, use the snmp disable operation. Ports 161 and 162
are closed. Administrative users only.
snmp disable
235
Set the System Location
Set the System Location
To set the system location as used in the SNMP MIB II System variable sysLocation, use the snmp
set sysLocation operation. Administrative users only.
snmp set sysLocation location
For example, to give a location of bldg3-rm222:
# snmp set sysLocation bldg3-rm222
Reset the System Location
To reset the system location to the system value displayed by the command system show
location or an empty string if the system value is empty, use the snmp reset
sysLocation operation. Administrative users only.
snmp reset sysLocation
Set a System Contact
To set the system contact as used in the SNMP MIB II System variable sysContact, use the snmp
set sysContact operation. Administrative users only.
snmp set sysContact contact
For example, to give a contact of bob-smith:
# snmp set sysContact bob-smith
Reset a System Contact
To reset the system contact to the system value displayed by the command system show
admin-email or an empty string if the system value is empty, use the snmp reset
sysContact operation. Administrative users only.
snmp reset sysContact
236
Add a Trap Host
Add a Trap Host
To add a trap host to the list of machines that receive SNMP traps generated by the restorer, use the
snmp add trap-host operation. With one or more trap hosts defined, alerts messages are also
sent as traps, even when the SNMP agent is disabled. Administrative users only.
snmp add trap-host hostname
For example, to add a trap host admin12:
# snmp add trap-host admin12
Delete a Trap Host
To delete one or more trap hosts from the list of machines that receive SNMP traps generated by the
restorer, use the snmp del trap-host operation. Administrative users only.
snmp del trap-host hostname
For example, to delete a trap host admin12:
# snmp del trap-host admin12
Delete All Trap Hosts
To return the trap hosts list to the default of empty, use the snmp reset trap-host operation.
snmp reset trap-hosts
Add a Community String
To add one or more community strings that enable access to a restorer, use one of the snmp add
community operations. One operation gives read/write permissions and one gives read-only
permission. A common string for read/write access is private. A common string for read-only
access is public. Administrative users only.
snmp add rw-community community-string
snmp add ro-community community-string
For example, to add a community string of private with read/write permissions:
# snmp add rw-community private
Chapter 19: SNMP Management and Monitoring
237
Delete a Community String
Delete a Community String
To delete one or more community strings that enable access to a restorer, use one of the snmp del
community operations. One operation deletes community strings that have read/write
permissions and one deletes those that have read-only permission. Administrative users only.
snmp del rw-community community-string
snmp del ro-community community-string
For example, to delete the community string private that gives read/write permissions:
# snmp del rw-community private
Delete All Community Strings
To return the community strings lists to the defaults of empty, use one of the snmp reset
community operations. One operation resets the read/write permissions list and one resets the
read-only permissions list. Administrative users only.
snmp reset rw-community
snmp reset ro-community
Reset All SNMP Values
To return all SNMP values to the defaults, use the snmp reset operation. Administrative users
only.
snmp reset
Display SNMP Agent status
The status of the SNMP agent on the restorer is either enabled or disabled.
Display
To display the status of the SNMP agent on a restorer (enabled or disabled), use the snmp
status operation o click SNMP in the left panel of the Data Domain Enterprise Manager.
snmp status
238
Display Trap Hosts
Display Trap Hosts
To display the trap host list on a restorer, use the snmp show trap-hosts operation.
snmp show trap-hosts
The output is similar to the following:
# snmp show trap-hosts
Trap Hosts:
admin10
admin11
Display All Parameters
The SNMP configuration entries set by an administrator are:
•
sysLocation The system location as used in the SNMP MIB II System variable sysLocation.
•
sysContact The system contact as used in the SNMP MIB II System variable sysContact.
•
Trap Hosts The list of machines that receive SNMP traps generated by the restorer.
•
Read-only Communities One or more read-only community strings that enable access to the
restorer
•
Read-write Communities One or more read-write community strings that enable access to the
restorer.
Display
To display all of the SNMP parameters, use the snmp show config operation. Administrative
users only.
snmp show config
# snmp show config
---------------------SNMP sysLocation
SNMP sysContact
Trap Hosts
Read-only Communities
Read-write Communities
----------------------
Chapter 19: SNMP Management and Monitoring
------------------bldg3-rm222
[email protected]
admin10 admin11
public snmpadmin23
private snmpadmin1
-------------------
239
Display the System Contact
Display the System Contact
To display the system contact on a restorer, use the snmp show sysContact operation.
snmp show sysContact
Display the System Location
To display the system location on a restorer, use the snmp show syslocation operation.
snmp show sysLocation
Display Community Strings
To display the community strings on a restorer, use one of the snmp show communities
operations. Administrative users only.
snmp show rw-communities
snmp show ro-communities
# snmp show rw-communities
RW Community Strings:
private
snmpadmin1
Display the MIB and Traps
The MIB display formats the complete management information base and SNMP traps. The traps
are listed at the end of the file under the tag Common Notifications.
You can download the MIB is by mounting the restorer /ddvar directory from another system.
Use any SNMP MIB browser to view the downloaded MIB. The MIB location and name are:
/ddvar/snmp/mibs/DATA_DOMAIN.mib
To view the MIB in the Data Domain Enterprise Manager graphical user interface, select SNMP
from the left panel and find the SNMP MIB files section. Click on the DATA DOMAIN.mib link.
240
Log File Management
20
The log command allows you to view restorer log file entries and to save and clear the log file
contents. Messages from the alerts feature, the autosupport reports, and general system
messages go to the log directory and into the file messages. A log entry appears for each restorer
command given on the system. The log directory is /ddvar/log.
Every Sunday at 3 a.m., the restorer automatically opens new log files and renames the previous
files with an appended number of 1 (one) through 9, such as messages.1. Each numbered file is
rolled to the next number each week. For example, at the second week, the file messages.1 is
rolled to messages.2. If a file messages.2 already existed, it would roll to messages.3.
An existing messages.9 is deleted when messages.8 is rolled to messages.9. See
“Procedure: Archive Log Files” on page 245 for instructions on saving log files.
Scroll New Log Entries
To display a view of the messages file that adds new entries as they occur, use the watch
operation. Use the key combination <Control> c to break out of the watch operation. With no
filename, the command displays the current messages file.
log watch [filename]
Send Log Messages to Another System
Some log messages can be sent outside of a restorer to other systems. A restorer exports the
following facility.priority selectors for log files. For managing the selectors and receiving messages
on a third-party system, see your vendor-supplied documentation for the receiving system.
•
*.notice Sends all messages at the notice priority and higher.
•
*.alert Sends all messages at the alert priority and higher (alerts are included in *.notice).
•
kern.* Sends all kernel messages (kern.info log files).
•
local7.* Sends all messages from system startups (boot.log files).
The log host commands manage the process of sending log messages to another system:
241
Send Log Messages to Another System
Add a Host
To add a system to the list that receives restorer log messages, use the log host add command.
log host add host-name
For example, the following command adds the system log-server to the hosts that receive log
messages:
# log host add log-server
Remove a Host
To remove a system from the list that receives restorer log messages, use the log host del
command.
log host del host-name
For example, the following command removes the system log-server from the hosts that receive log
messages:
# log host del log-server
Enable Sending Log Messages
To enable sending log messages to other systems, use the log host enable command.
log host enable
Disable Sending Log Messages
To disable sending log messages to other systems, use the log host disable command.
log host disable
Reset to Default
To reset the log sending feature to the defaults of an empty list and disabled, use the log host
reset command.
log host reset
242
Display a Log File
Display the List and State
To display the list of systems that receive log messages and the state of enabled or disabled, use he
log host show command.
log host show
# log host show
Remote logging is enabled.
Remote logging hosts
log-server
Display a Log File
To view the log files, use the log view operation. With no filename, the command displays the
current messages file. When viewing the log, use the up and down arrows to scroll through the
file; use the q key to quit; enter a slash character (/) and a pattern to search through the file.
log view [filename]
The display of the messages file is similar to the following. The last message in the example is an
hourly system status message that the restorer generates automatically. The message reports system
uptime, the amount of data stored, NFS operations, and the amount of disk space used for data
storage (%). The hourly messages go to the system log and to the serial console if one is attached.
# log view
Jun 27 12:11:33 localhost rpc.mountd: authenticated unmount
request from perfsun-g.datadomain.com:668 for /ddr/col1/segfs
(/ddr/col1/segfs)
Jun 27 12:28:54 localhost sshd(pam_unix)[998]: session opened
for user jsmith10 by (uid=0)
Jun 27 13:00:00 localhost logger: at 1:00pm up 3 days, 3:42,
52324 NFS ops, 84763 GB data col. (1%)
Chapter 20: Log File Management
243
List Log Files
List Log Files
The basic log files are:
access Tracks users of the Data Domain Enterprise Manager graphical user interface.
boot.log Kernel diagnostic messages generated during the booting up process.
ddfs.info Debugging information created by the file system processes.
ddfs.memstat Memory debugging information for file system processes.
destroy.id_number.log All of the actions taken by an instance of the filesys
destroy command. Each instance produces a log with a unique ID number.
disk-error-log Disk error messages.
error Lists errors generated by the Data Domain Enterprise Manager operations.
kern.error Kernel error messages.
kern.info Kernel information messages.
messages The system log, generated from restorer actions and general system operations.
network Messages from network connection requests and operations.
perf.log Performance statistics used by Data Domain support staff for system tuning.
secure Messages from unsuccessful logins and changes to user accounts. (Not shown in the
graphical user interface.)
space.log Messages about disk space use by restorer components and data storage, and
messages from the clean process. A space use message is generated every hour. Each time the
clean process runs, it creates about 100 messages. All the messages are in comma-separatedvalue format with tags that you can use to separate out the disk space or clean messages. You can
use third-party software to analyze either set of messages. The tags are:
CLEAN for data lines from clean operations.
CLEAN_HEADER for lines that contain headers for the clean operations data lines.
SPACE for disk space data lines.
SPACE_HEADER for lines that contain headers for the disk space data lines.
ssi_request Messages from the Data Domain Enterprise Manager when users connect with
HTTPS.
windows Messages about CIFS-related activity from CIFS clients attempting to connect to the
restorer.
244
Procedure: Archive Log Files
Display
To list all of the files in the log directory, use the log list operation or click Log Files in the
left panel of the Data Domain Enterprise Manager.
log list
The list is similar to the following:
# log list
Last modified
----------------------Tue May 24 12:15:01 2005
Wed May 25 00:28:27 2005
Wed May 25 08:43:03 2005
Sun May 22 03:00:01 2005
Sun May 15 03:00:00 2005
Size
----3 KB
933 KB
42 KB
70 KB
111 KB
File
------------boot.log
ddfs.info
messages
messages.1
messages.2
To archive log files, use FTP to copy the files to another machine.
1. On the restorer, use the adminaccess show ftp command to see that the FTP service is
enabled. If the service is not enabled, use the command adminaccess enable ftp.
2. On the restorer, use the adminaccess show ftp command to see that the FTP access list
has the IP address of your remote machine or a class-C address that includes your remote
machine. If the address is not in the list, use the command adminaccess add ftp
<ipaddr>.
3. On the remote machine, open a web browser.
4. In the Address box at the top of the web browser, use FTP to access the restorer. For example:
ftp://restorer_name.yourcompany.com/
Note Some web browsers do not automatically ask for a login if a machine does not accept
anonymous logins. In that case, add a user name and password to the FTP line. For example:
ftp://sysadmin:your-pw@restorer_name.yourcompany.com/
5. At the login popup, log into the restorer as user sysadmin.
6. On the restorer, you are in the directory just above the log directory. Open the log directory
to list the messages files.
Chapter 20: Log File Management
245
7. Copy the file that you want to save. Right-click on the file icon and select Copy To Folder from
the menu. Choose a location for the file copy.
8. If you want the FTP service disabled on the restorer, use SSH to log into the restorer as
sysadmin and give the command adminaccess disable ftp.
246
Hardware Servicing
21
Replacement of components in a restorer falls into two categories: general customer operations and
trained service personnel operations. Replacing parts in the second category requires an awareness
of electrical shock hazards and, in the case of cooling fans, possible mechanical hazards from
rotating fan blades.
Caution If the internal batteries on the adapter cards fail or internal fuses in the system fail,
return the equipment to the manufacturer. The components are not to be serviced in the
field.
Customer Operations
Customers can replace disks and power supplies in a restorer. Data Domain recommends timely
replacement of components that generate error log messages for failures or are out of normal
operating tolerances. Check with Data Domain Support staff for what constitutes excessive error
messages and out-of-range operating tolerances. After an error message, a component can continue
to degrade, leading to an automatic system shutdown. For example, the restorer generates a
warning message if the interior temperature of the machine reaches 47 degrees centigrade. If the
temperature reaches 50 degrees centigrade, the machine shuts down.
As an addition to error log messages, you can check components by using the restorer command
alerts show current, which includes messages about power supplies, disks, temperature
extremes, and fans if anything is not within system specifications.
Note If you see messages for components that are not replaced as a customer operation, contact
the Data Domain field or Support staff.
•
The Temperature Extremes... summary displays information about CPU
temperatures and contains an entry if the overall machine temperature is above an acceptable
level.
-
If the overall temperature for the machine reaches 47 degrees centigrade, a warning
message is generated. If the temperature reaches 50 degrees centigrade, the machine shuts
down.
247
Customer Operations
•
If a CPU temperature reaches 60 degrees centigrade, a warning message is generated. If a
CPU temperature reaches 74 degrees centigrade, the machine shuts down.
If one or more fans have failed or are running below the minimum required speed, the Fan
Failure ... summary lists the failed or failing fans. To replace a fan, see “Replace Fans”
on page 256.
Replace Disks
Note Use only Data Domain Field Replaceable Units. Do not use disks from other sources. Spare
disks are supplied in a carrier for a restorer or a carrier for an expansion shelf. DO NOT
move a disk from one carrier to another.
Data Domain recommends timely replacement of components that generate excessive error log
messages or that are out of normal operating tolerances. To display details for disk hardware status,
use the disk show reliability-data command. The display is similar to the following:
# disk show reliability-data
Disk
ATA Bus
Command
Command Drive
Soft Err Timeouts Faults Soft Err
------ -------- -------- ------- -------disk1
0
0 0/ 0/ 0
0/
0
disk2
0
0 0/ 0/ 0
0/
0
disk3
0
0 0/ 0/ 0
0/
0
disk4
0
0 0/ 0/ 0
1/
0
.
.
.
Awaiting
Realloc
------0
0
0
0
Already
Realloc
------0
1
0
0
Temp
----28 C
35 C
30 C
27 C
The Already Realloc column indicates the end of the useful disk lifetime when the value
approaches the vendor-specific limit. The limit is 2000 for Maxtor Western Digital disks. Use the
disk show hardware command to display the disk vendor.
A restorer has either 8 or 15 disks, depending on the model. Each disk has two LEDs at the bottom
of the disk carrier. The right LED on each disk flashes green whenever the system accesses the
disk. The left LED glows red when the disk has failed. Both LEDs are dark on the disk that is
available as a spare. A system maintains data integrity of all data in the file system with a
maximum of two failed disks.
248
Customer Operations
Figure 28 shows disk numbering as seen from the front of the restorer: 1 through 15, left to right.
The numbering for models with 8 disks also starts with disk 1 at the left of the front of the restorer.
Models with 8 disks include a blank faceplate that covers the area shown as disks 9 through 15 in
Figure 28.
Power
button
1 2 3 4
5
6 7 8
9 10 11 12 13 14 15
Figure 28: Disk numbering
Note Return the failed/replaced disk to Data Domain. Reuse the packaging from the new disk and
use the included prepaid waybill for shipping. Reference the RMA number on the outside of
the package. Returns with no RMA number cannot be accepted.
The system assigns a disk state to a replacement disk depending on the history of the disk. Use the
disk show raid-info to display the state of all disks.
•
A Data Domain Field Replaceable Unit disk is labeled as Spare.
•
A failed disk that is removed and reinserted into the system is recognized as a failed disk and is
labeled as Failed.
•
A disk that was on another restorer as a spare retains the state of Spare.
•
A disk that was on another restorer and that contained data is seen as Foreign. Use the disk
unfail command to move the disk to the state of Spare.
To replace a failed disk:
1. If a disk is not marked as Failed in output from the disk show raid-info command, use
the following command (with the correct disk-id) to fail the disk.
# disk fail disk-id
2. Identify the physical disk. The left LED on a failed disk is red. You can also use the following
commands to identify a disk by name and then to flash the LED on the disk:
# disk beacon disk-id
3. Remove the replacement disk from the packaging and remove the antistatic bag from the disk.
Chapter 21: Hardware Servicing
249
Customer Operations
4. Put the antistatic bag on a flat surface and set down the replacement disk on the antistatic bag.
5. On the failed disk, push down on the disk’s locking tab to unhook the handle. See Figure 29.
Handle
Locking tab
Figure 29: Locking tab
6. Pull on the handle to slide the disk out about an inch, until it unseats from the harness.
7. Wait for about 30 seconds for the disk to spin down and the heads to park and lock. Treat a
failed disk carefully when removing the disk from the system and when shipping the disk back
to Data Domain.
8. Gently remove the failed disk.
9. On the replacement disk, make sure that the handle is unlocked. Push down the locking tab if
needed. See Figure 29.
10. With the handle remaining in the unlocked position, gently slide the replacement disk into the
chassis until it stops short of being fully installed. Excessive force may damage the
replacement disk.
11. The disk stops short because a lip on the bottom of the disk carrier meets a ridge near the back
of the slot. Tilt the disk carrier so that the back of the carrier is tilted up to clear the ridge and
slide the disk into the slot until you feel resistance.
12. Close the handle as you push the disk the rest of the way into the chassis. Be sure that the disk
seats securely.
13. Use the following command (with the proper disk ID for the replaced disk) to move the disk to
a known state:
# disk unfail disk-id
250
Customer Operations
14. Use the following command to check that the disk is recognized by the restorer. In the
command display, the disk State should be hot spare or the Additional Status should be
reconstructing.
15. Return the removed disk in the antistatic bag and other packaging from the replacement disk.
Copy the RMA number onto the packaging.
Replace Power Units
A restorer has three power supply units that are accessible from the back panel of the chassis (see
Figure 30). A restorer needs a minimum of two functional power units to power up and to run.
Always replace a failed power unit as soon as possible.
The alerts show current command includes a message if a power unit fails. The system
status command includes a line that gives the status of power supplies. To identify the failed
unit, look at the back panel of the machine, and check the LED on each unit.
Power
units
Figure 30: Power units
Each power unit has an LED that glows green when the unit is functional. The LED glows orange if
the unit has failed, but still has power. The LED is completely off if the unit has no power. In
Figure 30, the pointers to the power units end at the LEDs near the top of each unit. Also, when a
unit fails, the power unit failure LED on the front panel of the system glows red. See Figure 31 on
page 252.
251
Customer Operations
Power unit failure
indicator
Figure 31: Power unit failure indicator on the front panel
Note Return the failed/replaced power unit to Data Domain. Reuse the packaging from the new
unit and use the included prepaid waybill for shipping. Reference the RMA number on the
outside of the package. Returns with no RMA number cannot be accepted.
Power units can be replaced while the system is running. As long as two power units are functional,
you do not have to power-down the system. To replace a power unit:
1. Look at the power unit LEDs to determine which unit failed.
2. If your system has the power cord retainer brackets, pinch the two “wings” on the power cord
retainer bracket and slide the bracket back off of the power cord plug. See Figure 32.
Note To receive the optional power cord retainer kit, contact your Data Domain representative.
Retainer
bracket
wings
Figure 32: Power cord retainer bracket
252
Customer Operations
3. Remove the power cord. Push the locking lever to the right, pull on the power unit handle, and
slide out the unit as shown in Figure 33.
Locking lever
Handle
Figure 33: Remove a power unit
4. Slide in the new unit. When the unit is nearly completely in the slot, grasp the handle and push
in the unit with enough force to seat the unit into the frame. Make sure that the unit is seated
securely and that it lines up with the other power units.
5. Attach the power cord.
6. Slide the power cord retainer bracket over the cord.
7. If your system has the power cord retainer brackets, pinch the two “wings” on the bracket and
slide the bracket down over the power cord plug until the bracket is flush with the back of the
power unit. The wings secure the plug by clicking into the power unit handle brackets. See
Figure 34 on page 254.
253
Trained Service Personnel Operations
Power unit handle brackets
Retainer
bracket
wings
Figure 34: Replace a power cord retainer bracket
8. Check that the LED glows green.
9. Enter the system show status command. Look for the following line in the output:
All power supply modules operating normally.
10. Return the removed power unit in the packaging from the replacement unit. Each failed unit is
evaluated to find the reason for the failure. Copy the RMA number onto the packaging.
Caution Only trained and qualified personnel should install or replace equipment in this section.
Replacement procedures in this section require an awareness of electrical shock hazards
and, in the case of cooling fans, possible mechanical hazards from rotating fan blades.
Remove/Replace the Top Panel
You must remove the restorer top panel to access all replacement parts other than power supply
units and disks. If the restorer is in a rack with another box directly above, the restorer may need to
be removed from the rack to remove the top panel. Always use two people when moving a restorer,
as the system weighs 88 pounds (40 kilograms).
The only tool needed to remove and replace a top panel is a Phillips #2 screwdriver.
254
To remove the top panel:
1. Remove the two screws that lock to top panel onto the chassis. The screws are located in the
top-panel lip that folds over the sides of the chassis, 6 inches (about 15 cm.) from the front of
the chassis. See Figure 35.
2. Push down on and hold in the two release buttons that secure the top panel to the chassis.
Top panel release buttons
Top panel
Screw
Screw
Figure 35: Top panel screws and release buttons
3. From the back of the system, slide back the top panel by pulling on the rolled edge of the top
panel that hangs over the back panel. See Figure 36. The top panel slides back about an inch.
Rolled edge
Figure 36: Top panel rolled edge
255
4. Pull up the top panel. When another box is directly above, firmly grasp the rolled edge at the
back of the top panel and lift the panel up about two inches to clear internal stops.
To replace the top panel:
1. Keep the top panel about two inches above the restorer while positioning the panel above the
restorer and back about an inch from where the top panel will be when completely replaced.
2. Lower the top panel and push it forward until the two release buttons at the front catch.
3. Secure the top panel with the two screws that you removed to allow removal of the panel.
Replace Fans
Note Shut down the system before replacing a fan. If a fan does not slide smoothly out of the
chassis, the resulting sharp movement may damage disks.
A restorer has two sets of fans. Use the system show fans command to check on the fans. To
see the fans, remove the restorer top panel.
Looking from the front of the restorer, the first fan set is four fans in a rack just behind the disks
and across the width of the box. The fans in the rack cool the disks. The fans are numbered from 1
to 4 from left to right as viewed from the front of the machine. See Figure 37 on page 257.
The second fan set is two fans on the back panel, as shown in Figure 37 on page 257. Back panel
fans are numbered 1 and 2 from left to right as viewed from the front of the restorer.
256
Back panel fan 2
Back panel fan 1
Disk fan 4
Disk fan 3
Disk fan 2
Disk fan 1
Figure 37: Fan locations
Replace Disk Fans
Disk fans are numbered 1 through 4 from left to right as viewed from the front of the restorer. You
can replace disk fans while the restorer is running. To replace disk fans:
1. Check the system show fans command output to determine which fan failed.
# system show fans
Fan
Description
----------------1
Crossbar fan #1
2
Crossbar fan #2
3
Crossbar fan #3
4
Crossbar fan #4
Current RPM
----------4967
0
4913
4825
Normal
-----4500
4500
4500
4500
Delta
----467
4500
413
325
Status
-----ok
Failed
ok
ok
2. Remove the restorer top panel.
3. On the failed fan, find the locking tab on the left side of the fan frame. Push the locking tab to
the right and pull up on the frame tab on the top of the fan frame. See Figure 38 on page 258.
257
Locking tab
Frame tab
Figure 38: Tabs on a disk fan
4. Pull the fan out of the rack as shown in Figure 39.
Figure 39: Disk fan pulled out of the rack
5. Note the power plug at the bottom of the fan rack.
258
6. Position the replacement fan with the plastic grill facing toward the front of the machine and
the power plug facing down.
7. Slide the fan into the rack making sure that the power plug seats securely. The fan frame
should line up with the other frames in the rack.
8. Replace the top panel.
9. Restart the system if you shut down the system for the replacement procedure.
10. Use the system show fans command to check the fan speed, which confirms that the
replacement is working.
Replace Back Panel Fans
Back panel fans are numbered 5 and 6 from left to right as viewed from the front of the restorer. To
remove a fan:
1. Check the system show fans command output to determine which fan failed.
# system show fans
Fan
Description
----------------1
Crossbar fan #1
2
Crossbar fan #2
3
Crossbar fan #3
4
Crossbar fan #4
5
Rear fan #1
6
Rear fan #2
-----------------
Current RPM
----------4967
4913
4791
4825
0
5060
-----------
Normal
-----4500
4500
4500
4500
4500
4500
------
Delta
----467
413
291
325
4500
560
-----
Status
-----ok
ok
ok
ok
Failed
ok
------
2. Remove the restorer top panel.
3. On the failed fan, find the locking tab on the right side of the fan frame. Push the locking tab to
the left and pull up on the frame tab on the top of the fan frame. See Figure 40 on page 260.
259
Locking tab
Frame tab
Figure 40: Tabs on a back panel fan
4. Note the power plug on the side of the fan rack.
5. Position the replacement fan with the plastic grill facing toward the front of the system and the
power plug facing down. See Figure 41.
Figure 41: Back panel fan lined up for replacement
260
6. Slide the fan into the rack making sure that the power plug seats securely. The fan frame
should line up with the frame of the other fan.
8. Restart the system if you shut down the system for the replacement procedure.
9. Use the system show fans command to check the fan speed, which confirms that the
replacement is working.
Replace the Motherboard Battery
The lithium battery on the motherboard should not need replacement. In the unusual case of a
battery failure, the disk controller in peripheral card slot two and optional gigabit Ethernet NIC in
slot three must be removed to reach the battery. Figure 42 shows the battery location in the back left
corner of the system. The figure does not show the peripheral cards that are usually in place over
the battery.
Battery
Figure 42: Motherboard battery
1. Shut down the system with the system poweroff command.
2. Remove all three power cords.
3. Remove the system top panel.
Caution Make sure that all three power cords are removed from the system.
261
4. Remove the peripheral cards that block access to the battery. Use an ESD cable to protect the
cards from static electricity.
-
Each card has a mounting bracket that folds over the top edge of the back panel. Each
mounting bracket is held onto the back panel with a screw.
-
Carefully note which card is installed in which slot.
-
Remove the screw from the bracket for each card that needs to be removed and gently pull
out the card.
Figure 43 is a schematic showing the numbers and locations of the peripheral card slots. Note
that in slot 3, a restorer can have either an HBA card for the VTL feature or the optional gigabit
Ethernet card, but not both
Back
Front
Figure 43: Peripheral card slots.
5. Push back the battery locking tab (the small tab facing the front of the system.) to release the
battery. Remove the battery.
6. Press the replacement battery into the battery frame so that the locking tab clicks into place.
7. Replace the application cards.
262
-
Match each card with the proper slot.
-
Line up each card’s mounting bracket facing the rear of the chassis and line up the bottom
edge of the card over the slot.
-
Firmly push the each card into its slot.
-
Confirm that all cards are seated. Check the mounting bracket positions and heights.
-
Using the bracket mounting screws, secure the brackets to the chassis.
9. Re-install the three power cords.
10. Restart the system.
Caution A risk of explosion exists if the battery is replaced by an incorrect type. Dispose of used
batteries according to the manufacturer’s instructions.
263
264
Appendix A: Time Zones
Africa
Africa/Abidjan
Africa/Accra
Africa/Addis_Ababa
Africa/Algiers
Africa/Asmera
Africa/Bamako
Africa/Bangui
Africa/Banjul
Africa/Bissau
Africa/Blantyre
Africa/Brazzaville
Africa/Bujumbura
Africa/Cairo
Africa/Casablanca
Africa/Conakry
Africa/Dakar
Africa/Dar_es_Salaam Africa/Djibouti
Africa/Douala
Africa/Freetown
Africa/Gaborone
Africa/Harare
Africa/Johannesburg
Africa/Kampala
Africa/Khartoum
Africa/Kigali
Africa/Kinshasa
Africa/Lagos
Africa/Libreville
Africa/Lome
Africa/Luanda
Africa/Lumumbashi
Africa/Lusaka
Africa/Malabo
Africa/Maputo
Africa/Maseru
Africa/Mbabane
Africa/Mogadishu
Africa/Monrovia
Africa/Nairobi
Africa/Ndjamena
Africa/Niamey
Africa/Nouakchott
Africa/Ouagadougou
Africa/Porto-Novo
Africa/Sao_Tome
Africa/Timbuktu
Africa/Tripoli
Africa/Tunis
Africa/Windhoek
America
America/Adak
America/Anchorage
America/Anguilla
America/Antigua
America/Aruba
America/Asuncion
America/Atka
America/Barbados
America/Belize
America/Bogota
America/Boise
America/Buenos_Aires
America/Caracas
America/Catamarca
America/Cayenne
America/Cayman
America/Chicago
America/Cordoba
America/Costa_Rica
America/Cuiaba
America/Curacao
America/Dawson
America/Dawson_Creek America/Denver
America/Detroit
America/Dominica
America/Edmonton
America/El_Salvador
America/Ensenada
America/Fort_Wayne
America/Fortaleza
America/Glace_Bay
America/Godthab
America/Goose_Bay
America/Grand_Turk
265
America/Grenada
America/Guadeloupe
America/Guatemala
America/Guayaquil
America/Guyana
America/Halifax
America/Havana
America/Indiana
America/Indianapolis
America/Inuvik
America/Iqaluit
America/Jamaica
America/Jujuy
America/Juneau
America/Knox_IN
America/La_Paz
America/Lima
America/Los_Angeles
America/Louisville
America/Maceio
America/Managua
America/Manaus
America/Martinique
America/Mazatlan
America/Mendoza
America/Menominee
America/Mexico_City
America/Miquelon
America/Montevideo
America/Montreal
America/Montserrat
America/Nassau
America/New_York
America/Nipigon
America/Nome
America/Noronha
America/Panama
America/Pangnirtung
America/Paramaribo
America/Phoenix
America/Port_of_Spain America/Port-au-Prince America/Porto_Acre
America/Puerto_Rico
America/Rainy_River
America/Rankin_Inlet
America/Regina
America/Rosario
America/Santiago
America/Santo_Domingo
America/Sao_Paulo
America/Scoresbysund
America/Shiprock
America/St_Johns
America/St_Kitts
America/St_Lucia
America/St_Thomas
America/St_Vincent
America/Swift_Current America/Tegucigalpa
America/Thule
America/Thunder_Bay
America/Tijuana
America/Tortola
America/Vancouver
America/Virgin
America/Whitehorse
America/Winnipeg
America/Yakutat
America/Yellowknife
Antarctica
Antarctica/Casey
Antarctica/DumontDUrville Antarctica/Mawson
Antarctica/Palmer
Antarctica/South_Pole
Antarctica/McMurdo
Asia
Asia/Aden
Asia/Alma-Ata
Asia/Amman
Asia/Anadyr
Asia/Aqtau
Asia/Aqtobe
Asia/Ashkhabad
Asia/Baghdad
Asia/Bahrain
Asia/Baku
Asia/Bangkok
Asia/Beirut
Asia/Bishkek
Asia/Brunei
Asia/Calcutta
Asia/Chungking
Asia/Colombo
Asia/Dacca
Asia/Damascus
Asia/Dubai
Asia/Dushanbe
Asia/Gaza
Asia/Harbin
Asia/Hong_Kong
Asia/Irkutsk
Asia/Ishigaki
Asia/Istanbul
Asia/Jakarta
Asia/Jayapura
Asia/Jerusalem
266
Asia/Kabul
Asia/Kamchatka
Asia/Karachi
Asia/Kashgar
Asia/Katmandu
Asia/Krasnoyarsk
Asia/Kuala_Lumpur
Asia/Kuching
Asia/Kuwait
Asia/Macao
Asia/Magadan
Asia/Manila
Asia/Muscat
Asia/Nicosia
Asia/Novosibirsk
Asia/Omsk
Asia/Phnom_Penh
Asia/Pyongyang
Asia/Qatar
Asia/Rangoon
Asia/Riyadh
Asia/Saigon
Asia/Seoul
Asia/Shanghai
Asia/Singapore
Asia/Taipei
Asia/Tashkent
Asia/Tbilisi
Asia/Tehran
Asia/Tel_Aviv
Asia/Thimbu
Asia/Tokyo
Asia/Ujung_Pandang
Asia/Ulan_Bator
Asia/Urumqi
Asia/Vientiane
Asia/Vladivostok
Asia/Yakutsk
Asia/Yekaterinburg
Asia/Yerevan
Atlantic
Atlantic/Azores
Atlantic/Bermuda
Atlantic/Canary
Atlantic/Cape_Verde
Atlantic/Faeroe
Atlantic/Jan_Mayen
Atlantic/Madeira
Atlantic/Reykjavik
Atlantic/South_Georgia Atlantic/St_Helena
Atlantic/Stanley
Australia
Australia/ACT
Australia/Adelaide
Australia/Brisbane
Australia/Broken_Hill Australia/Canberra
Australia/Darwin
Australia/Hobart
Australia/LHI
Australia/Lindeman
Australia/Lord Howe
Australia/Melbourne
Australia/NSW
Australia/North
Australia/Perth
Australia/Queensland
Australia/South
Australia/Sydney
Australia/Tasmania
Australia/Victoria
Australia/West
Australia/Yancowinna
Brazil
Brazil/Acre
Brazil/DeNoronha
Brazil/East
Brazil/West
267
Canada
Canada/Atlantic
Canada/Central
Canada/East-Saskatchewan
Canada/Eastern
Canada/Mountain
Canada/Newfoundland
Canada/Pacific
Canada/Saskatchewan
Canada/Yukon
Chile
Chile/Continental
Chile/EasterIsland
Etc
Etc/GMT
Etc/GMT+0
Etc/GMT+1
Etc/GMT+2
Etc/GMT+3
Etc/GMT+4
Etc/GMT+5
Etc/GMT+6
Etc/GMT+7
Etc/GMT+8
Etc/GMT+9
Etc/GMT+10
Etc/GMT+11
Etc/GMT+12
Etc/GMT0
Etc/GMT-0
Etc/GMT-1
Etc/GMT-2
Etc/GMT-3
Etc/GMT-4
Etc/GMT-5
Etc/GMT-6
Etc/GMT-7
Etc/GMT-8
Etc/GMT-9
Etc/GMT-10
Etc/GMT-11
Etc/GMT-12
Etc/GMT-13
Etc/GMT-14
Etc/Greenwich
Etc/UCT
Etc/Universal
Etc/UTC
Etc/Zulu
Europe/Amsterdam
Europe/Andorra
Europe/Athens
Europe/Belfast
Europe/Belgrade
Europe/Berlin
Europe/Bratislava
Europe/Brussels
Europe/Bucharest
Europe/Budapest
Europe/Chisinau
Europe/Copenhagen
Europe/Dublin
Europe/Gibraltar
Europe/Helsinki
Europe/Istanbul
Europe/Kiev
Europe/Kuybyshev
Europe/Lisbon
Europe/Ljubljana
Europe/London
Europe/Luxembourg
Europe/Madrid
Europe/Malta
Europe/Minsk
Europe/Monaco
Europe/Moscow
Europe/Oslo
Europe/Paris
Europe/Prague
Europe/Riga
Europe/Rome
Europe/San_Marino
Europe/Sarajevo
Europe/Simferopol
Europe/Skopje
Europe/Sofia
Europe/Stockholm
Europe/Tallinn
Europe/Tirane
Europe
268
Europe/Vaduz
Europe/Vatican
Europe/Zagreb
Europe/Zurich
Europe/Vienna
Europe/Vilnius
Europe/Warsaw
GMT
GMT
GMT+1
GMT+2
GMT+3
GMT+4
GMT+5
GMT+6
GMT+7
GMT+8
GMT+9
GMT+10
GMT+11
GMT+12
GMT+13
GMT-1
GMT-2
GMT-3
GMT-4
GMT-5
GMT-6
GMT-7
GMT-8
GMT-9
GMT-10
GMT-11
GMT-12
Indian (Indian Ocean)
Indian/Antananarivo
Indian/Chagos
Indian/Christmas
Indian/Cocos
Indian/Comoro
Indian/Kerguelen
Indian/Mahe
Indian/Maldives
Indian/Mauritius
Indian/Mayotte
Indian/Reunion
Mexico
Mexico/BajaNorte
Mexico/BajaSur
Mexico/General
Miscellaneous
Arctic/Longyearbyen
CET
CST6CDT
Cuba
EET
Egypt
Eire
EST
EST5EDT
Factory
GB
GB-Eire
Greenwich
Hongkong
HST
Iceland
Iran
Israel
Jamaica
Japan
Kwajalein
Libya
MET
MST
MST7MDT
Navajo
NZ
NZ-CHAT
Poland
Portugal
269
PRC
PST8PDT
ROC
ROK
Singapore
Turkey
UCT
Universal
UTC
WET
W-SU
Zulu
Pacific
Pacific/Apia
Pacific/Auckland
Pacific/Chatham
Pacific/Easter
Pacific/Efate
Pacific/Enderbury
Pacific/Fakaofo
Pacific/Fiji
Pacific/Funafuti
Pacific/Galapagos
Pacific/Gambier
Pacific/Guadalcanal
Pacific/Guam
Pacific/Honolulu
Pacific/Johnston
Pacific/Kiritimati
Pacific/Kosrae
Pacific/Kwajalein
Pacific/Majuro
Pacific/Marquesas
Pacific/Midway
Pacific/Nauru
Pacific/Niue
Pacific/Norfolk
Pacific/Noumea
Pacific/Pago_Pago
Pacific/Palau
Pacific/Pitcairn
Pacific/Ponape
Pacific/Port_Moresby
Pacific/Rarotonga
Pacific/Saipan
Pacific/Samoa
Pacific/Tahiti
Pacific/Tarawa
Pacific/Tongatapu
Pacific/Truk
Pacific/Wake
Pacific/Wallis
Pacific/Yap
SystemV/AST4
SystemV/AST4ADT
SystemV/CST6
SystemV/CST6CDT
SystemV/EST5
SystemV/EST5EDT
SystemV/HST10
SystemV/MST7
SystemV/MST7MDT SystemV/PST8
SystemV/PST8PDT
SystemV/YST9
SystemV/YST9YDT
System V
US (United States)
US/Alaska
US/Aleutian
US/Arizona
US/Central
US/East-Indiana
US/Eastern
US/Hawaii
US/Indiana-Starke
US/Michigan
US/Mountain
US/Pacific
US/Pacific-New
US/Samoa
Aliases
GMT=Greenwich, UCT, UTC, Universal, Zulu CET=MET (Middle European Time)
US/Eastern=Jamaica US/Mountain=Navajo
270
Index
A
add
a new shelf to a volume 58
adminaccess command 103
administrative email, display address 93
administrative host, display host name 93
AIX 46
alerts
add an email address 114
command 114
display current 115
display current and history 117
display the email list 116
display the history 116
remove an address from the email list 114
set the email list to the default 115
test the list 114
alias
add 162
command 162
defaults 163
display 163
remove 163
authentication mode for CIFS 191
autonegotiate, set 172
autosupport
command 118
display all parameters 121
display history file 122
display list 121
display schedule 121
remove an email address 119
run the report 119
send a report 118
send command output 120
B
set all parameters to default 120
set list to the default 119
set the schedule 120
set the schedule to the default 120
test report 118
backup, recommendations for full
C
4
CIFS
add a backup client 190
add a client 189
add a user 188
add an administrative client 190
Add IP address/hostname mappings 192
configuration set up 41
disable client connections 189
display active clients 194
display clients 195
display configuration 195
Display IP address/hostname mappings 196
display statistics 196
display status 196
display valid CIFS options that can be set 194
enable client connections 189
hostname change effects 170
identify a WINS server 193
Increase memory for more user accounts 193
remove a client 190
remove all clients 191
remove all IP address/hostname mappings 192
remove an administrative client 190
Remove one IP address/hostname mapping 192
remove the NetBIOS hostname 191
remove the WINS server 193
reset CIFS options 194
271
resolve NetBIOS name 192
set a NetBIOS hostname 191
set the authentication mode 191
set the logging level 193
user access 187
clean
change schedule 131
display amount parameters 133
display schedule 133
display status 134
display throttle 133
monitor operations 134
set schedule to the default 132
set throttle 132
set throttle to the default 132
start 131
stop 131
system defaults 130
command
output, remote with SSH 107
send output using autosupport command
commands listed 7
compression
algorithms 134
set for none 134
config
command 89
command details 89
configuration
basic additions 46
change settings 89
defaults 6
first time 36
context 200
CPU
display load 154, 155
temperature extremes 248
D
data
272
compression 4
integrity checks
migration 96
3
120
at system installation 29
introduction 5
system administration with 48
system configuration 36, 90
date
display 160
set 152, 160
DDR Manager
monitor multiple systems 23
opening and use 9
default gateway
change 178
display 180
reset 178
DHCP
disable 168
enable 168
server installation tasks 35
disk
add disks and LUNs 53, 141
add enclosure command 54
beacon 140
command 139
command format 53
display performance statistics 146
display RAID status 143
display type and capacity 142
estimate use of space 18
failures and spares 50
flash the running light 141
manage use of space 19
reclaim space 26
reliability statistics 147
replacing 248
rescan 53, 141
set statistics to zero 141
set to failed 140
show status 54, 141
spare when add an expansion shelf 58
unfail a disk 140
DNS
add server 169
display servers 175, 176
domain name display 170
duplex, set line use 171
E
enclosure
beacon 56
display hardware status 57
fans, display status 56
port connections, display 57
power supply status 57
temperature, display 56
enclosures, list 55
Enterprise Manager 23
Ethernet, display interface settings 173
expansion shelf
add first 50
add second 52
disk add enclosure command 141
look for new 53
site requirements 31
F
fans
display status 158
replacing for disks 257
replacing on back panel 259
view sets 256
fans, display status 56
file system
compression algorithms 134
delete all data 126
disable 125
display compression 128
display status 126
display uptime 126
display utilization 127
enable 125
restart 125
filesys command 125
FTP
add a host 103
display user list 107
remove a host 104
set user list to empty 105
G
gateway system
add a LUN 67, 140
command differences
installation 64
points of interest 59
troubleshooting 66
GB defined 8
GUI, see DDR Manager
H
halt See poweroff
hard address, private loop 75
hardware
display status 57
hardware, replacing components 247
host name
add 171
delete 172
display 172
hourly status message 122
HTTPS, generate a new certificate 106
I
I/O, display load 154, 155
installation
DD460g 64
default directories under /ddvar 6
DHCP server tasks 35
hardware 32
login and configuration 36
interface
autonegotiate 172
change IP address 170
change transfer unit size 169
disable 167
display Ethernet configuration 173
display settings 173
enable 167
overview 5
set line speed 171
IP address, change for an interface 170
K
KB defined
Index
61
8
273
L
license
add 94
configuration setup 39
display 95
remove 95
remove feature licenses 95
location
display 93
set 92
log
archive the log 245
command 241
create file bundles 122
list file names 244
remote logging 241
scroll new entries 241
set the CIFS logging level 193
support upload command 122
view all current entries 243
login, first time 36
LUN masking 82
add a client 82
add a LUN mask 84
procedure 85
vtl initiator command 82
M
mail
change server 92
display server 175
display server name 93
maximum transfer unit size, change
MB defined 8
migration
set up 96
with replication 101
monitor multiple systems 23
MTU, change size 169
N
name
change 170
display 175
274
169
ndmp
add a filer 231
backup operation 232
display known filers 234
display process status 234
remove a filer 231
remove passwords 233
restore operation 232
stop a process 233
stop all processes 233
test for a filer 234
net command 167
net, display Ethernet hardware settings
netmask, change 168
network
network parameters, reset 171
NFS
add client, read/write 181
clear statistics 183
command 181
detailed statistics 185
disable client 182
display active clients 183
display allowed clients 184
display status 186
enable client 182
remove client 182
set client list to default 183
ntp
add a time server 164
delete a time server 165
disable service 164
display settings 166
display status 165
enable service 164
reset to defaults 165
NTP, display server 175
P
password, change
ping a host 169
174
110
seeding 218
bidirectional 221
many-to-one 226
one-to-one 219
set bandwidth 208
set delay 208
setup and start bidirectional 215
setup and start collection 215
setup and start directory 214
setup and start many-to-one 216
start 202
statistics 212
suspend 202
throttle override 207
throttle rate 206
throttle reset 207
throttle, add an event 205
throttle, delete an event 206
throttle, display settings 209
use a network name 204
route
add a rule 177
change default gateway 178
command 177
display a route 178
display default gateway 180
display Kernel IP routing table 179
display static routes 179
remove a rule 178
reset default gateway 178
pools
add 87
and replication 201
delete 87
display 87
using 86
port connections
display 57
power supply
display status 57, 159
replacing 251
poweroff 149
private loop, hard address 75
privilege level, change 110
R
RAID
and a failed disk 140
create a new group 58
display detailed information 145
display status 54, 141, 143
groups 50
type in a restorer 3
with gateway restorers 60
reboot hardware 150
remote command output 107
replication
change a destination port 205
change a source port 204
change originator name 204
configure 200
context 200
convert to directory from collection
display status 211
introduced 199
move data to originator 203
pools 201
remove configuration 203
repair a broken recovery 208
replace collection source 217
replace directory source 216
reset authorization 203
reset bandwidth 208
reset delay 208
resume 202
Index
218
S
serial number, display 153
shutdown See poweroff
site install requirements 30
SNMP
add community strings 237
add trap hosts 237
delete a community string 238
delete a trap host 237
delete all community strings 238
delete all trap hosts 237
disable 235
display all 239
display community strings 240
275
display status 238
display the system contact 240
display the system location 240
display trap hosts 239
enable 235
reset all SNMP values 238
reset location 236
reset system location 236
system contact 236
system location 236
software
display version 161
space management 17
space.log, format 244
SSH
add a public key 105
display the key file 106
remove a key file entry 106
remove the key file 106
statistics
clear NFS 183
disk performance 146
disk reliability 147
display for the network 176
display NFS 184
graphic display 157
NFS detailed 185
set disk to zero 141
status, hourly message 122
support
log file bundles 122
upload command 122
system
change name 170
command 149
display status 158
display uptime 154
display version 161
location 92
location display 93
serial number 153
276
T
TB defined 8
TELNET
add a host 103
remove a host 104
temperature extremes 247
temperature, display 56, 158
time
display 160
display zone 94
set 152, 160
set zone 92
Tivoli Storage Manager 46
traceroute 178
U
upgrade software 150
uptime, display 154
users
add 109
change a password 110
change a privilege level 110
display all 111, 112
regular 109
remove 109
set list to default 110
sysadmin 109
V
verify
process explanation 3
see when the process is running 155
Virtual Tape Library
See VTL
volume expansion 58
VTL
create a VTL 71
create tapes 72
delete a VTL 75
disable 71
display a tape summary 77, 79
display all tapes 77
display configurations 76
W
display status 76
display tapes in the vault 79
enable 71
export tapes 73
features and limitations 69
import tape 73
insert tape manually 74
LUN masking 82
private loop hard address 75
remove tape manually 74
remove tapes 73
retrieve a tape from a destination 80
tape information by VTL 78, 79
WINS server for CIFS 193
WINS server for CIFS, remove 193
Index
277
278
© 2011 - 2013 EMC Corporation. All Rights Reserved.
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without
notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO
REPRESENTATIONS OR
WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND
SPECIFICALLY
DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United State and other
countries.
All other trademarks used herein are the property of their respective owners.

Restorer Operating System User Guide

Transcription

Similar documents

Brush of artist, hand of restorer

Ziua doctoranzilor

OS X Formatting Guide (10.6

How to Manually Regenerate or Cycle Your Kinetico Softener

Kumihimo on a Plate

Cleaning House - Linux Magazine

Jim Ryner - Model A Ford Club of America

El Capitan Formatting Guide

Issue 122 - Jan 2002 - Isle of Wight PC User Group

Imaging degenerative disk disease in the lumbar spine