HP ProLiant DL380G5-WSS 3.7.0 HP StorageWorks HP Scalable NAS File Serving Sof - Page 404

Configuration steps

Page 404 highlights

• The Samba options described in this appendix have been tested by HP. Samba has many other configuration options; those options have not been thoroughly tested by HP in the clustered Samba environment. If they are suited to your Samba environment, they can be used; however, if you use configuration parameters other than those included in this appendix, HP recommends that you test your configuration carefully before deploying it in a production environment. In general, the guidelines found in Samba documentation and online forums are valid in this environment but the administrator should be especially wary of any configuration parameters that affect the location of the Samba Tiny Database (TDB) or the configuration files. • The newly released Samba functionality known as clustered Samba (or CTDB support) has not been tested with HP Scalable NAS 3.7. While clustered Samba using CTBD support may work in the 3.7 environment, it has not been integrated into the HA management structure for the cluster and it has not been tested for stability or performance. For these reasons, HP does not support clustered Samba configurations that use CTDB over HP Scalable NAS. Configuration steps When using Samba with HP Scalable NAS, you should be aware of the following: • The smb_meth script provided with HP Scalable NAS controls the Samba startup. You do not need to configure Samba to start automatically. • Before configuring Samba for the first time, be sure that the smb.conf and smb.default files are in sync. To do this, copy the smb.default file over the smb.conf file. The basic steps to configure Samba with HP Scalable NAS are as follows: 1. Create the necessary Samba configuration files. 2. If necessary, set passwords for Samba users. 3. Run the HP Scalable NAS smbcfg_dist utility to copy the Samba configuration files to the other nodes in the cluster. 4. Configure HP Scalable NAS virtual hosts. Each virtual Samba server can be broadcast by only one node at a time. You can configure a primary node and one or more backup nodes for each virtual server. This is done by creating a virtual host for each virtual Samba server and then assigning the primary and backup nodes to it. 5. Create a CUSTOM service monitor for each virtual host. This monitor watches the Samba service on the primary node and controls Samba start and stop operations when the virtual host fails over to a backup node. 404 Samba configuration

  • 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
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435

The Samba options described in this appendix have been tested by HP. Samba
has many other configuration options; those options have not been thoroughly
tested by HP in the clustered Samba environment. If they are suited to your Samba
environment, they can be used; however, if you use configuration parameters
other than those included in this appendix, HP recommends that you test your
configuration carefully before deploying it in a production environment. In general,
the guidelines found in Samba documentation and online forums are valid in this
environment but the administrator should be especially wary of any configuration
parameters that affect the location of the Samba Tiny Database (TDB) or the
configuration files.
The newly released Samba functionality known as clustered Samba (or CTDB
support) has not been tested with HP Scalable NAS 3.7. While clustered Samba
using CTBD support may work in the 3.7 environment, it has not been integrated
into the HA management structure for the cluster and it has not been tested for
stability or performance. For these reasons, HP does not support clustered Samba
configurations that use CTDB over HP Scalable NAS.
Configuration steps
When using Samba with HP Scalable NAS, you should be aware of the following:
The
smb_meth
script provided with HP Scalable NAS controls the Samba startup.
You do not need to configure Samba to start automatically.
Before configuring Samba for the first time, be sure that the
smb.conf
and
smb.default
files are in sync. To do this, copy the
smb.default
file over the
smb.conf
file.
The basic steps to configure Samba with HP Scalable NAS are as follows:
1.
Create the necessary Samba configuration files.
2.
If necessary, set passwords for Samba users.
3.
Run the HP Scalable NAS
smbcfg_dist
utility to copy the Samba configuration
files to the other nodes in the cluster.
4.
Configure HP Scalable NAS virtual hosts. Each virtual Samba server can be
broadcast by only one node at a time. You can configure a primary node and
one or more backup nodes for each virtual server. This is done by creating a
virtual host for each virtual Samba server and then assigning the primary and
backup nodes to it.
5.
Create a CUSTOM service monitor for each virtual host. This monitor watches
the Samba service on the primary node and controls Samba start and stop
operations when the virtual host fails over to a backup node.
Samba configuration
404