Queuing of object consolidation sessions – HP B6960-96035 User Manual
Page 234
2.
The CSM opens the IDB, reads the information about the needed media, and
writes the information about the object consolidation 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.
4.
The CSM starts the Media Agents on the systems with devices that will be used
in the session. The Media Agents load the source and target media allocated
according to the backup policies.
If destination devices are not specified per object, Data Protector selects them
automatically from those you selected in the object consolidation specification
according to the following criteria in the order of priority:
• destination devices with the same block size as source devices are selected
before those with a different one
• locally attached devices are selected before network attached devices
5.
One Media Agent reads the full object version. It sends the data to another
Media Agent that reads incremental object versions. The latter Media Agent
does the actual consolidation and sends the data to the Media Agent that writes
the data to the target media.
If the full backup and the incremental backups reside in the same file library,
the same Media Agent reads all the backups and consolidates them.
If the block size of the source device is smaller than that of the destination device,
blocks are repackaged.
6.
When the object consolidation session is completed, the CSM closes the session.
How many sessions can run concurrently?
A number of object consolidation sessions can run in the cell at the same time. Object
consolidations sessions are treated like backup sessions and their number is limited
by the same factors.
Queuing of object consolidation sessions
Timeout
When an object consolidation session is started, Data Protector tries to allocate all
needed resources. The session is queued until the required minimum resources are
How Data Protector operates
234