content tables Vs occupancy tables.

2001-07-11 Thread Ofer
Hi all, I have a 100 DLT cartridges library with 35/70GB capacity each. This is like 7TB approximately data on the library if the compression utilization is like 100%( which is not the case). In addition, there are like 37 cartridges with scratch status. I would like to know how much

Re: content tables Vs occupancy tables.

2001-07-11 Thread Richard Sims
'select node_name,sum(file_size) as sum_file_size from contents group by node_name' 'select node_name,sum(PHYSICAL_MB) as sum_phys_mb from occupancy group by node_name' and I got the following result 9,030,520 MB from the contents table 2,422,690 MB from the occupancy table From the

Re: content tables Vs occupancy tables.

2001-07-11 Thread Ofer
Hi Richard. First, thanks for the quick answer :-), Thus I need to asume from my select results, that the real size of the backups in the library is taken from the occupancy table? which is a reasonable number 2.5TB, and if its the only way to know what is the real size of my library? regards

Re: content tables Vs occupancy tables.

2001-07-11 Thread Richard Sims
Thus I need to asume from my select results, that the real size of the backups in the library is taken from the occupancy table? Hi, Ofer - Yes, the Occupancy statistics reflect the real utilization of your storage pools. Also consider doing Audit Licence followed by Query

Re: content tables Vs occupancy tables.

2001-07-11 Thread Robin Sharpe
Ofer, A couple of issues here. First, and probably this is your answer, the 70GB capacity for DLT IV cartridges on DLT7000 drives is an estimate assuming 2:1 compression. The compression is done using a version of the Lempel-Ziv algorithm, like that used by PKZIP and many other software