Backing up multiple generations – HP Serveur lame HP ProLiant BL465c Gen8 User Manual

Page 33

Advertising
background image

When selecting a secondary volume for a backup, you can either manually select the volume you
want to use or have Application Agent choose it for you. In order to have Application Agent choose
a secondary volume for you, you need to use the volume copy function. When manually selecting a
volume, specify the generation name unique to the desired volume. Application Agent creates
generation names using the following format:

local_

MU# or

remote_

MU#

Each element used to create a unique generation name is described below:

local

Specify this when the secondary volume will be stored on the same storage system as the primary
volume.

remote

Specify this when the secondary volume will be stored on a different storage system than the
primary volume.

MU#

The MU number defined in the RAID Manager configuration definition file (

horcm

n

.conf

).

When you back up data to a Continuous Access Software secondary volume (on a remote site), the
assigned generation name is

remote_0

.

The following figure shows an example of what happens when backing up multiple generations. In
this example, because a maximum of only three generations can be made, after generations 1 to 3
are created, the fourth generation (generation 4) 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.

Figure 4 Backing up multiple generations

Normally, Application Agent automatically determines which secondary volume to use for the backup
destination. However, if there are specific secondary volumes that you do not want to use for backup
purposes, you can use a Application Agent command to lock the contents of the secondary volumes.

The figure below illustrates the process of backing up multiple generations when a specific copy group
is locked. In this example, after generation 1 is obtained, the generation 1 copy group is locked in
order to prevent it from being overwritten. As a result, the remaining secondary volumes, 2 and 3,
are used as containers for any remaining generations.

Application Agent CLI User Guide

33

Advertising