HP B6960-96035 - Manual (Page 230)

What is an object copy session?
An object copy session is a process that creates an additional copy of the backed
up data on a different media set. During an object copy session, the selected backed
up objects are copied from the source to the target media.
Automated and interactive object copy sessions
Automated object copy session
An automated object copy session can either be scheduled or started immediately
after a backup. A scheduled object copy session is started at the time you have
specified using the Data Protector Scheduler. A post-backup object copy session is
started after the specified session finishes. You can view the progress of the automated
object copy session in the Data Protector monitor.
Interactive object copy session
An interactive object copy session is started from the Data Protector user interface
directly. The Data Protector monitor starts immediately and you can view the progress
of the session. Multiple users can monitor the same object copy session. You may
want to stop monitoring by disconnecting the user interface from the session. The
session will then continue in the background.
Object copy session data flow and processes
What happens in an object copy session?
The information flow of an object copy session is shown in Figure 67 on page 232.
When an object copy session is started, the following happens:
1. The Copy and Consolidation Session Manager (CSM) process is started on the
Cell Manager system. This process reads the object copy specification for
information on what to copy and which options, media, and devices to use. It
also controls the object copy session.
2. The CSM opens the IDB, reads the information about the media needed for
copying, and writes the information about the object copy session, such as
generated messages, to the IDB.
3. The CSM locks the devices. The session is queued until all read Media Agents
and the minimum required write Media Agents are locked, with the same timeout
as for backup. If the resources are still unavailable after the timeout, the session
is aborted.
How Data Protector operates 230