Table of Contents
Advertisement
Figure 61 TSM LAN-based backups
1.
Data on application servers (A-G) is backed up by TSM server via the SAN to the TSM disk
pool. A typical TSM primary disk pool is sized for a minimum of one nightly backup.
2.
As the primary disk pool fills, TSM moves data from it via the SAN to the primary tape pool.
Unscheduled Migrations Undersized disk storage pools; a common mistake is to define disk
pools that do not have the capacity to hold one night's worth of backup data. Doing so results
in data migration to tape starting when the disk pool has reached its high migration threshold,
rather than starting as scheduled using the "migrate" function. Unscheduled migrations can
interfere with backups causing them to fail or run beyond the allowable window.
3.
Data is copied (migrated) from the primary disk pool to the primary tape storage pool on a
tape library. This migration is an I/O and CPU-intensive operation, which is typically limited
by the speed of tape drives. If a migration occurs during a backup, the backup performance
slows dramatically.
4.
Data is copied from the primary tape storage pool to a copy storage pool, making a set of
tapes to send off-site for disaster protection. By replacing the primary tape storage pool with
a virtual library, you can dramatically improve backup and restore times, reduce the need for
primary disk, and enable more use of advanced TSM functions such as LAN—free backups.
Figure 62 (page 143)
to improve backup performance and reduce LAN load. The steps are described below.
142 VLS Configuration and Backup Application Guidelines
shows an overview of TSM LAN-free backups that incorporate virtual libraries
Advertisement
Table of Contents
