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

Node replication and dissimilar policies

Rigido

ADSM.ORG Senior Member
Joined
Apr 21, 2006
Messages
129
Reaction score
5
Points
0
Location
Rome, Italy
Hi all,
after reading some manuals and a fast IBM presentation on TSM 7.1/8 new features we told to a customer that "with dissimilar policies, a new feature for TSM 7.1, you can set up a primary server with a 7 days retention and the replication server with a longer retention".
The problem, and I opened a PMR with IBM, is that you can't take advantage of such configuration until you're not recovering the node (and access directly to the replication server).
IBM, after a misunderstanding with client development, told me to open a Request For Enhancement that now is in "Uncommitted Candidate" so I think it should be voted.

If you think it deserves vote, here it is the link: THANKS.
 

Rigido

ADSM.ORG Senior Member
Joined
Apr 21, 2006
Messages
129
Reaction score
5
Points
0
Location
Rome, Italy
NODE A archives data on SERVER A with a RETVER of 7 days.
SERVER A replicate node data to SERVER B, with dissimilar policies on, on SERVER B archive copygroup has RETVER of 30.
NODE A can't access to older data stored on SERVER B until you make SERVER A unavailable.

Now, no one told me if it could be safe just to change TCPSERVERADDRESS on dsm.sys to make SERVER A unreachable and try a retrieve from SERVER B, that's why I asked IBM.
 

Rigido

ADSM.ORG Senior Member
Joined
Apr 21, 2006
Messages
129
Reaction score
5
Points
0
Location
Rome, Italy
I found an old presentation from the 2015 TSM Symposium, IBM call this "Node replication with transparent client access" (even if they don't talk about dissimilar policies). I look forward for the "always on" replication too...
 

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,753
Messages
135,377
Members
21,748
Latest member
fabiont
Top