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


    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.

Move Oracle TDP client to correct domain

I have an oracle client that was wrongly configured and it has been for months before I started here.
As the client is oracle in manages its own retention via Rman (8 days) and the retain only version on TSM is set to 90
It is easy enough to change the domain of the client to the correct domain which is set correctly for an oracle client.


the data associated with this client is around 14TB and it would take me a couple of days to move it using move nodedata and by the time I had moved it the client would have deleted a couple of days anyway and in 8 days all the original data will have gone

I'm not sure which is the best way to go about this, if the clients domain changes does it lose access to the data in the other domain, am I better leaving the data in the wrong domain and will the client have access to delete it as normal?
If I need a restore from the older data could I change the domain back to the old domain, do the restore then flip it back or will the data in the new domain be disassociated from the client?
Could tdpoconf be used to sync up the backups?


ADSM.ORG Moderator
When you change a node to a different domain, there is no data movement. Data remains exactly where it is, the node still owns it and more importantly, can still restore it.

All data previously backed up will use the retention in the management classes in the new domain if management classes with the same name exist. If some of the management classes don't exist, the objects bound to those will use the data retention from the default management class.

New backups will go in the destination of the management class in the new domain.

So, it's essentially just one command and you are done, nothing else needed.

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

    Votes: 59 60.8%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.4%
  • Other (please comement)

    Votes: 8 8.2%

Forum statistics

Latest member