HP StorageWorks 2/16V Brocade Fabric Manager Administrator's Guide (53-1000019 - Page 247

Deleting a Zone Database from the Local Repository, Undoing the Automatic Checkout of a Zone Database

Page 247 highlights

Managing Zoning Offline 15 Deleting a Zone Database from the Local Repository The following procedures describes how to delete a zone database from the local repository. You cannot delete the zone database that is on the fabric. Every fabric has a zone database associated with it, even if the zone database is empty. To delete a zone database from the local repository 1. Click Tasks > Zone Management > Zone Administration from the menu bar. The Zone Administration module launches, as shown in Figure 15-1. 2. Select one or more zone databases that are located in the repository. You cannot delete zone databases that are currently in the fabric. 3. Click Delete Zone DB. 4. Click OK in the confirmation window. Undoing the Automatic Checkout of a Zone Database When you edit a zone database, either through the Zone Editor Tool or the Compare/Merge Zone Database module, you are implicitly checking out the zone database. Fabric Manager displays the user name of all users who have checked out a copy of the zone database in the Who has taken a copy? column of the Zone Administration table. If the authentication mechanism has changed (from RADIUS to Windows Domain, for example), the user names displayed in the Who has taken a copy? column might not be accurate. Caution Before you edit a zone database, check this column to determine whether other users are modifying it at the same time, so that your changes do not overlap. If you have checked out a zone database but are not planning to update it, you can undo the checkout so that other users can update it without worrying about their changes being overwritten. When you undo the checkout, the user names of other users who are currently logged in to the client are also removed. Ensure that those other users are not updating the zone database before you undo the checkout. To undo the checkout of a zone database 1. Click Tasks > Zone Management > Zone Administration from the menu bar. The Zone Administration module launches, as shown in Figure 15-1. 2. Select a zone database that you have checked out (your user name is in the Who has taken a copy? column). 3. Right-click the zone database and select Undo Zone DB Checkout from the context menu. 4. Click Yes in the confirmation window. This removes the user names of users currently logged in to the client from the Who has taken a copy? column for this zone database. Fabric Manager Administrator's Guide Publication Number: 53-1000196-01-HP 15-15

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406

Fabric Manager Administrator’s Guide
15-15
Publication Number: 53-1000196-01-HP
Managing Zoning Offline
15
Deleting a Zone Database from the Local Repository
The following procedures describes how to delete a zone database from the local repository.
You cannot delete the zone database that is on the fabric. Every fabric has a zone database associated
with it, even if the zone database is empty.
To delete a zone database from the local repository
1.
Click
Tasks > Zone Management > Zone Administration
from the menu bar.
The Zone Administration module launches, as shown in
Figure 15-1
.
2.
Select one or more zone databases that are located in the repository. You cannot delete zone
databases that are currently in the fabric.
3.
Click
Delete Zone DB
.
4.
Click
OK
in the confirmation window.
Undoing the Automatic Checkout of a Zone Database
When you edit a zone database, either through the Zone Editor Tool or the Compare/Merge Zone
Database module, you are implicitly
checking out
the zone database. Fabric Manager displays the user
name of all users who have checked out a copy of the zone database in the
Who has taken a copy?
column of the Zone Administration table.
If the authentication mechanism has changed (from RADIUS to Windows Domain, for example), the
user names displayed in the
Who has taken a copy?
column might not be accurate.
If you have checked out a zone database but are not planning to update it, you can undo the checkout so
that other users can update it without worrying about their changes being overwritten.
When you undo the checkout, the user names of other users who are currently logged in to the client are
also removed. Ensure that those other users are not updating the zone database before you undo the
checkout.
To undo the checkout of a zone database
1.
Click
Tasks > Zone Management > Zone Administration
from the menu bar.
The Zone Administration module launches, as shown in
Figure 15-1
.
2.
Select a zone database that you have checked out (your user name is in the
Who has taken a copy?
column).
3.
Right-click the zone database and select
Undo Zone DB Checkout
from the context menu.
4.
Click
Yes
in the confirmation window.
This removes the user names of users currently logged in to the client from the
Who has taken a
copy?
column for this zone database.
Caution
Before you edit a zone database, check this column to determine whether other users are modifying it at
the same time, so that your changes do not overlap.