• 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.

General explanation of database user instance?

ldmwndletsm

ADSM.ORG Member
Joined
Oct 30, 2019
Messages
165
Reaction score
1
Points
0
Can someone afford me a brief explanation of the TSM database instance? I'm completely confused about how the whole db2 creation, configuration, formatting, etc. works in conjunction with the TSM software itself.

Why does the database have to be configured separately from the install of the TSM software? Why not just make it all one install? Why not just have root own everything? Why do they break it down into this labyrinthine complexity?
 

marclant

ADSM.ORG Moderator
Joined
Jun 16, 2006
Messages
3,619
Reaction score
580
Points
0
Location
Canada
Website
www-947.ibm.com
I can`t explain all the why.

But the software install is just that, the software install.

There's a lot of thought that goes into how you setup an instance. Like putting the database on 4 or more dedicated LUNs, the active log on a dedicated LUN, the archive log on a decidated LUN, the storage pools on multiple dedicated LUNs. The install would not know this ahead of time.

As far as running the whole thing as root, a lot of entreprises and security experts frown on that. Root is for the OS, the instance owner is for the instance. Separation of duties, in small/medium businesses it's often the same person, in large organization with multiple servers, there's a team managing the OS, and another team managing Spectrum Protect. For that reason, the instance is usually owned by a dedicated user.

Since regular users can't install software and since root is not the preferred instance owner, the 2 tasks have to be separated.
 

Advertise at ADSM.ORG

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

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

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: 18 18.2%
  • Keep using TSM for Spectrum Protect.

    Votes: 61 61.6%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.1%
  • Other (please comement)

    Votes: 8 8.1%

Forum statistics

Threads
31,755
Messages
135,384
Members
21,748
Latest member
fabiont
Top