Missed Backup’s:
a) If the Client machine or client server is down then the backup may get missed.
Sol: In that case we need to check whether there is communication between TSM server and client machine (or) node by using ping command if there is no communication we need to inform to windows team.
b) If the client scheduler goes down. Then also Backup may get missed.
Sol: In that case we need to refresh the client scheduler services by going to Services.msc if it is windows machine.
c) If the node password got expired then backup may get missed.
Sol: In that case we need to update the node password in the TSM Server using update command. (or) if we set the password expiration period =0 then the password never expires. Once we update the password then initially we need to login to DSMC command prompt using new password and from next time onwards TSM Server may login directly using password access generate file stored in its OS.
d) If there is any network connectivity problem between TSM server and Client machine then also backup may get failed.
Sol: In such case we need to check the communication between TSM Server and Client machine using Q sess (or) Ping command. If there is no communication then we need to contact network team for resolving the issue.
REASONS FOR BACKUP FAILURES
e) If there are no sufficient scratch tapes available in the tape library.
Sol: In that case we need to load (or) check-in new scratch tapes into the tape library (or) we can also get avail of scratch tapes if we run expire inventory process and reclamation process on primary and copy tapes.
f) If there is any problem regarding VSS (In Windows Machine) in that case backup may get failed due to errors in VSS writers.
Sol: in such case we need to contact windows team and inform them regarding VSS errors and ask them to resolve the issue.
g) If there is no sufficient space for Primary disk storage pool (or) TSM DB (or) Recovery Log then the Backup may get failed.
Sol: In there is no sufficient space in Primary disk storage pool then we need to manually start migration to get free space in the Primary disk storage pool.
If there is no sufficient space in the TSM DB then we need to add one more volume to the TSM DB.
If there is no sufficient space in the Recovery Log then we need to add one more volume to the Recovery log
h) In Lanfree backup if there are no tape drives available for tape mounting then also backup may get failed.
Sol: In such case either we need to wait till the tape drives are available for tape mounting for backup (or) we need to check the process which is using the tape drives and cancel any of the process based on the priority and then carry on the backup.
I) Backup may get failed due to file I/O errors i.e., if any file is having any read (or) write errors then the TSM Server cannot backup that file then backup may get failed.
Sol: to resolve file I/O issues we have to run the below command
Chkdsk drivename
We will not be running this command just we need to inform the O.S team regarding the issue and they will take care of the issue and let us know once troubleshooting was done.
VOLUME SHADOW COPY
1) Volume shadow copy service is in windows O.S and it helps the TSM Server to take the backup of the drives online i.e., TSM can take the backup the disk though if it is being used by any other application.
2) It also helps in taking the system state backup i.e., it can also take the backup of the services running under the O.S which helps us to restore total system when required.
MIGRATION FAILURES
1) If there are no available scratch tapes within the tape library then the migration fails.
2) If there are no tape drives available for the tape mount then migration may get failed.
3) If the tape library reaches it max scratch limit then the migration may get failed.
RECLAMATION FAILURES
1) If the tapes are not within the tape library then the reclamation process may get failed.
2) If the library slots in the tape library gets full then we will be ejecting some tapes from tape library and store them in the on-site itself. Then tape goes to unavailable state.
3) If we try to run the reclamation for those tapes (or) volumes in that case TSM Server tries to access those tapes and as TSM Server is unable to access those tapes then those tapes goes to unavailable state.
4) If any of the tape label is unable to read then that tape also goes to unavailable state.
HARDWARE ISSUES
1) DRIVE HARDWARE ISSUES
a) Sometimes tapes may get struck in the Tape drives in that case we need to login to the tape library using its I.P address and once we login into the GUI Console of Library then on the left side we can see the option drive summary once we click on the option we can see the total available drives in the Library and once we click on the drive which is struck and select move option. We can either move the tape to the available slot in the library (or) to the Library I/O station.
b) Sometimes we can eject the tapes by using Library GUI console also in that case we will ask the on-site media management team to eject the tape manually. If they are also not able to eject the tape then we will log a call with IBM technical engineer and they will resolve the issue and eject the tape and check if drive is corrupted and if it is corrupted they will replace the corrupted drive with new one.
c) Default username and password of Library GUI is “admin and Secure” respectively.
2) LIBRARY HARDWARE ISSUES
a) Sometimes tapes may get struck in the grippers of the library. In that case we need to login to the GUI console of the library and on the left hand side we can see the option accessor and once we expand that option we can find the option grippers and there we can see the total grippers available in the Library and also we can see which gripper got struck.
b) Then we can ask the on-site media management team to remove the struck tape from the gripper. Once the tape is removed most of the times gripper will work normally but if does not works then we need to log a call with IBM engineer and they will replace the damaged gripper with new one.
a) If the Client machine or client server is down then the backup may get missed.
Sol: In that case we need to check whether there is communication between TSM server and client machine (or) node by using ping command if there is no communication we need to inform to windows team.
b) If the client scheduler goes down. Then also Backup may get missed.
Sol: In that case we need to refresh the client scheduler services by going to Services.msc if it is windows machine.
c) If the node password got expired then backup may get missed.
Sol: In that case we need to update the node password in the TSM Server using update command. (or) if we set the password expiration period =0 then the password never expires. Once we update the password then initially we need to login to DSMC command prompt using new password and from next time onwards TSM Server may login directly using password access generate file stored in its OS.
d) If there is any network connectivity problem between TSM server and Client machine then also backup may get failed.
Sol: In such case we need to check the communication between TSM Server and Client machine using Q sess (or) Ping command. If there is no communication then we need to contact network team for resolving the issue.
REASONS FOR BACKUP FAILURES
e) If there are no sufficient scratch tapes available in the tape library.
Sol: In that case we need to load (or) check-in new scratch tapes into the tape library (or) we can also get avail of scratch tapes if we run expire inventory process and reclamation process on primary and copy tapes.
f) If there is any problem regarding VSS (In Windows Machine) in that case backup may get failed due to errors in VSS writers.
Sol: in such case we need to contact windows team and inform them regarding VSS errors and ask them to resolve the issue.
g) If there is no sufficient space for Primary disk storage pool (or) TSM DB (or) Recovery Log then the Backup may get failed.
Sol: In there is no sufficient space in Primary disk storage pool then we need to manually start migration to get free space in the Primary disk storage pool.
If there is no sufficient space in the TSM DB then we need to add one more volume to the TSM DB.
If there is no sufficient space in the Recovery Log then we need to add one more volume to the Recovery log
h) In Lanfree backup if there are no tape drives available for tape mounting then also backup may get failed.
Sol: In such case either we need to wait till the tape drives are available for tape mounting for backup (or) we need to check the process which is using the tape drives and cancel any of the process based on the priority and then carry on the backup.
I) Backup may get failed due to file I/O errors i.e., if any file is having any read (or) write errors then the TSM Server cannot backup that file then backup may get failed.
Sol: to resolve file I/O issues we have to run the below command
Chkdsk drivename
We will not be running this command just we need to inform the O.S team regarding the issue and they will take care of the issue and let us know once troubleshooting was done.
VOLUME SHADOW COPY
1) Volume shadow copy service is in windows O.S and it helps the TSM Server to take the backup of the drives online i.e., TSM can take the backup the disk though if it is being used by any other application.
2) It also helps in taking the system state backup i.e., it can also take the backup of the services running under the O.S which helps us to restore total system when required.
MIGRATION FAILURES
1) If there are no available scratch tapes within the tape library then the migration fails.
2) If there are no tape drives available for the tape mount then migration may get failed.
3) If the tape library reaches it max scratch limit then the migration may get failed.
RECLAMATION FAILURES
1) If the tapes are not within the tape library then the reclamation process may get failed.
2) If the library slots in the tape library gets full then we will be ejecting some tapes from tape library and store them in the on-site itself. Then tape goes to unavailable state.
3) If we try to run the reclamation for those tapes (or) volumes in that case TSM Server tries to access those tapes and as TSM Server is unable to access those tapes then those tapes goes to unavailable state.
4) If any of the tape label is unable to read then that tape also goes to unavailable state.
HARDWARE ISSUES
1) DRIVE HARDWARE ISSUES
a) Sometimes tapes may get struck in the Tape drives in that case we need to login to the tape library using its I.P address and once we login into the GUI Console of Library then on the left side we can see the option drive summary once we click on the option we can see the total available drives in the Library and once we click on the drive which is struck and select move option. We can either move the tape to the available slot in the library (or) to the Library I/O station.
b) Sometimes we can eject the tapes by using Library GUI console also in that case we will ask the on-site media management team to eject the tape manually. If they are also not able to eject the tape then we will log a call with IBM technical engineer and they will resolve the issue and eject the tape and check if drive is corrupted and if it is corrupted they will replace the corrupted drive with new one.
c) Default username and password of Library GUI is “admin and Secure” respectively.
2) LIBRARY HARDWARE ISSUES
a) Sometimes tapes may get struck in the grippers of the library. In that case we need to login to the GUI console of the library and on the left hand side we can see the option accessor and once we expand that option we can find the option grippers and there we can see the total grippers available in the Library and also we can see which gripper got struck.
b) Then we can ask the on-site media management team to remove the struck tape from the gripper. Once the tape is removed most of the times gripper will work normally but if does not works then we need to log a call with IBM engineer and they will replace the damaged gripper with new one.