IBM E16RMLL-I Implementation Guide - Page 73
Database volume identification, Tivoli Storage Manager recovery log
View all IBM E16RMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 73 highlights
2.8.6 Database volume identification The total required database size including both backup and archive requirements will be 190 + 1192.32 = 1382.4 MB. We recommend using the Tivoli Storage Manager mirroring function for the database instead of a hardware or operating system mirroring, because Tivoli Storage Manager has additional functions to handle error conditions that may affect the mirrored copy. If you are using Tivoli Storage Manager mirroring, you need to plan for the mirror copy by doubling the amount of disk for the database. Various file systems have different maximum capacities, so the database may have to be split across numerous volumes to make up your database size. To ensure no single point of failure when mirroring the database, each volume in a mirrored set should be placed on a separate drive and even controller. Note: By summing up backup and archive database sizes, you will have a full, consolidated database for the calculated time frame. You can start with a smaller configuration initially but leave enough spare disk space for growth. You should round up database volume sizes to multiples of 4 MB plus 1 MB for overhead. Complete Table 2-9 with the database file names and the volume names for your primary database and copy database. This table includes the space for the backup and archive requirements. Table 2-9 Database worksheet - backup and archive requirements Database volume File name (primary) Size MB File name (copy) Vol1 /tsm/database/primary/file01 693 /tsm/database/copy/file01 Vol2 /tsm/database/primary/file02 693 /tsm/database/copy/file02 Total 1386 Total Size MB 693 693 1386 2.8.7 Tivoli Storage Manager recovery log The size of the recovery log depends on the amount of data changed between Tivoli Storage Manager database backups. The larger the amount of data, the larger the recovery log needs to be. Either a full or an incremental Tivoli Storage Manager database backup (in roll-forward mode) resets the recovery log back to empty. If the recovery log fills up completely, Tivoli Storage Manager stops and Chapter 2. Implementation planning 43