Based on your description, I gather you are running the B/A Client on (for
example) Nodename in Domain1 backing up to ManageClass, and the TDP client
on Nodename_Dom in Domain2 to backing up to ManageClass_Dom, and backing up
all .nsf and .txn via the B/A client on Nodename. You now want to stop
backing up the .nsf and .txn files via the B/A client.
Adding Exclude \...\*.nsf and exclude \...\*.txn (or something similar) to
your B/A client will "inactivate" all of the "active" backups for those
files (just as if it was deleted from the client). Retention rules should
then follow ManageClass in Domain1, and those last active versions
inactivated by the exclude will be deleted from the storage pools in TSM in
"Retain Only" days after the next full INCRemental via the B/A client.
If you have tested your TDP backups and restores, and don't change anything
in the TDP dsm.opt to affect these files, TDP backups will not be impacted
by this.
I don't see why you would want to keep those .nsf or .txn files backed up
by the B/A client. Once your TDP retention policies have taken over, those
B/A client versions of the files are trash, really. You essentially have
dual backups going with the B/A client and the TDP client backing up the
same databases.
Hope that helps.
Todd
|--------+------------------------>
| | Shannon Bach |
| | <SBach AT MGE DOT COM|
| | > |
| | Sent by: |
| | "ADSM: Dist |
| | Stor Manager" |
| | <ADSM-L AT VM DOT MAR|
| | IST.EDU> |
| | |
| | |
| | 05/23/2003 |
| | 11:49 AM |
| | Please respond|
| | to "ADSM: Dist|
| | Stor Manager" |
| | |
|--------+------------------------>
>--------------------------------------------------------------------------------------------------------------------------|
|
|
| To: ADSM-L AT VM.MARIST DOT EDU
|
| cc:
|
| Fax to:
|
| Subject: After Domino TDP install
|
>--------------------------------------------------------------------------------------------------------------------------|
We have been running both ITSM Backup Client (NOTES) and the ITSM Domino
TDP Client (NOTES) for a week (separate nodes, Policy Domains etc..) and
testing the restores. I am now ready to start excluding the Notes
databases, templates and transaction log files from the regular TSM Backup
client as the TDP now does all that. After looking through all the TDP
manuals and Redbooks, I cannot find an answer to this question;
When I put in the excludes, what does the TSM Server think has happened to
these files? If it thinks they are deleted from the client, that would be
very, very bad for us. I need the data to stay binded to the Management
class it is currently backed up under. If the TSM Server does not think
the data was deleted off the Client, does the last backed up file (but now
excluded) stay active?
Thanks,
Shannon
Shannon
Madison Gas & Electric Co.
e-mail sbach AT mge DOT com
|
