The number of required Tivoli® Storage FlashCopy® Manager backup
servers is determined by the number of servers that are used to access
backup images. The number of clone servers is determined by the number
of servers where you want to store a cloned database of the production
database. A clone server can also be used as a backup server.
For example, to access backup images on either site of a disaster
recovery environment, at least two backup servers are needed. A backup
server can also simultaneously be used for multiple applications and
multiple production servers.
Tivoli Storage FlashCopy Manager can
mount a backup image on a backup server. For the following scenarios,
at least one backup server is required or if FlashCopy cloning is used, a clone server
is required.
- Mount backup images on another server.
- When Tivoli Storage FlashCopy Manager is
used with other products for example, IBM® Tivoli Storage Manager for Enterprise
Resource Planning to
offload backups to Tivoli Storage Manager.
- When Tivoli Storage FlashCopy Manager requires
a mount operation, during a backup operation because the following
conditions exist:
- The database is running in an LVM mirrored environment on AIX®
- FlashCopy cloning
is used
- Conditions that require a so called Tivoli Storage FlashCopy Manager forced
mount operation for the different storage subsystem environments:
- SAN Volume Controller, Storwize® V7000, and IBM System Storage® DS8000®
- A forced mount is required if the option PREASSIGNED_VOLUMES is
set for the profile parameter BACKUP_HOST_NAME and
the operating system is Linux or
Solaris.
- IBM System Storage DS8000
- A forced mount is required if the option PREASSIGNED_VOLUMES is
set for the profile parameter BACKUP_HOST_NAME.
In addition, the following conditions must also exist a freeze and
thaw action was not used for the file systems and the operating system
is AIX or HP-UX.
For a physically partitioned DB2® database,
multiple backup servers can be used. The physical partitioning of
the production server is not required to be identical to the physical
partitioning of the backup server. However, the number of DB2 partitions
and the DB2 partition numbers must be identical on the production
and backup server.