IBM E16RMLL-I - Tivoli Storage Manager, Руководство по внедрению

Страница: 54 / 828

24
IBM Tivoli Storage Manager Implementation Guide
2.2.14 GB copied per archive
Calculate or estimate the amount of data to be archived during each archive
session. Archives target specific data files. Typically, you do not archive whole
systems.
2.2.15 Number of files archived
Calculate or estimate the number of files archived in each archive session. You
can calculate this number by using an operating system utility to verify the size of
a directory tree or an entire file space.
2.2.16 Number of archives kept
Identify how many archives will be kept. For example, if an archive is performed
monthly, you may want to keep 12 copies of that archive. Note that this number
is basically influenced by the retention period for that archive, since archives,
unlike backups, do not have versions that expire.
2.2.17 Archive frequency
Determine how often you want to perform an archive function. Archives are
typically run less frequently than incremental backups. Time frames such as
monthly or yearly are common.
2.2.18 Archive window times
Enter the times between which Tivoli Storage Manager must start and complete
its archive cycle for this client. This window is influenced by when end-user client
usage drops off, by availability requirements, by network capacity usage time
frames, or by when the data becomes available for archive.
Archive time frames may be less time sensitive than incremental backups if they
are going against copies of data or against data already processed. Often it is not
possible to automatically schedule this archive function using Tivoli Storage
Manager schedules, due to the dependency on other events external to Tivoli
Storage Manager.
This number may be a specific time frame, such as between 23:00 and 04:00, or
a more general time frame, such as after month-end processing finishes.
2.2.19 Archive number of hours
Identify the number of hours available to complete the archive function.