TSM COMPONENTS:
1) TSM DATABASE:
It is the main part of TSM server. It contains the information regarding Metadata of client data, Scheduling information, policy management information, client (or) Node information, Tapes or volumes information.
Maximum size of TSM DB in 5.5 version is 530 GB and in 6.0 Version is 1 TB.
Minimum size of TSM DB is 13MB.
Commands regarding TSM DB:
Q dbv f=d
Def dbv location f=capacity
Expand db capacity
Reduce db capacity
2) RECOVERY LOG:
It is a place where total log information will be stored. Whenever backup or archive is running all the metadata of client information will be moved to TSM DB and the same copy of Data will also be stored in TSM Recovery log. There are two modes of recovery log they are:
a) Normal Mode:
In normal mode while backup/archive is going on all the meta data is stored in both TSM DB and Recovery log and once the backup/archive is completed then the data in recovery log will be erased automatically.
· Main adv of normal mode is less space is utilized by recovery log.
· Main dis-adv of normal mode is we cannot recover the TSM DB to most current state in the case of TSM Server crash.
B) Roll Forward Mode:
In Roll forward Mode while backup/archive is going on all the metadata is stored in both TSM DB and Recovery log and once the transaction is completed data will not be erased in recovery log. The data in recovery log will only be erased once the data in TSM DB is backed up. Then the log data in recovery log will be erased.
· Main Adv of Roll Forward mode is we can recover the TSM DB to most current stat in the case of DR.
· Main Dis Adv of Roll forward mode is we need more space for Recovery log.
Commands for recovery Log:
Q logv f=d
Def logv location f=capacity
Expand log capacity
Reduce log capacity
Update logv mode=normal (or) rollforwardmode
3) STORAGE POOL
It is the place (or) location where actual data of client (or) customer is being stored. All the backed/archived data will be stored in storage pools. There are three different types of storage pools.
1) PRIMARY STORAGE POOL:
Again it is divided into two types:
a) PRIMARY DISK STORAGE POOL:
Initially when the client machine is backed up the metadata is moved to TSM DB and the actual data will be moved to Primary disk storage pool. It is a collection of volumes. Size of volumes will be defined by the admin.
It is also called as random access storage pool because on disk storage pool we can perform multiple operations at a time. Command to define disk storage pool.
Def stg storagepoolname deviceclassname pool f=capacity
b) PRIMARY TAPE STORAGE POOL:
Once the data in the primary disk storage pool is full and once it reaches to highest migration point then the actual data in the primary disk storage pool will be migrated to Tapes in the tape libraries.
It is also called as sequential access storage pool because we can perform only one operation at a time on tape storage pool.
Def stg storagepoolname deviceclassname pool maxscratch=number
2) COPY STORAGE POOL:
Copy storage pool is the place where the actual data of client is stored for future purpose in case of DR.
Once the data is written to Primary tape storage pool and the data from tapes and the TSM DB is backed up again to copy storage tapes and these tapes are stored @ DR site which will be useful in case of DR when all the primary tapes damaged and TSM server crash.
It is also called as sequential access storage pool because we can perform only one operation at a time on tape storage pool.
Def stg storagepoolname deviceclassname pool maxscratch=number
3) ACTIVE DATA POOL:
It is a storage pool where all the active versions of the backed up data is stored. It is useful in case of restoring of active versions of the client data.
1) TSM DATABASE:
It is the main part of TSM server. It contains the information regarding Metadata of client data, Scheduling information, policy management information, client (or) Node information, Tapes or volumes information.
Maximum size of TSM DB in 5.5 version is 530 GB and in 6.0 Version is 1 TB.
Minimum size of TSM DB is 13MB.
Commands regarding TSM DB:
Q dbv f=d
Def dbv location f=capacity
Expand db capacity
Reduce db capacity
2) RECOVERY LOG:
It is a place where total log information will be stored. Whenever backup or archive is running all the metadata of client information will be moved to TSM DB and the same copy of Data will also be stored in TSM Recovery log. There are two modes of recovery log they are:
a) Normal Mode:
In normal mode while backup/archive is going on all the meta data is stored in both TSM DB and Recovery log and once the backup/archive is completed then the data in recovery log will be erased automatically.
· Main adv of normal mode is less space is utilized by recovery log.
· Main dis-adv of normal mode is we cannot recover the TSM DB to most current state in the case of TSM Server crash.
B) Roll Forward Mode:
In Roll forward Mode while backup/archive is going on all the metadata is stored in both TSM DB and Recovery log and once the transaction is completed data will not be erased in recovery log. The data in recovery log will only be erased once the data in TSM DB is backed up. Then the log data in recovery log will be erased.
· Main Adv of Roll Forward mode is we can recover the TSM DB to most current stat in the case of DR.
· Main Dis Adv of Roll forward mode is we need more space for Recovery log.
Commands for recovery Log:
Q logv f=d
Def logv location f=capacity
Expand log capacity
Reduce log capacity
Update logv mode=normal (or) rollforwardmode
3) STORAGE POOL
It is the place (or) location where actual data of client (or) customer is being stored. All the backed/archived data will be stored in storage pools. There are three different types of storage pools.
1) PRIMARY STORAGE POOL:
Again it is divided into two types:
a) PRIMARY DISK STORAGE POOL:
Initially when the client machine is backed up the metadata is moved to TSM DB and the actual data will be moved to Primary disk storage pool. It is a collection of volumes. Size of volumes will be defined by the admin.
It is also called as random access storage pool because on disk storage pool we can perform multiple operations at a time. Command to define disk storage pool.
Def stg storagepoolname deviceclassname pool f=capacity
b) PRIMARY TAPE STORAGE POOL:
Once the data in the primary disk storage pool is full and once it reaches to highest migration point then the actual data in the primary disk storage pool will be migrated to Tapes in the tape libraries.
It is also called as sequential access storage pool because we can perform only one operation at a time on tape storage pool.
Def stg storagepoolname deviceclassname pool maxscratch=number
2) COPY STORAGE POOL:
Copy storage pool is the place where the actual data of client is stored for future purpose in case of DR.
Once the data is written to Primary tape storage pool and the data from tapes and the TSM DB is backed up again to copy storage tapes and these tapes are stored @ DR site which will be useful in case of DR when all the primary tapes damaged and TSM server crash.
It is also called as sequential access storage pool because we can perform only one operation at a time on tape storage pool.
Def stg storagepoolname deviceclassname pool maxscratch=number
3) ACTIVE DATA POOL:
It is a storage pool where all the active versions of the backed up data is stored. It is useful in case of restoring of active versions of the client data.