HP XP P9000 Command View Advanced Edition Software - Manual (Page 365)

23 Managing application replicas
This chapter describes how to manage application replicas using Replication Manager.
About application replicas
An application replica is a snapshot of an application server that is saved to a series of secondary
volumes on an immediate or scheduled basis. As with copy pair management, the creation and
management of application replicas is organized around tasks and storage assets. Replication Manager
is used to create, manage, and (manually) restore replicas.
Related topics
• Creating an application replica , page 386
• Adding an instance of Application Agent , page 58
Managing generations (replica rotation)
Application Agent can manage multiple secondary volumes for a single primary volume. In these
cases, the secondary volumes are referred to as generations (or generational backups).
Normally, Replication Manager automatically determines which secondary volumes to use for the
backup destinations. In this way, the volumes where replicas are stored are automatically rotated in
the same way that backup tapes are created and later re-used. This (default) behavior is determined
by the Target Generation option located on the 2. Setup Options page of the Create Replica Wizard.
When selecting a secondary volume for a backup, you can either manually select the volume you
want or use the default. To have Replication Manager choose a secondary volume for you, you need
to use the volume copy function. When manually selecting a volume, choose the generation name
unique to the desired volume. Replication Manager creates generation names using the following
format:
local_MU# or remote_MU#
Each element used to create a unique generation name is described below:
Specify this when the secondary volume will be stored on the same storage system as the primary
volume.
local
Specify this when the secondary volume will be stored on a different storage system than the
primary volume.
remote
The MU number defined in the P9000 RAID Manager configuration definition file ( horcmn.conf ). MU#
When you back up data to a Continuous Access secondary volume (on a remote site), the assigned
generation name is
remote_0 .
As shown in Figure 12 , because there is a limit of three generations, the fourth generation must write
over one of the preexisting volumes. In this case, the oldest volume (generation 1) is overwritten.
Generations 5 and 6 follow the same pattern of overwriting the oldest, existing generation.
User Guide 365