Example
Windows: C:\tmp, 32, 1024; D:\tmp\tmp_1, 10, 1024
UNIX: /tmp, 10, 1024; /var/tmp, 5, 60
When the files in the first directory are full, the integration writes data to the files
in the next specified directory. If the allocated disk space is used up during the
backup, the backup fails.
File history swap files can increase in size significantly. Use the following formula
to calculate approximate disk consumption:
EstConsumption = (NumOfFiles + NumOfDirs) x (136 +
AverageFileNameSize)
where NumOfFiles is the number of backed up files and NumOfDirs is the
number of backed up directories.
See the calculations in
directories is up to 10% of the total number of files, the average directory name
length is 25 characters, and the average file name length is 10 characters.
Table 27 Approximate disk consumption by file history swap files
Number of backed up files and
directories
5 Millions
10 Millions
20 Millions
Media management
Data Protector media management is limited because data is backed up by NDMP
Server in its specific data format.
Data Protector supports the following media management functionalities:
•
Import and export of media.
•
Media scan.
•
Media initialization.
•
Dirty drive detection.
Data Protector does not support the following media management functionalities:
192
Integrating NDMP Server and Data Protector
Table 27
on page 192 that presume that the number of
Approximate disk consumption by file
history swap files
0.7 GB
1.4 GB
2.8 GB
Need help?
Do you have a question about the Data Protector A.06.11 and is the answer not in the manual?
Questions and answers