
To prevent Data Protector processes from exceeding system capabilities, the maximum
number of concurrent backup sessions is limited. The limit is configurable.
Figure 64
on page 223 shows multiple sessions running concurrently.
Figure 64 Backup session information flow - multiple sessions
Pre-exec and post-exec commands
Data Protector pre-exec commands enable you to execute some actions before a
backup or a restore session. Data Protector post-exec commands enable you to
execute some actions after a backup or a restore session. A typical pre-exec action
would be to shut down a database to put data in a consistent state.
The pre-exec and post-exec commands can be set for a backup specification and,
as such, executed on the Cell Manager system, or they can be specified as a backup
object option and thus executed on the client system where the respective Disk Agent
is running.
Pre-exec and post-exec script commands can be written as executables or shell scripts.
These are not supplied by Data Protector and must be written separately by, for
example, the backup operator.
Concepts guide
223
Summary of Contents for B6960-96035
Page 17: ...Overview of backup and automated media copy sessions 340 105 Concepts guide 17 ...
Page 20: ...20 ...
Page 22: ...Publication history 22 ...
Page 132: ...Planning your backup strategy 132 ...
Page 182: ...Media management and devices 182 ...
Page 186: ...Users and user groups 186 ...
Page 204: ...The Data Protector internal database 204 ...
Page 218: ...Figure 62 Direct SIP integration example Service management 218 ...
Page 242: ...Integration with database applications 242 ...
Page 264: ...Synthetic backup 264 ...
Page 274: ...Split mirror concepts 274 ...
Page 288: ...Snapshot concepts 288 ...
Page 344: ...Further information 344 ...
Page 402: ...Glossary 402 ...