Ideally, you want to physically separate transaction logs, data files, backup files, and perhaps
specific filegroups onto different data arrays. Don??™t be intimidated by the complexity
of a SAN, and argue your point when it comes to disaster recovery.
CHAPTER 10 n HARDWARE CONSIDERATIONS 256
SAN-A-PHOBIA
It??™s common for DBAs making the transition from locally attached storage to a SAN environment to be
skeptical about the I/O configuration for the various data files/filegroups for their database. Their skepticism
and paranoia is, at times, valid. Some SANs are installed and configured by an outside vendor with
little or no knowledge to transfer to in-house staff (this is more common with small- to mid-sized companies
where IT budgets are tight). While the DBA requests separate I/O for certain files or filegroups,
the ultimate configuration may be one, single, huge disk array. To make things worse, there may be
only one path into the SAN, shared by everyone.
Tape Storage
Backups must be portable. Traditionally, portability is a side effect of magnetic tape storage.
I always advocate that backups should ultimately end up on tape storage.
Pages:
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470