Hi Josef,
this is the policy setting:
Policy Domain Name NT_NOTES
Policy Set Name ACTIVE
Mgmt Class Name MC_NT_NOTES
Copy Group Name STANDARD
Versions Data Exists 5
Versions Data Deleted 1
Retain Extra Versions 30
Retain Only Version 60
Copy Mode MODIFIED
Copy Serialization SHRDYNAMIC
Copy Frequency 0
In my opionion the last backuped file should go away at the 60th day after
beeing deleted at Domino Server. But it does not ,... .
Have you got an idea ?
Thank you !
--
Holger Bitterlich
Holger Bitterlich
Stadtsparkasse Köln
Organisation und Datenverarbeitung
Telefon: (0221) 226 - 54 18
Fax: (0221) 226- 51 00
mailto:Holger.Bitterlich AT sk-koeln DOT de
http://www.sk-koeln.de
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> schrieb am 11.07.2002
11:53:59:
> Hi Holger
> what is your policy settings for data from Domino server (copy group
> setting from management class under which is Domino data backuped)?
>
>
> Ing. Jozef Zatko
> Login a.s.
> Dlha 2, Stupava
> tel.: (421) (2) 60252618
>
>
>
>
> Holger Bitterlich <holger.bitterlich AT SK-KOELN DOT DE>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 11.07.2002 09:15
> Please respond to "ADSM: Dist Stor Manager"
>
>
> To: ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject: Domino TDP leaves old databases, second try
>
>
> I need your help! I posted the following, but Michael was the only one
> with
> ideas. But unfortunately that was no solution to my problem. So, has
> anybody an idea?
>
> Here `s the full story:
>
> Hi *sm`ers
> >
> > the amount of data pertaining our Lotus Domino Servers is enlarging
> > enormous. The domino guys tell me that they can restore very old
> databases
> > although the domino db`s are deleted a long time ago. When we try to
> > restore such an old database which on the domino server has been
deleted
> a
> > long time ago, we still see the last version of this db. How can this
> > happen ?
> > Since we backup the transaction logs every hour there is a second
> problem.
> > The transaction log backups are retained - no deletion happened !
> > Why is no Log inactivated ?
> >
> > We use TSM 3.7.3 on server side, and tsm 4.1.16 with TDP for Domino
> 1.1.2
> > on Client side.
> >
> > Our translog backup script looks like this:
> >
> > set domlogdir=c:\ssw\tivoli\tsm\log\online_nt_dom_tlog.log
> > domdsmc arch /logfile=%domlogdir%
> > domdsmc inactivate /logfile=%domlogdir%
> >
> >
> > The log output is:
> >
> > Total Domino transaction log files ready for archive: 4
> > Total Domino transaction log files archived: 4
> > Throughput rate: 5,193.11 Kb/Sec
> > Total bytes transferred: 268,439,552
> > Elapsed processing time: 50.48 Secs
> > Tivoli Storage Manager
> > Tivoli Data Protection for Lotus Domino - Version 1, Release 1, Level
> 2.0
> > (C) Copyright IBM Corporation 1999, 2001. All rights reserved.
> > License file exists and contains valid license data.
> > ACD5221I The C:\ssw\Tivoli\TSM\domino\domdsm.log log file has been
> pruned
> > successfully.
> > Number of Logs Inactivated: 0
> >
> >
> > The weekly online backup script is like that:
> >
> > set logdir=c:\ssw\tivoli\tsm\log\domdsm.log
> > domdsmc selective * /subdir=yes /logfile=%domlogdir% >> %logdir%
> > domdsmc inactivate /logfile=%domlogdir% >> %logdir%
> >
> >
> > and the output reads like this:
> >
> > Total Domino databases inspected: 4,433
> > Total Domino databases backed up: 4,433
> > Total Domino databases excluded: 0
> > Throughput rate: 4,820.92 Kb/Sec
> > Total bytes transferred: 99,557,318,730
> > Elapsed processing time: 20,167.09 Secs
> > Tivoli Storage Manager
> > Tivoli Data Protection for Lotus Domino - Version 1, Release 1, Level
> 2.0
> > (C) Copyright IBM Corporation 1999, 2001. All rights reserved.
> > License file exists and contains valid license data.
> > ACD5221I The c:\ssw\tivoli\tsm\log\domdsm.log log file has been pruned
> > successfully.
> > Number of Logs Inactivated: 0
> >
> >
> >
> > Thank you !
>
>
--------------------------------------------------------------------------------
---------
> ----
> ----
>
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> schrieb am 09.07.2002
> 15:50:45:
>
> > Hi Holger,
> > with TDP for Lotus Domino every database is treated as if it was one
> filespace.
> > On your TSM Server you can see this using "q files
> > <nodename>".
> >
> > Like with the ba-client TSM updates the filespace when you perform an
> > incremental backup and otherwise leaves the filespace as it
> > is. So when you stop backing up a certain filespace (=domino database),
> this
> > filespaces active files (documents) will stay unchanged
> > in TSM forever.
> >
> > When you want to discontinue backing up a database and you don't want
to
> keep
> > this db in TSM, just delete it using "delete files
> > <nodename> <filespacename>" in the admin interface (dsmadmc).
> >
> > Good luck,
> > regards,
> > Michael
> > --
> > Michael Bartl, Dipl. Inform. (FH) mailto:michael.bartl AT cw DOT
> > com
> > Backup Services, IT Ops Germany/Austria Tel: +49-89-92699-806
> > Cable & Wireless Deutschland GmbH. Fax: +49-89-92699-302
> > Landsberger Str. 155, D-80687 Muenchen http://www.cw.com/de
> >
>
>
-----------------------------------------------------------------------------
------
>
>
> Hi Michael,
>
> when we do a 'q files nodename' the result looks like This:
>
> Node Name Filespace Platform
> Filespace Capacity Pct
> Name
> Type (MB) Util
> ------------------------------ -----------
--------
> --------- -------- -----
> --------- -------- -----
> XXXXX_LN \\YYYYY\d$ WinNT NTFS
> 138,927. 73.60
> XXXXX_LN \\YYYYY\c$ WinNT NTFS
> 4,044.1 55.1
> XXXXX_LN ZZZZZ4.DOMLOGS WinNT
> API:DominoData 0.0 0.0
> XXXXX_LN ZZZZZ4.DOMDBS WinNT
> API:DominoData 0.0 0.0
>
> So it looks like all databases together are treated as one filespace. Is
> this a bug, misconfiguration or is it normal?
>
> Greetings
> Gisbert Schneider
>
> --
> Holger Bitterlich
> Stadtsparkasse Köln
> Organisation und Datenverarbeitung
> Telefon: (0221) 226 - 54 18
> Fax: (0221) 226- 51 00
> mailto:Holger.Bitterlich AT sk-koeln DOT de
> http://www.sk-koeln.de
> Da E-Mails leicht unter fremdem Namen erstellt oder manipuliert werden
> koennen, muessen wir zu Ihrem und unserem Schutz die rechtliche
> Verbindlichkeit der vorstehenden Erklaerungen ausschliessen. Die fuer die
> Stadtsparkasse Koeln geltenden Regeln ueber die Verbindlichkeit von
> rechtsgeschaeftlichen Erklaerungen mit verpflichtendem Inhalt bleiben
> unberuehrt.
>
>
Da E-Mails leicht unter fremdem Namen erstellt oder manipuliert werden
koennen, muessen wir zu Ihrem und unserem Schutz die rechtliche
Verbindlichkeit der vorstehenden Erklaerungen ausschliessen. Die fuer die
Stadtsparkasse Koeln geltenden Regeln ueber die Verbindlichkeit von
rechtsgeschaeftlichen Erklaerungen mit verpflichtendem Inhalt bleiben
unberuehrt.
|
