Opt, changing the values for archlogdirectory and archfailoverlogdir to your new paths. Start the tsm server up again and the directory structure will be automatically generated in the new empty filesystem. There is no need to copy the archive logs over from the original location, because your full backup emptied them out. If you want to prove to yourself that this worked, then a 'query log fd' command should show the new locations. If you really need to, or even just want to, it is possible to update db2 directly to change the log location. You should really ask your ibm support rep for advice before you start, but an outline process would go like. Backup your database (full devconfig and volhistory files.
Database mirroring on sql server Express
Your next option is to check to see if your logs are mirrored, and if so then tell tsm about to use the mirror copy. From an os command line issue the command below and check the output dsmserv display logv this will tell you if the logs are mirrored if the command shows more than one copy for the log files. If they are mirrored, then add the option mirrorread log verify in the dsmserv. Opt file, and that will force the tsm server to sync from the other copy. Opt already contains a mirrorread line then comment it out to make sure that your option is used. If the tsm server starts ok, then it has fixed the issue by copying the uncorrupted data over from the copy log, and all is well. If this fails, then you will probably have to restore your database to the latest backup, but you might want to contact ibm for further advice first. You may want to change the location of the achive logs, maybe because you have added a bigger file system and this is usually quite easy. Take a full database backup, not just because that is the starting point for any change, but also because a full backup of the tsm database will clear the archive logs down. Halt the tsm server Edit the dsmserv.
Run the db2 command get db cfg for tsmdb1 and check the output, which should have the default values set like this. Number of database backups to retain (NUM_DB_backups) 1 Recovery history retention (days) (REC_HIS_retentn) 0 Auto deletion of recovery objects (auto_DEL_REC_OBJ) on once the number of backups specified by the num_DB_backups is reached, the old backups are marked as expired and will be deleted by the. The auto_DEL_REC_obj parameter specifies whether the database log files, backup images, and load copy images associated with those backups should be deleted at the same time. These parameters cannot be changed from within tsm by a tsm administrator and should not be changed from the db2 command line, but left at the default values. If you get a logread388 error, then the tsm server will crash. This error happens when a recovery log volume becomes corrupted. If this happens to you, your first option should be to check your operating system error logs. If they indicate that a file system has corruption errors or disk errors, get your system administrator to check out the operating system and see if the error can be fixed there.
A pinned backup can result in the active log becoming full. It is possible to resume automatically identify and terminate any hung or long-running client sessions by using the throughputdatathreshold and throughputtimethreshold options. These are specified in the dsmserv. Opt file and are used by the server to monitor the status of each client session. If after the amount of time specified by throughputtimethreshold, the average throughput is less than the value specified by the throughputdatathreshold parameter, then the session will be cancelled by the server. You code these parameters in dsmserv. Opt like this: throughputtimethreshold 100 throughputdatathreshold 60 offer This means that if a session is not achieving an average throughput of at least 60KB per second after running for 100 minutes, the server will cancel this client session. These values are for illustration purposes, you need to pick the values that work best for your site. The archive logs should be automatically deleted after a full database backup completes, but in some cases this might not happen and then the archive logs will continue to grow until the filespace is full.
The logmode is equivalent to legacy roll-forward. In DB2 terms, these are archive logs, not circular logs. This means that the log files can fill up, so log file management is still required. You can specify a failover log for the Archive log to help prevent this, but the Active log cannot failover and the size is fixed between 2gb and 512gb, so don't allocate all the space that you have available for the Active log, keep some. It is highly recommended that failoverArchivelog space be set aside for possible emergency use. You can use slower disks for failoverArchivelog space. Prevention is better than cure, and the active log can become pinned by client sessions that are either hung or running very slowly.
Private tutor Resume samples
It also gives you detailed deduplication information like chunk count and average chunk size. Back to top Recovery log sizing and tuning tsm has three recovery logs. The Active log contains updates that have not been committed to disk yet and is used for roll-forward or roll-back in case of problems. Once a transaction is committed, the data is moved to the archive log. The default size for the Active log is 2gb and the size can be increased by increments of 512MB right up to 128GB.
The word Archive log contains committed transaction data and is used for pit recovery of the database. The Archive log is cleared out by a full database backup. However it retains all data updates applied right back to the second last backup, so you need to size your archive log with that in mind. The failover Archive log tsm collectively calls these three logs the 'recovery log but a db2 dba would just call them 'transaction logs'. The log files form part of the tsm database, and unlike the legacy tsm database there is no need to create and format log volumes.
There is no exact formula for working out that database increase, but it is possible to estimate the database size impact. Deduplication data is stored in 'chunks' of variable size, but the average size is about 100k. Each chunk uses about 490 bytes in the database, and then another 190 bytes if it is copied to a copy storage pool. Compare that with the normal overhead of 200 bytes needed to store metadata for every copy of every file backed. If you want to know how many files are stored on your tsm server, use the following select command select sum(cast(num_files as bigint) from occupancy where node_name is not null and filespace_id is not null.
So it would appear reasonably easy to estimate your database size, all you need to know is backup file count and the number of bytes in your storage pools. However it is not quite as easy as this, as the first set of chunks that are created are called 'base chunks' and they are not automatically expired when that file is deleted, as other files may be linked to them. Worst case, and very unlikely, is that this effect could double the chunk count. A starting point is to estimate your database size without deduplication, and to do this you use the formula db_size file_count * number_of_backup_copies * 200 Now to estimate the database size with deduplicaton, considering an enterprise that is managing 20tb of data, with the primary. Estimated of chunks created 200,000,000 (20,000,000,000,000 / 100,000) Database cost for storing chunks in primary pool 98,000,000,000 (200,000,000 x 490) Database cost for storing chunks in copy pool 38 gb (200,000,000 x 190) Initial estimated database cost for deduplication 136 gb add in the. Ibm provides a pearl script that provides details on how your database handles deduplication content, once you have been running dedup for a while. Search the ibm site for tsm_dedup_ and you should find. It gives you information like database size broken down by rows in the large tables, the number of client nodes registered, by storage pool, the percentage of pool deduplicated and how many bytes deduplication is saving in each pool.
How to perform database restore with Database Encryption
When all tablespaces have done the rebalance, execute the following commands to reduce the same list of tablespaces : db2 alter tablespace tablename reduce max. After the rebalance/reduce, the file systems should be equally utilized and none should be full. The maximum database size for tsm.3 and tsm.1 is 4tb, and 2TB for tsm.2. The db2 database is largely self tuning, so there is no requirement for DB2 tuning skills. A new parameter, dbmempercent, replaces the old buffpoolsize. This set of buffers contains much more data than the old buffer so the recommendation is to set its size to unlimited. In fact, tsm/DB2 will try to change it to unlimited on startup. The deduplication effect on Database size. Deduplication reduces write the amount of storage space used for backups, engelsk but this comes at the cost of increased database space as tsm must track the metadata needed to reconstitute deduplicated data.
Location total size of space used free space. File system(MB) (MB) available (MB) /tsm/tivoli/dbdir001 102,144 6,919.22 98,224 /tsm/tivoli/dbdir002 102,144 6,919.22 98,224 /tsm/tivoli/dbdir003 102,144 6,919.22 98,224, when a tsm database is initially created on multiple file systems, that database will be spread equally over all the file systems. However if you add an extra file system to the database space using the 'extend dbs' command, db2 will not rebalance the database to spread the data equally. This means that if some of the original file spaces were 100 full, they will still be 100 full after the new filespace is added and this could cause the tsm to stop. If you are running tsm server.2 or above you can rebalance the database dynamically using DB2 commands. I suggest that you look up the ibm story technote about this, and also contact ibm for advice before trying this. However in outline the process goes like this: At a quiet time, log into the db2 command line with the db2 administrator userid and run these commands db2 connect to tsmdb1 db2 set schema tsmdb1 db2 alter tablespace tablename rebalance, the tables that ibm mention. It can take about 30 minutes to rebalance a large tablespace.
commands : db2 connect to tsmdb1 db2 set schema tsmdb1. After you connect to the database, you can run DB2 select commands. For example to get the list of all table indexes that are used by the tivoli Storage manager server, run the following command : db2 "select indname from dexes where indschema'tsmdb1. 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 a list of indexes that used by the backup_objects table, run the following command : db2 "select indname from dexes where indschema'tsmdb1' and tabname'backup_objects. To get a list of table names, run the following command : db2 "select tabname from syscat. Tables where tabschema'tsmdb1' and type'v back to top, database sizing and tuning, the database can exist in up to 128 directories or 'containers' to use the correct DB2 term. The data is striped evenly across the directories and the containers do not require an initial format before they can be used. The q dbspace output below shows a database striped over 3 containers.
A tsm 'instance' is everything required to run a tsm server, including house database, logs, storage pools etc. The database uses DB2 relational consistency rules to prevent incorrect data from entering, and is self auditing. The database will also run automatic 'runstats' from time to time. This is a db2 feature that optimises storage paths through the database to improve performance. The database also uses relational indices, so it does not require special index tables to speed up sql queries. As the database is DB2, it is possible to connect to it directly, outside of tsm and run query commands. To do this in a windows environment, follow this procedure: Open a windows command prompt. Run the db2cmd command. This opens a new command window with the db2 environment set.
Importing Data into a mysql, dB Instance - amazon
Tsm database version.1 and later. Tsm database version.5 and earlier. This information has been moved to a separate page as tsm.x is proposal now out of support. Tsm.x, basic database structure, tSM now uses a db2 relational database. This means it can be much bigger than the old legacy database, does not need database audits and will automatically re-organise itself if required. Software database mirroring is no longer supported. One thing to note is that you cannot have any other DB2 applications running on the same server as the one hosting your tsm database, though you can have multiple tsm instances on one host server.