Professional Documents
Culture Documents
Datadomain Command Guide PDF
Datadomain Command Guide PDF
Datadomain Command Guide PDF
9
Command Reference
Guide
762-0007-0001 Revision A
March 26, 2010
Copyright 2010 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.
EMC and Data Domain are registered trademarks, and Global Compression is
a trademark of EMC Corporation
2
Contents
2 adminaccess . . . . . . . . . . . . . . . . . . . . . . . . . . .47
About the adminaccess Command. . . . . . . . . . . . . . . . . . 48
adminaccess Command Options . . . . . . . . . . . . . . . . . . . 48
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
add host-list . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
add ssh-keys . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4 Contents
web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
web option reset . . . . . . . . . . . . . . . . . . . . . . . . 54
web option set http-port . . . . . . . . . . . . . . . . . . . 54
web option set https-port . . . . . . . . . . . . . . . . . . 55
web option set session-timeout . . . . . . . . . . . . . . 55
web option show . . . . . . . . . . . . . . . . . . . . . . . . 55
adminaccess Examples . . . . . . . . . . . . . . . . . . . . . . . . . 56
Configuring adminaccess . . . . . . . . . . . . . . . . . . . . . 56
Add a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Add an Authorized SSH Public Key . . . . . . . . . . . . . 56
Return Command Output to a Remote Machine . . . . . . 57
3 alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
About the alerts Command . . . . . . . . . . . . . . . . . . . . . . 59
alerts Command Options . . . . . . . . . . . . . . . . . . . . . . . 60
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
del. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
show alerts-list . . . . . . . . . . . . . . . . . . . . . . . . . 61
show all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
show current . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
show daily . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
show history . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
alerts Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4 alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
About the alias Command . . . . . . . . . . . . . . . . . . . . . . .67
alias Command Options . . . . . . . . . . . . . . . . . . . . . . . . .68
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
alias Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Add an Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
5 authentication . . . . . . . . . . . . . . . . . . . . . . . . . 71
About the authentication Command. . . . . . . . . . . . . . . . .71
authentication Command Options . . . . . . . . . . . . . . . . . .71
disable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
6 Contents
domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
domain reset . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
domain set . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
domain show . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
groups add . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
groups del . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
groups reset . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
groups show . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
servers add . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
servers del . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
servers reset . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
servers show . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6 autosupport . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
About the autosupport Command . . . . . . . . . . . . . . . . . . 75
autosupport Command Options . . . . . . . . . . . . . . . . . . . 77
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
del. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
7 cifs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
About the cifs Command . . . . . . . . . . . . . . . . . . . . . . . .86
cifs Command Options. . . . . . . . . . . . . . . . . . . . . . . . . .86
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
add /backup . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
add /ddvar . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
8 Contents
del. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
del /backup . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
del /ddvar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
hosts add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
hosts del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
hosts reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
hosts show . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
nb-lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
option reset . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
option set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
option show . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
reset authentication . . . . . . . . . . . . . . . . . . . . . . 94
reset clients . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
reset nb-hostname . . . . . . . . . . . . . . . . . . . . . . . 94
reset wins-server . . . . . . . . . . . . . . . . . . . . . . . . 94
set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
set authentication active-directory . . . . . . . . . . . . 95
set authentication nt4 . . . . . . . . . . . . . . . . . . . . 95
set authentication workgroup . . . . . . . . . . . . . . . 96
set nb-hostname . . . . . . . . . . . . . . . . . . . . . . . . 96
set wins-server . . . . . . . . . . . . . . . . . . . . . . . . . 96
8 cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
About the cluster Commands . . . . . . . . . . . . . . . . . . . . 106
cluster Command Options . . . . . . . . . . . . . . . . . . . . . . 106
10 Contents
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
destroy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
show config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
9 config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
About the config Command. . . . . . . . . . . . . . . . . . . . . 111
config Command Options . . . . . . . . . . . . . . . . . . . . . . 112
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
reset location . . . . . . . . . . . . . . . . . . . . . . . . . 112
reset mailserver . . . . . . . . . . . . . . . . . . . . . . . 112
reset timezone . . . . . . . . . . . . . . . . . . . . . . . . 112
set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
set admin-email . . . . . . . . . . . . . . . . . . . . . . . 113
set admin-host . . . . . . . . . . . . . . . . . . . . . . . . 113
set location . . . . . . . . . . . . . . . . . . . . . . . . . . 114
set mailserver . . . . . . . . . . . . . . . . . . . . . . . . . 114
set timezone . . . . . . . . . . . . . . . . . . . . . . . . . . 115
setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
10 disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
About the disk Command . . . . . . . . . . . . . . . . . . . . . . . 119
disk Command Options . . . . . . . . . . . . . . . . . . . . . . . . 120
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
add dev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
add enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . 121
beacon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
expand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
12 Contents
multipath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
multipath failback . . . . . . . . . . . . . . . . . . . . . . 123
multipath option set auto-failback . . . . . . . . . . . 123
multipath option set monitor . . . . . . . . . . . . . . . 124
multipath option reset auto-failback . . . . . . . . . . 124
multipath option reset monitor . . . . . . . . . . . . . 124
multipath option show . . . . . . . . . . . . . . . . . . . 124
multipath reset stats . . . . . . . . . . . . . . . . . . . . 125
multipath resume . . . . . . . . . . . . . . . . . . . . . . 125
multipath show history . . . . . . . . . . . . . . . . . . . 125
multipath show stats . . . . . . . . . . . . . . . . . . . . 125
multipath status . . . . . . . . . . . . . . . . . . . . . . . 125
multipath suspend . . . . . . . . . . . . . . . . . . . . . . 125
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
port enable . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
port show stats . . . . . . . . . . . . . . . . . . . . . . . . 126
port show summary . . . . . . . . . . . . . . . . . . . . . 126
rescan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
set spindle-group . . . . . . . . . . . . . . . . . . . . . . . 127
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
show hardware . . . . . . . . . . . . . . . . . . . . . . . . 128
show detailed-raid-info . . . . . . . . . . . . . . . . . . . 129
show failure-history . . . . . . . . . . . . . . . . . . . . . 130
show performance . . . . . . . . . . . . . . . . . . . . . . 131
show raid-info . . . . . . . . . . . . . . . . . . . . . . . . . 132
show reliability-data . . . . . . . . . . . . . . . . . . . . 133
DD OS 4.9 Command Reference Guide 13
status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
unfail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
disk Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Add an Expansion Shelf . . . . . . . . . . . . . . . . . . . . . . 135
Important Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
11 enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
About the enclosure Command . . . . . . . . . . . . . . . . . . . 137
enclosure Command Options. . . . . . . . . . . . . . . . . . . . . 138
beacon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
show all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
show controllers . . . . . . . . . . . . . . . . . . . . . . . . 138
show fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
show powersupply . . . . . . . . . . . . . . . . . . . . . . . 141
show summary . . . . . . . . . . . . . . . . . . . . . . . . . 142
show temperature-sensors . . . . . . . . . . . . . . . . . 142
show topology . . . . . . . . . . . . . . . . . . . . . . . . . 143
test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
test topology . . . . . . . . . . . . . . . . . . . . . . . . . . 144
enclosure Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Display the Enclosure Temperature . . . . . . . . . . . . . . 145
12 filesys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
About the filesys Command . . . . . . . . . . . . . . . . . . . . . 148
filesys Command Options . . . . . . . . . . . . . . . . . . . . . . . 148
14 Contents
clean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
clean reset . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
clean set schedule . . . . . . . . . . . . . . . . . . . . . . 150
clean set throttle . . . . . . . . . . . . . . . . . . . . . . . 150
clean show config . . . . . . . . . . . . . . . . . . . . . . 151
clean show schedule . . . . . . . . . . . . . . . . . . . . . 151
clean show throttle . . . . . . . . . . . . . . . . . . . . . 151
clean start . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
clean status . . . . . . . . . . . . . . . . . . . . . . . . . . 152
clean stop . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
clean watch . . . . . . . . . . . . . . . . . . . . . . . . . . 153
destroy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
encryption algorithm reset . . . . . . . . . . . . . . . . 155
encryption algorithm set . . . . . . . . . . . . . . . . . . 156
encryption algorithm show . . . . . . . . . . . . . . . . 156
encryption disable . . . . . . . . . . . . . . . . . . . . . . 156
encryption enable . . . . . . . . . . . . . . . . . . . . . . 156
encryption lock . . . . . . . . . . . . . . . . . . . . . . . . 157
encryption passphrase . . . . . . . . . . . . . . . . . . . 157
encryption show . . . . . . . . . . . . . . . . . . . . . . . 157
encryption unlock . . . . . . . . . . . . . . . . . . . . . . 158
fastcopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
16 Contents
Retention Lock Procedure . . . . . . . . . . . . . . . . . . . 171
Performing Retention Lock File Control Commands
on the Client Operating System . . . . . . . . . . . 172
Additional Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Local Compression . . . . . . . . . . . . . . . . . . . . . . . . 173
Global Compression . . . . . . . . . . . . . . . . . . . . . . . 174
Replicator Destination Read/Write Option. . . . . . . . . 174
Tape Marker Handling . . . . . . . . . . . . . . . . . . . . . . 174
Disk Staging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Retention Lock and Replication . . . . . . . . . . . . . . . . 176
Retention Lock and Fastcopy . . . . . . . . . . . . . . . . . 176
Retention Lock and Filesys Destroy . . . . . . . . . . . . . 176
13 help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
About the help Command . . . . . . . . . . . . . . . . . . . . . . 179
help Command Options . . . . . . . . . . . . . . . . . . . . . . . 180
help Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
14 license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
About the license Command . . . . . . . . . . . . . . . . . . . . 181
license Command Options. . . . . . . . . . . . . . . . . . . . . . 183
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
del. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
license Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Add a License . . . . . . . . . . . . . . . . . . . . . . . . . 184
16 migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
About the migration Command . . . . . . . . . . . . . . . . . . . 195
migration Command Options. . . . . . . . . . . . . . . . . . . . . 196
abort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
show stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
18 Contents
migration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Migrate Between Source and Destination . . . . . . . . . 202
Migrate with Replication . . . . . . . . . . . . . . . . . . . . 202
17 net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
About the net Command. . . . . . . . . . . . . . . . . . . . . . . 206
net Command Options . . . . . . . . . . . . . . . . . . . . . . . . 206
aggregate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
aggregate add . . . . . . . . . . . . . . . . . . . . . . . . . 206
aggregate del . . . . . . . . . . . . . . . . . . . . . . . . . 207
aggregate reset . . . . . . . . . . . . . . . . . . . . . . . . 207
aggregate show . . . . . . . . . . . . . . . . . . . . . . . . 208
config. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
config ifname 0 . . . . . . . . . . . . . . . . . . . . . . . . 208
config ifname autoneg . . . . . . . . . . . . . . . . . . . 209
config ifname dhcp . . . . . . . . . . . . . . . . . . . . . 209
config ifname duplex speed . . . . . . . . . . . . . . . . 210
config ifname ipaddr . . . . . . . . . . . . . . . . . . . . 210
config ifname mtu . . . . . . . . . . . . . . . . . . . . . . 211
config ifname netmask . . . . . . . . . . . . . . . . . . . 211
config ifname type . . . . . . . . . . . . . . . . . . . . . . 211
config ifname up | down . . . . . . . . . . . . . . . . . . 212
create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
create interface . . . . . . . . . . . . . . . . . . . . . . . 212
create virtual . . . . . . . . . . . . . . . . . . . . . . . . . 213
destroy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
20 Contents
set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
set dns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
set domainname . . . . . . . . . . . . . . . . . . . . . . . 222
set hostname . . . . . . . . . . . . . . . . . . . . . . . . . 222
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
show all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
show config . . . . . . . . . . . . . . . . . . . . . . . . . . 223
show dns . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
show domainname . . . . . . . . . . . . . . . . . . . . . . 223
show hostname . . . . . . . . . . . . . . . . . . . . . . . . 224
show hardware . . . . . . . . . . . . . . . . . . . . . . . . 224
show settings . . . . . . . . . . . . . . . . . . . . . . . . . 225
show stats . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
tcpdump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
tcpdump capture . . . . . . . . . . . . . . . . . . . . . . . 226
tcpdump del . . . . . . . . . . . . . . . . . . . . . . . . . . 227
net Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Sample Failover Workflow . . . . . . . . . . . . . . . . . . . 227
Sample Aggregation Workflow. . . . . . . . . . . . . . . . . 229
Important Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Considerations for Ethernet Failover and
Net Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Supported Interfaces . . . . . . . . . . . . . . . . . . . . 231
18 nfs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
About the nfs Command . . . . . . . . . . . . . . . . . . . . . . . 233
nfs Command Options . . . . . . . . . . . . . . . . . . . . . . . . 234
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
19 ntp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
About the ntp Command . . . . . . . . . . . . . . . . . . . . . . . 241
ntp Command Options . . . . . . . . . . . . . . . . . . . . . . . . . 242
add timeserver . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
del timeserver. . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
disable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
reset timeservers. . . . . . . . . . . . . . . . . . . . . . . . . . 243
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
22 Contents
ntp Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Add an NTP Server . . . . . . . . . . . . . . . . . . . . . . . . 244
20 ost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
About the ost Command . . . . . . . . . . . . . . . . . . . . . . . 246
ost Command Options . . . . . . . . . . . . . . . . . . . . . . . . 247
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
destroy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
ifgroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
ifgroup add interface . . . . . . . . . . . . . . . . . . . . 248
ifgroup del interface . . . . . . . . . . . . . . . . . . . . 249
ifgroup disable . . . . . . . . . . . . . . . . . . . . . . . . 249
ifgroup enable . . . . . . . . . . . . . . . . . . . . . . . . . 249
ifgroup show config . . . . . . . . . . . . . . . . . . . . . 249
ifgroup reset . . . . . . . . . . . . . . . . . . . . . . . . . . 250
ifgroup status . . . . . . . . . . . . . . . . . . . . . . . . . 250
lsu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
lsu create . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
lsu delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
lsu show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
21 replication . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
About the replication Command . . . . . . . . . . . . . . . . . . 262
24 Contents
replication Command Options . . . . . . . . . . . . . . . . . . . 263
abort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
abort recover . . . . . . . . . . . . . . . . . . . . . . . . . 263
abort resync . . . . . . . . . . . . . . . . . . . . . . . . . . 263
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
break . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
initialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
modify low-bw-optim . . . . . . . . . . . . . . . . . . . . 266
modify source-host or destination-host . . . . . . . . 267
modify connection-host . . . . . . . . . . . . . . . . . . 268
modify connection-host port . . . . . . . . . . . . . . . 269
option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
option reset . . . . . . . . . . . . . . . . . . . . . . . . . . 269
option set bandwidth . . . . . . . . . . . . . . . . . . . . 269
option set delay . . . . . . . . . . . . . . . . . . . . . . . 270
option set listen-port . . . . . . . . . . . . . . . . . . . . 270
option show . . . . . . . . . . . . . . . . . . . . . . . . . . 270
reauth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
recover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
22 route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
About the route Command . . . . . . . . . . . . . . . . . . . . . 305
route Command Options . . . . . . . . . . . . . . . . . . . . . . . 306
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
del. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
show config . . . . . . . . . . . . . . . . . . . . . . . . . . 307
show gateway . . . . . . . . . . . . . . . . . . . . . . . . . 308
show table . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
route Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Add a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
23 snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
About the snapshot Command. . . . . . . . . . . . . . . . . . . . 311
snapshot Command Options . . . . . . . . . . . . . . . . . . . . . 312
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Names of Snapshots Created by a Schedule . . . . . . 313
create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
expire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
rename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
snapshot Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Schedule a Snapshot . . . . . . . . . . . . . . . . . . . . . . . . 319
24 snmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
About the snmp Command . . . . . . . . . . . . . . . . . . . . . . 323
snmp Command Options . . . . . . . . . . . . . . . . . . . . . . . 324
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
add ro-community . . . . . . . . . . . . . . . . . . . . . . . 324
add rw-community . . . . . . . . . . . . . . . . . . . . . . 324
add trap-host . . . . . . . . . . . . . . . . . . . . . . . . . . 325
28 Contents
del. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
del ro-community . . . . . . . . . . . . . . . . . . . . . . 325
del rw-community . . . . . . . . . . . . . . . . . . . . . . 325
del trap-host . . . . . . . . . . . . . . . . . . . . . . . . . . 326
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
reset ro-community . . . . . . . . . . . . . . . . . . . . . 326
reset rw-community . . . . . . . . . . . . . . . . . . . . . 326
reset sysContact . . . . . . . . . . . . . . . . . . . . . . . 327
reset sysLocation . . . . . . . . . . . . . . . . . . . . . . . 327
reset trap-hosts . . . . . . . . . . . . . . . . . . . . . . . . 327
set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
set sysContact . . . . . . . . . . . . . . . . . . . . . . . . . 327
set sysLocation . . . . . . . . . . . . . . . . . . . . . . . . 328
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
show config . . . . . . . . . . . . . . . . . . . . . . . . . . 328
show ro-communities . . . . . . . . . . . . . . . . . . . . 328
show rw-communities . . . . . . . . . . . . . . . . . . . . 329
show sysContact . . . . . . . . . . . . . . . . . . . . . . . 329
show sysLocation . . . . . . . . . . . . . . . . . . . . . . . 329
show trap-hosts . . . . . . . . . . . . . . . . . . . . . . . . 329
status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Important Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
25 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
About the support Command . . . . . . . . . . . . . . . . . . . . 331
support Command Options . . . . . . . . . . . . . . . . . . . . . 331
DD OS 4.9 Command Reference Guide 29
upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
26 system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
About the system Command . . . . . . . . . . . . . . . . . . . . . 334
system Command Options . . . . . . . . . . . . . . . . . . . . . . 334
headswap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
option reset . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
option set . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
option show . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
poweroff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
sanitize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
sanitize abort . . . . . . . . . . . . . . . . . . . . . . . . . . 337
sanitize start . . . . . . . . . . . . . . . . . . . . . . . . . . 337
sanitize status . . . . . . . . . . . . . . . . . . . . . . . . . 337
sanitize watch . . . . . . . . . . . . . . . . . . . . . . . . . 337
set date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
30 Contents
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
show all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
show date . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
show detailed-stats . . . . . . . . . . . . . . . . . . . . . 339
show detailed-version . . . . . . . . . . . . . . . . . . . . 341
show hardware . . . . . . . . . . . . . . . . . . . . . . . . 342
show meminfo . . . . . . . . . . . . . . . . . . . . . . . . . 342
show modelno . . . . . . . . . . . . . . . . . . . . . . . . . 343
show nvram . . . . . . . . . . . . . . . . . . . . . . . . . . 343
show performance . . . . . . . . . . . . . . . . . . . . . . 344
show ports . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
show serialno . . . . . . . . . . . . . . . . . . . . . . . . . 349
show stats . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
show uptime . . . . . . . . . . . . . . . . . . . . . . . . . . 351
show version . . . . . . . . . . . . . . . . . . . . . . . . . . 351
status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Upgrade by Using HTTP . . . . . . . . . . . . . . . . . . . 355
Examples for system . . . . . . . . . . . . . . . . . . . . . . . . . 356
Display System Statistics . . . . . . . . . . . . . . . . . . . . 356
Set the System Date and Time . . . . . . . . . . . . . . . . 356
Display System Performance . . . . . . . . . . . . . . . . . . 356
Display a Banner. . . . . . . . . . . . . . . . . . . . . . . . . . 357
27 user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
About the user Command . . . . . . . . . . . . . . . . . . . . . . 359
user Command Options . . . . . . . . . . . . . . . . . . . . . . . 360
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
DD OS 4.9 Command Reference Guide 31
change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
change password . . . . . . . . . . . . . . . . . . . . . . . . 361
change priv . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
disable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
password aging option reset . . . . . . . . . . . . . . . . 362
password aging option set . . . . . . . . . . . . . . . . . . 362
password aging option show . . . . . . . . . . . . . . . . 362
password aging reset . . . . . . . . . . . . . . . . . . . . . 362
password aging set . . . . . . . . . . . . . . . . . . . . . . 363
password aging show . . . . . . . . . . . . . . . . . . . . . 363
password strength show . . . . . . . . . . . . . . . . . . . 363
password strength reset . . . . . . . . . . . . . . . . . . . 364
password strength set . . . . . . . . . . . . . . . . . . . . 364
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
show active . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
show detailed . . . . . . . . . . . . . . . . . . . . . . . . . . 365
show list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
user Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Add a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Remove a User . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Change a Password. . . . . . . . . . . . . . . . . . . . . . . . . 366
Change a Privilege Level . . . . . . . . . . . . . . . . . . . . . 366
Reset to the Default User . . . . . . . . . . . . . . . . . . . . 366
32 Contents
Display Current Users . . . . . . . . . . . . . . . . . . . . . . 367
Display All Users. . . . . . . . . . . . . . . . . . . . . . . . . . 368
28 vtl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
About the vtl Command . . . . . . . . . . . . . . . . . . . . . . . 370
Options for the vtl Command . . . . . . . . . . . . . . . . . . . 371
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
cap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
cap add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
cap del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
del. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
drive add . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
drive del . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
group add . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
group create . . . . . . . . . . . . . . . . . . . . . . . . . . 376
group del . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
group destroy . . . . . . . . . . . . . . . . . . . . . . . . . 377
group modify . . . . . . . . . . . . . . . . . . . . . . . . . 377
group rename . . . . . . . . . . . . . . . . . . . . . . . . . 379
group show . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
group use . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
34 Contents
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
show config . . . . . . . . . . . . . . . . . . . . . . . . . . 389
show element-address . . . . . . . . . . . . . . . . . . . 390
show stats . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
slot add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
slot del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
tape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
tape add . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
tape del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
tape modify retention-lock . . . . . . . . . . . . . . . . 394
tape modify writeprotect . . . . . . . . . . . . . . . . . 395
tape move . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
tape show . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Add a VTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Move Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Manually Import and Export Tapes . . . . . . . . . . . . . . 398
Important Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Tape Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Data Structures . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
36 Contents
About This Guide
Chapter Summaries
The DD OS 4.9 Command Reference Guide includes the following
chapters:
Audience
This guide is for system administrators who are familiar with
standard backup software packages and general backup
administration.
CLI Shortcuts
Recall Commands
Ctrl+P or Retrieve the previous command from the
Down Arrow history buffer.
Ctrl+N or Up Retrieve the next command from the history
Arrow buffer.
Delete Characters
Ctrl+D Delete the character at the cursor.
Ctrl+H Delete the character before the cursor (same as
Delete key).
Ctrl+K Delete all characters from the cursor to the end
of the line.
Command Completion
Tab or Ctrl+I Complete a partially typed keyword if enough
characters are entered to uniquely identify it.
Cursor Movement
Ctrl+A Move the cursor back to the start of the line.
Ctrl+B Move the cursor back one character.
Ctrl+E Move the cursor to the end of the line.
Ctrl+F Move the cursor forward one character.
Transpose Characters
Ctrl+T Transpose the character at the cursor with the
preceding character.
The adminaccess command creates access control lists for the use
of HTTP, FTP, Telnet, and SSH administrative protocols on the
Data Domain system.
The adminaccess command has the following options:
add Add hosts to a protocol or add an Page48
SSH public key.
authentication Manage and display authentication. Page49
certificate Display the host or CA certificate. Page50
del Remove client administrative access Page51
to the DD system through a specified
protocol, or delete an SSH key from
the key file.
disable Disable a service. Page51
enable Enable a service. Page51
reset Set the given access list to the factory Page52
defaults, or remove the authorized
SSH keys file from the Data Domain
system.
show Display hosts, status, and the SSH Page52
key file.
trust Manage trust with a given host. Page53
web Manage Web options. Page54
48 adminaccess
add ssh-keys
adminaccess add ssh-keys [user username]
Use this command to add an SSH public key, created on a remote
machine, to the SSH authorized keys file on the Data Domain
system. The operation allows users to log in without giving a
password. On the remote machine, create a public key using the
ssh-keygen command. Use the key ~/.ssh/id_dsa.pub as
generated on the remote machine by ssh-keygen as input to the
add ssh-keys command. Refer to Add an Authorized SSH Public
Key for more information.
authentication
authentication add cifs
adminaccess authentication add cifs
Use this command to allow Windows domain users who have no
local account on the Data Domain system to access the system
through SSH, Telnet, and FTP using Windows domain group
credentials. For administrative access, the user must be in either
the standard Windows Domain Admins group or in a group that
you create named Data Domain. Users from both group names
are always accepted as administrative users. The command also
gives user-level access (no administrative operations allowed) to
all other users from the domain. Users must be from the domain
that includes the Data Domain system or a related, trusted domain.
The SSH, Telnet, or FTP command that accesses the Data Domain
system must include the domain name, a backslash, and the user
name in double quotation marks.
Note: For this command to work, CIFS must be enabled and the
Data Domain system must be part of a Windows domain.
authentication show
adminaccess authentication show
Use this command to display the current value of the setting that
allows a Windows administrative user to access a Data Domain
system when no local account exists. For example,
# adminaccess authentication show
CIFS authentication: disabled
certificate
certificate show
adminaccess certificate show {ca | host}
Use this command to display the host or CA certificate. This
command is available to all users. For example:
# adminaccess certificate show ca
Cert Type Root CA
Subject dd120-18.datadomain.com
Valid From Tue Oct 14 13:39:35 2008
Valid Until Thu Oct 7 12:39:35 2038
Finger Print D6:E2:7B:55:F8:90:E9:27
50 adminaccess
del
del
adminaccess del {ftp | telnet | ssh | http} host-list
Use this command to remove hosts (IP addresses, hostnames, or
asterisk (*)) from the FTP, HTTP, SSH, or Telnet access lists. You
can enter a list that is separated by commas, spaces, or both. This
command is available to administrative users only.
del ssh-keys
adminaccess del ssh-keys lineno [user username]
Use this command to delete an SSH key from the key file. The
lineno is a line number as displayed by the adminaccess show
ssh-keys command. Users may delete their own keys.
Administrators may delete any users keys. Use adminaccess
show ssh-keys to get the line number value for the key to delete.
disable
adminaccess disable {http | https | ftp | telnet | ssh | all}
Use this command to disable a service on the Data Domain system.
Disabling FTP or Telnet does not affect entries in the access lists. If
all services are disabled, the Data Domain system is accessible only
through a serial console or keyboard and monitor. This command
is available to administrative users only.
enable
adminaccess enable {http | https | ftp | telnet | ssh | all}
Use this command to enable a protocol on the Data Domain
system. By default, the SSH, HTTP, and HTTPS services are
enabled and FTP and Telnet are disabled. HTTP and HTTPS allow
users to log in through the Web-based graphical user interface. To
use FTP and Telnet, you must also add host machines to the access
lists. This command is available to administrative users only.
reset ssh-keys
adminaccess reset ssh-keys [user username]
Use this command to remove the authorized SSH keys file for a
user specified user or for the operator account from the Data
Domain system. After you remove the file, every SSH connection
needs password authentication. Administrators can reset SSH keys
for themselves (by omitting the user option) or for other users.
Regular users can only reset the SSH keys for their own account.
show
show
adminaccess show
Use this command to display every access service available on a
Data Domain system, 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. An asterisk means
all hosts are allowed. For example:
# adminaccess show
Service Enabled Allowed Hosts
------- ------- -------------
ssh yes -
telnet no -
ftp no *
http yes -
https yes -
------- ------- -------------
52 adminaccess
Web options:
Option Value
--------------- -----
http-port 80
https-port 443
session-timeout 10800
--------------- -----
This command is available to administrative users only.
show ssh-keys
adminaccess show ssh-keys [user username]
Use this command to display the SSH key file with a line number
for each entry. Administrators can view the SSH key files of any
user. Regular users can only view their own SSH key file.
trust
You can add trust between Data Domain systems for group and
Global Deduplication Array management purposes. The trust
commands let administrators manage trust relationships. There
are two scenarios where trust relationships are used.
Group management in the Enterprise Manager is based on
trust relationships between nodes. You can view these trust
relationships with the trust commands. If you add the trust
relationship from the DD OS command line, when a Data
Domain system is imported into the EM for group
management, the sysadmin password is not required for
setting up the management of the external Data Domain
system (because the trust has been already established).
Global Deduplication Array management is also based on trust
relationships. As nodes are added to the Global Deduplication
Array by using the cluster add command, you can view the
trust relationships and their details by using the adminaccess
trust show command.
trust copy
adminaccess trust copy {source | destination} hostname
Use this command to copy the trust to or from the given host.
trust del
adminaccess trust del hostname [type mutual]
Use this command to remove trust from the given host. The type
mutual option removes the mutual trust from that host.
trust show
adminaccess trust show hostname
Use this command to show the list of trusted Certificate
Authorities (CAs). This command is available to all users.
web
web option reset
adminaccess web option reset [http-port | https-port | session-
timeout]
Use this command to reset all Web options or the specified Web
option to their default values.
54 adminaccess
web option set https-port
adminaccess web option set https-port port-number
Use this command to set the https access port for the Web client.
Port 443 is set by default.
Configuring adminaccess
Add a Host
To add the host srvr24 to the Telnet access list:
adminaccess add telnet srvr24.yourcompany.com
To add all hosts in a domain to the Telnet access list:
adminaccess add telnet *.yourcompany.com
To add a range of IP addresses to the Telnet access list:
adminaccess add telnet 10.24.20.0/24
56 adminaccess
Return Command Output to a Remote Machine
Using SSH, you can have output from Data Domain system
commands return to a remote machine at login and then
automatically log out. 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
sysadmin@dd10s password:
The filesystem is enabled
You can create a file with a number of Data Domain system
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
The login and the returned data look similar to the following:
ssh -l sysadmin dd10 < cmds11
sysadmin@dd10s password:
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 Data Domain system, see
Add an Authorized SSH Public Key on page 56 to eliminate the need
for a password.
Use the alerts command to manage the alert email list. The
alerts command has the following options:
add
alerts add email-list
Use this command to add email addresses to the list that receives
system alert emails. The email-list is a list of email addresses
that are separated by commas, spaces, or both.
By default, the list includes an address for Data Domain support
staff. After adding to the list, always use the alerts test
command to test for mailer problems. This command is available
to administrative users only.
clear
alerts clear alert-id alert-id-list
Use this command to clear a specified alert. The alert-id-list is
a list of active alert IDs separated by commas, spaces, or hyphens.
This command is available to administrative users only.
del
alerts del email-list
Use this command to delete email addresses from the list. The
email-list is a list of email addresses that are separated by
commas, spaces, or both. This command is available to
administrative users only.
reset
alerts reset
Use this command to set the email alerts list to the factory default
of autosupport-alert@autosupport.datadomain.com. This
command is available to administrative users only.
60 alerts
show
show alerts-list
alerts show alerts-list
Use this command to display the alerts email list, which 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.
show all
alerts show all
Use this command to display the alerts email list and the
administrator email address, along with the current list of active
alerts.
show current
alerts show current
Use this command to display alerts for all situations that have not
been dealt with.
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.
show daily
alerts show daily
Use this command to display current alerts and the alerts events
history for the last 24 hours. Use the up and down arrow keys to
move through the log. Use the q key to exit. Enter a slash character
(/) and a pattern to search for and highlight lines of particular
interest.
DD OS 4.9 Command Reference Guide 61
show history
alerts show history
Use this command to display the alerts events history file. The
event history file includes one line (date and reason) for every
system alert. Use the up and down arrow keys to move through
the log. Use the q key to exit. Enter a slash character (/) and a
pattern to search for and highlight lines of particular interest.
The alerts history lists alerts messages from all of the existing
messages system log files, which hold messages for up to ten
weeks.
test
alerts test [email-addr]
Use this command to send an email to all addresses on the alerts
list or to one or more specified addresses. After adding addresses
to the email list, always use this operation to test for mailer
problems.
62 alerts
alerts Examples
Configuring alerts
Add to the Email List
To add the email addresses js@yourcompany.com and
bjones@yourcompany.com to the alerts email list, use the
command:
alerts add js@yourcompany.com, bjones@yourcompany.com
Managing alerts
Test the Email List
To test for the address jsmith@yourcompany.com:
alerts test jsmith@yourcompany.com
64 alerts
Recent Alerts and Log Messages
------------------------------
Nov 5 20:56:43 localhost sysmon: EMS: Rear fan #2
failure: Current RPM is 960, nominal is 8000
Important Notices
The alerts feature sends an email whenever a critical component
in the system fails or is known, through monitoring, to be out of
the acceptable range. Consider adding pager email addresses to
the alerts email list so that someone is informed immediately about
system problems. For example, multiple fan failures can cause a
system to begin overheating, which generates an alerts email.
Each disk, fan, and CPU in the Data Domain system is monitored.
Temperature extremes are also monitored.
add
alias add
Use this command to add a command alias. Give the name for the
alias and then give the complete Data Domain system command
enclosed in double quotation marks ("..."). The new alias is
available only for the user that adds the alias.
del
alias del
Use this command to delete an alias by name.
reset
alias reset
Use this command to return to the default alias list, removing all
user-added aliases.
show
alias show
Use this command to display all aliases and their command
definitions.
68 alias
alias Examples
Add an Alias
The following command adds an alias named rely for the Data
Domain system command that displays disk reliability statistics:
# alias add rely "disk show reliability-data"
disable
authentication nis disable
Use this command to disable the NIS client. This command is
available to administrative users only.
domain set
authentication nis domain set domain [servers server-list]
Use this command to set the NIS domain name and optionally to
add NIS servers to the server-list. This command is available to
administrative users only.
domain show
authentication nis domain show
Use this command to display the NIS domain name. The display is
similar to the following:
# authentication nis domain show
NIS domain is "datadomain.com".
enable
authentication nis enable
Use this command to enable the NIS client. This command is
available to administrative users only.
groups
groups add
authentication nis groups add group-list priv {user | admin}
Use this command to add the privileges for NIS users in the
group-list as administrators or users. This command is
available to administrative users only.
72 authentication
groups del
authentication nis groups del group-list priv {user | admin}
Use this command to delete the privileges for NIS users in the
group-list as administrators or users. This command is available
to administrative users only.
groups reset
authentication nis groups reset
Use this command to delete all added NIS groups. This command
is available to administrative users only.
groups show
authentication nis groups show
Use this command to display lists of both NIS user groups and NIS
admin groups.
reset
authentication nis reset
Use this command to delete the NIS configuration and set it to the
default.
servers
servers add
authentication nis servers add server-list
Use this command to add NIS servers to the server-list. This
command is available to administrative users only.
servers del
authentication nis servers del server-list
Use this command to delete NIS servers from the server-list.
This command is available to administrative users only.
servers show
authentication nis servers show
Use this command to display a list of NIS servers. The display is
similar to the following:
# authentication nis servers show
NIS Servers:
dd120-18
show
authentication nis show
Use this command to display the NIS configuration. The display is
similar to the following:
# authentication nis servers show
NIS Servers:
dd120-18
sysadmin@dd120-19# authentication nis show
NIS Summary:
Domain: datadomain.com
Servers: dd120-18
Admin Groups:
User Groups:
Enabled: No
Status: N/A (NIS Disabled)
status
authentication nis status
Use this command to display the NIS status.
74 authentication
6 autosupport
76 autosupport
autosupport Command Options
add
autosupport add email-list
Use this command to add email addresses to the list that receives
system reports. The email-list is a list of email addresses that are
separated by commas, spaces, or both. (The autosupport email list
contains the autosupport@autosupport.datadomain.com
address by default.) This command is available to administrative
users only.
In Global Deduplication Arrays, this command is run on the
master controller only.
To add the email address djones@yourcompany.com to the list,
use the command:
# autosupport add djones@yourcompany.com
del
autosupport del email-list
Use this command to delete email addresses from the list. The
email-list is a list of email addresses that are separated by
commas, spaces, or both. This command is available to
administrative users only.
In Global Deduplication Arrays, this command is run on the
master controller only.
For example, to remove an email address from the list, use:
# autosupport del jsmith@yourcompany.com
reset schedule
autosupport reset schedule
Use this command to set the system report schedule to the default
(daily 0600). This command is available to administrative users
only.
In Global Deduplication Arrays, this command is run on the
master controller only and the email list and schedule set on the
master controller are automatically propagated to the worker
controller.
reset support-list
autosupport reset support-list
Use this command to set the email list to the factory defaults. This
command is available to administrative users only.
In Global Deduplication Arrays, this command is run on the
master controller only and the email list and schedule set on the
master controller are automatically propagated to the worker
controller.
78 autosupport
send
autosupport send [email-addr] [cmd "cmd"]
Use this command to run the system report and email the results to
either a single address (using the email-addr option) or all
addresses on the autosupport list.
With an email address and a Data Domain system command,
autosupport sends the output of the command to the address.
Enclose the command that is to generate output in double
quotation marks.
With only a command, autosupport sends the command
output to the autosupport list.
When neither email addresses nor a command is specified,
then an autosupport message is generated and sent to all email
addresses in the autosupport list.
To send an autosupport message to djones@yourcompany.com,
use the command:
# autosupport send djones@yourcompany.com
To send the output of net stats show to
djones@yourcompany.com, use:
# autosupport send djones@yourcompany.com cmd net show stats
show
show all
autosupport show all
Use this command to display all autosupport parameters. 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. The display is similar to the following:
# autosupport show all
The Admin email is: admin@yourcompany.com
The Autosupport email list is:
autosupport@datadomain.com
admin@yourcompany.com
Autosupport is scheduled to run "Sun" at "0600"
80 autosupport
show history
autosupport show history
Use this command to display the event history file, which includes
the date for each Autosupport Report. Use the up and down arrow
keys to move through the log. Use the q key to exit. Enter a
forward slash (/) and a pattern to search for and highlight lines of
particular interest.
The command returns entries similar to the following:
# autosupport show history
Nov 10 03:00:19 scheduled autosupport
Nov 11 03:00:19 scheduled autosupport
Nov 12 03:00:19 scheduled autosupport
show report
autosupport show report
Use this command to run and display the normal system report,
but not send email. Use the up and down arrow keys to move
through the log. Use the q key to exit. Enter a forward slash (/) and
a pattern to search for and highlight lines of particular interest.
show schedule
autosupport show schedule
Use this command to display the system report schedule.
The display is similar to the following:
# autosupport show schedule
Autosupport is scheduled to run "Sun" at "0600"
show support-list
autosupport show support-list
Use this command to display the autosupport email list.
autosupport Examples
Configuring autosupport
Schedule the Autosupport Report
To schedule the system report for every Tuesday at 3 p.m., use the
following command:
# autosupport set schedule tue 1500
To schedule the system report for 2 p.m. every Monday and
Friday, use:
# autosupport set schedule mon,fri 1400
To send a copy of the log file messages.1 to Data Domain
Support, use:
# autosupport send support@datadomain.com cmd "log
view messages.1"
Managing autosupport
Run the Autosupport Report
Use the autosupport show report command to manually run
and immediately display the Autosupport Report. 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.
82 autosupport
The display is similar to the following. The first section gives
system identification and uptime information:
# autosupport show report
========== GENERAL INFO ==========
GENERATED_ON=Wed Feb 11 13:17:48 UTC 2009
VERSION=Data Domain OS 4.6.0.0-62320
SYSTEM_ID=Serial number: 22BM030026
MODEL_NO=DD560
HOSTNAME=dd10.yourcompany.com
LOCATION=Bldg12 room221 rack6
ADMIN_EMAIL=admin@yourcompany.com
UPTIME= 1:17pm up 124 days, 14:31, 2 users, load
average: 0.00, 0.00, 0.00
The next sections display output from numerous Data Domain
system 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.
84 autosupport
7 cifs
add
Note: Data Domain recommends using the cifs share create
command instead of the cifs add command, except when adding
the name of an individual client.
When entering the client list for the cifs add command:
Separate clients in the list by a comma, a space, or both.
The client-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.
86 cifs
add /backup
cifs add /backup client-list
Use this command to specify the CIFS backup clients that can
access a Data Domain systems /backup directory. The /backup
directory is the target directory for compressed backup server
data.
add /ddvar
cifs add /ddvar client-list
Use this command to specify the administrative clients that can
access a Data Domain systems /ddvar directory, which contains
Data Domain system core and log files.
Note: After a CIFS client name has been added, it needs to be
configured to access the Data Domain system. If CIFS is not
enabled on the Data Domain system, it must be enabled via the
cifs enable command. Data Domain integration documents
explain how to configure the client. Go to the Documentation >
Integration Documentation page at the Data Domain Support Web
site (https://my.datadomain.com). Select the vendor for the clients
operating system and then select the appropriate tuning
document.
del
Note: Data Domain recommends using the cifs share destroy
command instead of the cifs del command, except when
deleting the name of an individual client.
When entering the client list for the cifs del command:
Separate clients in the list by a comma, a space, or both.
The client-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.
del /ddvar
cifs del /ddvar client-list
Use this command to specify administrative clients to remove from
the list of clients that can access a Data Domain systems /ddvar
directory, which contains Data Domain system core and log files.
disable
cifs disable
Use this command to disable the CIFS service on the Data Domain
system, thereby preventing CIFS clients from connecting to it.
enable
cifs enable
Use this command to enable the CIFS service on the Data Domain
system and give clients CIFS access.
hosts
hosts add
cifs hosts add ipaddr host-list
Use this command to add an lmhosts mapping. The lmhosts file
is a local text file that maps IP addresses to NetBIOS names. One IP
address can have multiple hostnames.
88 cifs
hosts del
cifs hosts del ipaddr
Use this command to remove the lmhosts mapping for the
specified IP address.
hosts reset
cifs hosts reset
Use this command to reset the lmhosts mapping to the default,
which is to remove all IP address and NetBIOS hostnames from the
lmhosts file.
hosts show
cifs hosts show
Use this command to display lmhosts mappings.
nb-lookup
cifs nb-lookup nb_hostname
Use this command to display the IP address for the specified
NetBIOS name when CIFS is enabled.
option
option reset
cifs option reset name
Use this command to reset the specified option to its default value.
90 cifs
option set interfaces
cifs option set interfaces value
Use this command to set the interfaces network interfaces on
which the CIFS server listens for client connections. The value
is a list of interface names. Multiple interfaces must be
separated by a space and enclosed within double quotation
marks; for example, "eth0 eth2".
By default, the CIFS server listens on all Data Domain system
NIC-active interfaces. Use this command to restrict the CIFS
server access to specified interfaces.
restrict-anonymous
cifs option set restrict-anonymous {enabled | disabled}
Use this command to control anonymous connections. The default
value is disabled, which allows anonymous connections.
92 cifs
option set smbd-mem-limit
cifs option set smbd-mem-limit value
Use this command to set the amount of memory available for
SMBD connections. Some backup applications open more SMBD
sessions and connections if the system does not process SMBD
operations as fast as expected, which might be the case when there
is a large number of file deletions. New connections also slow
down operations. Increase memory for SMBD to avoid looping.
The value is an integer from 52428800 to 1073741824 with a default
value of 209715200.
option show
cifs option show
Use this command to display the CIFS options.
reset clients
cifs reset clients
Use this command to reset the CIFS client access list for the backup
and administrative clients (shared backup and ddvar) to the
default, which does not grant access to any client. In addition, the
backup and ddvar shares are also removed.
reset nb-hostname
cifs reset nb-hostname nb_hostname
Use this command to reset the NetBIOS hostname to the default,
which is none.
reset wins-server
cifs reset wins-server
Use this command to set the WINS server IP address to the default,
which is none.
94 cifs
set
set authentication active-directory
cifs set authentication active-directory realm {[dc1[dc2...]]/
| *}
Use this command to set the authentication to the active directory.:
The realm must be a fully qualified name.
Note: Data Domain does not recommend specifying a domain
controller. Instead, specify all controllers by entering an asterisk
(*).
(Optional) Specify multiple domain controllers (dc). The
entries in the domain controller list entries can be separated
by commas, spaces, or both.
When you enter this command, you are prompted for a user
account. Enter either a user on your companys domain, or a user
in a domain that is a trusted domain of your company. This user
must have permission to create accounts in your companys
domain.
The Data Domain system automatically adds a host entry to the
DNS server, so it is not necessary to manually create the DNS host
entry for the Data Domain system.
Note: If you set NetBIOS hostname using the command cifs set
nb-hostname, the entry is created for NetBIOS hostname instead
of the system hostname. Otherwise, the system hostname is used.
set nb-hostname
cifs set nb-hostname nb_hostname
Use this command to set the NetBIOS hostname.
set wins-server
cifs set wins-server ipaddr
Use this command to set the WINS server IP address. If CIFS
clients are using NetBIOS, a WINS server may be needed to resolve
NetBIOS names to IP addresses.
share
share create
cifs share create share-name path path {max-connections number
| clients "client-list" | browsing {enabled | disabled} |
writeable {enabled | disabled} | users "user-names" |comment
"comment"}
Use the share create command to add a share.
Note: /backup subdirectory is not supported in Global
Deduplication Array.
Note the command options:
share-name A descriptive name for the share.
path The path to the target directory.
max-connections The maximum number of connections to the
share that are allowed at one time.
96 cifs
client-list A comma-separated list of clients that are
allowed to access the share. You can specify the
clients by host name or IP address. No blanks or
tabs (white space) characters are allowed. The list
must be enclosed in double quotation marks. For
example, use:
"host1,host2"
"host1,10.24.160.116"
browsing The share can be seen (enabled, which is the
default), or not seen (disabled) by Web browsers.
writeable The share can be writable (enabled, the default),
or not writable (disabled).
Note: All administrative users have write
privileges, by default, even if writable is disabled
user-names A comma-separated list of user names. Other
than the comma delimiter, any white space
(blank or tab) characters are treated as part of the
user name because a Windows user name can
have a space character in the name. The list must
be enclosed in double quotation marks. For
example, "user1,user2" or
"user1,@group1"
The user names list can include group names,
which must be proceeded by the at (@)
symbol, such as @group1.
All users in the client list can access the share,
unless one or more user names are specified, in
which case only the listed names can access the
share. Group names and user names should be
separated only by commas, not by spaces.
There can be spaces inside the name of a
group, but there should not be spaces between
groups.
comment A descriptive comment about the share.
share destroy
cifs share destroy share share
Use this command to delete a share.
share disable
cifs share disable share share
Use this command to disable a share.
share enable
cifs share enable share share
Use this command to enable a share.
share modify
cifs share modify share {max-connections number |clients
"client-list" | browsing {enabled | disabled} |writeable
{enabled | disabled} | users "user-names"}
Use this command to modify a share configuration with the same
configuration options as in the cifs share create command,
98 cifs
except for its path. You cannot change the path for an existing
share. Modifications apply to new connections only.
See the share create command for a description of the command
variables. To remove a user list for the share, specify "user-
names".
share show
cifs share show share
Use this command to display share configurations for all shares, or
for a specified share.
show
show active
cifs show active
Use this command to display all active CIFS clients.
show clients
cifs show clients
Use this command to display all allowed CIFS clients for the
default /ddvar administrative share and the default /backup data
share.
Note: Use the cifs share show command to show client access
information for custom shares.
show config
cifs show config
Use this command to display the CIFS configuration.
Note: In the output display, the entry "Windows 2002 Service Pack
2 2600" is more commonly known as Windows XP.
show stats
cifs show stats
Use this command to display statistics for SMB reads, writes, and
total operations.
status
cifs status
Use this command to display whether the CIFS service is enabled
or disabled on the system.
troubleshooting
troubleshooting domaininfo
cifs troubleshooting domaininfo
Use this command to report domain information. Specifically, it
useful when you want to check the connectivity between the Data
100 cifs
Domain system and the domain or when you suspect that, due to
domain connectivity, you have authentication issues.
troubleshooting groups
cifs troubleshooting group groupname
Use this command to list details for a specified group.
troubleshooting list-groups
cifs troubleshooting list-groups
Use this command to list all CIFS groups.
troubleshooting list-users
cifs troubleshooting list-users
Use this command to list all CIFS users.
troubleshooting performance
cifs troubleshooting performance
Use this command to collect tcpdump and ddfs traces for CIFS
performance analysis. If you are having performance problems,
enter these commands in succession:
# cifs troubleshooting performance
# support upload bundle
troubleshooting users
cifs troubleshooting user username
Use this command to list details for a specified user.
Add a Share
1. On the Data Domain system, add the list of clients that can
access the system. For example:
# cifs share create backup path /backup clients "10.24.160.116"
2. On a CIFS client, browse to \\dd\backup and create the share
directory, such as \\dd\backup\dir2.
3. On the CIFS client, set share directory permissions or security
options.
4. On the Data Domain system, create the share and add users,
which are the clients that were given access to the system. For
example:
# cifs share create dir2 path /backup/dir2 clients
"host1,host2" users "domain\user5,domain\user6"
5. To create a share named user5 and allow a maximum of five
client connections with client access for a client named db1,
enter:
# cifs share create user5 path /backup/user5 max-connections
5 clients "db1.domain.com" comment "user5 backups"
To create a share named share6 and limit access to the share to the
built-in CIFS user sysadmin, enter:
# cifs share create share6 path /backup/share6 clients * users
"sysadmin"
Note: When mapping share6, use the Data Domain system name
as the domain name; for example, use dd1\sysadmin.
6. To give Data Domain system administrative access to a
Windows group named backup-admin and to map the Data
Domain system "dd admin group1" to the group, enter:
# cifs option set "dd admin group1" "windows backup-admin"
102 cifs
Allow Class C Network Access to a Share
To allow class C network access to a share, use CIDR notation or
the class C network's address and subnet mask to specify the
client.
To add a subnet by using CIDR notation:
# cifs share create test path /backup clients "192.168.4.0/22"
To add a subnet by using a class C network subnet mask:
# cifs share create test path /backup clients
"192.168.4.0/255.255.252.0"
To add two class C network subnets:
# cifs share create test path /backup/test clients
"192.168.4.0/255.255.255.0,192.168.5.0/255.255.255.0"
add
cluster add node-name [license license-code]
After creating a Global Deduplication Array, enter this
administrative command from the master controller to add the
second controller to the Global Deduplication Array. The file
system must be disabled on the master controller. The second
controller must be identical to the master controller in terms of DD
OS software, storage capacity, and hardware model. The second
controller must have a pristine file system. To add the first
controller, use the cluster create command.
All of the controllers added to the Global Deduplication Array
must have a Global-Deduplication license.
alerts
cluster alerts show
Use this administrative command to show active alerts in the
Global Deduplication Array.
Each controller reports its alert status, even if there are no active
alerts. If there is an alert for a controller, the alert time and a
description of the problem are given.
An example summary of the number of alerts for each controller
follows:
Alerts from node dd880-1.company.com (Serial No:
8DDXXXXXXX)
106 cluster
An example from a two-controller Global Deduplication Array
follows:
sysadmin@dd690-43(Master:1)# cluster alerts show
Alerts from node "dd690-43.datadomain.com" (Serial No:
8DD6927005)
No active alerts.
Alerts from node "dd690-44.datadomain.com" (Serial No:
8DD6927006)
Alert Id Alert Time Description
-------- ---------------- -------------------------
4 Thu Sep 24 11:13 Encl 2 (50050CC100100D33) Disk 15 has
failed and should be replaced
-------- ---------------- -------------------------
There is 1 active alert.
create
cluster create cluster-name
Use this administrative command to create a new Global
Deduplication Array. The name you assign is the name by which
the Global Deduplication Array is identified within the CLI and
Data Domain Enterprise Manager. This command must be
executed on the master controller. The file system must be in a
pristine state.
destroy
cluster destroy cluster-name
Use this administrative command to destroy the filesystem on all
of the arrays controllers and to separate the controllers from the
Global Deduplication Array. All of the controllers are converted to
single-controller functionality.
This command must be executed on the master controller. This
command reboots all of the controllers in the Global Deduplication
Array.
108 cluster
show config
cluster show config
All users can run this command on any controller of the Global
Deduplication Array to display array membership information.
The following information is shown for each controller in the
Global Deduplication Array:
Name: for example, dd880-1.company.com
Serial Number
Role: Master or Worker
Management Interface: the IP address of the management
interface for the controller.
Data Interface: the IP address of the data interface.
Replication Interface: the IP address of the replication interface.
Global Deduplication Array Interface: the IP address of the
Global Deduplication Array interconnect between the arrays
controllers.
Number: the number assigned to the controller; for example, 1,
2.
status
cluster status [node node-name | all]
All users can run this command to show the status for a specific
controller or for all controllers in the Global Deduplication Array.
You can run this command on the master controller only.
If you enter cluster status without any options, a summary of
the arrays status is displayed for each controller. This summary
provides the following information:
Filesystem status, such as:
The filesystem is enabled and running.
Name: For example, dd880-1.company.com
Role: Master or Worker
110 cluster
9 config
reset
reset location
config reset location
Use this command to reset the location description to the system
default of a null entry. This command is available to
administrative users only
reset mailserver
config reset mailserver
Use this command to reset the mail server used by the Data
Domain system to the system default of a mail. This command is
available to administrative users only.
reset timezone
config reset timezone
Use this command to reset the time zone used by the Data Domain
system to the system default of US/Pacific. This command is
available to administrative users only.
112 config
set
set admin-email
config set admin-email email-addr
Use this command to give the required address for alerts and
autosupport emails to other recipients. The system needs only one
administrative email address. Use the autosupport and alerts
commands to add other email addresses. This command is
available to administrative users only.
For example, use the command:
# config set admin-email jsmith@company.com
The Admin Email is: jsmith@company.com
To check the current setting, use the config show admin-email
command.
set admin-host
config set admin-host host
Use this command to set the machine from which you can log into
the Data Domain system to see system logs and use system
commands. The host name can be a simple host name, a host name
with a fully-qualified domain name, or an IP address. The host is
also added to the FTP and Telnet lists and (if the features are
licensed) to the CIFS and NFS lists for access to /ddvar and
/backup. This command provides a quick way to add
authentication privileges. This command is available to
administrative users only.
For example, to set the administrative host to
admin12.yourcompany.com, use:
# config set admin-host admin12.yourcompany.com
The System Admin host is admin12.yourcompany.com
To check the current setting, use the config show admin-host
command.
set mailserver
config set mailserver host
Use this command to change the SMTP mail server used by the
Data Domain system. This command is available to administrative
users only.
For example, to set the mail server to mail.yourcompany.com,
use:
# config set mailserver mail.yourcompany.com
The Mail (SMTP) server is: mail.yourcompany.com
To check the current setting, use the config show mailserver
command.
114 config
set timezone
config set timezone zonename
Use this command to set the system clock to a specific time zone.
The default setting is US/Pacific. For the change to take effect for
all currently running processes, you must reboot the Data Domain
system. This command is available to administrative users only.
For example, to set the system clock to the time zone that includes
Los Angeles, California, USA, use:
# 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
Ambiguous timezone name; matching...
US/Alaska US/Aleutian US/Arizona US/Central
US/Eastern US/East-Indiana US/Hawaii US/Indiana-Starke
US/Michigan US/Mountain US/Pacific US/Samoa
setup
config setup
Use this command to change multiple essential configuration
settings. The command displays the current value for each setting.
Press the Enter key to retain the current value for a setting. This
command is available to administrative users only.
Many other Data Domain system commands change configuration
settings. For example, the user command adds another user
account each time a user is added.
show admin-host
config show admin-host
Use this command to display the administrative host from which
you can log into the Data Domain system to see system logs and
use system commands.
The display is similar to the following:
# config show admin-host
The Admin Host is: admin12.yourcompany.com
show all
config show all
Display all config command settings
show location
config show location
Use this command to display the Data Domain system location
description, if you gave one.
The display is similar to the following:
# config show location
The System Location is: bldg12 rm 120 rack8
116 config
show mailserver
config show mailserver
Use this command to display the name of the mail server that the
Data Domain system uses to send email.
The display is similar to the following:
# config show mailserver
The Mail (SMTP) server is: mail.yourcompany.com
show timezone
config show timezone
Use this command to display the time zone used by the system
clock.
The display is similar to the following:
# config show timezone
The Timezone name is: US/Pacific
config Examples
Configuring config
Set the Timezone
To set the time zone for the Pacific coast of the U.S.A., use:
# config set timezone Los_Angeles
To find all time zones that include a match for new, use:
# config set timezone new
Ambiguous timezone name; matching ...
America/New_York Canada/Newfoundland
add
add dev
disk add devdisk_id spindle-group 1-16
Use this command to add a new LUN to the current volume,
optionally assigning it to the specified spindle-group. To get the
devid#, use the disk rescan command and then use the disk
show raid-info command. The devid# format is the word dev
and the number as seen in output from the disk show raid-info
command.
If the keyword spindle-group is specified, the LUN disk-id is
assigned to the given spindle-group. The designated spindle-
group must be within the range of 1 through 16. Spindle-group 1 is
the default spindle-group. By default, the device is assigned to the
default spindle-group (1).
For example, to add a LUN with a devid# of 2 as shown by the
disk show raid-info command, use:
120 disk
# disk add dev2
To add a new LUN and assign it to a spindle-group, use:
# disk add dev2 spindle-group 7
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 or destroying the filesystem.
Are you sure? (yes|no|?) [no]: yes
ok, proceeding.
Please enter sysadmin password to confirm 'disk
add':
This command may take several minutes to complete;
please wait.
disk add device............. [ - ]
disk add device............. [success]
This device has created a new spindle-group 7. When
creating new spindle-groups, the filesystem should
be re-started to load-balance correctly
Notes:
The disk add command adds a disk to the filesystem.
Once the disk is added, it cannot be removed from the
filesystem without destroying the filesystem.
Also, when creating new spindle-groups, the filesystem
should be re-started to load-balance correctly.
add enclosure
disk add enclosure enclosure-id
Use this command to add a Data Domain expansion shelf disk
storage unit. The enclosure-id is always 2 for the first added
shelf, 3 for the second, and so forth all the way up to 7 for the sixth
added shelf. The Data Domain system always has the enclosure-
id number of 1 (one).
expand
disk expand
Use this command to expand disk usage from eight disks plus one
spare to 14 disks plus one spare for the DD510 and DD530, or six
disks plus one to 11 disks plus one spare for the later Data Domain
systems.
Expansion can occur only when the first nine disks are not in a
degraded state, and there is at least one spare disk. (To verify this,
enter the disk status command. In the output, the in use line
must show at least eight disks as in use, and the spare line must
show at least one disk as spare.)
122 disk
fail
disk fail enclosure-id.disk-id
Use this command to set a disk to the failed state. The command
asks for a confirmation before carrying out the operation. This
command is available to administrative users only.
A failed disk is automatically removed from a RAID disk group
and is replaced by a spare disk (when a spare is available). The
disk use changes from spare to in use and the status becomes
reconstructing. See show detailed-raid-info to list the available
spares.
Up to two disks in the head unit can be failed at the same time in
most Data Domain systems, with the exception of the DD120 and
DD140, which have only three disks (and no spare) so only one
disk can be failed.
Always replace a failed disk as soon as possible. Spare disks are
supplied in a carrier for a Data Domain system or a carrier for an
expansion shelf. DO NOT move a disk from one carrier to another.
multipath
multipath failback
disk multipath failback
Use this command to manually force all disks to use the primary
path. This command works on gateway models only. This
command is available to administrative users only.
124 disk
multipath reset stats
disk multipath reset stats
Use this command to clear the statistics of all paths to all disks in
all expansion shelves. This command is available to administrative
users only.
multipath resume
disk multipath resume port port-id
Use this command to allow I/O on specified initiator port. This
command is available to administrative users only.
multipath status
disk multipath status [port-id]
Use this command to show multipath configurations and run time
status.
multipath suspend
disk multipath suspend port port-id
Use this command to disallow I/O on specified initiator port, and
to stop traffic on particular ports during scheduled maintenance of
the SAN or storage array, and so forth. This command does not
drop the FC link. This command is available to administrative
users only.
126 disk
Offline
Disabled
When a port is listed as disabled, the following message
appears:
Contact your contracted support provider or
visit us online at https://my.datadomain.com
rescan
disk rescan
Use this command to check for new internal or external storage of
all types. This command is available to administrative users only.
reset
disk reset performance
Use this command to reset disk performance statistics to zero. See
show detailed-raid-info for displaying disk statistics. This command
is available to administrative users only.
set
set spindle-group
disk set devdisk_id spindle-group 1-16
Use this command to assign a LUN group to the disk. This
command is available to administrative users only. For example:
# disk set dev1 spindle-group 8
The 'disk set' command assigns a lun-group to the
disk/lun. Are you sure? (yes|no|?) [no]: yes
ok, proceeding.
Please enter sysadmin password to confirm 'disk
set':
This command may take several minutes to complete;
please wait.
Disk dev1 has been added to spindle-group 8. The
result will be effective after the filesystem is
restarted.
128 disk
Capacity The amount of data in a volume sent to the Data
Domain system.
Spindle-Group The spindle-group for this LUN. (Present for
gateway systems only.)
show detailed-raid-info
disk show detailed-raid-info
Use this command to display RAID disk groups and disk status
within each group. On a gateway system, the display does not
include information about individual disks.
The short example below does not include a spare disk. RAID
groups usually have a spare disk.
Disk Status
show failure-history
disk show failure-history
Use this command to display a list of serial numbers for all disks
that have ever been failed in the Data Domain system. Use the
disk show hardware command to display the serial numbers of
current disks.
130 disk
show performance
disk show performance
Use this command to display disk performance statistics for each
disk. Each column displays statistics averaged over time since the
last disk reset performance command or since the last system
power cycle. See reset for reset details.
Command output from a gateway Data Domain system lists each
LUN accessed by the Data Domain system as a disk.
Disk (enc/disk) The enclosure and disk numbers.
Read sects/s The average number of sectors per second
written to each disk.
Write sect/s The average number of sectors per second
written to each disk.
Cumul. MiBytes/s The average number of megabytes per second
written to each disk.
Busy The average percent of time that each disk has at
least one command queued.
132 disk
show reliability-data
disk show reliability-data
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 The enclosure.disk-id disk identifier.
ATA Bus CRC Err The uncorrected raw UDMA CRC errors.
Reallocated Sectors The number of mapped-out defective sectors.
Temperature The current temperature of each disk in Celsius
and Fahrenheit. The allowable case temperature
range for disks is from 5 centigrade to 55
centigrade.
status
disk status
Use this command to report the overall status of disks in the
system. It displays the number of disks in use and failed, the
number of spare disks available, and whether or not a RAID disk
group reconstruction is underway.
Note: 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.
On a gateway Data Domain system, the display shows only the
number and state of the LUNs accessed by the Data Domain
DD OS 4.9 Command Reference Guide 133
system. The remainder of the display is not valid for a gateway
system.
Reconstruction is done on one disk at a time. If more than one disk
is to be reconstructed, the disks waiting for reconstruction show as
spare or hot spare until reconstruction starts on the disk.
134 disk
unfail
disk unfail enclosure-id.disk-id
Use this command to change a disk status from failed to
available. Use the command when replacing a failed disk. The
new disk in the failed slot is seen as failed until the disk is
unfailed. This command is available to administrative users only.
Caution: Use of this command repartitions the disk. Any data
residing on the disk will be difficult, if not impossible to retrieve.
disk Examples
136 disk
11 enclosure
beacon
enclosure beacon enclosure-id
Use this command to check that the DD OS and hardware
recognize an enclosure. The command causes the green (activity)
LED on each disk in an enclosure to flash green. Press Ctrl+c to
halt the command. This command is available to administrative
users only.
show
show all
enclosure show all [enclosure-id]
Use this command to display the temperatures and the status of
fans and power supplies.
Note: The status of individual power supplies is displayed with
the exception of 4xx models (including 560), which are shown in
aggregated status. For an enclosure connected to a 560, you will
see an individual report.
show controllers
enclosure show controllers [enclosure-id]
Use this command to display information and status for the ES20
enclosure and the shelf controller systems or a specific controller
system.
# enclosure show controllers
Enclosure 1
Model ES20
Capacity 16 Slots
WWN 50050CC1001010B1
Serial # 50050CC1001010B1
Number of Controllers 2
Controller A
WWN 50050CC1010203CF
138 enclosure
Firmware 0605
Serial # IMS5846010203CF
Status OK
HOST port 12.0 Gbps
EXP'N port 12.0 Gbps
Controller B
WWN 50050CC1010371CF
Firmware 0605 R02
Serial # IMS5846010371CF
Status OK
HOST port 12.0 Gbps
EXP'N port 0.0 Gbps
show fans
enclosure show fans [enclosure-id]
Use this command to display the current status of fans in all
enclosures or in a specific enclosure.
To show the status of all fans for a system:
# enclosure show fans
Enclosure 1
Fans
Description Level Status
-------------- ------ ------
140 enclosure
Cooling fan #1 medium OK
Cooling fan #2 medium OK
-------------- ------ ------
show powersupply
enclosure show powersupply [enclosure-id]
Use this command to display the status USAF power supplies in
all enclosures or in a specific enclosure.
Note: The status of individual power supplies is displayed with
the exception of 4xx models (including 560), which are shown in
aggregated status. For an enclosure connected to a 560, you will
see an individual report.
This report for shows the status of individual power supplies:
# enclosure show powersupply
Enclosure Description Status
--------- --------------- ------
1 Power Module #1 OK
1 Power Module #2 OK
2 Power Module #1 OK
2 Power Module #2 OK
--------- --------------- ------
This report for shows the aggregated status of all power supplies:
# enclosure show powersupply
Power Supply
Status
------
OK
------
show summary
enclosure show summary
Use this command to list known enclosures, model numbers, serial
numbers, and capacity (number of disks in the enclosure). The
serial number for an expansion shelf is the same as the chassis
serial number, which is the same as the enclosure WWN (world-
wide name) and the OPS panel WWN.
# enclosure show summary
Enclosure Model No. Serial No. Capacity
--------- --------- ---------- --------
1 DD560 8F41214030 15 Slots
2 ES20 50050CC100123456 16 slots
2 ES20 50050CC100123457 16 slots
--------- --------- ---------------- --------
3 enclosures present.
show temperature-sensors
enclosure show temperature-sensors [enclosure-id]
Use this command to list the internal and CPU chassis
temperatures for a system and the internal temperature for
expansion shelves. CPU temperatures may be shown in relative or
ambient readings. The CPU numbers depend on the Data Domain
system model. With newer models, the numbers are negative
when the status is OK and move toward 0 (zero) as CPU
temperature increases; if a CPU temperature reaches 0 Celsius,
the Data Domain system shuts down. With older models, the
numbers are positive; if the CPU temperature reaches 80 Celsius,
the Data Domain system shuts down. A Status of Critical
indicates that the temperature is above the shutdown threshold.
142 enclosure
In the following example, the temperature for CPU 0 is 97
Fahrenheit below the maximum:
# enclosure show temperature-sensors
Enclosure Description C/F Status
--------- --------------- ------- ------
1 CPU 0 Relative -54/-97 OK
Chassis Ambient 23/73 OK
--------- --------------- ------- ------
show topology
enclosure show topology
Use this command to show the layout of the SAS enclosures
attached to a system.
The output of the command looks like the following sample:
# enclosure show topology
Error Message:
-----------------
No error detected
144 enclosure
enclosure Examples
clean
The filesys clean command reclaims physical storage occupied
by deleted objects in the Data Domain file system. Only a filesys
clean command reclaims the physical storage used by files that
are deleted and that are not present in a snapshot.
During the clean operation, the Data Domain 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 Data Domain system. 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.
148 filesys
When the clean operation finishes, it sends a message to the
system log giving the percentage of storage space that was
cleaned.
A default schedule runs the clean operation every Tuesday at 6
a.m. (tue 0600). You can change the schedule or you can run the
operation manually with the filesys clean commands. Data
Domain recommends running the clean operation once a week. If
you want to increase file system availability and if the Data
Domain system is not short on disk space, consider changing the
schedule to clean less often.
Notes:
Any operation that shuts down the Data Domain system file
system, such as the filesys disable command, or that shuts
down the Data Domain system, 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 clean
operation.
Replication between Data Domain systems can affect filesys
clean operations. If a source Data Domain system receives
large amounts of new or changed data while replication is
disabled or disconnected, resuming replication may
significantly slow down filesys clean operations.
When there is a large replication lag, cleaning is not efficient
and does not clean up much space, because what has not been
replicated is not cleaned.
clean reset
filesys clean reset {schedule | throttle | all}
Use this command to set the clean schedule to the default of
Tuesday at 6 a.m. (tue 0600), the default throttle of 50%, or both.
The operation is available only to administrative users.
Time is 24-hour military time. 2400 is not a valid time. mon 0000 is
midnight between Sunday night and Monday morning. A new set
schedule command cancels the previous setting.
150 filesys
the system is busy. A percentage of 100 allows cleaning to use
system resources in the usual way. The default is 50. When the
Data Domain system is not busy with backup or restore
operations, cleaning runs at 100% (uses resources as does any other
process). This command is available to administrative users only.
For example, to set the clean operation to run at 30% of its
possible speed, use:
# filesys clean set throttle 30
clean status
filesys clean status
Use this command to display the active or inactive status of the
clean process. When the clean process is running, the command
displays progress.
The display is similar to the following:
# filesys clean status
Cleaning started at 2009/02/06 10:21:51: phase 6 of
10
64.6% complete, 2496 GiB free; time: phase 1:06:32,
total 8:53:21
clean stop
filesys clean stop
Use this command to stop the clean process. Stopping the process
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. This command is
available to administrative users only.
152 filesys
clean watch
filesys clean watch
Use this command to monitor an ongoing clean process,. The
output is the same as output from the filesys clean status
command, but continuously updates. Press Ctrl+c to stop
monitoring the progress of a clean process. The process continues,
but the reporting stops. Use the filesys clean start command
to restart monitoring. This command is available to administrative
users only.
destroy
filesys destroy [and-zero] [and-shrink]
Use this command to delete all data in the Data Domain system file
system and re-initialize the file system. This command also
removes Replicator configuration settings. Deleted data is not
recoverable. This command is available to administrative users
only.
and-zero This option writes zeros to all disks, which can take
many hours.
and-shrink This option removes any additional external storage
that was added to the system using the disk add
command and returns the system to the factory
default state. When this option is used in conjunction
with the and-zero option, the file system is zeroed
prior to removing any storage.
disable
filesys disable
Use this command to stop the Data Domain system file system,
which stops Data Domain system operations (including cleaning).
This command is available to administrative users only.
Note: The file system in a Global Deduplication Array is treated as
a single file system so the command output differs.
enable
filesys enable
Use this command to start the Data Domain system file system,
allowing Data Domain system operations to begin. This command
is available to administrative users only.
Note: The file system in a Global Deduplication Array is treated as
a single file system so the command output differs.
154 filesys
encryption
The optional Encryption of Data at Rest feature encrypts all
incoming data before being written to the physical storage media.
The data is physically stored in an encrypted manner and cannot
be accessed on the existing Data Domain system or in any other
environment without first decrypting it.
The Encryption at Rest feature protects stored data in these
situations:
Theft or loss of a Data Domain system or its external storage
hardware while in transit from one customer location to
another
Theft or loss of a disk drive from a Data Domain system or its
external storage hardware
Failure of a storage device in transit for replacement
The encryption feature uses a passphrase to encrypt and decrypt
the keys that, in turn, get used to encrypt and decrypt the data.
Thus, changing the passphrase does not require re-encryption of
any stored data.
The encryption feature requires a separate license.
Caution: Unencrypted data that was stored before enabling this
feature is not automatically encrypted. To protect all of the data on
the system, be sure to enable encryption before you put the system
into use.
For a description of how Encryption at Rest works, and
information about configuring and managing the feature, see
Managing Encryption of Data at Rest in the DD OS 4.9
Administration Guide.
encryption disable
filesys encryption disable
Use this command to deactivate the encryption feature.
encryption enable
filesys encryption enable
Use this command to activate the encryption feature for new data
written to the file system and specify a new passphrase. After
running this command, you must restart the file system with the
filesys restart command. Here is an example:
# filesys encryption enable
Enter new passphrase:
Re-enter new passphrase:
Passphrases matched.
The passphrase is 'mypassphrase'.
The encryption feature is now enabled.
The filesystem must be restarted to effect this
change.
156 filesys
encryption lock
filesys encryption lock
Use this command to prepare the Data Domain system and its
external storage devices for shipment. This command creates a
new passphrase and destroys the cached copy of the current
passphrase, so anyone who does not possess the new passphrase
will not be able to decrypt the data.
Before you run this command, you must run filesys disable.
To run this command, you need to know the user names and
passwords for two accounts with system administration privileges.
# filesys encryption lock
Enter a second authorized user name: sysadmin2
Enter password:
Enter the current passphrase:
Enter new passphrase:
Re-enter new passphrase:
Passphrases matched.
The filesystem is now locked.
encryption passphrase
filesys encryption passphrase change
Use this command to change the passphrase. Before running this
command, you must run filesys disable.
encryption show
filesys encryption show
Use this command to check the status of the encryption feature.
Here is an example:
# filesys encryption show
Encryption is enabled
Algorithm: aes_256_cbc
The filesystem is unlocked
fastcopy
filesys fastcopy [force] source src-path destination dest-path
Use this command to copy a file or directory tree from a Data
Domain system source directory to another destination on the Data
Domain system. See snapshot for snapshot details.
src-path The location of the directory or file that you want to
copy. The first part of the path must be /backup.
Snapshots always reside in /backup/.snapshot.
Use the snapshot list command to list existing
snapshots.
dest-path The destination for the directory or file being copied.
The destination cannot already exist.
force Allows the fastcopy to proceed without warning
in the event the destination exists. The force option is
useful for scripting, because it is not interactive.
filesys fastcopy force causes the destination
to be an exact copy of the source even if the two
directories had nothing in common before.
Note: Users may want or need to use fastcopy
force if they are scripting fastcopy operations to
simulate cascaded replication, the major use case for
the option. It is not needed for interactive use,
because regular fastcopy warns if the destination
exists and then re-executes with the force option if
allowed to proceed.
158 filesys
Caution: If the destination has retention-locked files, fastcopy
and fastcopy force fail, aborting the moment they encounter
retention-locked files.
For example, to copy the directory /user/bsmith from the
snapshot scheduled-2007-04-27 and put the bsmith directory
into the user directory under /backup, use:
# filesys fastcopy
source /backup/.snapshot/scheduled-2007-04-
27/user/bsmith
destination /backup/user/bsmith
Like a standard UNIX copy, filesys fastcopy makes the
destination equal to the source, but not at a particular point in
time. If you change either folder while copying, there are no
guarantees that the two are or were ever equal.
option
option disable report-replica-as-writable
filesys option disable report-replica-as-writable
Use this command to set the reported read/write status of a
replication destination file system to read-only. Use the filesys
disable command before changing this option and use the
filesys enable command after changing the option. With CIFS,
use the cifs disable command before changing the option and
use the cifs enable command after changing the option. This
command is available to administrative users only.
160 filesys
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
162 filesys
After changing the setting, enter the following two commands to
enable the new setting:
# filesys disable
# filesys enable
option show
filesys option show {local-compression-type | marker-type |
report-replica-as-writable | global-compression-type}
Use this command to show the file system option settings. The
options are:
global- Display the current global compression
compression-type type.
local-compression- Display the current compression algorithm.
type
marker-type Display the current marker setting.
report-replica-as- Display the current reported setting on the
writable destination Data Domain system.
restart
filesys restart
Use this command to disable and enable the Data Domain system
file system in one operation. This command is available to
administrative users only
164 filesys
Client-Side Retention Lock File Control
This section describes how files must be processed on the client-
side interface to become retention-locked (and a UNIX interface is
described in this sectionyour interface may differ). These
changes on the client side must be implemented in addition to the
setup/configuration of the retention lock feature on the Data
Domain system.
The client-side commands are used to control the retention locking
of individual files.
Note: The commands listed in this section are to be used only on
the client-side interface, not the Data Domain system CLI.
retention-lock disable
filesys retention-lock disable
Use this command to disable the retention lock feature. This
command is available to administrative users only.
166 filesys
retention-lock enable
filesys retention-lock enable
Use this command to enable the retention lock feature. This
command is available to administrative users only.
retention-lock reset
filesys retention-lock reset path
Use this command to reset retention lock for all files on a specified
path, that is, allow all files on the specified path to be modified or
deleted (with the appropriate access rights). For example, to reset
the retention lock on all files in /backup/dir1, use the command:
# filesys retention-lock reset /backup/dir1
Resetting retention lock raises an alert and logs the names of the
retention-locked files that have been reset. On receiving such an
alert, the user should verify that the particular reset operation is
intended. This command is available to administrative users only.
retention-lock status
filesys retention-lock status
Use this command to show retention lock status. The possible
values of retention lock status are enabled, disabled, or
previously enabled.
show
show compression
filesys show compression [filename] [last n {hours | days}]
[no-sync]
Use this command to display the space used by and compression
achieved for files, directories, and file systems. In general, the more
often a backup is done for a particular file or file system, the higher
168 filesys
the compression. The output does not include global and local
compression factors for the Currently Used row, but uses a dash
(-) instead. Note that the display on a busy system may not return
for several hours, depending on the number of files. Other factors
may influence the display. The meta-data value is an estimate of
index data.
Note: Specifying a file name is not recommended. If there are
many files, it could take several hours.
filesys show compression [summary | daily | daily-detailed]
{[last n {hours | days | weeks | months}] | [start date [end
date]]}
show compression daily
Use this command to display the space used by and compression
achieved for files, directories, and file systems, daily over the
previous four full weeks and the current partial week.
show compression daily-detailed
Use this command to display a slightly more detailed version of
show compression daily. This command adds the rows Global-
Comp Factor and Local-Comp Factor.
show space
filesys show space
Use this command to display the space available to and used by
file system components. Values are in gigabytes to one decimal
place.
The display is similar to the following:
# filesys show space
Resource Size GiB Used GiB Avail GiB Use% Cleanable GiB*
------------------ -------- -------- --------- ---- --------------
/backup: pre-comp - 206.2 - - -
/backup: post-comp 342.2 3.1 339.0 1% 0.0
/ddvar 19.7 0.6 18.1 3% -
------------------ -------- -------- --------- ---- --------------
Note: GiB = Gibibyte, the base-2 equivalent of Gigabyte.
The total amount of space available for data storage can change
because an internal index may expand as the Data Domain system
fills with data. The index expansion takes space from the Avail
GiB amount.
If Use% is always high, use the filesys clean show-schedule
command to see how often the cleaning 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 Data
Domain system.
show uptime
filesys show uptime
Use this command to display the amount of time that has passed
since the file system was last enabled. The display is in days,
hours, and minutes.
170 filesys
The display is similar to the following:
# filesys show uptime
Filesys has been up 47 days, 23:28
status
filesys status
Use this command to display the state of the file system process.
The display gives a basic status of enabled or disabled with more
detailed information for each basic status.
The display is similar to the following:
# filesys status
The filesystem is enabled and running
If the file system was shut down with a Data Domain system
command, such as filesys disable, the display includes the
command. For example:
# filesys status
The filesystem is disabled and shutdown. [filesys
disable]
Note: The file system in a Global Deduplication Array is treated as
a single file system so the command output differs.
sync
filesys sync
Use this command to sync all modified files to disk.
filesys Examples
172 filesys
1. Put a retention lock on the existing file SavedData.dat by
setting its atime to a value greater than the current time plus
the minimum retention period:
ClientOS# touch -a -t 200912312230 SavedData.dat
2. To extend the retention date of the file:
ClientOS# touch -a -t 202012121230 SavedData.dat
3. To identify retention-locked files and list retention date:
ClientOS# touch -a -t 202012121200 SavedData.dat
ClientOS# ls -l --time=atime SavedData.dat
4. To delete an expired retention-locked file:
Additional Notes
A Data Domain system that has become full may need multiple
clean operations to clean 100% of the file system, especially if
there is an external shelf. 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.
Local Compression
A Data Domain system 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.
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.
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 Data Domain system using type 1 global compression
continues to use type 1 when upgraded to a new release. A
Data Domain system 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 Data Domain system 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.
When using CIFS on the Data Domain system, use the cifs
disable command before changing the reported state and use
the cifs enable command after changing the reported state.
Disk Staging
Disk staging enables a Data Domain system to serve as a staging
device, where the system is viewed as a basic disk via a CIFS share
or NFS mount point. You use disk staging in conjunction with your
backup software, such as Symantecs NetBackup (NBU),
OpenStorage lifecycle, or Legatos NetWorker.
The Data Domain disk staging feature does not require a license
and is disabled by default.
The reason that some backup applications use disk staging devices
is to enable tape drives to stream continuously. After the data is
copied to tape, it is retained on disk for as long as space is
available. Should a restore be needed from a recent backup, more
than likely the data is still on disk and can be restored from it more
conveniently than from tape. When the disk fills up, old backups
can be deleted to make space. This delete-on-demand policy
maximizes the use of the disk.
In normal operation, the Data Domain System does not reclaim
space from deleted files until a cleaning operation is done. This is
not compatible with backup software that operates in a staging
mode, which expects space to be reclaimed when files are deleted.
When you configure disk staging, you reserve a percentage of the
total space, typically 20 to 30 percent, to allow the system to
simulate the immediate freeing of space.
The amount of available space, which is shown by the filesys
show space command, is reduced by the amount of the staging
reserve. When the amount of data stored uses all of the available
space, the system is full. However, whenever a file is deleted, the
system estimates the amount of space that will be recovered by
cleaning and borrows from the staging reserve to increase the
DD OS 4.9 Command Reference Guide 175
available space by that amount. When cleaning runs, the space is
actually recovered and the reserve restored to its initial size. Since
the amount of space made available by deleting files is only an
estimate, the actual space reclaimed by cleaning may not match the
estimate. The goal of disk staging is to configure enough reserve so
that you do not run out before cleaning is scheduled to run.
176 filesys
as well as max-retention-period options are set back to their
default values on the newly created file system.
Use the help command to display help files for Data Domain
system commands.
help Examples
To list all of the Data Domain system commands by name, enter:
# help
To show the help for the command adminaccess, enter:
# help adminaccess
180 help
14 license
182 license
license Command Options
add
license add license-key [...]
Use this command to add one or more licenses for the same
feature. The code for each license is a string of 16 letters with
dashes. Include the dashes when entering the license code. Specify
multiple licenses to license a feature on multiple nodes in a Global
Deduplication Array. In a Global Deduplication Array, you must
run this command on the master controller. This command is
available to administrative users only.
del
license del license-key | license-feature
Use this command to remove a current license by specifying the
key or feature name. Enter the license feature name or key (as
shown with the license show command). In a Global
Deduplication Array, you must run this command on the master
controller. This command is available to administrative users only.
reset
license reset
Use this command to remove all licenses. This command is
available to administrative users only and is not available in a
Global Deduplication Array.
show
license show [local]
Use this command to display the features licensed on the Data
Domain system. This command is available to administrative users
only.
Running this command on the master controller in a Global
Deduplication Array displays licenses for all nodes in the Global
Deduplication Array, unless you use the local keyword. For
license Examples
Add a License
To add a license, use:
# license add ABCD-EFGH-IJKL-MNOP
To display current licenses, use:
# license show
## License Key Feature
-- ------------------- -----------------
1 BCDE-FGHI-JKLM-NOPQ REPLICATION
2 ABCD-EFGH-IJKL-MNOP VTL
-- ------------------- ----------------
184 license
15 log
Use the log command to display and manage the log file. The log
command has the following options:
host Manage the process of sending log Page186
messages to another system.
list List files in the log directory. Page188
view View the system log or another log file. Page190
watch Watch the system log or another log Page191
file scroll.
host
Data Domain systems can send log messages to other systems
which must be enabled to listen for network log messages. The
Data Domain system sends the log in the standard syslog format.
When remote logging is enabled, all of the messages in the
messages and kern.info files are exported. For managing the
selectors and receiving messages on a third-party system, see your
vendor-supplied documentation for the receiving system.
*.notice Send all messages at the notice priority and higher.
*.alert Send all messages at the alert priority and higher (alerts
are included in *.notice).
kern.* Send all kernel messages (kern.info log files).
local7.* Send all messages from system startups (boot.log files).
host add
log host add host-name
Use this command to add a system to the list that receives Data
Domain system log messages. This command is available to
administrative users only.
For example, the following command adds the system log-server
to the hosts that receive log messages:
# log host add log-server
186 log
host del
log host del host-name
Use this command to remove a system from the list of systems that
receive Data Domain system log messages. This command is
available to administrative users only.
For example, the following command removes the system log-
server from the hosts that receive log messages:
# log host del log-server
host disable
log host disable
Use this command to disable sending log messages to other
systems. This command is available to administrative users only.
host enable
log host enable
Use this command to enable sending log messages to other
systems. This command is available to administrative users only.
host reset
log host reset
Use this command to reset the log sending feature to the defaults
of disabled and an empty list. This command is available to
administrative users only.
list
log list [debug]
Use this command to list the files in the log directory with the date
each file was last modified and the size of each file.
When the command is executed without the debug option, the
following files are listed:
messages The system log, generated from Data Domain
system actions and general system operations.
space.log Messages about disk space use by Data
Domain system 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-separated-value 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.
188 log
When the command is executed with the debug option, the
following files are added to the list of files above:
access Track 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 All of the actions taken by an instance of the
.log filesys destroy command. Each instance
produces a log with a unique ID number.
disk-error-log Disk error messages.
error List errors generated by the Data Domain
Enterprise Manager operations.
kern.error Kernel error messages.
kern.info Kernel information messages.
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.
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 Data
Domain system.
view
log view [filename]
Use this command to view the log files. 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 (/) to search forward or a
question mark (?) to search backward for a pattern (for example, a
date) in the file.
190 log
watch
log watch [filename]
Use this command to display a view of the messages file that adds
new entries as they occur. Use the key combination Ctrl+c to break
out of the watch operation. With no filename, the command
displays the current messages file.
log Examples
If using FTP:
1. On the Data Domain system, use the adminaccess show
command to see that the FTP service is enabled. If the service is
not enabled, use the command adminaccess enable ftp.
2. On the Data Domain system, use the adminaccess show
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 Data Domain system. For example:
ftp://Data Domain system_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,
add:
ftp://sysadmin:your-pw@Data Domain
system_name.yourcompany.com/
5. At the login popup, log into the Data Domain system as user
sysadmin.
192 log
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 Data Domain
system, use SSH to log into the Data Domain system as
sysadmin and give the command adminaccess disable ftp.
Use the migration command to move all data from one Data
Domain system to another. The migration command has the
following options:
abort Add a migration or migration enclosure. Page196
commit Flash a migration ID LED. Page197
receive Expand Data Domain system storage Page197
capacity.
send Start migration. Page198
show stats Fail a migration and force reconstruction. Page200
status Manage and display migration Page201
information.
watch Show migration port information. Page201
abort
migration abort
Use this command to kill a migration process that is in progress.
The command stops the migration process and returns the Data
Domain system to its previous state. If the migration source Data
Domain system is part of a replication pair, replication is re-
started. Run the command on the migration source and the
migration destination. This command is available to
administrative users only.
Notes:
A migration abort leaves the password on the destination
system the same as the password on the migration source.
Using the migration abort command on a migration destination
will require a filesys destroy on that machine before the file
system can be enabled on it again.
196 migration
commit
migration commit
Use this command to limit 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 Data Domain
system at the time of the commit command (including data newly
written since the migration started) is migrated to the destination
Data Domain system. 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 you enter 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. This
command is available to administrative users only.
receive
migration receive source-host src-hostname
Use this command to prepare a Data Domain system to be a
migration destination. This command is available to
administrative users only. Use the command:
Only on the migration destination.
Before entering the migration send command on the
migration source.
After running the filesys destroy operations on the
destination.
For example, to prepare a destination for migration from a
migration source named hostA:
# filesys destroy
# migration receive source-host hostA
Caution: When preparing the destination, do not run the filesys
enable command.
198 migration
The migration send command stays open until a migration
commit command is entered. The migration commit command
should be entered first on the migration source and then on the
destination.
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, use:
# migration send col://hostB destination-host hostC
To start migration with a directory replication context of
dir://hostB/backup/dir2, use:
# migration send dir://hostB/backup/dir2
destination-host hostC
To start migration with two replication contexts using context
numbers 2 and 3, use:
# migration send rctx://2 rctx://3 destination-host
hostC
To migrate all replication contexts, use:
# migration send all destination-host hostC
For example:
# migration show stats
Destination Bytes Sent Bytes Received
Received Time
----------- ------------ ---------- ----------------
hostB 153687473704 1974621040 Fri Jan 13 09:37
----------- ------------ ---------- ----------------
200 migration
Processed
Time
----------------
Fri Jan 13 09:37
-------------------
status
migration status
Use this command to display the current status of migration. This
command is available to administrative users only.
For example:
migration status
CTX: 0
Mode: migration source
Destination: hostB
Enabled: yes
Local file system status enabled
Connection connected since Tue Jul 17
15:20:09
State: migrating 3/3 60%
Error: no error
Destination lag: 0
Current throttle: unlimited
Contexts under migration: dir://hostA/backup/dir2
watch
migration watch
Use this command to track the initial phase of migration (when
write access is blocked). The command output shows the percent
of the migration process that has been completed. This command
is available to administrative users only.
202 migration
2. On hostA (the migration and replication source), run the
following command.
# migration send dir://hostB/backup/dir2
destination-host hostC
Note that this command also disables the file system.
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.
# migration commit
Note that this command also disables the file system.
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
aggregate
Link aggregation provides improved network performance and
resiliency by using two to four network ports in parallel, thus
increasing the link speed and reliability over that of a single port.
The net aggregate commands control this feature. (Link
aggregation and Ethernet trunking are different terms for the same
thing.)
aggregate add
net aggregate add virtual-ifname mode {xor-L2 |xor-L2L3 |
roundrobin} interfaces physical-ifname-list
See Considerations for Ethernet Failover and Net Aggregation on
page 230 before setting up aggregation.
Note: To create a virtual interface, see the net create virtual
command.
Use the net aggregate add command to enable aggregation on
an existing virtual interface by specifying the physical interfaces
and mode (the mode must be specified). Available modes are the
Layer 2 or Layer 3/Layer4 implementations of the static balanced
mode, or round-robin. Choose the mode that is compatible with
the requirements of the system to which the ports are directly
attached.
206 net
The command enables aggregation on a virtual interface virtual-
ifname in the specified mode with the physical interfaces named
in physical-ifname-list. The aggregated links transmit packets
out of the Data Domain system.
The supported aggregate modes are:
aggregate del
net aggregate del virtual-ifname interfaces physical-ifname-
list
Use this command to delete interfaces from the physical list of the
aggregate virtual interface.
For example, to delete physical interfaces eth1 and eth2 from the
aggregate virtual interface veth1, use the following command:
# net aggregate del veth1 interfaces eth2,eth3
aggregate reset
net aggregate reset virtual-ifname
Use this command to remove all physical interfaces from an
aggregate virtual interface.
aggregate show
net aggregate show
Use this command to display basic information on the aggregate
setup.
The output is similar to the following:
# net aggregate show
Ifname Hardware Address Aggregation Mode Configured Interfaces
------ ---------------- ---------------- ---------------------
veth1 00:15:17:0f:63:fc balance hash xor-L2 eth4,eth5
config
net config ifname [ipaddr][netmask mask][up | down] [dhcp {yes
| no}][mtu {size | default}][autoneg][duplex {full | half}]
[speed {10 | 100 | 1000}] [0]
config ifname 0
net config ifname 0
Use this command to reset a network interface card to its default
(unconfigured) mode. For example, use net config eth0 0 to
reset interface 0. This command is available to administrative users
only.
208 net
config ifname autoneg
net config ifname autoneg
Use this command to allow the network interface card to
autonegotiate the line speed and duplex setting for an interface.
This command is available to administrative users only.
Note: This command is not applicable with 10 Gb Ethernet cards.
For example, to set autonegotiation for interface eth1, use:
# net config eth1 autoneg
210 net
config ifname mtu
net config ifname mtu {size | default}
Use this command to change the maximum transfer unit size for an
Ethernet interface. Supported values are from 1500 to 9014. 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. This command is available to administrative users only.
For example, to set a maximum transfer unit size of 9014 for the
interface eth2, use the command:
# net config eth2 mtu 9014
create
create interface
net create interface {physical-ifname|virtual-ifname} vlan
vlan-id
Use this command to create a new VLAN interface from either a
physical port or a virtual interface. The range of vlan-id is between
1 and 4095. Use the net config commands to configure the IP
212 net
address and netmask, or to enable or disable the interface. The
maximum number of interfaces is 512. The VLAN interface is
named ifname.vlan-id.
Notes:
The total number of VLAN and virtual interfaces that can be
created is limited to 80.
A VLAN interface cannot be created on a failover interface
consisting of Chelsio 10 GbE interfaces.
For example, to create a VLAN interface named eth0.2:
# net create interface eth0 vlan 2
create virtual
net create virtual virtual-id
Use this command to create a new virtual interface. The virtual
interface name virtual-id must begin with veth. The remainder
of the name can be decimal or hexadecimal numbers
(0-9 and aA-fF are permitted). Interface names must be unique.
This command is available to administrative users only.
For example, to create a virtual interface named veth12, use:
# net create virtual veth12
destroy
net destroy {virtual-ifname|vlan-ifname}
Use this command to delete an existing VLAN or virtual interface.
For example to destroy a VLAN named eth1.35 and a virtual
interface named veth23:2, use:
# net destroy eth1.35
# net destroy veth23
disable
net disable ifname
ddns
DDNS (Dynamic DNS) is the protocol that allows machines on a
network to communicate with, and register their IP address on, a
DNS server.
ddns add
net ddns add (ifname-list | all)
Use this command to add interfaces to the DDNS registration list.
This command is available to administrative users only.
ddns del
net ddns del (ifname-list | all)
Use this command to remove interfaces from the DDNS
registration list. This command is available to administrative users
only.
ddns disable
net ddns disable
Use this command to disable DNS updates. This command is
available to administrative users only.
ddns enable
net ddns enable
Use this command to enable DNS updates. This command is
available to administrative users only.
214 net
ddns register
net ddns register
Use this command to manually register configured interfaces with
DNS. This command is available to administrative users only.
ddns reset
net ddns reset
Use this command to reset the DDNS registration list to its defaults
and disable registration. This command is available to
administrative users only.
ddns show
net ddns show
Use this command to display interfaces in the DDNS registration
list.
ddns status
net ddns status
Use this command to display whether DDNS registration is
enabled or not.
enable
net enable ifname
Use this command to enable a disabled Ethernet interface on the
Data Domain system, where ifname is the name of an interface.
This command is available to administrative users only.
For example, to enable the interface eth0, use:
# net enable eth0
failover
Ethernet failover provides improved network stability and
performance, and is implemented with the net failover
failover add
net failover add virtual-ifname interfaces physical-ifname-list
[primary physical-ifname | none]
Use this command to enable failover on an existing virtual
interface name in the form vethx, where x is a unique string
(typically one or two digits). A typical full virtual interface name is
veth56.3999:199. The maximum length of the full name is 16
characters, which typically limits the name string x to two
characters. Using special characters in the string x other than the
period (.) and the colon (:) is allowed but not recommended.
The virtual interface must already be present on the system; to
check for the presence of a virtual interface, use the net show
settings command. To designate one of the physical interfaces as
the primary failover interface, use the optional primary
parameter. This command is available to administrative users
only.
Note: A primary interface must be part of the failover and cannot
be deleted from the failover while it is the primary interface. Use
the net failover modify command to change the primary
interface.
For example, to associate a failover virtual interface named veth1
with the physical interfaces eth2 and eth3, and with eth2 as the
primary, use:
# net failover add veth1 interfaces eth2 eth3
primary eth2
Current interfaces for veth1: eth2, eth3, primary
eth2
216 net
failover del
net failover del virtual-ifname interfaces physical-ifname-list
Use this command to remove a physical Ethernet interface from a
failover virtual interface. The physical interface remains disabled
after being removed from the virtual interface. This command is
available to administrative users only.
For example, to remove eth2 from the virtual interface veth1,
which has eth2 and eth3 as slaves and eth3 as the primary
interface, use:
# net failover del veth1 interfaces eth2
Interfaces "eth2" have been removed from "veth1".
Current interfaces for veth1: eth3, primary: eth3
failover modify
net failover modify virtual-ifname primary {physical-ifname |
none}
Use this command to modify the physical Ethernet interface
designated as primary for failover on a virtual interface. This
command is available to administrative users only.
failover reset
net failover reset virtual-ifname
Use this command to reset a virtual interface and remove all
physical interfaces that were associated with it. Resetting a virtual
interface removes all associated physical interfaces from the virtual
interface. This command is available to administrative users only.
For example, the following command removes the virtual interface
veth1 and releases all of its associated physical interfaces. (The
physical interfaces are still disabled and must be enabled for any
other use than as part of another virtual interface.)
# net failover reset veth1
failover show
net failover show
Use this command to display configured failover virtual interfaces.
This command shows what is configured at the bonding driver. To
see what is in the registry, use the net show settings command.
Note: The registry settings may be different from the bonding
configuration. When interfaces are added to the virtual interface
the information is not sent to the bonding module until the virtual
interface is brought up. Until that time the registry and the
bonding driver configuration will be different.
The value in the Hardware Address column is the physical
interface currently used by the failover virtual interface.
# net failover show
Ifname Hardware Address Configured Interfaces
------ ----------------- ---------------------
veth1 00:04:23:d4:f1:27 eth3
------ ----------------- ---------------------
hosts
hosts add
net hosts add ipaddr {host | host [alias]} ...
Use this command to associate an IP address with a hostname,.
The hostname is a fully-qualified domain name or a hostname. The
entry is added to the /etc/hosts file. This command is available
to administrative users only.
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, use the command:
218 net
# net hosts add 192.168.3.3 bkup20.yourcompany.com bkup20
hosts del
net hosts del ipaddr
Use this command to delete a hostname or IP address entry from
the /etc/hosts file. This command is available to administrative
users only.
For example, to remove the host entries with an IP address of
192.168.3.3, use:
# net hosts del 192.168.3.3
hosts reset
net hosts reset
Use this command to delete all hostname and IP address entries
from the /etc/hosts file. This command is available to
administrative users only.
hosts show
net hosts show
Use this command to display hostnames and IP addresses from the
/etc/hosts file. This command is available to administrative
users only.
The display looks similar to the following:
# net hosts show
Hostname Mappings:
192.168.3.3 -> bkup20 bkup20.yourcompany.com
iperf
The iperf Linux command measures the quality and bandwidth
of network connections. The net iperf command provides the
equivalent capabilities.
iperf server
net iperf server [port port] [window-size bytes]
Use this command to run the iperf command in server (-s) mode.
This command is available to administrative users only.
net iperf server Option Equivalent iperf Option
port port -p port
window-size bytes -w iperf_bytes
lookup
net lookup {ipaddr | hostname}
Use this command to look up DNS entries.
220 net
ping
net ping host [broadcast] [count n] [interface ifname]
Use this command to check that a Data Domain system can
communicate with a remote host with a hostname or IP address.
broadcast Allow pinging a broadcast address.
count Give the number of pings to issue.
interface Give the interface to use: eth0 through eth3.
reset
net reset {hostname | domainname | dns}
Use this command to reset the hostname, domain name, and DNS
parameters to their default values (empty). The command requires
at least one parameter and accepts multiple parameters. Changes
take effect only after a system reboot. This command is available to
administrative users only.
For example, to reset the system host name, use:
# net reset hostname
set
set dns
net set dns ipaddr1[, ipaddr2[, ipaddr3]]
Use this command to add or change DNS servers for the Data
Domain system to use in resolving addresses to give DNS server IP
addresses. The command writes over the current list of DNS
servers. Only the servers given in the latest command are available
to a Data Domain system. Entries in the list can be separated by
commas, spaces, or both. This command is available to
administrative users only.
set domainname
net set domainname name
Use this command to change the domain name used by the Data
Domain system. This command is available to administrative users
only.
For example, to set the domain name to yourcompany-ny.com,
use:
# net set domainname yourcompany-ny.com
set hostname
net set hostname host
Use this command to change the name other systems use to access
the Data Domain system. Because of a restriction with some
browsers, the hostname should not include an underscore
character. If the hostname contains an underscore, it can prevent
logins to that host from the GUI, and would result in the GUI not
being able to manage that host. This command is available to
administrative users only.
For example, to set the Data Domain system name to dd10:
# net set hostname dd10
To check the operation, use the net show hostname command.
If the Data Domain system is using CIFS with active directory
authentication, changing the hostname causes the Data Domain
system to drop out of the domain. Use the cifs set
authentication command to rejoin the active directory domain.
222 net
show
show all
net show all
Use this command 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.
show config
net show config [ifname]
Use this command to display the current network driver settings
for an Ethernet interface. With no ifname, the command returns
configuration information for all Ethernet interfaces.
show dns
net show dns
Use this command to display the DNS servers used by a Data
Domain system.
The display looks similar to the following. The last line indicates
whether the servers were configured manually or by DHCP.
# net show dns
# Server
- -----------
1 192.168.1.3
2 192.168.1.4
- -----------
show domainname
net show domainname
Use this command to display the domain name used for email sent
by a Data Domain system.
DD OS 4.9 Command Reference Guide 223
The display looks similar to the following:
# net show domainname
The Domainname is: yourcompany.com
show hostname
net show hostname
To display the current hostname used by the Data Domain system,
use the net show hostname operation. The display is similar to
the following:
# net show hostname
The Hostname is: dd10.yourcompany.co
show hardware
net show hardware
Use this command to display hardware information. The display
looks similar to the following:
# net show hardware
224 net
Hardware The MAC address.
Address
Physical Shows whether the port is Copper or Fiber.
Cable Shows whether or not the port currently has a cable
attached and the carrier is up.
show settings
net show settings
Use this command to display network 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 Data Domain System does not have a live
Ethernet connection, the interface is not actually enabled.
# net show settings
port enabled DHCP IP address netmask additional setting
----- ------- ---- ---------------- ---------------- ------------------
eth0 yes yes 192.168.9.199* 255.255.252.0*
eth1 yes yes (not specified)* (not specified)*
veth0 no n/a n/a n/a
veth1 no n/a n/a n/a
veth2 no n/a n/a n/a
veth3 no n/a n/a n/a
----- ------- ---- ---------------- ---------------- ------------------
* Value from DHCP
tcpdump
tcpdump capture
net tcpdump capture filename [interface iface]
[{host host | net net [mask mask]}] [port port] [snaplen bytes]
Use this command to run the Linux tcpdump command and save
packet data to a file for later analysis. You can use this command to
collect data and then copy the output file to another system for
analysis. This command converts the options from the command
line to equivalent tcpdump options. The output files are placed in
/ddvar/traces from where you can upload them to autosupport.
A maximum of 10 output files may be retained on the system; if
226 net
this limit is reached, the command prompts you to delete some of
the existing files. This command is available to administrative
users only.
Command options are translated as follows:
net tcpdump Option Equivalent tcpdump Options
filename -w /ddvar/traces/tcpdump_filename
-C 100M -W 5
interface iface -i iface
host host host host
net net net net
mask mask mask mask
port port port port
snaplen bytes -s bytes
tcpdump del
net tcpdump del {filename | all}
This command deletes output files created by the net tcpdump
capture command. Specify a filename to delete all files that
match the pattern /ddvar/traces/tcpdump_filename *. Specify
all to remove all net tcpdump output files. This command is
available to administrative users only.
net Examples
228 net
Sample Aggregation Workflow
1. Disable the interfaces eth2, eth3, and eth4 to use as
aggregation interfaces:
# net disable eth2
# net disable eth3
# net disable eth4
2. If virtual interface veth1 does not exist on the system, create it:
# net create virtual veth1
3. Enable link aggregation on virtual interface veth1 for physical
interfaces eth2 and eth3 in xor-L2 mode:
# net aggregate add veth1 mode xor-L2 interfaces eth2 eth3
4. Enable the virtual interface:
# net config veth1 192.168.45.119 netmask 255.255.248.0
5. Show the aggregate setup:
# net aggregate show
Ifname Hardware Address Aggregation Mode Configured Interfaces
------ ---------------- ---------------- ---------------------
veth1 00:15:17:0f:63:fc xor-L2 eth2,eth3
------ ----------------- ---------------- ---------------------
Important Notices
230 net
Supported Interfaces
1 Gb to 1 Gb
Dual-port copper Supported across ports on Supported across ports on a
a card, across ports on the card, across ports on the
motherboard, or across motherboard, or across
cards cards
Dual-port fiber
Supported across ports on Supported across ports on a
a card or across cards card or across cards
10 Gb to 10 Gb
Dual-port copper Not supported Supported only on the
same NIC
Single-port fiber Not supported Not supported
232 net
18 nfs
The nfs command manages NFS clients for a Data Domain system.
This command includes the following options.
add Add NFS clients to an export. Page234
del Delete NFS clients from an export. Page235
disable Disable NFS clients from connecting. Page235
enable Enable NFS clients to connect. Page235
reset Reset the client list so that no clients can Page236
connect.
show Show active NFS clients, all allowed NFS Page236
clients, and an NFS histogram of the time
needed for NFS operations.
status Show whether or not NFS is enabled. Page238
add
nfs add {/ddvar | /backup[/sub-dir]} client-list [nfs-options]
Use this command to add NFS clients that can access the Data
Domain system. To specify multiple clients, create a list of entries
separated by commas, spaces, or both. A client can be a fully-
qualified domain hostname, class-C IP addresses, IP addresses
with either netmasks or length, an NIS netgroup name with the
prefix @, or an asterisk (*) wildcard with a domain name, such as
*.yourcompany.com.
234 nfs
anonuid="id" Set an explicit user ID for the anonymous
account. The ID is an integer bounded from 0 to
65635, which must be enclosed in double
quotation marks.
anongid=id Set an explicit group ID for the anonymous
account. The ID is an integer bounded from 0 to
65635, which must be enclosed in double
quotation marks.
del
nfs del {/ddvar | /backup[/subdir]} client-list
Use this command to delete specific directories, including a
backup subdirectory, for one or more clients. The client-list
can contain IP addresses, hostnames, or an asterisk (*) that
represents all clients. Separate items in the list by commas, spaces,
or both. This command is available to administrative users only.
Note: /backup subdirectory is not supported in Global
Deduplication Array.
disable
nfs disable
Use this command to disable all NFS clients. This command is
available to administrative users only.
enable
nfs enable
Use this command to allow all NFS-defined clients to access the
Data Domain system. This command is available to administrative
users only.
reset stats
nfs reset stats
Use this command to clear the NFS statistics. This command is
available to administrative users only.
show
show active
nfs show active
Use this command to list all of the clients that have been active in
the past 15 minutes and the mount path for each active client.
show clients
nfs show clients
Use this command to list the NFS clients allowed to access the Data
Domain system, and the mount path and NFS options for each.
show detailed-stats
nfs show detailed-stats
Use this command to display NFS cache entries and status for
purposes of troubleshooting.
236 nfs
show histogram
nfs show histogram [op]
Use this command to display NFS operations in a histogram.
Optionally, use the op argument to plot a histogram for a specific
NFS operation. This command is available to administrative users
only. The command displays the following output.
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.
2ms The number of operations that took 2 ms or less.
4ms The number of operations that took between 2ms
and 4ms.
6ms The number of operations that took between 4ms
and 6ms.
8ms The number of operations that took between 6ms
and 8ms.
10ms The number of operations that took between 8ms
and 10ms.
100ms The number of operations that took between 10ms
and 100ms.
1s The number of operations that took between 100ms
and 1 second.
10s The number of operations that took between 1
second and 10 seconds.
>10s The number of operations that took over 10
seconds.
show stats
nfs show stats
Use this command to display NFS statistics.
status
nfs status
Enter this option to determine whether or not the NFS system is
operational. When the files system is active and running, the
output shows the total number of NFS requests since the file
system started, or since the last time that the NFS statistics were
reset.
238 nfs
nfs Examples
add timeserver
ntp add timeserver server_name
Use this command to add a remote time server to NTP list. This
command is available to administrative users only.
For example, to add an NTP time server named
srvr26.yourcompany.com to the list, enter:
# ntp add timeserver srvr26.yourcompany.com
del timeserver
ntp del timeserver server_name
Use this command to delete a manually added time server from
the list. This command is available to administrative users only.
For example, to delete an NTP time server named
srvr26.yourcompany.com from the list, enter:
# ntp del timeserver srvr26.yourcompany.com
disable
ntp disable
Use this command to disable NTP service on a Data Domain
system. This command is available to administrative users only.
242 ntp
enable
ntp enable
Use this command to enable NTP service on a Data Domain
system. This command is available to administrative users only.
reset
ntp reset
Use this command to reset the NTP configuration to the default
settings. This command is available to administrative users only.
reset timeservers
ntp reset timeservers
Use this command 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). This
command is available to administrative users only.
show
ntp show config
Use this command to display whether NTP is enabled or disabled,
and show the time server list.
The following example shows the information that is returned:
# ntp show config
NTP is currently enabled.
# Server eth0 eth1
- --------------- ---- ----
1 192.168.244.208 X
2 192.168.244.214 X
- --------------- ---- ----
Showing NTP servers configured by DHCP.
ntp Examples
244 ntp
20 ost
246 ost
Distributed Segment Processing
The Distributed Segment Processing feature increases backup
throughput in almost all cases by eliminating duplicate data
transmission between the media server and the Data Domain
system.
Note: You manage Distributed Segment Processing via the ost
option commands.
Low-Bandwidth Optimization
NetBackup customers who utilize optimized duplication over a
low-bandwidth network (WAN) can increase image duplication
speed by using low-bandwidth optimization (low-bw-optim). This
feature provides additional compression during data transfer.
Low-bandwidth compression is available to Data Domain systems
with an installed Replication license.
Note: You manage low-bandwidth optimization via the ost
opt-dup commands.
enable
ost enable
Administrators use this command to create and export the
/backup/ost directory.
destroy
ost destroy
Administrators use this command to delete all LSUs and their
contents from the Data Domain system. The command
permanently removes all of the data (images) contained in the
LSUs.
disable
ost disable
Administrators use this command to disable OST for the Data
Domain system.
ifgroup
Notes:
248 ost
Notes:
1 GigE and 10GigE connections cannot be used in the same
interface group.
You can add public or private IP addresses for data transfer
connections.
ifgroup disable
ost ifgroup disable
Administrators use this command to disable the Advanced Load
Balancing and Failover option for new jobs. Currently running jobs
are not affected.
If the OST feature is disabled, the message disabled is displayed.
ifgroup enable
ost ifgroup enable
Administrators use this command to enable Advanced Load
Balancing and Failover. At least one IP address must have already
been added.
ifgroup status
ifgroup status
Use this command to show whether OST Link Aggregation is
enabled or disabled.
lsu
lsu create
ost lsu create lsu-name
Administrators use this command to create an LSU with a given
name.
Note: If you invoke the filesys destroy command, you need to
run ost disable followed by ost enable and then create an LSU
using ost lsu create. If you do not run this series of commands,
the Data Domain system reports an error.
lsu delete
ost lsu delete lsu-name
Administrators use this command to delete a specified LSU and all
of its contents. You must also manually remove (expire) the
corresponding NetBackup catalog entries.
250 ost
lsu show
ost lsu show [compression] [lsu-name]
Use this command to display the names of all LSUs or, optionally,
the names of all images in a specified LSU.
To display the compression for all LSUs (the original byte size,
global compression, and local compression for all LSUs), enter the
compression option.
Note: To interrupt the output of this command, press Ctrl+C.
opt-dup
Note: The low-bandwidth optimization option is not supported in
a Global Deduplication Array.
Direction: Inbound
Network bytes received: 88,383,976
Pre-compressed bytes received: 436,874,240
Bytes after filtering: 153,080,417
Bytes after low-bw-optim: 145,547,868
Bytes after local compression: 83,628,271
Compression ratio: 4.9
254 ost
option
option set boost
ost option set boost {enabled | disabled}
Administrators can use this command to enable or disable the
Distributed Segment Processing feature on the DD OS. By default,
it is enabled for DD OS 4.9. If this feature presents any problem for
a media server, use this command to disable the feature on the
Data Domain system.
Distributed Segment Processing is supported only if the installed
version of the OST plug-in is version 2.0 or later, and the feature is
enabled on the DD OS.
Notes:
Distributed Segment Processing is enabled by default in DD
OS 4.8. If a system is upgraded from DD OS 4.6.x or 4.7.x to DD
OS 4.8, and the OST license is installed at the time of the
upgrade, Distributed Segment Processing is not automatically
enabled.
The Distributed Segment Processing feature is enabled in a
Global Deduplication Array, you cannot disable it.
option reset
ost option reset [boost]
Administrators use this command to reset Distributed Segment
Processing to the default option, which is enabled.
option show
ost option show [boost]
Use this command to show whether the Distributed Segment
Processing option is enabled or disabled.
reset stats
ost reset stats
Administrators use this command as follows:
to reset all statistics when OST is enabled, or
as a network recovery procedure to clear job connections after
the network connection has been lost.
set user-name
ost set user-name ost-user
Administrators use this command to set the OST user name when
OST is enabled.
You must disable and then re-enable OST for OST user-name
modifications to take effect.
There can be only one OST user at a time. The username and
password must have already been set up on the Data Domain
system by using the DD OS CLI command: user add
username [password password]
256 ost
show
show connections
ost show connections
Use this command to show the following information:
the number of active clients, and for each active client:
the clients name
whether or not the client is idle (yes/no)
the number of installed CPUs
the amount of memory in MiB
the installed OST plug-in version number
the name and version of the operating system
the NetBackup version number.
the number of connections that a system uses for OST, and
whether these connections are spread across interfaces using
Advanced Load Balancing and Failover. (See sample output for
client connections below.)
the number of connections used for a given group, even when
the interface has been removed from the ifgroup.
an overview of interfaces available for OST.
Note: For a Global Deduplication Array, the ifgroup status is
always disabled, and the member column value is always no.
Client Connections:
Max Client Connections: 65
ifgroup status: Disabled
show stats
ost show stats [interval seconds]
Use this command to show the output of previous show stats
command, the number of bytes written to and read from OST
images contained in LSUs, and the number of OST images created
and deleted from LSUs. The number of errors encountered for each
operation is also shown. Optionally, you can show statistics for a
specific number of seconds.
258 ost
If Distributed Segment Processing is enabled, the number of bytes
transferred and the amount of compression achieved is displayed.
show user-name
ost show ost-user
Use this command to display the current OST user.
status
ost status
Enter this command to determine whether OST is enabled or
disabled.
262 replication
replication Command Options
abort
abort recover
replication abort recover destination
Use this command to stop a recover process. This command can
be executed only on the destination. Once the command is
executed, reconfigure replication on the source and restart the
recover process.
abort resync
replication abort resync destination
Use this command to stop an ongoing resync operation. This
command can be invoked from either the source or the destination
directory replication systems.
add
replication add source source destination destination
[low-bw-optim {enabled | disabled}]
Use this command to create a replication pair on both the source
and destination Data Domain systems. This command is available
to administrative users only.
Note: This command is just one of the commands that are used to
create a replication pair. Refer to the entire procedure in
Configuring Replication on page 288 before using this command.
break
replication break {destination | all}
Use this command to remove either the source or the destination
Data Domain system from a replication pair, or to remove all
Replicator configurations from a Data Domain system. A
destination variable or all is required.
Note: This command is just one of the commands that are used to
remove a replication pair. Refer to the entire procedure in Delete a
Replication Pair on page 293 before using this command.
264 replication
disable
replication disable {destination | all}
Use this command to temporarily halt the replication of data
between the source and the destination on either the source or the
destination. While replication is disabled, you can change the
bandwidth and delay parameters on both sides of the connection
with the replication option set command.
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 Data Domain system when replication is disabled,
replication remains disabled even after the file system is restarted.
This command is available to administrative users only.
Note: The replication disable command should be used as a
short-term solution. A filesys clean operation may proceed
very slowly on a replication context when that context is disabled,
and cannot reclaim space for files that are deleted but not yet
replicated. Use the replication break command to permanently
stop replication and to avoid slowing filesys clean operations.
Note: Using the command replication break on a collection
replication replica or recovering originator requires the use of
filesys destroy on that machine before the file system can be
enabled again.
enable
replication enable {destination | all}
Use this command to restart replication that is temporarily halted
on the Data Domain system 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 Data Domain system when replication is enabled,
replication is enabled when the file system is restarted. This
command is available to administrative users only.
initialize
replication initialize destination
Use this command on the source to start replication between a
source and destination. 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. As an alternative,
consider placing both Data Domain systems of the Replicator pair
in the same location with a direct link to reduce initialization time.
A destination variable is required. This command is available to
administrative users only.
Note: This command is just one of the commands that are used to
create a replication pair. Refer to the entire procedure in
Configuring Replication on page 288 before using this command.
modify
modify low-bw-optim
replication modify destination low-bw-optim {enabled |
disabled}
Use this command to enable delta replication on an existing
replication context. This option is only active when it is enabled on
both the source and the destination. This command is available to
administrative users only.
266 replication
modify source-host or destination-host
replication modify destination {source-host | destination-host}
hostname
Use this command when replacing a system in a replication pair to
assign a new name for the replacement system on the other side of
the replication pair. The hostname must be the name returned by
the hostname command on the system receiving the new
hostname.
If you are changing the hostname on an existing source Data
Domain system, use the replication modify command 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. This command is available to administrative users
only.
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:
# filesys disable
# replication modify
dir://ca.company.com/backup/dir2 destination-host
ny.company.com
# filesys enable
268 replication
modify connection-host port
replication modify destination connection-host hostname [port
port]
The default listen-port for a destination Data Domain system is
2051. Use the replication modify command on a source to
change the port to which the source sends data. A destination can
have only one listen port. If multiple sources use one destination,
each source must send to the same port.
Note: See the procedure Change the Destination Listen Port on
page 297 for an example using this command.
option
option reset
replication option reset {bandwidth | delay | listen-port}
To reset system bandwidth to the default of unlimited or delay to
the default of none, or listen port to 2151, use the replication
option reset operation. Use the filesys disable command
before making changes and use the filesys enable command
after making changes.
option show
option show
Use this command to display the current bandwidth and delay
settings. If these settings are at the default of none, the operation
returns just a command prompt with no setting information.
270 replication
reauth
replication reauth destination
To reset authentication between a source and destination, use the
replication reauth command on both the source and the
destination. A destination variable is required. This command is
available to administrative users only.
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 Data Domain system. See Replace a
Directory SourceSame Directory Name on page 296.
recover
replication recover destination
To move data from a surviving destination to a new source, use the
replication recover command on the new source. This
command is available to administrative users only.
A destination variable is required.
This command must be invoked only from the source.
With collection replication, first use the filesys disable and
filesys destroy commands on the new source.
show
show config
replication show config [destination | all]
Use this command to display configuration parameters for a
specific destination or for all destinations.
On the replica, the per-context display is modified to include an
asterisk; if at least one context was marked with an asterisk, the
footnote Used for recovery only is also displayed.
The display with a destination variable is similar to the
following. The all option returns a similar display for each
context.
# replication show config dir://host3.company.com/backup/dir2
CTX: 2
Source: dir://host2.company.com/backup/host2
Destination: dir://host3.company.com/backup/host2
Connection Host: ccm34.datadomain.com
272 replication
Connection Port: (default)
Low-bw-optim: enabled
Enabled: yes
# replication show config all
CTX: 1
Source dir://syrah22.datadomain.com/backup/syrah22
Destination dir://dd580.pr.datadomain.com/backup/syrah22
Connection Host: dd580.princeton.datadomain.com
Connection Port: (default)
Low-bw-optim: enabled
Enabled: yes
The columns in the output are:
show detailed-stats
replication show detailed-stats [destination | all]
Use this command to display cumulative stats since the context
was created. This command provides byte-count statistics related
to identity-filtering, delta-compression, and local-compression.
The ratio of the byte values Bytes after filtering by
destination to Bytes after low bandwidth optimization
gives the additional compression ratio supplied by delta
compression.
show history
replication show history {destination | all} [duration duration
{hr | min}] [interval number {hr | min}]
To display a history of replication, use the replication show
history command. Statistics are generated only once an hour, so
the smallest interval that appears is one hour.
The columns in the output are:
Pre-Comp (KB) The amount of pre-compression data that is not
Remaining replicated.
Replicated (KB) The amount of pre-compressed data that is
Pre-Comp replicated.
Replicated (KB) The amount of compressed data sent over the
Network network.
274 replication
Synced-as-of The time when the most recently replicated
Time data on the destination was generated on the
source. A value of unknown appears during
replication initialization.
Low-bw-optim The additional compression ratio supplied by
delta compression.
show performance
replication show performance {obj-spec-list | all} [interval
sec] [count count]
To display current replication activity, use the replication show
performance command. The default interval is two seconds.
276 replication
The value of 3 for Streams means that replication is sending
three files in parallel for this context.
# replication show performance rctx://1
07/31 10:09:27
rctx://1
Pre-comp Network Streams Busy Waiting
(KB/s) (KB/s) Reading Meta Dest Network
--------- --------- ------- -------------- --------------
21798 10173 3 31 0 0 264
19914 9427 3 27 0 0 269
23091 11314 3 42 0 0 253
19446 9161 3 20 0 0 276
24002 11604 3 52 0 0 242
22725 10829 3 47 0 0 248
18662 9119 3 41 0 0 254
24263 11355 3 31 0 0 264
20179 9640 3 28 0 0 267
23887 11162 3 40 0 0 255
21125 9957 3 23 0 0 272
278 replication
show stats
replication show stats [destination | all]
To display replicator statistics for all replication pairs or for a
specific destination pair, use the replication show stats
command.
The display is similar to the following:
# replication show stats
CTX: 1
Destination: dir://33.company.com/backup/rig14_8
Network bytes sent: 3,904
Pre-compressed 612
bytes sent:
Compression ratio: 0.0
Sync'ed-as-of time: Tue Dec 11 18:30
Pre-compressed 0
bytes remaining:
280 replication
column gives the full (approximately) 8 GB, being the sum of the
sizes of the eight files involved. 7.6 is the ratio between pre-comp
bytes sent and network bytes sent.
Originator:
sym2# replication show stats all
CTX: 1
Destination:
dir://syrah33.datadomain.com/backup/example
Replica:
sym3# replication show stats all
CTX: 1
Destination:
dir://syrah33.datadomain.com/backup/example
282 replication
Synced-as-of-time The time when the most recently replicated
data on the destination was generated on
the source. A value of unknown appears
during replication initialization.
Current Throttle The current throttle setting.
sync status
replication sync status destination
To check on progress when running the sync start command,
use the replication sync status command.
throttle
throttle add
replication throttle add sched-spec rate
To change the rate of network bandwidth used by replication, use
the throttle add command. By default, the network bandwidth
use is unlimited (as fast as possible at all times). This command is
available to administrative users only.
Replication runs at the given rate until the next scheduled change
or until new throttle commands force a change.
Note: The system enforces a minimum rate of 98,304 bits per
second (12 KiB).
284 replication
The sched-spec must specify either:
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. Rate can also
be 0 (the zero character), disable, or disabled (each stops
replication until the next rate change). If you set rate to zero, any
new contexts also get throttled to zero.
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, 2000 KiB). The default rate is bits per second.
In the rate variable:
bps or b equals raw bits per second
throttle reset
replication throttle reset {current | override | schedule |
all}
This command can reset a throttling schedule:.
current Remove the rate set by the replication
throttle set current command.
override Remove the rate set by the replication
throttle set override command.
schedule Remove all scheduled change entries.
all Remove any current or override settings and
remove all scheduled change entries, returning
the system to the default settings.
286 replication
throttle set
replication throttle set {current | override} rate
throttle show
replication throttle show [KiB]
Use this command to display all scheduled throttle entries and
rates. Use the KiB option to display the rate in Kibibytes (the base-
2 equivalent of Kilobytes) per second. Without the option, the rate
is displayed in bits per second.
watch
replication watch destination
Use this command to display the progress of a replication
initialization, resync, or recovery operation. This command is
available to administrative users only.
Configuring Replication
Before starting the replication configuration, be sure to consider
the following:
Ensure adequate storage is available on the source and
destination. At a minimum, the destination must have more
space than the source.
Determine the type of replication configuration to use.
Ensure the destination directory is empty or its contents are not
required, as it will be overwritten.
Limitations
Before configuring directory replication, review the following
information.
Table 21-1: Maximum Contexts for Directory Replication
Model Maximum Number of Contexts
DD880 180
DD690 and DD690g 90
DD580, DD565, and DD560 45
DD630, DD565, and DD560 with 8 GB RAM 20
All other models 20
288 replication
Configuring Replication Pairs
Create either a collection or directory replication pair, as described
in the following sections.
290 replication
Create Bi-Directional Directory Replication
To set up and start directory replication for dir2 from hostA to
hostB and for dir1 from hostB to hostA, follow this procedure.
292 replication
destination hostname and the pool name. For example, a
destination of pool://hostB/hostA/pool2 is not allowed.
Note: When a new directory or pool replication pair is being
created, the source directory cannot be written to until the
replication relationship between source and destination systems
has been established. Attempts to write to the newly configured
replication source directory will fail until the replication
relationship has been established. Instead, schedule the replication
configuration at a time when backups are not occurring.
1. 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 both Data
Domain systems:
replication add source pool://hostA/pool2
destination pool://hostB/pool2
The replication from source to destination begins.
Managing Replication
294 replication
2. On the destination, run a file system cleaning operation:
filesys clean
1. If the new source has any data in the target directories, delete
all data from the directories.
2. 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
3. Run the following commands on the new source:
replication add source dir://hostC/backup/dir2
destination dir://hostB/backup/dir2
replication recover dir://hostB/backup/dir2
4. 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.
296 replication
# 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 Apr8 23:38:11
State: recovering
Error: no error
Destination lag: less than 5 minutes
Current throttle: unlimited
298 replication
Managing Delta Replication
Delta replication, also called low bandwith optimization, can
increase the virtual throughput of directory replication across links
with less than 6 Mbps of available (or throttled) bandwidth. Delta
replication incurs significant additional CPU and I/O overhead on
both the source and destination Data Domain systems. If low
bandwidth optimization is enabled across links with greater than 6
Mbps of bandwidth, it is unlikely that any gain in virtual
throughput will be realized.
Delta Replication applies more computation time to data
compression, which utilizes a low-bandwidth link more efficiently
and reduces the time required to perform replication. When a low-
bandwidth link is fully loaded, Delta Replication can cut
replication time by 50%. For high-bandwidth links (faster than T3
capacity), Delta Replication might not speed up, and could slow
down, the replication process.
Low bandwidth optimization increases the virtual throughput of
directory replication on most data sets by a factor of 2x or more.
However, low bandwidth optimization does not compress
segment metadata. If the data to be replicated is more than 96%
identical to data already existing on the destination system (that is,
the over-the-wire compression ratio reported by the replication
show stats command is 25x or more, and thus most of the
bandwidth is being consumed by segment metadata), it is unlikely
that low bandwidth optimization will increase virtual throughput
significantly.
If the data to be replicated is less than 96% identical to data already
existing on the destination system; and there is less than 6 Mbps of
available bandwidth; and both systems have spare CPU and I/O
capacity; then enable low bandwidth optimization and monitor the
output of replication show history over several weeks. The
Low-bw-optim ratio should average 2.00 or more, and the network
throughput (network bytes divided by time interval) should not be
much less than the available bandwidth.
If the Low-bw-optim ratio does not average 2.00 or more, then
delta compression is probably not effective on the data set and
should be disabled. If the network throughput is much less than
the available bandwidth, then most likely one or both Data
300 replication
In this example, the destination system reports that Bytes after
low bandwidth optimization is not smaller than Bytes after
filtering by destination.
destination# replication show detailed-stats all
CTX: 1
Destination: dir://1.2.3.4/backup/destination
Network bytes received from 5,576,867,192
source:
Pre-compressed bytes written to 13,618,616,344
source:
Pre-compressed bytes sent to 13,618,616,344
destination:
Bytes after filtering by 8,068,500,019
destination:
Bytes after low bandwidth 8,068,500,019
optimization:
Bytes after local compression: 5,475,813,069
Pre-compressed bytes remaining: 0
Files remaining: 0
Compression ratio: 2.4
Sync'ed-as-of time: Thu Mar 12 21:14
302 replication
Pre-compression bytes written might be higher than pre-
compression bytes sent in cases where a large amount of file
content is written, then overwritten prior to the file being
closed on the sender. This is unusual for backup applications,
but is possible with database applications.
add
route add {-host host-name | -net ipaddr netmask mask} gw gw-
addr
Use this command to add a routing rule. If the target being added
is a network, use the -net option. If the target is a host, use the
-host option. The gateway (gw) can be either an IP address or a
hostname that is available to the Data Domain system and that can
be resolved to an IP address. This command is available to
administrative users only.
To add a route for the host user24 with a gateway of srvr12, use:
# 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, use:
# 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 gw srvr14
del
route del {-host host-name | -net ipaddr netmask mask}
Use this command to remove a routing rule. 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. This command
is available to administrative users only.
306 route
To remove a route for host user24, use:
# route del -host user24
To remove a route with a route specification of 192.168.1.x and a
gateway of srvr12, use:
# route del -net 192.168.1.0 netmask 255.255.255.0
gw srvr12
reset
route reset gateway
Use this command to reset the default routing gateway to the
default value (empty). This command is available to
administrative users only.
set
route set gateway ipaddr
Use this command to change the routing default gateway. This
command is available to administrative users only.
For example, to set the default routing gateway to the IP address of
192.168.1.2, use:
# route set gateway 192.168.1.2
show
show config
route show config
Use this command to display the configured static routes that are
in the Route Config list.
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
show table
route show table
Use this command to display all entries in the Kernel IP routing
table.
The display looks similar to the following (each line in the example
wraps):
# route show table
trace
route trace host
Use this command to display a route used by a Data Domain
system to connect with a particular destination.
For example, to trace the route to srvr24, use:
# 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
308 route
route Examples
Add a Route
To add a route with a route specification of 192.168.1.x, a
netmask, and a gateway of srvr12, use:
# route add -net 192.168.1.0 netmask 255.255.255.0
gw srvr12
To add a route for host user24 with a gateway of srvr12, use:
# route add -host user24 gw srvr12
Delete a Route
To delete a route with a route specification of 192.168.1.x and a
netmask of 255.255.255.0, use:
# route del -net 192.168.1.0 netmask 255.255.255.0
add
snapshot add schedule name [days days] time time [,time...]
[retention period]
snapshot add schedule name [days days] time time every mins
[retention period]
snapshot add schedule name [days days] time time - time [every
hrs | mins] [retention period]
Use these commands to set up a series of snapshots to be taken at a
regular intervals in the future.
Notes:
It is strongly recommended that snapshot schedules always
explicitly specify a retention time. The default retention time is
14 days. If no retention time is specified, all snapshots are
retained for 14 days, consuming valuable resources.
Multiple snapshot schedules can be active at the same time.
If multiple snapshots are scheduled to occur at the same time,
only one is retained. However, which one is retained is
indeterminate, thus only one snapshot should be scheduled for
a given time.
snapshot add schedule name [days days] time time [,time...]
[retention period]
312 snapshot
The default for days is daily and the user can specify a list of
hours.
snapshot add schedule name [days days] time time
every mins [retention period]
The default for days is daily. The user can also specify the interval
in minutes.
snapshot add schedule name [days days] time time -
time [every hrs | mins] [retention period]
The default for days is daily. When every is omitted, the
command defaults to 1hr.
days Are one or more three-letter day
abbreviations, such as tue for Tuesday. Use
a hyphen ( - ) between days to denote a
range. For example, mon-fri creates a
snapshot every day, Monday through Friday.
time A 24-hour clock that starts at 00:00 and goes
to 23:59. The format in the command is a
three- or four-digit number with an optional
colon ( : ) between hours and minutes. For
example, 4:00 or 04:00 or 0400 sets the time to
4:00 a.m., and 14:00 or 1400 sets the time to
2:00 p.m.
retention period A number plus days, weeks or wks, or
months or mos with no space between the
number and the days, weeks, or months
tag. For example, 6wks. The months or mos
period is always 30 days.
create
snapshot create snapshot [retention {date | period]
Use this command to create a snapshot. This command is available
to administrative users only.
snapshot A descriptive name for the snapshot.
retention date A four-digit year, a two-digit month, and a two-
digit day separated by dots ( . ), slashes ( / ), or
hyphens ( - ). For example, 2009.05.22.
With a retention date, the snapshot is retained
until midnight (00:00, the first minute of the
day) of the given date. With a retention period,
the snapshot is retained until the same time of
day as the creation.
retention period A number of days, weeks or wks, or months
or mos with no space between the number and
the days, weeks, or months. For example, 6wks.
The months or mos period is always 30 days.
314 snapshot
del
snapshot del schedule [name | all]
Use the snapshot del schedule name command to delete a
specific snapshot schedule. Use this command to delete all
snapshot schedules with the argument all. This command is
available to administrative users only.
Note that there are two ways to delete all scheduled snapshots:
snapshot del schedule all
or
snapshot reset schedule
expire
snapshot expire snapshot [retention {date | period | forever}]
Use this command to set or reset the retention time of an existing
snapshot. This command is available to administrative users only.
snapshot The name of an existing snapshot.
retention date The four-digit year, a two-digit month, and a
two-digit day separated by dots ( . ), slashes
( / ), or hyphens ( - ). For example,
2009.05.22.
With a retention date, the snapshot is retained
until midnight (00:00, the first minute of the
day) of the given date. With a retention period,
the snapshot is retained until the same time of
day as the snapshot expire command was
entered.
retention period The number of days, weeks or wks, or
months or mos with no space between the
number and the days, weeks, or months. For
example, 6wks. The months or mos period is
always 30 days.
forever The snapshot does not expire.
list
snapshot list
Use this command to list existing snapshots. The display gives the
snapshot name, the pre-compression amount of data in the
snapshot, the creation date, the retention date, and the status. The
status is either blank or expired. An expired snapshot remains
available until the next file system clean operation. Use the
snapshot expire command to set a future expiration date for an
expired, but still available, snapshot.
For example:
# snapshot list
316 snapshot
modify
snapshot modify schedule name {[days days] time time [,time...]
[retention period]}
snapshot modify schedule name {[days days] time time every mins
[retention period]}
snapshot modify schedule name {[days days] time time - time
[every hrs | mins] [retention period]
Use this command to modify an already-existing snapshot
schedule, with the same syntax as the snapshot add schedule
command. This command is available to administrative users only.
There are several possible syntaxes:
snapshot modify schedule name {[days days] time
time [,time...] [retention period]}
The default for days is daily and the user can specify a list of
hours.
snapshot modify schedule name {[days days] time
time every mins [retention period]}
The default for days is daily. The user can also specify the interval
in mins.
snapshot modify schedule name {[days days] time
time - time [every hrs | mins] [retention period]
The default for days is daily. When every is omitted, the
command defaults to every 1hr.
rename
snapshot rename snapshot new-name
Use this command to change the name of a snapshot. This
command is available to administrative users only.
For example, to change the name from snap12-20 to snap12-21,
use:
# snapshot rename snap12-20 snap12-21
Snapshot snap12-20 renamed to snap12-21.
show
snapshot show schedule name
Use this command to display a given snapshot schedule.
To display a list of all snapshot schedules currently in effect, use
the snapshot show schedule operation without an argument.
For example,
# snapshot show schedule
Snapshots are scheduled to run "daily" at "0700".
Snapshots are scheduled to run "daily" at "1900".
Snapshots are retained for "60" days.
318 snapshot
snapshot Examples
Schedule a Snapshot
To schedule a snapshot every day at 8:00p.m., use:
add schedule every_day_8_pm days daily time 20:00
or
add schedule every_day_8_pm days mon-sun time 20:00
Note: The name every_day_8_pm is the name of a snapshot
schedule. Snapshots generated by that schedule will have
names like scheduled-2008-03-24-20-00, scheduled-2008-03-
25-20-00, etc.
To schedule a snapshot every midnight, use:
add schedule every_midnight days daily time 00:00
retention 3days
or
add schedule every_midnight days mon-sun time 00:00
retention 3days
To schedule a snapshot every weekday at 6:00a.m., use:
add schedule wkdys_6_am days mon-fri time 06:00
retention 4days
or
add schedule wkdys_6_am days mon,tue,wed,thu,fri
time 06:00 retention 4days
To schedule a snapshot every weekend Sun at 10:00a.m., use:
add schedule every_sunday_10_am days sun time 10:00
retention 2mos
To schedule a snapshot every Sunday at midnight, use:
add schedule every_sunday_midnight days sun time
00:00 retention 2mos
320 snapshot
To schedule a snapshot every weekday at 10:30a.m. and 3:30p.m.,
use:
add schedule ev_weekday_1030_and_1530 days mon-fri
time 10:30,15:30 retention 2mos
add
add ro-community
snmp add ro-community community-string
Use this command to add one or more community strings to
enable read-only access to the Data Domain system. A common
string for read-only access is public. This command is available to
administrative users only.
add rw-community
snmp add rw-community community-string
Use this command to add one or more community strings to
enable read/write access to the Data Domain system. A common
string for read/write access is private. This command is available
to administrative users only.
For example, to add a community string of private with
read/write permissions, use the command:
# snmp add rw-community private
324 snmp
add trap-host
snmp add trap-host hostname[:port]
Use this command to add one or more trap hosts (hostname or IP
address) to receive SNMP traps generated by the Data Domain
system. With one or more trap hosts, alerts are also sent as traps,
even when the local SNMP agent is disabled. By default, port 162 is
used, but another port can be assigned. This command is available
to administrative users only.
For example, to add a trap host admin12, use the command:
# snmp add trap-host admin12
del
del ro-community
del ro-community community-string
Use this command to delete one or more community strings that
enable read-only access to the Data Domain system. This
command is available to administrative users only.
del rw-community
snmp del rw-community community-string
Use this command to delete one or more community strings that
enable read-only access to the Data Domain system. This
command is available to administrative users only.
For example, to delete the community string private that gives
read/write permissions, use the command:
# snmp del rw-community private
disable
snmp disable
Use this command to disable the SNMP agent and close port 161.
This command is available to administrative users only.
enable
snmp enable
Use this command to enable the SNMP agent and open port 161.
This command is available to administrative users only.
reset
Use this command to return all SNMP values to the defaults. This
command is available to administrative users only.
reset ro-community
snmp reset ro-community
Use this command to reset the read-only community list to empty.
This command is available to administrative users only.
reset rw-community
snmp reset rw-community
Use this command to reset the read-write community list to empty.
This command is available to administrative users only.
326 snmp
reset sysContact
snmp reset sysContact
Use this command to reset the system contact to the system value
displayed by the command system show admin-email, or to an
empty string if the system value is empty. This command is
available to administrative users only.
reset sysLocation
snmp reset sysLocation
Use this command to reset the system location to the system value
displayed by the command system show location, or to an
empty string if the system value is empty. This command is
available to administrative users only.
reset trap-hosts
snmp reset trap-hosts
Use this command to return the trap hosts list to the default of
empty. This command is available to administrative users only.
set
set sysContact
snmp set sysContact contact
Use this command to set the system contact as used in the SNMP
MIB II system variable sysContact. This command is available to
administrative users only.
For example, to give a contact of bob-smith, use the command:
# snmp set sysContact bob-smith
show
show config
snmp show config
Use this command to display all of the SNMP parameters. This
command is available to administrative users only. The output is
similar to the following:
# snmp show config
---------------------- -------------------
SNMP sysLocation bldg3-rm222
SNMP sysContact smith@company.com
Trap Hosts admin10 admin11
Read-only Communities public snmpadmin23
Read-write Communities private snmpadmin1
---------------------- -------------------
show ro-communities
snmp show ro-communities
Use this command to display all read-only community strings.
328 snmp
show rw-communities
snmp show rw-communities
Use this command to display all read/write community strings.
The output is similar to the following:
# snmp show rw-communities
RW Community Strings:
private
snmpadmin1
show sysContact
snmp show sysContact
Use this command to display the system contact on a Data Domain
system.
show sysLocation
snmp show sysLocation
Use this command to display the system location on a Data
Domain system.
show trap-hosts
snmp show trap-hosts
Use this command to display the trap host list on a Data Domain
system.
The output is similar to the following:
# snmp show trap-hosts
Trap Hosts:
admin10
admin11
status
snmp status
Use this command to display the status of the SNMP agent on a
Data Domain system (enabled or disabled).
DD OS 4.9 Command Reference Guide 329
Important Notices
Data Domain systems support SNMP versions V1 and V2C.
SNMP management requires two primary elements: an SNMP
manager and an SNMP agent.
An SNMP manager is software running on a workstation from
which an administrator monitors and controls the different
hardware and software systems on a network. These devices
include, but are not limited to, storage systems, routers, and
switches.
An SNMP agent is software running on equipment that
implements the SNMP protocol. SNMP defines exactly how a
SNMP manager communicates with an SNMP agent. For example,
SNMP defines the format of requests that an SNMP manager sends
to an agent and the format of replies the agent returns.
The SNMP feature allows a Data Domain system to respond to a
set of SNMP get operations from a remote machine.
From an SNMP perspective, a Data Domain system is a read-only
device with the following exception: A remote machine can set the
SNMP location, contact, and system name on a Data Domain
system. To configure community strings, hosts, and other SNMP
variables on the Data Domain system, use the snmp command.
With one or more trap hosts defined, a Data Domain system takes
the additional action of sending alert messages as SNMP traps,
even when the SNMP agent is disabled.
Note: The SNMP sysLocation and the location set with the
config set location command are the same. If sysLocation is
not set with an SNMP command, the variable defaults to the
values specified with the config set commands. However, the
sysContact variable does not default to the value set by the
config set admin-email command.
330 snmp
25 support
upload
upload file-list
The file-list contains filenames available under /ddvar. If more
than one file is specified, filenames must be space-separated.
upload {bundle [file-list]|traces|file-list}
Use the bundle option to send various Data Domain system log
files that are often needed by the support staff. The optional file-
list contains filenames available under /ddvar. If more than one
file is specified, filenames must be space-separated.
Use the traces option to send multiple perf.log (performance log)
files that are often needed by the support staff.
332 support
26 system
headswap
system headswap
To restore the configuration to a DD690, DD690g, DD880, or
DD880g system after a head unit replacement, use the system
headswap command.
option
option reset
system option reset login-banner
To reset the login banner to the default of no banner, use this
command. This command is available to administrative users only.
334 system
option set
system option set login-banner filename
To select a text file to display whenever someone logs in, use this
command.
1. Mount the Data Domain system directory /ddvar from another
system.
2. Create a text file with your login message as the text on the
other system.
3. From the Data Domain system, use the system option set
login-banner command with the path and file name of the
file that you created.
This command is available to administrative users only.
For example, to use the text from a file named banner, use the
command:
# system option set login-banner /ddvar/banner
option show
system option show
To display the location of the file that contains the login banner
text, use this command. This command is available to
administrative users only. The command output shows the path
and file name:
# system option show
Option Value
----------------- -------------
Login Banner File /ddvar/banner
----------------- -------------
reboot
system reboot
To shut down and reboot a Data Domain system, use this
command. The command automatically performs an orderly
shutdown of file system processes.
The display includes a warning similar to the following:
# system reboot
The 'system reboot' command reboots the system.
File access is interrupted during the reboot.
Are you sure? (yes|no|?) [no]:
This command is available to administrative users only.
336 system
sanitize
System sanitization, which is often required in government
installations, ensures that all traces of deleted files are completely
disposed of (shredded) and that the system is restored to a state as
if the deleted files never existed. Its primary use is to resolve
Classified Message Incidents (CMIs), in which classified data is
inadvertently copied into another system, particularly one not
certified to hold data of that classification. This command is
available to administrative users only.
sanitize abort
system sanitize abort
Stop the system sanitization process.
sanitize start
system sanitize start
Start the system sanitization process. While this command is
running, vtl is temporarily disabled. Therefore, running this
command during scheduled backup times might not be desirable.
sanitize status
system sanitize status
Check system sanitization process status.
sanitize watch
system sanitize watch
Monitor system sanitization progress.
show
show all
system show all
To display memory usage information together with other
available system information, use this command. The output
includes the results of the following commands:
system show detailed-version
system show meminfo
system show modelno
system show serialno
338 system
system show uptime
system show date
show date
system show date
To display the system date and time, use this command.
show detailed-stats
system show detailed-stats [start | stop | ([[interval] nsecs]
[count count])]
system show detailed-stats nsecs count
By default, the statistics cover the time period since the last reboot.
Use the command options to specify a different interval for
collecting statistics. If the system is too busy to determine a value,
the column shows a dash ( - ) instead of a number.
start Begin collecting statistics.
stop Stop collecting statistics and report the data gathered from
the time that you entered the command
system show detailed-stats start.
The results are the averages per second of the statistics
during the time between the start and stop commands.
nsecs Run the command every nsecs seconds. The first report is
for current activity. Each subsequent report is for activity in
the last nsecs. The default interval is five seconds.
count Generate count number of reports. To specify count
without interval, you must use the count keyword.
Otherwise, the keyword is optional.
340 system
Repl KB/s The amount of data in kilobytes per second being
replicated between one Data Domain system and
another. For directory replication, the value is the total
of all in and out traffic for all replication contexts.
show detailed-version
system show detailed-version
To display the versions of Data Domain system components on
your system, use this command.
The display is similar to the following:
# system show detailed-version
Data Domain OS 4.9.0.0-132588
Distribution: /auto/builds64e/distro/pinot/123033/localbld
//prod/main/app/...@132588
132588
//prod/main/platform/os/...@132387
//prod/main/platform/os/linux-2.6.12/arch/x86_64/...@61933
//prod/main/platform/os/linux-2.6.12/arch/i386/...@76935
//prod/main/platform/os/linux-2.6.12/arch/ia64/...@25442
//prod/main/platform/os/debugrpm/...@124034
//prod/main/platform/user/samba/...@132364
show meminfo
system show meminfo
To display a summary of the memory in a Data Domain system,
use this command.
Here is an example:
# system show meminfo
Memory Usage Summary
Total memory: 7987 MiB
Free memory: 1102 MiB
Total swap: 12287 MiB
Free swap: 12287 MiB
342 system
show modelno
system show modelno
To display the model number of a Data Domain system, use this
command.
show nvram
system show nvram
To display information about the memory and battery status of the
NVRAM cards, use this command. The display is similar to the
following:
# system show nvram
NVRAM Card Component Value
---------- ------------------- --------------------
1 memory size 512.00 MiB
number of batteries 2
errors 0 PCI, 0 memory
battery 1 100% charged, enabled
battery 2 100% charged, enabled
---------- ------------------- --------------------
Note: MiB = Mebibytes (the binary equivalent of Megabytes)
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 Alert Summary 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% within three days (or if a battery is not
enabled), replace the card.
The output is too large to print here, but the fields are as follows:
344 system
Throughput
Read Read throughput from the Data Domain system.
Write Write throughput to the Data Domain system.
Repl Network Replication network throughput into and out of the
Data Domain system.
Repl Pre-comp Replication pre-compressed (logical) throughput
into and out of the Data Domain System. The value
is always zero for collection replication.
Utilization
proc Percent of time spent processing requests.
recv Percent of time spent receiving requests over the
network.
send Percent of time spent sending requests over the
network.
idle Percent of time spent idle.
Compression
gcomp Global compression rate.
lcomp Local compression rate.
Streams
rd The number of active read streams.
wr The number of active write streams.
r+ The number of reopened read file streams in the past
30 seconds.
w+ The number of reopened write file streams in the past
30 seconds.
346 system
State
C Cleaning.
D Disk reconstruction.
B Currently unused.
V Verification.
M Fingerprint merge.
S Summary vector checkpoint.
Utilization
cpu The average and maximum CPU utilization. The CPU
ID of the most loaded CPU is shown in the brackets.
disk The maximum (highest) disk utilization over all disks.
The disk ID of the most loaded disk is shown in the
brackets (may not correspond to the ID used by disk
show commands).
Latency
avg/std The average and standard deviation of the response
time for ddfs to service all protocol requests excluding
the time to receive/send the request/reply.
show ports
system show ports
To display information about ports, use this command. The
display is similar to the following:
# system show ports
Port Connection Link Firmware Hardware
Type Speed Address
---- ---------- ------ -------------- -----------------------
0a Enet 1 Gbps 00:15:17:0f:6e:bd (eth1)
0b Enet 1 Gbps 00:15:17:0f:6e:bc (eth0)
5a VTL 4.04.00 [IP]
[84 00:64:a1:91:00:00:00:00 WWNN
50:06:0b:00:00:64:a1:90 WWPN
5b VTL 4.04.00 [IP]
[84 00:64:a1:93:00:00:00:00 WWNN
50:06:0b:00:00:64:a1:92 WWPN
6a VTL 4.04.00 [IP]
[84 00:64:a0:75:00:00:00:00 WWNN
50:06:0b:00:00:64:a0:74 WWPN
6b VTL 4.04.00 [IP]
[84 00:64:a0:77:00:00:00:00 WWNN
50:06:0b:00:00:64:a0:76 WWPN
---- ---------- ------ -------------- -----------------------
348 system
Port The port number. See the Data Domain Hardware Guide
(for older systems) or the model-specific installation and
setup guide to match a slot to a port number. A DD580,
for example, shows port 3a as a SAS HBA in slot 3 and
port 4a as a SAS HBA in slot 4. A gateway Data Domain
system with a dual-port Fibre Channel HBA always
shows #a as the top port and #b as the bottom port,
where # is the HBA slot number, depending on the Data
Domain system model.
Link The speed in Gbps (Gigabits per second).
Speed
Firmware The Data Domain system HBA firmware version.
Hardware A MAC address, a WWN, or a WWPN/WWNN, as
Address follows:
An address followed by an Ethernet port number is a
MAC address.
WWN is the world-wide name of the Data Domain
system SAS HBA on a system with expansion shelves.
WWPN/WWNN is the world-wide port name or node
name from the Data Domain system FC HBA on
gateway systems.
show serialno
system show serialno
To display the system serial number, use this command. The
display is similar to the following:
# system show serialno
Serial number: 8F46942007
show stats
system show stats [start | stop | ([interval nsecs]
[count count] )]
system show stats nsecs count
To display system statistics for CPUs, disks, Ethernet ports,
replication, and NFS, use this command. By default, the statistics
cover the time period since the last reboot. Use the command
DD OS 4.9 Command Reference Guide 349
options to specify a different interval for collecting statistics. If the
system is too busy to determine a value, the column shows a dash
( - ) instead of a number.
start Begin collecting statistics.
stop Stop collecting statistics and report the data gathered from
the time that you entered the command
system show stats start.
The results are the averages per second of the statistics
during the time between the start and stop commands.
nsecs Run the command every nsecs seconds. The first report is
for current activity. Each subsequent report is for activity
in the last nsecs. The default interval is five seconds.
count Generate count number of reports. To specify count
without an interval, you must use the count keyword.
Otherwise, the keyword is optional.
350 system
show uptime
system show uptime
To display the time since the last reboot and the file system uptime,
use this command. The display includes the following information:
Current time
Time since the last reboot (in days and hours)
The current number of users
The average load for file system operations, disk operations,
and the idle time over the preceding 1, 5, and 15 minute
intervals
The Filesystem line displays the time that has passed since the
file system was last started.
The output is similar to the following:
# 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
show version
system show version
To display the Data Domain OS version, use this command. The
display gives the release number and a build identification
number. The display is similar to the following:
# system show version
Data Domain OS 4.9.0.0-132588
354 system
Do NOT disable replication on either system in the pair.
Note: Before starting an upgrade, always read the Release Notes
for the new release. DD OS changes in a release may require new
upgrade procedures.
Issuing this command on the master controller upgrades all
controllers in a Global Deduplication Array simultaneously with
the specified filename. A progress bar monitors the upgrade.
After the first phase of the upgrade, which is installing the new
DDOS upgrade on a secondary partition, the controllers reboot.
After all of the controllers have rebooted, the master controller
checks their status and initiates the second phase of the upgrade
automatically on all controllers. If the automatic upgrade checks
fail for some reason, an alert is sent describing the cause of failure,
and the automated upgrade process exits.
Note: You can run the second phase of the upgrade manually
using the system upgrade command. If the problem is not fixable,
the command allows you to rollback the upgrade to the previous
version.
356 system
Display a Banner
To have a text message appear at each login, mount the Data
Domain system /ddvar directory from a third-party physical disk
system and create a text file with the message as the text. For
example, to use text from a file named banner, use the following
command on the Data Domain system:
# system option set login-banner /ddvar/banner
add
user add user-name [password password] [priv {admin | user}]
[min-days-between-change days] [max-days-between-change days]
{warn-days-before-expire days] [disable-days-after-expire days]
[disable-date date]
Use this command to add a new user. If password is not specified,
the system prompts for one. The default privilege level is user. A
user-name must start with an alphanumeric character. Special
characters cannot be used. The user names root and test are
default existing names on every Data Domain system and are not
available for general use.
password Password must be at least 6
characters.
min-days-between-change Minimum number of days
allowed before the password can
be changed again.
max-days-between-change Maximum number of days
before password expires.
warn-days-before-expire Number of days of warning
before a password expires.
disable-days-after- Account is disabled if inactive
expire after N days past expiration.
disable-date Account is disabled on this date.
360 user
change
change password
user change password [user-name]
Use this command to change a users password. The admin user
can change any users password by using the user-name option.
Users with the user privilege level can change only their own
passwords. Passwords must comply with the password strength
policy, which you can check with the command user password
strength show.
change priv
user change priv user-name {admin | user}
Use this command to change a user privilege level to either admin
or user. This command is available to users who currently have
the admin privilege.
del
user del user-name
Use this command to remove a user. This command is available to
administrative users only.
disable
user disable user-name
Use this command to disable the specified user account. This
prevents the user from logging on to the Data Domain system. This
command is available to administrative users only.
enable
user enable user [disable-date date]
Use this command to enable a specified user account with the
optionally specified account disable date. The account must
already exist on the system. If not specified, the disable-date
previously assigned to the account is used. This command is
available to administrative users only.
DD OS 4.9 Command Reference Guide 361
password
password aging option reset
user password aging option reset {all |
[min-days-between-change] [max-days-between-change]
[warn-days-before-expire] [disable-days-after-expire]}
Use this command to reset one or more rules in the default
password aging policy to the current default values. New accounts
inherit the policy in effect at the time they are created, unless you
set different aging options with the user add command. This
command is available to administrative users only.
362 user
password aging set
user password aging set user [min-days-between-change days]
[max-days-between-change days] [warn-days-before-expire days]
[disable-days-after-expire days]
Use this command to set the password aging policy for the
specified user. This command is available to administrative users
only.
364 user
reset
user reset
Use this command to delete all users except for the sysadmin
account and the current login. The password aging and password
strength options also get reset to their default values. This
command is available to administrative users only.
show
show active
user show active
Use this command to display the currently logged-in users.
show detailed
user show detailed [user-name]
Use this command to show detailed information for a specified
user or for all users. This command is available to administrative
users only.
show list
user show list
Use this command to display a valid list of system users. This
command is available to administrative users only.
user Examples
Add a User
To add a user named fred with password barney and with admin
privileges, run this command:
user add fred password barney priv admin
user "fred" added.
Change a Password
To change the password for the user named wilma, run this
command:
user change password wilma
Enter new password:
Re-enter new password:
Passwords matched
Password changed for user "wilma".
366 user
Password strength requirements reset to defaults:
- min-length: 1
- min-character-classes: 1
Resetting password strength options.....[DONE]
368 user
28 vtl
370 vtl
Options for the vtl Command
add
vtl add vtl [model model] [slots num-slots] [caps num-caps]
Add a tape library (up to 64 library instances). This command is
available to administrative users only.
vtl A name of your choice.
model A tape library model name. The current supported
model names are L180 and RESTORER-L180. See the
Data Domain technical note for your backup
software for the model name that you should use. If
using RESTORER-L180 as the model name, your
backup software may require an update.
num-slots The number of slots in the library. You cannot add
more drives than the number of configured slots. The
maximum number of slots for all VTLs on a Data
Domain system is 20,000. The default is 20 slots.
num-caps The number of cartridge-access ports. The default is
0 (zero) and the maximum is 100 per library or 1000
per system.
cap
cap add
vtl cap add vtl [count num-caps]
Add num-caps CAPs to a Virtual Tape Library. The total number
of CAPs cannot exceed 100 per library or 1000 per system. This
command is available to administrative users only.
cap del
vtl cap del vtl [count num_to_del]
Delete num_to_del CAPs from a Virtual Tape Library. The CAPs
are deleted from the end. This command is available to
administrative users only.
disable
vtl disable
Close all libraries and shut down the VTL process. This command
is available to administrative users only.
drive
drive add
vtl drive add vtl [count num_drives] [model model]
Add virtual drives to a VTL.
vtl The virtual tape library name.
num_drives The number of drives to add. The maximum
number of drives across all VTLs is 64 to 256,
depending on the memory installed in your Data
Domain system. Systems with 4 G of memory
(DD4xx, DD510 and DD530) can have a maximum
of 64 drives. Systems with 8 GB to 38 GB (DD580,
DD660, and DD690) can have a maximum of 128
drives. Systems with 39 GB or more (DD880 and
later) can have a maximum of 256 drives.
model One of IBM-LTO-1, IBM-LTO-2, or IBM-LTO-3. The
default drive type is IBM-LTO-3.
Drives are added by starting with drive number 1 and scanning for
any holes left by the vtl drive del command. Once the holes are
filled, the drives are appended to the end of the library. The
number of slots within a library can never be less than the number
of drives in the library. If an attempt is made to add more drives
than the current number of slots, the system will automatically add
the needed number of slots. This command is available to
administrative users only.
372 vtl
Note: You cannot mix drive models within the same library.
drive del
vtl drive del vtl drive drive_number [count num_to_del]
Delete virtual drives from a VTL. Any drive can be deleted, which
means there can be holes in the drive list. This may cause issues
with some applications. This command is available to
administrative users only.
enable
vtl enable
Start the VTL process. This command is available to administrative
users only.
export
vtl export vtl {slot | drive | cap} address [count count]
Remove tapes from a slot, drive, or cartridge-access port and send
them to the vault. Use the vtl tape show vtl-name command to
display slots and tape barcodes.
vtl The virtual tape library name.
address The number of the slot, drive, or cartridge-access port.
count The number of tapes to remove.
group
The VTL group feature allows clients to access only selected LUNs
(devices, which are virtual media changers or virtual tape drives)
from a Data Domain system. This command is available to
administrative users only.
VTL group changes may require the media server to rescan the
SCSI bus, or you can use the vtl reset hba command to reset the
link.
group add
vtl group add group_name initiator alias_or_WWPN
vtl group add group_name vtl vtl_name {all | changer | drive
drive_list} [lun lun] [primary-port {all | none | port-list}]
[secondary-port {all | none | port-list}]
Add an item to the specified VTL access group. You can add an
initiator, a VTL, or devices within a VTL, optionally starting at a
given LUN. You can optionally specify primary and secondary
Data Domain system VTL port lists. By default, the port lists
contain all Data Domain system VTL ports. This command is
available to administrative users only.
374 vtl
lun A device address to pass to the initiator. The
maximum Logical Unit Number (LUN) is 16383.
A LUN must be unique within a group, but need
not be unique across the system. LUNs for VTL
devices within a group must start with 0 (zero)
and be contiguous numbers.
primary-port The primary VTL ports on which the devices are
all | none | visible. By default, or if you specify all, the VTL
port-list devices are visible on all ports. Specify none if
the devices should not be visible on any ports.
See below for a description of port-list.
This option lets you apply VTL access groups to
specific Data Domain system VTL ports. This
feature supports path flexibility for handling path
failure and load-balancing of VTL devices across
ports.
secondary-port The secondary VTL ports on which the devices
all | none | are visible to the vtl group use secondary
port-list command. By default, the devices are visible on
all ports. See below for a description of port-
list.
The secondary port list supports path
redundancy. Use the vtl group use primary
command to return the group to the primary port
list after the path gets repaired. See group use on
page 379.
port-list A comma-separated list of Data Domain system
VTL ports. You can specify port names as a range
separated by a hyphen (-). The ports must already
exist.
To list port names, use the vtl port show
summary command.
You can set an alias for the initiators with the vtl
initiator set alias command.
Related Commands
Use the vtl group use command to switch between the primary
and secondary port lists in the event of path failure.
The vtl show config command displays configuration
information for all defined VTLs.
group create
vtl group create group_name
Use this command to create a VTL access group with a specified
group-name. Each Data Domain system device (media changer or
tape drive) as well as initiators may then be added to the VTL
access group. This command is available to administrative users
only.
group_name The name of the new group. The name must be
unique, must not be longer than 256 characters, and
can contain only the characters 0-9, a-z, A-Z,
underscore(_), and hyphen (-). You can create up to
128 groups. Do not use the reserved group names
Default, TapeServer, all and summary.
Note: VTL group names are case-insensitive.
group del
vtl group del group_name initiator alias_or_WWPN
vtl group del group_name vtl vtl_name {all | changer | drive
drive_list}
Use this command to delete an initiator from a group. Specify the
initiator by its WWPN or alias. This command immediately
removes access from the specified initiator to the VTL devices
376 vtl
within the group. This command is available to administrative
users only.
group_name The group from which to delete the item.
vtl_name The VTL to delete from the group, or the VTL
that contains the devices to delete.
drive_list A comma-separated list of drives. The drive
number can be a single number, or a range of
two numbers separated by a hyphen (-). The
drive numbers are integers starting from 1.
Examples include 1, 2, 3-1, and 3-2.
alias_or_WWPN The initiator to delete.
group destroy
vtl group destroy group_name
Use this command to delete the specified empty VTL access group.
Before you destroy a group, use the vtl group del command to
remove the initiators and devices from the group. This command
is available to administrative users only.
group_name The group to destroy.
group modify
vtl group modify group_name vtl vtl_name {all | changer [lun
lun] | drive drive_list [lun lun]} [primary-port {all | none |
port-list}] [secondary-port {all | none | port-list}]
Use this command to modify a group without removing and
replacing devices or initiators in the group. You can use this
command to change LUN assignments, and primary and
secondary port assignments. The main purpose of this command is
to change group port assignments. This command is available to
administrative users only.
group_name The group from which to delete the item.
vtl_name The VTL to delete from the group, or the VTL that
contains the devices to delete.
378 vtl
group rename
vtl group rename src_group_name dst_group_name
Use this command to rename an existing VTL access group. The
dst_group_name must not already exist. See group create on
page 376 for a description of group name rules.
This command does not interrupt any active sessions. This
command is available to administrative users only.
group show
vtl group show [all | vtl vtl-name | group_name]
Use this command to show information about VTL access groups.
This command is available to administrative users only.
all Show information about all groups (default).
vtl-name Show information about all VTL access groups that
contain any devices within the specified vtl-name.
group_name Show detailed information about the specified
group.
group use
vtl group use group_name [vtl vtl-name {all | changer | drive
drive_list}] {primary | secondary}
Use this command to immediately change the access path to the
primary or secondary port for the selected VTL components in an
access group. When the path gets restored, you can use this
command to return the group to its primary port list. This
command is available to administrative users only.
group_name The VTL access group to use.
vtl-name The VTL to use.
drive_list A comma-separated list of drives. The drive number
can be a single number, or a range of two numbers
separated by a hyphen (-). The drive numbers are
integers starting from 1. Examples include 1, 2, 3-1,and
3-2.
import
vtl import vtl_name barcode barcode [count count]
[pool pool_name] [element {drive | cap | slot}] [address addr]
Use this command to move existing tapes from the vault into a
slot, drive, or cartridge access port. This command is available to
administrative users only.
vtl_name The VTL to use.
barcode The identifier for a virtual tape.
count The number of tapes to import.
pool_name The name of the pool, which is required if the tapes are
in a pool.
element The destination element. The default is slot.
addr The address. The default is 1.
Use the vtl tape show vtl-name command to display the total
number of slots for a VTL and which slots are currently used. Use
backup software commands from the backup server to move VTL
tapes to and from drives.
The following two commands are equivalent:
# vtl import VTL1 barcode TST010L1 count 5
# vtl import VTL1 barcode TST010L1 count 5 element slot
address 1
380 vtl
Rules for the Number of Tapes Imported
The number of tapes that you can import at one time is limited by:
The number of empty slots. (You cannot import more tapes
than the number of currently empty slots.)
The number of slots that are empty and that are not reserved
for a tape that is currently in a drive.
If a tape is in a drive and the tape origin is known to be a slot,
the slot is reserved.
If a tape is in a drive and the tape origin is unknown (slot or
CAP), a slot is reserved.
A tape that is known to have come from a CAP and that is in a
drive does not get a reserved slot. (The tape returns to the CAP
when removed from the drive.)
The number of tapes you can import equals:
(Total empty slots) - (the number of tapes that came from slots)
- (the number of tapes of unknown origin)
initiator
initiator reset address-method
vtl initiator reset address-method initiator alias_or_WWPN
Use this command to reset the address method used by REPORT
LUNS back to the default (auto). This command is available to
administrative users only.
382 vtl
initiator set alias
vtl initiator set alias alias_name wwpn wwpn
This command sets an alias for an initiator's WWPN. An initiator is
any Data Domain system client HBA's world-wide port names
(WWPN). This command does not interrupt traffic or VTL group
access. This command is available to administrative users only.
Use the vtl initiator show command on the Data Domain
system to list the client WWPNs detected by the Data Domain
system. You must match the WWPNs in the command output to
the client's HBA WWPN, including colon delimiters.
The alias must be unique, must not be longer than 256 characters,
and can contain only the characters 0-9, a-z, A-Z, underscore(_),
and hyphen (-). You can create up to 128 aliases.
The following example uses the client name and port number as
the alias to avoid confusion with multiple clients that may have
multiple ports:
# vtl initiator set alias client22_2a
wwpn 21:00:00:e0:8c:11:33:04
initiator show
vtl initiator show [initiator initiator | port port]
Use this command to display the following information about one
or all initiators:
Group
Status
WWNN
WWPN
Port
Symbolic port name
Address method
This command is useful in troubleshooting and during setup. This
command is available to administrative users only.
384 vtl
option enable
vtl option enable {auto-eject | auto-offline}
Use this command to enable either the auto-eject or the auto-
offline option. This command is available to administrative users
only.
auto-eject Automatically move any tape that is in a cartridge-
access port to the vault. The exception is that if the
tape came from the vault, the tape stays in the
cartridge-access port (CAP).
Note: With auto-eject enabled, a tape moved from
any element to a CAP is ejected to the vault unless an
ALLOW_MEDIUM_REMOVAL command with a value of
0 (false) was issued to the library to prevent the
removal of the medium from the CAP to the outside
world.
auto-offline Automatically move a tape offline when a move
command is generated. Use this option when backup
or other software does not issue an offline command
to the tape drive before issuing a move command to
the media changer.
pool
pool add
vtl pool add pool_name
Use this command to create a tape pool to allow replication by
pools. A pool is a named vault for tapes. If you do not create a
pool, the tapes get placed in the vault named Default. Pools are
for replication commands only.
This command is available to administrative users only.
pool del
vtl pool del pool_name
Use this command to delete a tape pool. You must first use the vtl
tape del command to remove all of the tapes from the pool.
pool show
vtl pool show {all | pool_name}
Use this command to list the configured tape pools or the contents
of a specific pool_name. This command is available to
administrative users only.
386 vtl
port
port disable
vtl port disable {all | port-list}
Use this command to disable all of the Fibre-Channel ports, or the
specific ports in port-list. The port-list may contain ports that
are already disabled. All of the specified ports must exist. This
command is available to administrative users only.
port enable
vtl port enable {all | port-list}
Use this command to enable one or more Fibre-Channel ports. The
port-list may contain ports that are already enabled. All of the
specified ports must exist. This command is available to
administrative users only.
388 vtl
port show summary
vtl port show summary
Use this command to show the following information:
Port
HBA slot
HBA port
Connection type
Link speed
Port ID
Enabled
Status
This command is available to administrative users only.
reset hba
vtl reset hba
Use this command to broadcast new VTLs and VTL changes to
clients. This command is available to administrative users only.
Note: Avoid using the vtl reset hba command during active
backup or restore jobs. The changes may cause an active job to fail
depending on the backup application and host type.
show
show config
vtl show config [vtl]
For all VTLs, or optionally a single VTL, this command displays
the following information:
Library name and model
Tape drive model
This command is available to administrative users only.
DD OS 4.9 Command Reference Guide 389
show element-address
vtl show element-address [vtl]
For all VTLs, or optionally a single VTL, this command displays
the following information:
Starting element address
Slot count and starting address
CAP count and starting address
Drive count and starting address
Changer count and starting address
This command is available to administrative users only.
show stats
vtl show stats vtl [drive {drive-list | all}] [port {port-list |
all}] [interval secs] [count count]
Use this command to show detailed traffic statistics for devices
that belong to the specified VTL. The statistics include the speed of
reads and writes in KiB per second, per VTL drive. If you omit
both drive and port (or specify all for both), you see the total
traffic statistics for all devices on all ports. This command is
available to administrative users only.
390 vtl
secs The interval between repeated displays of
statistics. For example, interval 1, shows
statistics every second. The default interval is 2
seconds.
count Show statistics for count number of times. For
example, count 10 displays statistics 10 times, each
instance being interval secs apart. The default
count is infinity, that is, the statistics display forever (or
until the command is aborted with Ctrl+C).
slot
slot add
vtl slot add vtl [count num_to_add]
Use this command to add one or more slots to the end of the
specified Virtual Tape Library. The maximum is 20,000 slots,
distributed across one or more libraries. This command is available
to administrative users only.
vtl The VTL to modify.
num_to_add The number of slots to add. The default is 20 slots.
slot del
vtl slot del vtl [count num_to_del]
Use this command to delete one or more slots from the end of the
specified Virtual Tape Library. This command is available to
administrative users only.
vtl The VTL to modify.
num_to_del The number of slots to delete. The default is 20 slots.
status
vtl status
Use this command to display the state of the VTL process. This
command is available to administrative users only.
392 vtl
Sample Barcodes
000000L1 Create tapes of 100 GiB capacity which can accept a
count of up to 1,000,000 tapes (from 000000 to
999999). You can create up to 100,000 tapes in a
single operation.
AA0000LA Create tapes of 50 GiB capacity which can accept a
count of up to 10,000 tapes (from 0000 to 9999).
AAA350LB Create tapes of 30 GiB capacity and can accept a
count of up to 650 tapes (from 350 to 999).
5M7Q3KLC Create one tape of 10 GiB capacity. You can create
only one tape with this name; you cannot increment
the name.
tape del
vtl tape del barcode [count count] [pool poolname]
Use this command to delete one or more tapes and all of the data
on those tapes. This command is available to administrative users
only.
barcode The barcode identifier for the tape (or for the first tape,
if you also specify count).
count The number of tapes to delete, in order, based on the
numeric characters in the bar code.
poolname The name of the pool that contains the specified tape.
This option is required if the tapes are in a pool.
394 vtl
tape modify writeprotect
vtl tape modify barcode [count count] [pool poolname]
writeprotect {on | off}
Use this command to set the write protect state of a specified tape.
If the volume is not mounted, the tape file permission gets changed
immediately. Otherwise, any outstanding writes are synchronized
first. If the file system is read-only and you try to use this
command to turn write protection off, the command fails. This
command is available to administrative users only.
barcode The barcode identifier for the tape.
count The number of tapes to modify, in order, based on the
numeric characters in the bar code.
poolname The name of the pool that contains the specified tape.
This option is required if the tapes are in a pool.
tape move
vtl tape move barcode barcode [count count] source src-pool
destination dest-pool
Use this command to move tapes between VTL pools.
barcode The barcode identifier for the tape.
count The number of tapes to move. These tapes must have
sequential barcodes.
src-pool The current pool.
dest-pool The new pool.
tape show
vtl tape show {all | pool pool | vault | vtl} [summary] [count
count] [barcode barcode] [sort-by {barcode | pool | location |
state | capacity | usage | percentfull | compression | modtime}
[{ascending | descending}]]
Use this command to display information about tapes. This
command is available to administrative users only.
all Show information about all tapes.
pool pool Show information about the tapes in the specified
pool.
vault Show information about tapes in the vault.
vtl Show information about tapes in the specified vtl.
summary Show a summary of all tapes and tape usage.
count count Show the specified number of tapes in order, based on
the numeric characters in the bar code.
barcode Show information about tapes that match the specified
barcode barcode.
When using count and barcode together, use a wild
card character in the barcode to have the count be
valid. An asterisk (*) matches any character in that
position and all further positions. A question mark (?)
matches any character in that position.
396 vtl
sort-by Sort the report on the specified column: barcode,
pool, location, state, capacity, usage (number
of bytes used on the tape), percentfull,
compression, or modtime (modification time).
ascending | Sort the report in the specified order.
descending
Examples
Add a VTL
The following commands add a VTL, add tapes, and then populate
the VTL slots with tapes. The VTL is then ready for backup
commands.
1. Create a new VTL:
# vtl add libr01 model L180 slots 200 caps 2
2. Add four IBM-LTO-3 drives to the VTL:
# vtl drive add libr01 count 4 model IBM-LTO-3
3. Adds tapes to the VTL:
# vtl tape add ABC100L1 capacity 75 count 50
4. Import tapes into the VTL slots:
# vtl import libr01 barcode ABC100L1 count 10
Move Tapes
1. Move ten tapes starting at AA0000LC from pool srcpool to
pool dstpool:
# vtl tape move barcode AA0000LC count 10 source
srcpool destination dstpool
398 vtl
Barcode Pool Location State Size Used
(%) Comp ModTime
ABC000L1 Default lib1 cap 1 RW 100 GiB 0.0 GiB (
0.00%) 0x 2009/10/29 12:07:31
ABC001L1 Default lib1 cap 2 RW 100 GiB 0.0 GiB (
0.00%) 0x 2009/10/29 12:07:31
VTL Tape Summary
----------------
Total number of tapes: 2
Total pools: 1
Total size of tapes: 200 GiB
Total space used by tapes: 0.0 GiB
Average Compression: 0.0x
6. Export two tapes from CAPs.
# vtl export lib1 cap 1 count 2
... exported 2 tape(s)...
7. Import three tapes to slots.
# vtl import lib1 barcode ABC000L1 count 3
... imported 3 tape(s)...
8. Check the results of the import.
# vtl tape show lib1
Processing tapes....
Barcode Pool Location State Size Used
(%) Comp ModTime
ABC000L1 Default lib1 slot 1 RW 100 GiB 0.0 GiB (
0.00%) 0x 2009/10/29 12:07:31
ABC001L1 Default lib1 slot 2 RW 100 GiB 0.0 GiB (
0.00%) 0x 2009/10/29 12:07:31
ABC002L1 Default lib1 slot 3 RW 100 GiB 0.0 GiB (
0.00%) 0x 2009/10/29 12:07:31
VTL Tape Summary
----------------
Total number of tapes: 3
Total pools: 1
Total size of tapes: 300 GiB
DD OS 4.9 Command Reference Guide 399
Total space used by tapes: 0.0 GiB
Average Compression: 0.0x
9. Export three tapes from slots.
# vtl export lib1 slot 1 count 3
... exported 3 tape(s)...
Important Notices
Before starting to use Data Domain VTL, you need to:
Obtain a license.
The VTL feature requires a license. See your Data Domain sales
representative to purchase a license.
Verify that a Fibre Channel (FC) interface card has been
installed.
Because the VTL feature communicates between a backup
server and a Data Domain system through a Fibre Channel
interface, the Data Domain system must have a Fibre Channel
interface card installed in the PCI card array.
Set the backup software minimum record (block) size.
Data Domain strongly recommends that backup software be
set up to use a minimum record (block) size of 64 KiB or larger.
Larger sizes usually give faster performance and better data
compression.
Note: If you change the size after initial configuration, data
written with the original size becomes unreadable.
Compatibility
Data Domain VTL is compatible with all DD400, DD500, DD600,
and DD800 series Data Domain systems.
For specific backup software and hardware configurations tested
and supported by Data Domain, see the VTL matrices at the Data
Domain Support Web site:
https://my.datadomain.com/documentation
400 vtl
Tape Drives
You can use tape and library drivers supplied by your backup
software vendor that support the IBM LTO-1 (the default), IBM
LTO-2, or IBM LTO- 3 drives and the StorageTek L180,
RESTORER-L180, or IBM TS3200 tape libraries. (See Compatibility
on page 400.)
Because the Data Domain system treats the IBM LTO drives as
virtual drives, you can set a maximum capacity of 800 GB for each
drive type.
The default capacities for each IBM LTO drive type are as follows:
LTO-1 drive: 100 GB
LTO-2 drive: 200 GB
LTO-3 drive: 800 GB
Note: You cannot mix drive types (LTO-1, LTO-2, and LTO-3) or
media types in the same library.
Tape Libraries
Data Domain VTL supports the StorageTek L180, RESTORER-
L180, and IBM TS3200 tape libraries with the following number of
libraries, tape drives, and tapes:
64 libraries (64 concurrently active virtual tape library
instances). Access to VTLs and tape drives can be managed
with the Access Grouping feature. See group on page 373.
Up to 256 tape drives, depending on the memory installed in
your Data Domain system.
Up to 100,000 tapes (cartridges) of up to 800 GiB for an
individual tape (Gibibytes, the base-2 equivalent of Gigabytes).
Restrictions
The number of recommended concurrent virtual tape drive
instances is platform-dependent and is the same as the number of
recommended streams between a Data Domain system and a
backup server. This number is system-wide and includes all
streams from all sources, such as VTL, NFS, and CIFS.
Caution: Data Domain VTL does not protect virtual tapes from a
Data Domain system filesys destroy command. The
command deletes all virtual tapes.
402 vtl
A MIB Reference
MIB Browser
The user may find it worthwhile to download a freeware MIB browser. Many can
be found by searching on Google. As an example, the iReasoning MIB browser
can be found for downloading at http://www.ireasoning.com/mibbrowser.shtml, at
the link Download Free Personal Edition.
currentAlertTable OBJECT-TYPE
SYNTAX SEQUENCE OF CurrentAlertEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing entries of
CurrentAlertEntry."
::= { currentAlerts 1 }
currentAlertEntry OBJECT-TYPE
SYNTAX CurrentAlertEntry
MAX-ACCESS not-accessible
STATUS current
currentAlertIndex OBJECT-TYPE
SYNTAX AlertIndexTC
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Current Alert Row index"
::= { currentAlertEntry 1 }
currentAlertTimestamp OBJECT-TYPE
SYNTAX AlertTimestampTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Timestamp of current alert"
::= { currentAlertEntry 2 }
currentAlertDescription OBJECT-TYPE
SYNTAX AlertDescriptionTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Alert Description"
::= { currentAlertEntry 3 }
--
************************************************************
Alerts (.1.3.6.1.4.1.19746.1.4)
The Alerts table is a set of containers (variables or fields) that hold
the current problems happening in the system.
By contrast, the Notifications table holds a set of rules for what the
system does in response to problems whenever they happen in the
system. See also Data Domain MIB Notifications (.1.3.6.1.4.1.19746.2) on
page 409.
Alerts are the system for communicating problems, Data Domain's
version of Notifications. The table currentAlertTable holds many
current alert entries at once, with an Index, Timestamp, and
Description for each. The Data Domain Alerts are shown in
FigureA-1 and Table A-2.