The block size for the DB varies depending on the tablespace, most are 16K, but a few are 32K. There should be a ratio of one database directory, array, or LUN for each inventory expiration process.
TSM AUTO QUEUE ARCHIVE
Avoid the slower internal disks included by default in most AIX servers, and avoid consumer grade PATA/SATA disks.įor most disk systems, performance is best if one database directory is on one LUN, which has one logical volume.Īs mentioned above, define more directory containers if you use deduplication, as the database will be queried more to find the various deduplicated extents.ĭo not mix Databse containers with active logs, archive logs, or system files such as page or swap space. Use fast, low latency disks for the Database, use SSD if you can afford it. Don't mix spinning disk and Flash storage. Place the directories on disks that have the same capacity and I/O characteristics. If possible, place each database directory in a different file system, then you will get parallelism when DB2 stripes the database data over the directories. The directories must all be the same size, one to remember if you do add more later. The way your database directories are spread over your disk storage will also affect performance. However, extending the database is a resource intensive task, so it is best to plan your configuration for future growth and including extra containers at the start. IBM recommends that you make your initial database size at least 25GB, spread over at least 4 directories, and if your SP server is large, say 2 TB with deduplication, then use at least 8 containers.
TSM AUTO QUEUE FREE
LOCATION TOTAL SIZE OF SPACE USED FREE SPACE The Q DBSPACE output below shows a 400GB database striped over 4 containers.
The data is striped evenly across the directories and the containers do not require an initial format before they can be used. The database can exist in up to 128 directories or 'containers' to use the correct DB2 term.
To get a list of table names, run the following command :ĭb2 "select tabname from syscat.tables where tabschema='TSMDB1' and type='V'" For example, to get a list of indexes that used by the BACKUP_OBJECTS table, run the following command :ĭb2 "select indname from syscat.indexes where indschema='TSMDB1' and tabname='BACKUP_OBJECTS'" To get a list of indexes that are used by a specific table, use the tabname parameter to identify the table name. For example to get the list of all table indexes that are used by the Tivoli Storage Manager server, run the following command :ĭb2 "select indname from syscat.indexes where indschema='TSMDB1'" In a UNIX or Linux environment, the process is:įrom a shell, run the following commands :Īfter you connect to the database, you can run DB2 select commands. This opens a new command window with the DB2 environment set up.įrom this new window, run the following commands :
TSM AUTO QUEUE WINDOWS
To do this in a Windows environment, follow this procedure: The database also uses relational indices, so it does not require special index tables to speed up SQL queries.Īs the database is DB2, it is possible to connect to it directly, outside of Spectrum Protect and run query commands.
This is a DB2 feature that optimises storage paths through the database to improve performance. The database will also run automatic 'runstats' from time to time. The database uses DB2 relational consistency rules to prevent incorrect data from entering, and is self auditing. A Spectrum Protect 'instance' is everything required to run an Spectrum Protect server, including database, logs, storage pools etc.
One thing to note is that you cannot have any other DB2 applications running on the same server as the one hosting your Spectrum Protect database, though you can have multiple Spectrum Protect instances on one host server. This means that it does not need database audits and will automatically re-organise itself if required. IBM Spectrum Protect uses a DB2 relational database. This information has been moved to a separate page as while TSM 5.x is way out of support, some sites still use it.
0 kommentar(er)
