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

You can create a copy group mount definition file even if the configuration is other than the above.
If a copy group mount definition file does not exist, Application Agent determines a mount point
automatically. Once you create a copy group mount definition file, you can perform the following
operations:
• You can mount the secondary volume to a specified mount point.
• If the same number of secondary volumes were provided as the number of multiple generations,
by defining a mount point for each generation, you can omit the mount point specification when
executing the command for mounting a secondary volume.
There are two methods to make the OS recognize the secondary volume: one is to make the OS
dynamically recognize the secondary volume, and another is to make the OS statically recognize the
secondary volume.
• Method to make the OS dynamically recognize the secondary volume:
Use the
drmdevctl command to conceal the secondary volume from the OS. This enables Ap-
plication Agent to mount and unmount the target secondary volume only when performing a backup
or restore. When using any of the following configurations, make sure that you use this method.
You can use this method in other cases as well.
• There are multiple generations of a secondary volume which is a dynamic disk.
• There are multiple generations of a secondary volume in a cluster configuration that uses Mi-
crosoft Cluster Service or Windows Server Failover Clustering.
• There are multiple generations of a secondary volume, and VSS is being used.
Note
Of the physical disks connected to the device adapter port, do not use the LUN#0 disk for the
primary and secondary volumes if the secondary volume is to be recognized dynamically. If
you use the LUN#0 physical disk, the system might not be able to recognize the other physical
disks.
• Method to make the OS statically recognize the secondary volume:
Reboot the backup server to make the OS statically recognize a single generation secondary
volume. Application Agent performs backups and restorations using this secondary volume. This
method is applicable when there is a single generation of the secondary volume only.
After commencing this operation, it is necessary to delete the copy group mount definition file, and
specify the method for mounting a secondary volume after a system initial construction or volume
configuration changes.
For details on how a mount point and secondary volume (copy group) are determined when the
command for mounting a secondary volume is executed, see “
Determining a mount point and mount
target when mounting a secondary volume ” on page 176.
Making the OS dynamically recognize the secondary volume
This subsection describes the procedure for specifying how to mount a secondary volume, by using
the method of making the OS dynamically recognize the secondary volume. The following describes
cases where a copy group mount definition file is created and cases where the file is not created.
A copy group mount definition file is created in the following location:
Application-Agent-installation-destination\DRM\conf\vm\CG_MP.conf
To specify how to mount a secondary volume:
Preparation for using Application Agent 164