HP Data Protector Operations Guide

mv /var/opt/omni/server/db40
/var/opt/omni/server/db40.save
mv <restore_location>/db40
/var/opt/omni/server/db40
7. The restore process also restored the configuration files into the same location as the database
files. You may want to move them into place as well if they need to be recovered. Note: this
step may be optional, if the files are intact. For Windows Cell Managers, use the windows
explorer. For Unix use the following commands:
mv /etc/opt/omni/server
/etc/opt/omni/server/omni.bkup
mv <restore_location>/omni/server
/etc/opt/omni/server
8. Start the Data Protector Servers using the newly recovered database.
omnisv -start
9. Verify that the database and all of the configurations are operational.
omnidbcheck …
Data Protector cell and client tuning
global variables
Global options affect the entire Data Protector cell and cover various aspects of Data Protector,
such as timeouts and limits. All global options are described in the global options file, which you
can edit to customize Data Protector.
Global options are read at the start of each backup session. Editing the global options file does
not require restarting the Data Protector services.
The global options file is located on the Cell Manager:
• UNIX systems: /
etc/opt/omni/server/options/global
• Windows Server 2008:
Data_Protector_program_data>\Config\Server\Options\global
• Other Windows systems:
<Data_Protector_home>\Config\Server\Options\global
To set global options, edit the global file. Uncomment the line of the desired option by removing
the “#” mark, and set the desired value.
Most users should be able to operate Data Protector without changing the global options.
The following list includes the most often used global variables. See the global options file for a
complete description:
Global variable Description
MediaView
Changes the fields and their order in the Media Management context.
MaxBSessions
Changes the default limit of five concurrent backups.
InitOnLoosePolicy
Enables Data Protector to automatically initialize blank or unknown
media if the loose media policy is used.
MaxMAperSM
Changes the default limit of concurrent devices per backup session
(maximum device concurrency is 32).
DCDirAllocation
Determines the algorithm used for selecting the dcbf directory for a
new detail catalog binary file: fill in sequence (default), balance size,
or balance number.
DailyMaintenanceTime
Determines the time after which the daily maintenance tasks can begin.
Default: 12:00 (noon).
DailyCheckTime
Determines the time after which the daily check can begin. Default:
12:30 pm. You can also disable the daily check.
43 | Page