Справочник Пользователя для HP (Hewlett-Packard) B6960-96035
•
Growth of your backup environment The number of systems being backed up in
the cell influences the IDB growth. Plan for the growth of your backup environment.
the cell influences the IDB growth. Plan for the growth of your backup environment.
•
Character encoding used for your filenames (applicable for UNIX only) Depending
on the filename encoding, a character in the filename can take up from one to
three bytes in the IDB. Shift-JIS encoded filenames, for example, take up to three
bytes in the IDB, while pure ASCII filenames take up only one byte. The character
encoding is relevant for growth of filename part of IDB on UNIX (on Windows,
all characters take up two bytes in the IDB).
on the filename encoding, a character in the filename can take up from one to
three bytes in the IDB. Shift-JIS encoded filenames, for example, take up to three
bytes in the IDB, while pure ASCII filenames take up only one byte. The character
encoding is relevant for growth of filename part of IDB on UNIX (on Windows,
all characters take up two bytes in the IDB).
•
Number of object copies and object mirrors The more object copies and object
mirrors you create, the more information is stored in the IDB. For object copies
and object mirrors, the IDB stores the same information as for backed up objects,
except for filenames.
mirrors you create, the more information is stored in the IDB. For object copies
and object mirrors, the IDB stores the same information as for backed up objects,
except for filenames.
IDB growth and performance: key tunable parameters
The logging level and catalog protection are the main factors of the IDB growth and
performance. Their impact on the IDB depends on the settings you use. For a graphic
representation of the impact of different logging level and catalog protection settings,
see
performance. Their impact on the IDB depends on the settings you use. For a graphic
representation of the impact of different logging level and catalog protection settings,
see
The Data Protector internal database
198