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

How does changing the pool or policydomain affect future backups?

ldmwndletsm

ADSM.ORG Member
#1
I may not be phrasing this correctly as I'm new to this:

If you change the pool or even policydomain that a given file (file system, directory, whatever) would normally get backed up by then does TSM run a new full and then start over again with ongoing incrementals, just like it did the first time it saw the file? Or does it instead continue along happily, writing the data to the new pool or policydomain, as if nothing changed?

So from above, if you're rebuilding a directory, and it has to go back to a tape that has the initial full (pool A or policydomain A), and then at some point during the restore it needs a tape from after the change (pool B or policydomain B) then is that going to work? Is it seamless?

What is the recommended action to take when making such changes?
 

marclant

ADSM.ORG Moderator
#2
If you change the pool or even policydomain that a given file (file system, directory, whatever) would normally get backed up by then does TSM run a new full and then start over again with ongoing incrementals, just like it did the first time it saw the file?
Changes to a storage pool don't affect backups.
Changes to a policy domain affect the retention and the destination of new backups, but if an object is previously backed up and not changed, it won't get backed up again.

So from above, if you're rebuilding a directory, and it has to go back to a tape that has the initial full (pool A or policydomain A), and then at some point during the restore it needs a tape from after the change (pool B or policydomain B) then is that going to work? Is it seamless?
The server keeps track of where each file is, it's seamless. You could have a backup that is spread in 10 storage pool across a combination of disks and multiple tapes, the restore will be seamless, the server knows where they are and will get them wherever that may be. The only time is not seamless if if some of the tapes are not in the library.
 

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

    Votes: 57 62.0%
  • Let's be formal and just say Spectrum Protect

    Votes: 10 10.9%
  • Other (please comement)

    Votes: 7 7.6%

Forum statistics

Threads
31,548
Messages
134,467
Members
21,616
Latest member
Jonasgo
Top