Using SANs and NAS help for storage administrators
Data is the lifeblood of modern business, and modern data centers have extremely demanding requirements for size, speed, and reliability. Storage Area Networks (SANs) and Network Attached Storage (NAS) allow organizations to manage and back up huge file systems quickly, thereby keeping their lifebl...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Sebastopol, California :
O'Reilly & Associates
2002.
|
| Edición: | 1st edition |
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627142106719 |
Tabla de Contenidos:
- Using SANs and NAS; What Is This Book For?; Conventions Used in This Book; Comments and Questions; Acknowledgments; 1. What Are SANs and NAS?; 1.2. What Is a SAN?; 1.3. Backup and Recovery: Before SANs; 1.3.2. Enter the SAN; 1.4. From NFS and SMB to NAS; 1.4.2. NFS; 1.4.3. NFS and CIFS: Before NAS; 1.4.4. Enter NAS; 1.5. SAN Versus NAS: A Summary; 1.6. Which Is Right for You?; 1.6.2. Pros and Cons of SANs; 1.6.3. It All Depends on Your Environment; 2. Fibre Channel Architecture; 2.1.2. What Is Fibre Channel?; 2.2. Fibre Channel Ports; 2.3. Fibre Channel Topologies; 2.3.2. Fabric
- 2.3.3. Arbitrated Loop2.3.4. FC-AL Versus Fabric; 2.3.4.2. Address selection; 2.3.5. Combining Fabric and Arbitrated Loop Topologies; 2.4. SAN Building Blocks; 2.4.2. Host Bus Adapters (HBAs); 2.4.3. Switches; 2.4.4. Hubs; 2.4.5. Hub Switches; 2.4.6. Routers and Bridges; 2.4.7. Disk Systems; 2.4.8. Cabling; 2.4.9. Software; 2.5. Fibre Channel and SANs: A Summary; 3. Managing a SAN; 3.1.2. Filesystems with Many, Many Files; 3.1.3. Databases Requiring Raw Device Access; 3.1.4. Vendors That Don&t (or Won&t) Support NAS; 3.2. SAN Issues to Be Managed
- 3.2.2. Multiple Servers Accessing the Same Device3.2.3. Storage Devices with Changing Addresses; 3.2.4. Lack of Interoperability; 3.3. Access to Storage Resources; 3.3.1.2. Striping/RAID; 3.3.2. Implementations of Virtualization; 3.3.2.2. Software-based implementation; 3.3.3. Zoning; 3.3.3.2. Hard zones; 3.3.3.3. Soft zones; 3.3.3.4. Broadcast zones; 3.3.3.5. Naming your zones; 3.3.4. LUN Masking; 3.3.5. Designing Your SAN for Availability; 3.3.6. Multipathing; 3.3.6.2. Load balancing; 3.3.6.3. Preventing thrashing; 3.3.7. Persistent Binding; 3.4. Ongoing Maintenance; 3.4.2. Monitoring
- 3.4.3. Maintenance3.5. Using SANs to Maximize Your Storage; 3.5.2. Is This for Real?; 3.5.3. Offline Storage Maximization; 3.5.4. Online and Offline Storage Maximization Combined; 3.5.5. Truly Highly Available Systems; 3.6. Summary; 4. SAN Backup and Recovery; 4.2. LAN-Free Backups; 4.2.1.2. Third-party queuing system; 4.2.2. Levels of Drive Sharing; 4.2.3. Restores; 4.2.4. Other Ways to Share Tape Drives; 4.2.4.2. SCSI over IP; 4.2.4.3. Shared SCSI; 4.2.5. A Variation on the Theme; 4.2.5.2. Problem solved; 4.2.6. Problems with LAN-Free Backups; 4.2.6.2. Recovery speed; 4.2.6.3. No other way?
- 4.3. Client-Free Backups4.3.2. Backing Up the Backup Mirror; 4.3.2.2. Back up the transaction logs; 4.3.2.3. Back up the datafiles; 4.3.2.3.2. Put the database in backup mode; 4.3.2.3.3. Split the backup mirror; 4.3.2.3.4. Take the database out of backup mode; 4.3.2.3.5. Import the backup mirror&s volumes to the backup server; 4.3.2.3.6. Back up the backup mirror volumes to tape; 4.3.3. Client-Free Recovery; 4.3.3.2. Restore backup mirror from tape; 4.3.3.3. Recovering after a tape recovery or if you lose the primary disk set and not the backup mirror
- 4.3.3.4. Restore primary disk set from the backup mirror
