Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
DB size?
- Thread starter ajordan
- Start date
tdparchitect
Technical User
The IBM Tivoli Storage Manager database size is based upon how many files are
managed with IBM Tivoli Storage Manager, and whether the files are in a primary
storage pool or a copy storage pool. The database holds two types of data:
entries for backups and entries for archives. The database also holds items such
as entries for image backups, server scripts and the volume history, but typically,
these are insignificant in sizing the database.
Backup sizing calculates the size of the IBM Tivoli Storage Manager database
holding backup entries. Archive sizing calculates the size of the IBM Tivoli
Storage Manager database holding archive entries. Use either or both depending
on the data you will be storing in IBM Tivoli Storage Manager. If both are used,
then add the calculated database sizes together to arrive at the total database
size. If you are planning to use backup sets, remember that these are not tracked
in the IBM Tivoli Storage Manager database, so they do not impact our
calculation. They do affect the tape library size if the media used is retained
online. Image backups are entered in the database, although only one entry for
each backup is required. The database space requirements for image backup
entries will therefore be small compared to the backups and archives, and we will
not include this in our calculation.
Our calculations are based on the following assumptions: each backed up or
archived file version uses 600 bytes of space in the server database. If offsite
copies are used as well, this takes an extra 200 bytes of space. Where we did not
know the number of files to be kept, but only the total storage, we estimated 5%
of the total server storage requirement for onsite copies and 1% for offsite.
managed with IBM Tivoli Storage Manager, and whether the files are in a primary
storage pool or a copy storage pool. The database holds two types of data:
entries for backups and entries for archives. The database also holds items such
as entries for image backups, server scripts and the volume history, but typically,
these are insignificant in sizing the database.
Backup sizing calculates the size of the IBM Tivoli Storage Manager database
holding backup entries. Archive sizing calculates the size of the IBM Tivoli
Storage Manager database holding archive entries. Use either or both depending
on the data you will be storing in IBM Tivoli Storage Manager. If both are used,
then add the calculated database sizes together to arrive at the total database
size. If you are planning to use backup sets, remember that these are not tracked
in the IBM Tivoli Storage Manager database, so they do not impact our
calculation. They do affect the tape library size if the media used is retained
online. Image backups are entered in the database, although only one entry for
each backup is required. The database space requirements for image backup
entries will therefore be small compared to the backups and archives, and we will
not include this in our calculation.
Our calculations are based on the following assumptions: each backed up or
archived file version uses 600 bytes of space in the server database. If offsite
copies are used as well, this takes an extra 200 bytes of space. Where we did not
know the number of files to be kept, but only the total storage, we estimated 5%
of the total server storage requirement for onsite copies and 1% for offsite.
- Status
Similar threads
- Locked
- Question