• 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 successful but a lot of data left behind

mirrorsaw

ADSM.ORG Member
#1
We acquired an old TSM server (7.1) with lots of legacy archive data on it, I've been asked to migrate the data to our newer 8.1 server(s). I've run a node replication on each, and they've all completed with 'SUCCESS' but it's not a like-for-like copy, looking at the file numbers in Q OCC, and the total amount of data, some nodes have 95% of what they had, and some closer to just 50%.

I thought it may be the ARREPLRULEDEFAULT setting but that's on ALL_DATA, I also considered the exclusions in the option sets, but there doesn't seem to be any pattern to what was copied and what was left behind.

I'm completely out of ideas so would really appreciate any help.

Thanks
 

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

    Votes: 58 60.4%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.5%
  • Other (please comement)

    Votes: 8 8.3%

Forum statistics

Threads
31,635
Messages
134,828
Members
21,670
Latest member
crypticsh
Top