Precautions on restoration, Precautions when executing commands simultaneously – HP Serveur lame HP ProLiant BL465c Gen8 User Manual
Page 229
Precautions on restoration
•
Make sure that the pair statuses of the copy group to be restored are
PSUS
(for primary volume)
and
SSUS
(for secondary volume).
•
Do not use the
drmresync
command while the
drmmediabackup
command is backing up data
from tape to the secondary volume, while the
drmmediarestore
command is restoring data
from the secondary volume to tape, or while the
drmmount
command is mounting the secondary
volume.
•
The following points should be considered regarding restoration when performing a configuration
change by adding a volume mounted in an arbitrary directory on a drive.
If a configuration change is made to mount a volume under
M:
, at
M:\mnt
, the
drmfsrestore
command is allowed to restore the backup information before the configuration change (back up
only the volume mounted at
M:
). At this time, if restoration is executed with it mounted at
M:\mnt
,
the information mounted at
M:\mnt
on the volume with
M:
as the mount point directory might be
overwritten and the
M:\mnt
mount released.
Be careful when restoring the backup information before the volume configuration change or when
performing a restoration by specifying a portion of the mount points in the
-target
option of the
drmfsrestore
command.
•
When you are restoring a backup obtained using NetBackup from a tape device, the Application
Agent restore command will result in an error if there are differences in the mount point specification
between the backup and the restoration, as shown below:
Backup:
Make the backup from the secondary volume of the directory mount point specification.
Restore:
Specify immediately under the drive letter as the mount point, and then perform the restoration.
For the restore processing to succeed, you must change the restore target to the directory mount
point specification. To prevent this problem from occurring, specify immediately below the drive
letter as the mount point, and then making the backup.
Note the following when using Fast Snap or Snapshot to perform restore operations:
•
Consider the free capacity of the data pool. Periodically check the free capacity of the data pool
and increase the capacity if necessary. For details about how to configure a data pool, see the
Fast Snap or Snapshot documentation.
•
For details about how to restore data from a tape to a primary volume in a Fast Snap or Snapshot
configuration, see
•
When restoration is executed in a Quick Restore environment, the volume maps on the primary
volume and secondary volume are swapped. Therefore, if performance of the disks used for the
primary volume and secondary volume are different, performance for the primary volume will
change and restoration might cause deterioration in performance. In such a case, performance
can be restored when restoration is performed again. For details on Quick Restore, see the
manual for Business Copy .
Precautions when executing commands simultaneously
While a command is executing, if a user attempts to execute another command that cannot be executed
concurrently with the executing command, the system will attempt to execute the latter command
indefinitely until the former command terminates. To prevent the system from attempting to execute
such a command indefinitely (until the former command terminates), you will need to edit the
init.conf
file. For details, see “
Stopping retry operations caused by a command that cannot execute
concurrently with other commands
Application Agent CLI User Guide
229