IBM E16RMLL-I - Tivoli Storage Manager, Implementation Manual

Page: 60 / 828

30
IBM Tivoli Storage Manager Implementation Guide
2.3.11 Backup set retention
A backup set execution creates a copy of the client node's previously backed up
active files and stores them on sequential media. This has an impact on the
number of tapes that you may need, especially if you want to retain those backup
sets for long periods of time or even if you want to have one copy onsite and one
for off-site purposes.
Determine how long you want to keep the backup sets. Use a small retention if
your data changes frequently and you do not need to keep it for long periods.
You can use a longer retention for special cases or for legal requirements.
2.4 Server architecture considerations
Having gathered information about the total client environment, you can now
make decisions about the architecture of the Tivoli Storage Manager server
environment. This section deals with issues related to the Tivoli Storage
Manager server.
2.4.1 Server platform
A Tivoli Storage Manager server runs on several platforms. How do you choose
one platform over another? With only minor differences, a Tivoli Storage
Manager server provides the same functionality on every platform. The major
differences between Tivoli Storage Manager server platforms relate to capacity,
cost, installation, operation, supported devices, and installed user base. Each of
these factors is explained below. Table 2-7 summarizes these considerations in
choosing a Tivoli Storage Manager server platform. Note these are indicative
only and designed for comparative purposes.
In many cases, the choice of server platform will be dictated by enterprise policy
or preference, and will be primarily related to the platforms already in use, and
with skilled administrators available.
Table 2-7 Tivoli Storage Manager server platform considerations
Windows
system UNIX iSeries™ zSeries®
Installed user base +++ AIX +++
Linux- ++;
HP-UX,
Sun™
Solaris™ + + +