Table of Contents
Advertisement
2.2.20 Number of image backups
Identify the number of eligible system images that you want to back up. For a
workstation that does not change very frequently, a good number could be six to
twelve per machine.
2.2.21 Image backup frequency
Identify how often you want to perform image backups. A good standard will be
on a monthly basis for less critical and static machines, with more frequent
backups for more critical and dynamic machines.
2.2.22 Number of backup sets
Determine the number of backup sets that you want to create. This number must
be balanced against your full recovery time and the change rate for data.
Consider a more frequent backup set for large file systems.
2.2.23 Backup set frequency
Determine how often you will need to generate a backup set. Although a backup
set is made of client data, it is a server-initiated process that requires some
scratch tapes in the automated library or some guidelines for the operations team
to run.
2.2.24 Policy domain
Leave this field blank. During the planning phase, this is unknown. We used this
field in 1.2.1, "Server implementation checklist" on page 8, to contain the policy
domain chosen for this client. For example, if you are implementing our
configuration, the policy domains would be SERVER or WORKSTN.
For more information about policy domains see Chapter 7, "Data storage
policies" on page 269.
2.2.25 Client option set
Leave this field blank. During the planning phase, this is unknown. We used this
field in 1.2.2, "Client implementation checklist" on page 11, to contain the client
option set chosen for this client. For example, if you are implementing our
configuration, the client options set names would be AIX, WINDOWS, or
NETWARE.
Chapter 2. Implementation planning
25
Advertisement
Table of Contents
