Jaiprasad, Here is what I received from the Tivoli Engineer regarding TDP interacting with Domino. In a nutshell, the Domino server will remove the log extents at normal reboot.
Title/Topic: Domino Transaction logging backups using the TDP Domino Abstract: How does Domino transaction logging backup work with TDP for Domino Content: When a "domdsmc" command is issued to backup the transaction logs on the Domino server, the TDP for Domino makes an API call to the Domino server and requests any transaction logs that are available for archive. The Domino Server provides the logs/data to the TDP which is then passed to the TSM server for storage. The TDP anticipates that Domino is passing valid data as the logs (and .nsf files) belong to the Domino server. It would not be possible for the TDP or TSM to verify the data as we would not know what should be contained in the files. It is the responsibility of the application which owns the data to pass valid information for storage. In regards to the logs on the Domino server machine, TDP never removes any log files, it only copies them (backs them up to TSM) and lets Domino know that it has successfully done so. It is the domino logger that controls deletion or reuse of extents that have been archived. The archived extents will only be deleted at normal server shutdown. However, the logger will reuse (ie. rename to the next log seq#) an archived log extent before allocating a new one. If the backup of the logs is interrupted such as a network disconnection (tcipip rc=-50, etc), then the logs will not be reported as backed up and then next time the archive log backup is run, these same logs would be backed up again. In this case, the communications problem would need to be resolved and/or run the log backup more often to try and get the log(s) backup completed successfully. Only after the log is successfully stored on the TSM server does it notify the Domino server; then the Domino server marks logs for reuse. The biggest concern for archival logging is the log partition does not become full as this will cause the Domino Server to crash. If the logs are not being reused or deleted from the Domino server, this can cause the Domino log partition to fill. If the archive log backup process is completed successfully, and the logs are not backed up a second time (so we know that they were successful), then it is an issue with the Domino log manager. TSM does not manipulate the log files as they belong to the Domino server and it is the responsibility of the Domino server to take care of them. --Kathy Pang Tivoli Storage Manager Technical Support Sr. Software Engineer Regards, Brian Scott EDS - BUR Engineering Enterprise Distributed Capabilities MS 3278 Troy, MI 48098 * phone: 248-265-4596 (8-365) * mailto:[EMAIL PROTECTED] -----Original Message----- From: Jaiprasad A Parthasarathy [mailto:[EMAIL PROTECTED]] Sent: Monday, July 29, 2002 7:57 AM To: [EMAIL PROTECTED] Subject: TSM / TDP - Domino - Archivelog *.txn files removal. Hi All, Need Clarification on Domino Achieving logs using TDP for Domino. The following is the setup: TSM Server Ver 5.1 on Windows W2K Operating System TSM client Ver 4.2 and TDP for Domino Ver 3.2 installed on Domino Server Ver 5.0.9 on Windows NT Operating System 4.0 We have a schedule to take backup of archivelog (S*.TXN) files when ever it gets qualified as we have Threshold parameters specified. and schedule runs perfectly. Question is - How do we / TDP for Domino will remove TXN files automatically? Is there any parameter to provide along with "domdsmc archivelog" to remove txn files automatically. as txn files are being created.... Requesting to share some experiences on this.. Pls. Thanking you, With Warm Regards, Jaiprasad, Certified Tivoli Consultant, Microsoft Certified Professional, Certified Unicenter Engineer, Tivoli Services (ISMS), IBM Global Services India, Subramanya Arcade, No. 12, Bannerghatta Main Road, Bangalore - 560029; Phone +91-80-2063000 Extn 3092; +91-80-2063092 (Direct) Fax : (91)-80-2063109 ; E-mail : [EMAIL PROTECTED]
