It is automated process of taking backup of the client data. And we can also run the TSM Admin jobs automatically. We have to run the client jobs and admin jobs regularly if we have to run the jobs manually it will be a hectic schedule for administrators because we may have thousands of nodes or clients which have to be backed up. So we will create a schedule in the TSM Server which will run all the Client jobs and Admin jobs automatically according to the schedule describes in the TSM Server. There are two types of schedules in TSM Server they are:
1) CLIENT SCHEDULE:
In client schedule we will be scheduling backup and archive jobs to the client machine. All the schedules which are defined in TSM Server which has to be run on Client machine are called as client Schedules. We can define backup and archive schedules under client schedules.
Parameters under Client Scheduling:
a) START DATE:
This parameter specifies from which day the schedule has to begin.
b) START TIME:
This parameter specifies at what time of the day the schedule has to be run or executed.
c) DURATION:
In some cases TSM Server cannot communicate with the client machine due to some reasons like client server may be down or client may be under maintenance and so on in such case for how much time TSM Server has to try to communicate with Client machine to run the pre defined schedule.
d) DURATION UNITS:
This Parameter defines the duration. Like hours /days/ weeks/ months. But in real time duration unit’s parameter will be in hours only. For example if we mention duration=1 and duration units=hours the TSM server will try to communicate with the client for 1 hour from the schedule time to run the schedule and if in the specified time TSM Server cannot communicate with client then the Schedule will be missed.
e) PERIOD:
This Parameter specifies how frequent the schedule has to be run. Period is mentioned in Number.
f) PERIOD UNITS:
This Parameter Specifies or defines the Period. Means days/weeks/months/years.
g) SCHEDULE STYLE:
There are two types of schedule styles in TSM they are
1) Classic
2) Enhanced
Default schedule style of TSM server is Classic. In real- time also we will configure schedule under Classic style only.
h) SCHEDULE MODES:
There are two types of schedule Modes in TSM Server.
1) CLIENT POOLING:
In this mode client machine will regularly contacts TSM Server and asks the TSM Server whether there is any schedule to be run on the client machine at that particular time. And if the TSM Server specifies that there is no schedule at that point of time the n the client goes to sleep mode and again after some time client again contacts the TSM Server regarding the schedule.
Client continuously contacts the TSM Server until it gets the Schedule time and the schedule is run. And this process goes on.
For configuring client pooling mode we have to modify the client configuration file i.e., dsm.opt file like this
Enter the below command in dsm.opt file to configure client pooling mode:
“Query schedule 1”
“1” parameter specifies that client will contact TSM Server for every one hour regarding the schedule.
2) SERVER PROMPTED:
In this mode TSM Server itself contacts the node or client machine regarding the schedule and specifies the client that there is a schedule to be run on the client machine at that particular time and the schedule gets initiated.
Main advantage of Server prompted mode is there will be no network traffic as the backup is being initiated by server. To configure schedule mode as server prompted then we have to mention the below command in client configuration file i.e., dsm.opt file.
“Schedmode prompted”
2) ADMIN SCHEDULE:
This admin schedule parameter defines the schedule which has to be defined in TSM Server and run on TSM Server. To maintain the TSM Server clean. This jobs or schedules are also known as TSM admin/ Maintenance/housekeeping jobs.
There are different types of Admin jobs they are:
a) STORAGE POOL BACKUP:
In this job we will take the backup of the actual data stored in primary tape storage pools to copy storage tapes. These copy tapes are then moved to DR site and preserve these tapes for DR purpose. i.e., if incase any disaster happens and total primary tape storage pool is crashed and all the tapes are lost then we can maintain the client machines or recover the client machine to system state by using these copy storage tapes.
Backup stg tapestoragepoolname copystoragepoolname maxpr=number
b) TSM DB BACKUP:
When the client backup job was run or executed all the metadata of the backed up data will be stored in TSM DB and in case if we want to restore any of the data back to client machine in that case TSM DB plays the main role .If TSM DB is crashed we cannot then it is waste of having the actual data without metadata. So for that purpose we will take backup of TSM DB and store them also in DR site for future purpose in case of Disaster.
Whenever we take the TSM DB backup we always use scratch or new tapes for TSM DB backup.
Backup db devc=devcname type=full scratch=yes/no
c) EXPIRE INVENTORY PROCESS:
This process helps the TSM Server to delete all the expired files from the TSM Server. Only when we run this expire inventory then only all the expired files will be deleted from the TSM server.
“Expire inventory” duration=60
d) MIGRATION:
Initially when the backup was executed on TSM Server the actual data is transferred to primary disk storage pool. If once the disk storage pool is full then the data from disk storage pool is migrated to tape storage pool. If we have to manually run this job daily it will be a hectic task for admin so we will schedule this job for migration.
Migrate stg stgpoolname low=20%
e) RECLAMATION:
It is process of moving the unexpired data from a fragmented tapes to filling tapes or scratch tapes and making the fragmented tapes to scratch tapes. If we perform this operation on onsite tapes that process is known as on-site reclamation.
If we perform the same process for off-site tapes that process is known as off-site reclamation.
1) ONSITE RECLAMATION:
It is process of moving the unexpired data from a fragmented tapes to filling tapes or scratch tapes and making the fragmented tapes to scratch tapes. If we perform this operation on onsite tapes that process is known as on-site reclamation.
Some tapes which are filled totally and once some data in such tapes is deleted i.e., only the metadata of the data is deleted from the TSM DB but the actual data will not be deleted. But the information in the tapes shows that the tapes capacity as 60% but when we check the tapes in the tape library they show as full tapes. And that space cannot be reused directly because tapes can only be used to write the data from beginning to end only but the data cannot be written in between of the tapes. So to use the space we have to run the reclamation. Once the reclamation process in run in the TSM server then the tapes in which the data is less than 40% the data in those tapes will be moved to scratch tapes or filling tapes and then we have to format the fragmented tapes and load them in the tape library.
If we perform the same process for off-site tapes that process is known as off-site reclamation.
Reclaim stg tapestoragepoolname threshold=%
2) OFF SITE- RECLAMATION:
It is process of moving the unexpired data from a fragmented tapes to filling tapes or scratch tapes and making the fragmented tapes to scratch tapes. If we perform this operation on off-site tapes that process is known as off-site reclamation.
Some tapes which are filled totally and once some data in such tapes is deleted i.e., only the metadata of the data is deleted from the TSM DB but the actual data will not be deleted. But the information of tapes in TSM DB shows that the tapes capacity as 60% but when we check the tapes in the tape library they show as full tapes. And that space cannot be reused directly because tapes can only be used to write the data from beginning to end only but the data cannot be written in between of the tapes. So to use the space we have to run the reclamation. Once the reclamation process in run in the TSM server then the tapes in which the data is less than 40%. Then we have to check the tapes on on-site which the data of off-site tape on which reclamation has to be run. Once we find the tapes we have to transfer the active or unexpired data to new or filling copy tapes and the copy tapes are moved to DR site. Then the offsite tape on which reclamation was run was called back to on-site. Once the tapes are back to onsite we have to format those tapes and load them to tape library as scratch tapes.
Reclaim stg copystoragepoolname threshold=%
1) CLIENT SCHEDULE:
In client schedule we will be scheduling backup and archive jobs to the client machine. All the schedules which are defined in TSM Server which has to be run on Client machine are called as client Schedules. We can define backup and archive schedules under client schedules.
Parameters under Client Scheduling:
a) START DATE:
This parameter specifies from which day the schedule has to begin.
b) START TIME:
This parameter specifies at what time of the day the schedule has to be run or executed.
c) DURATION:
In some cases TSM Server cannot communicate with the client machine due to some reasons like client server may be down or client may be under maintenance and so on in such case for how much time TSM Server has to try to communicate with Client machine to run the pre defined schedule.
d) DURATION UNITS:
This Parameter defines the duration. Like hours /days/ weeks/ months. But in real time duration unit’s parameter will be in hours only. For example if we mention duration=1 and duration units=hours the TSM server will try to communicate with the client for 1 hour from the schedule time to run the schedule and if in the specified time TSM Server cannot communicate with client then the Schedule will be missed.
e) PERIOD:
This Parameter specifies how frequent the schedule has to be run. Period is mentioned in Number.
f) PERIOD UNITS:
This Parameter Specifies or defines the Period. Means days/weeks/months/years.
g) SCHEDULE STYLE:
There are two types of schedule styles in TSM they are
1) Classic
2) Enhanced
Default schedule style of TSM server is Classic. In real- time also we will configure schedule under Classic style only.
h) SCHEDULE MODES:
There are two types of schedule Modes in TSM Server.
1) CLIENT POOLING:
In this mode client machine will regularly contacts TSM Server and asks the TSM Server whether there is any schedule to be run on the client machine at that particular time. And if the TSM Server specifies that there is no schedule at that point of time the n the client goes to sleep mode and again after some time client again contacts the TSM Server regarding the schedule.
Client continuously contacts the TSM Server until it gets the Schedule time and the schedule is run. And this process goes on.
For configuring client pooling mode we have to modify the client configuration file i.e., dsm.opt file like this
Enter the below command in dsm.opt file to configure client pooling mode:
“Query schedule 1”
“1” parameter specifies that client will contact TSM Server for every one hour regarding the schedule.
2) SERVER PROMPTED:
In this mode TSM Server itself contacts the node or client machine regarding the schedule and specifies the client that there is a schedule to be run on the client machine at that particular time and the schedule gets initiated.
Main advantage of Server prompted mode is there will be no network traffic as the backup is being initiated by server. To configure schedule mode as server prompted then we have to mention the below command in client configuration file i.e., dsm.opt file.
“Schedmode prompted”
2) ADMIN SCHEDULE:
This admin schedule parameter defines the schedule which has to be defined in TSM Server and run on TSM Server. To maintain the TSM Server clean. This jobs or schedules are also known as TSM admin/ Maintenance/housekeeping jobs.
There are different types of Admin jobs they are:
a) STORAGE POOL BACKUP:
In this job we will take the backup of the actual data stored in primary tape storage pools to copy storage tapes. These copy tapes are then moved to DR site and preserve these tapes for DR purpose. i.e., if incase any disaster happens and total primary tape storage pool is crashed and all the tapes are lost then we can maintain the client machines or recover the client machine to system state by using these copy storage tapes.
Backup stg tapestoragepoolname copystoragepoolname maxpr=number
b) TSM DB BACKUP:
When the client backup job was run or executed all the metadata of the backed up data will be stored in TSM DB and in case if we want to restore any of the data back to client machine in that case TSM DB plays the main role .If TSM DB is crashed we cannot then it is waste of having the actual data without metadata. So for that purpose we will take backup of TSM DB and store them also in DR site for future purpose in case of Disaster.
Whenever we take the TSM DB backup we always use scratch or new tapes for TSM DB backup.
Backup db devc=devcname type=full scratch=yes/no
c) EXPIRE INVENTORY PROCESS:
This process helps the TSM Server to delete all the expired files from the TSM Server. Only when we run this expire inventory then only all the expired files will be deleted from the TSM server.
“Expire inventory” duration=60
d) MIGRATION:
Initially when the backup was executed on TSM Server the actual data is transferred to primary disk storage pool. If once the disk storage pool is full then the data from disk storage pool is migrated to tape storage pool. If we have to manually run this job daily it will be a hectic task for admin so we will schedule this job for migration.
Migrate stg stgpoolname low=20%
e) RECLAMATION:
It is process of moving the unexpired data from a fragmented tapes to filling tapes or scratch tapes and making the fragmented tapes to scratch tapes. If we perform this operation on onsite tapes that process is known as on-site reclamation.
If we perform the same process for off-site tapes that process is known as off-site reclamation.
1) ONSITE RECLAMATION:
It is process of moving the unexpired data from a fragmented tapes to filling tapes or scratch tapes and making the fragmented tapes to scratch tapes. If we perform this operation on onsite tapes that process is known as on-site reclamation.
Some tapes which are filled totally and once some data in such tapes is deleted i.e., only the metadata of the data is deleted from the TSM DB but the actual data will not be deleted. But the information in the tapes shows that the tapes capacity as 60% but when we check the tapes in the tape library they show as full tapes. And that space cannot be reused directly because tapes can only be used to write the data from beginning to end only but the data cannot be written in between of the tapes. So to use the space we have to run the reclamation. Once the reclamation process in run in the TSM server then the tapes in which the data is less than 40% the data in those tapes will be moved to scratch tapes or filling tapes and then we have to format the fragmented tapes and load them in the tape library.
If we perform the same process for off-site tapes that process is known as off-site reclamation.
Reclaim stg tapestoragepoolname threshold=%
2) OFF SITE- RECLAMATION:
It is process of moving the unexpired data from a fragmented tapes to filling tapes or scratch tapes and making the fragmented tapes to scratch tapes. If we perform this operation on off-site tapes that process is known as off-site reclamation.
Some tapes which are filled totally and once some data in such tapes is deleted i.e., only the metadata of the data is deleted from the TSM DB but the actual data will not be deleted. But the information of tapes in TSM DB shows that the tapes capacity as 60% but when we check the tapes in the tape library they show as full tapes. And that space cannot be reused directly because tapes can only be used to write the data from beginning to end only but the data cannot be written in between of the tapes. So to use the space we have to run the reclamation. Once the reclamation process in run in the TSM server then the tapes in which the data is less than 40%. Then we have to check the tapes on on-site which the data of off-site tape on which reclamation has to be run. Once we find the tapes we have to transfer the active or unexpired data to new or filling copy tapes and the copy tapes are moved to DR site. Then the offsite tape on which reclamation was run was called back to on-site. Once the tapes are back to onsite we have to format those tapes and load them to tape library as scratch tapes.
Reclaim stg copystoragepoolname threshold=%