SAN Boot Implementation and Best Practices Guide ... - IBM Redbooks

More documents

Recommendations

Info

SG247958-Introduction to SAN Boot-CL.fm Draft Document for Review June 27, 2012 9:05 am By taking advantage of a SAN Boot host solution using both IBM disk storage systems and IBM Tivoli Storage Manager, host backup and recovery processing benefits from high performance disk storage and advanced functionality such as flashcopy to securely and efficiently meet ever demanding backup and recovery requirements. Continuous Operations According to recent research, a one-hour IT system outage can cost a business $1.1M. Your IT systems need to be able to prevent and avoid outages and recover from them quickly, IBM offers a range of reliable, high-performance solutions to ensure that a business can remain operational through component failures or significant disasters. IBM Tivoli Storage FlashCopy Manager Use of IBM Tivoli Storage FlashCopy Manager enables organizations to perform and manage frequent, near-instant, non-disruptive, application-aware backups and restores, leveraging advanced FlashCopy snapshot technologies in IBM storage systems. Just as IBM Tivoli Storage FlashCopy Manager takes advantage of IBM storage systems functionality, so to can SAN Boot host solutions utilizing IBM storage systems. With the ability to take instantaneous flashcopies of a host operating system, costly issues - that may be encountered with newly applied operating system or application code - can be quickly restored. By centralizing the location of the host operating system storage with use of SAN Boot, System Administrators are also able to rapidly recover from host hardware errors. By simply re-assigning SAN Boot volumes to standby hardware, recovery times and outage costs are greatly reduced. Control and Automation By automating management and enforcement of storage policies, you can keep storage infrastructure in its desired state efficiently. This can help you improve service quality, improve data protection, recovery, reliability and integrity while reducing ongoing staff intervention. Automated lifecycle management tools can help you meet information retention mandates, automate provisioning, backup and archive to optimize performance, utilization, lower costs and build agility. IBM Tivoli Storage Productivity Center IBM Tivoli Storage Productivity Center Standard Edition is a single integrated solution designed to help you improve your storage TCO and ROI by combining the assets, capacity, performance and operational management, traditionally offered by separate Storage Resource Management, SAN Management and Device Management applications, into a single platform. Implementing a SAN Boot host solution in conjunction with IBM Tivoli Storage Productivity Center can further improve and facilitate Storage Resource Management. By co-locating host operating storage on IBM storage systems, numerous benefits can be realized: – Capacity can be monitored at the storage system level, not at the individual host level – Automation can be implemented to create capacity on demand storage solutions – Overall storage utilization can be planned for at the storage subsystem level Retention and Compliance Today, significant amounts of data must be saved to meet business or legal requirements. As the amount of information stored grows and grows, effective data archiving solutions can help you improve productivity, control both infrastructure and legal costs, and manage compliance and operational risks. 20 SAN Boot Implementation and Best Practices Guide for IBM System Storage
Draft Document for Review June 27, 2012 9:05 am SG247958-Introduction to SAN Boot-CL.fm IBM Information Archive IBM Information Archive is a simple and flexible archiving solution to help organizations of all sizes address their complete information retention needs—business, legal or regulatory. With a SAN Boot host solution, retention is enhanced by the functionality of the IBM storage system that the data resides on. Use of centralized storage subsystem functionality, instead of utilizing a mixture of functionalities found with individual host level storage, reduces administrative overhead. In regards to compliance, SAN Boot host data can benefit from flashcopy snapshots of data and the retention of that data in a locked and immutable state - pending movement to an archive environment such as IBM Information Archive. Chapter 1. Introduction to SAN Boot 21
Page 1: Draft Document for Review June 27,
Page 4 and 5: 7958edno.fm Draft Document for Revi
Page 6 and 7: 7958edno.fm Draft Document for Revi
Page 8 and 9: 7958TOC.fm Draft Document for Revie
Page 14 and 15: 7958spec.fm Draft Document for Revi
Page 16 and 17: 7958pref.fm Draft Document for Revi
Page 18 and 19: 7958pref.fm Draft Document for Revi
Page 20 and 21: SG247958-Introduction to SAN Boot-C
Page 40 and 41: SG247958-DS5000-CL.fm Draft Documen
Page 86 and 87:
SG247958-DS5000-CL.fm Draft Documen
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
7958ch05_DS8000.fm Draft Document f
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
4.1 Overview The XIV Storage System
Page 220 and 221:
SAN boot for AIX 6.1 is separately
Page 222 and 223:
Figure 4-6 Qlogic configuration scr
Page 224 and 225:
Figure 4-10 Qlogic configuration sc
Page 226 and 227:
Figure 4-13 Emulex configuration sc
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
4.2.5 Zoning As an example of one p
Page 234 and 235:
connect one HBA port to on port on
Page 236 and 237:
Figure 4-28 shows the XIVGUI panel
Page 238 and 239:
Example 4-4 Creating an XIV host us
Page 240 and 241:
Figure 4-37 XIVGUI LUN Mapping pane
Page 242 and 243:
Figure 4-40 XIVGUI Add Port panel 4
Page 244 and 245:
Modules (DSMs) for MPIO and to buil
Page 246 and 247:
-----------------------------------
Page 248 and 249:
Verification of FC Multipath Connec
Page 250 and 251:
For additional XIV considerations,
Page 252 and 253:
Figure 4-49 SUSE Linux Enterprise S
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
-----------------------------------
Page 264 and 265:
Figure 4-59 RHEL 5.5: Partition ove
Page 266 and 267:
Figure 4-61 RHEL 5.5: Boot loader p
Page 268 and 269:
| RHEL | SLES 11 | SLES 10 | +-----
Page 270 and 271:
► Review section 4.3, “XIV Mana
Page 272 and 273:
1 hdisk1 U789C.001.DQDU764-P2-D5 >>
Page 274 and 275:
Example 4-19 Installation of the XI
Page 276 and 277:
Optimizing multipathing policies Fo
Page 278 and 279:
Once the mkinitrd process has compl
Page 280 and 281:
Figure 4-67 MPIO Policy - Round Rob
Page 282 and 283:
266 SAN Boot Implementation and Bes
Page 284 and 285:
Storwize_V7000.fm Draft Document fo
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 354 and 355:
Page 356 and 357:
Page 358 and 359:
Page 360 and 361:
Page 362 and 363:
Page 364 and 365:
Page 366 and 367:
Page 368 and 369:
Page 370 and 371:
Page 372 and 373:
Page 374 and 375:
Page 376 and 377:
Page 378 and 379:
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Page 386 and 387:
Page 388 and 389:
Page 390 and 391:
Page 392 and 393:
Page 394 and 395:
Page 396 and 397:
Page 398 and 399:
Page 400 and 401:
Page 402 and 403:
Page 404 and 405:
Page 406 and 407:
Page 408 and 409:
SG247958-iSCSI_DS5000-CL.fm Draft D
Page 410 and 411:
Page 412 and 413:
Page 414 and 415:
Page 416 and 417:
Page 418 and 419:
Page 420 and 421:
Page 422 and 423:
Page 424 and 425:
Page 426 and 427:
Page 428 and 429:
Page 430 and 431:
Page 432 and 433:
Page 434 and 435:
Page 436 and 437:
Page 438 and 439:
Page 440 and 441:
Page 442 and 443:
Page 444 and 445:
Page 446 and 447:
Page 448 and 449:
Page 450 and 451:
Page 452 and 453:
Page 454 and 455:
Page 456 and 457:
Page 458 and 459:
Page 460 and 461:
Page 462 and 463:
7958bibl.fm Draft Document for Revi
Page 464 and 465:
7958IX.fm Draft Document for Review
Page 466 and 467:
Page 468 and 469:
Page 470 and 471:
Page 472:
(2.0” spine) 2.0” 2.498” 105
show all

SAN Boot Implementation and Best Practices Guide ... - IBM Redbooks

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?