Joni, I am not quite sure I understand completely since for Domino, each database is contained in a single .NSF file... ...unless you are talking about groupings of Domino databases making up a logical database of some sort (like Domino.Doc)
Data Protection for Domino works at the database file level (.NSF file). You could assign a policy setting to meet the retention requirements through management classes on the backups. You would assign the management classes to those database backups by using the INCLUDE option in the DSM.OPT file (see User's Guide for details.) You may also want to look into the IBM CommonStore product that has document archive function for Domino servers. Thanks, Del ---------------------------------------------------- > I'm hoping there are some experts out here on TDP on domino servers. I am > not very familiar with the TDP portion and how it works with TSM, but here > is my question: The user's archive their databases, yet there are files > within the databases that have different retention requirements. What > would be the best way to manage this data? The easiest way would be to > archive the database under the longest retention period, but then you have > a lot of unneccessary data out on the system that, due to contracts, must > be deleted after a certain period of time. Is there any way to manage this > data properly? It was suggested by the user that they could archive the > database for one year, restore it and then choose the management class for > all of the files within the database. I think that this would be a very > big no no, but at the same time I am not sure what to tell them to do to > manage their data by their wishes. If anyone has any > suggestions/comments/practices of how to manage a similar infrastructure I > would appreciate any input. Thanks in advance!!!!!
