For the month end backups, you will have to specify a different TSM node
different management class.
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 11/03/2004
> That means,
> If DBIID changes, it will not be treated as a new
> database?????????????????? and
> older backups will be there as inactive? Great !!!
> That means, if i have to keep compaction running every week, and i
> am keeping my
> backups for say 12 versions then i would set:
> Version exists = 12
> Then i say that Backup retention (Grace period) is 90 days, that would
> that i am keeping my backups for 3 months and then deleting entirely
> tapes too.
> What if I have to take month end backups, 24 versions exists? and I will
> keeping those selctive backups in separate policy domain with separate
> retention period = 730 days that is for 2 year..
> Please correct me if i m wrong !!!!!!!!
> Kind Regards,
> Eduardo Esteban wrote:
> > Some answers to your questions:
> > 1. After you run compact, the incremental will do a full backup of all
> > your
> > logged databases. If you run the inactivatelog command afterwards,
> > all the transaction logs required to recover those databases will
> > be inactivated. Your management policy will determine the fate of
> > those logs. If you don't run compact, make sure to run selective,
> > that the inactivatelog command can inactivate logs.
> > 2. Version changes still apply after DBIID changes. The incremental
> > will mark the previous backup as inactive and your management
> > policy will determine how many and for how long these will be
> > 3. The Domino server knows which log extents have been backed
> > up and it reuses them. When the Domino server start it creates
> > a formatted set of log extent files (.TXN). When the server uses
> > all of them, it either creates a new one ,if none of the log
> > have been archived, or reuses the oldest log extents by renaming
> > the file to the next log extent number.
> > Eduardo
> > "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 11/03/2004
> > 09:52:09 AM:
> > > Dear All,
> > > Sorry to popup again with a new thing .. as i went through the
> > > documentation and
> > > list archive, and web searches.. i could not find what i was looking
> > for.
> > > My Lotus is on windows 2000 and i am using selective backups
> > for
> > > entire database (70GB).
> > > What I am going to do:
> > > 1- Taking incremental daily.
> > > 2- Doing archivelog daily.
> > > 3- Doing inactivate log daily.
> > > 4- Doing compaction of all the database on Sunday morning. (Space
> > > constraint on
> > > hard disk)
> > > 5- Doing incremental backups and archivelog there after till next
> > sunday.
> > > 6- I don't think i need to take selective backups monthly or weekly
> > > or whatever.
> > > What is my problem that i foresee:
> > > 1- If i am going to run compaction every sunday, i end up with so
> > > many databses
> > > with different DBIIDs all with their respective transaction logs.
> > > 2- If I want to delete backups taken 3 months ago, how do I do that?
> > Since no
> > > version policy applies here after DBIID changes.
> > > 3- If Transaction Logs deletion.
> > > ---- As I was going through the list archive, I fond somewhere
> > ...
> > > TDP forLotus tells lotus server that certain archive logs have been
> > > backedup, so
> > > lotus can delete or whatever those transaction log file.
> > > ?????? here is it right, if yes then how does that delete those
> > > transaction log files? ??????
> > > ????? if it is not right, then how do i go about deleting
> > > archivelogs that have been backedup??? (definitely i m not running
> > circular
> > > logging).
> > >
> > > OR OR OR OR
> > > What strategy should I follow????
> > > Please enlighten me in this !!!!!!!!!!!!!!!!!!!!!!!!!!!!
> > darknesssssssssss
> > > !!!!!!!!!!!!!!
> > > Kind Regards,
> > > Sandra