• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Daily Monitoring TSM + TS3100

chafik

ADSM.ORG Member
Joined
Jul 13, 2016
Messages
21
Reaction score
0
Points
0
Hello everyone,

I'm hired in a new company, they have a lot of troubles with TSM, I'm new to TSM but I can learn.
I'm looking for a document including a daily tasks to check on backups and tapes.

Thank you
 

moon-buddy

ADSM.ORG Moderator
Joined
Aug 24, 2005
Messages
7,033
Reaction score
405
Points
0
Location
Somewhere in the US
Looks like you will have your hands (and feet) full for the next two or so months as you learn the TSM routine.

First of all, you need to know (or, find out) some (and post here if you need further help) key factors:

- TSM Server version
- Platform on which TSM Server is running on
- Is DRM in use?
- Description of the environment: do you do traditional TSM backup: node -> disk -> tape and copy to tape for DR
- How big is the environment - number of nodes? Kinds of systems backed up: Windows, *NIX, SQL, Oracle, etc?

Answers to the above can dictate how simple or elaborate the daily routine or maintenance you should be doing.

The TSM daily maintenance fundamentals always has:

- have the nodes been backed up correctly?
- did the copy from primary to copy tape pool finished without issues?
- has the TSM DB been backed up?
- has expiration ran?
- do you have enough tapes - private or scratch?
- were the copy tapes removed from the library and send to offsite?
- if DRM is in use, have you created a RPF and saved it elsewhere?
- Saved a copy of the VOLHIST and DEVCONFIG elsewhere?

As I said, these are the basics on just the TSM Server side. If you also manage the missed and failed backups on the node side, then there is a lot of other routine or fire-fighting that you need to do.

If you are really new to TSM and would be the 'man' for the job, go and attend TSM courses.

Good luck!
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

DigitalOcean $100 Credit

Support ADSM.ORG and get DigitalOcean FREE credit. DigitalOcean currently offer a $100, 60-day Free Credit for new accounts. Sign-up here:

DigitalOcean Referral Badge

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 20 18.7%
  • Keep using TSM for Spectrum Protect.

    Votes: 65 60.7%
  • Let's be formal and just say Spectrum Protect

    Votes: 13 12.1%
  • Other (please comement)

    Votes: 9 8.4%

Forum statistics

Threads
31,902
Messages
136,004
Members
21,783
Latest member
london
Top