How does changing the pool or policydomain affect future backups?

[ldmwndletsm]

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]

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.

 

[ldmwndletsm]

Okay, that settles that then. Thanks a bunch.