Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*TDP\s+Domino\s+and\s+transaction\s+logs\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*TDP\s+Domino\s+and\s+transaction\s+logs\s*$/: 7 ]

Total 7 documents matching your query.

1. TDP Domino and transaction logs (score: 1): Author: Bill Boyer <bill.boyer AT VERIZON DOT NET>; Date: Wed, 23 Jul 2003 17:49:06 -0400; Domino 5 on Windows2k TDP for Mail V515 - Domino TSM Client 5.1.6.0 TSM Server 5.1.7.1 on AIX 5.1 Client is running transaction logging for all databases. The backup schedule is: Sunday - Full backup; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-07/msg00666.html (11,655 bytes)
2. Re: TDP Domino and transaction logs (score: 1): Author: Del Hoobler <hoobler AT US.IBM DOT COM>; Date: Wed, 23 Jul 2003 20:59:55 -0400; Bill, How about using the INCLUDE statement to bind the log backups to a management class with different policies? For example: INCLUDE S*.TXN MGMT_CLASS_7_DAYS where MGMT_CLASS_7_DAYS has settings o; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-07/msg00667.html (12,036 bytes)
3. Re: TDP Domino and transaction logs (score: 1): Author: Bill Boyer <bill.boyer AT VERIZON DOT NET>; Date: Thu, 24 Jul 2003 08:35:12 -0400; But I thought that the logs were uniquely named and wouldn't go away until you did an INACTIVATELOGS command?? And if my oldest backup is 35-days then the INACTIVATELOGS would only remove the logs th; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-07/msg00680.html (12,752 bytes)
4. Re: TDP Domino and transaction logs (score: 1): Author: Bill Boyer <bill.boyer AT VERIZON DOT NET>; Date: Thu, 24 Jul 2003 09:18:09 -0400; They haze just lifted with the 2nd cup of coffee.... When the INACTIVATELOGS runs, all it does is "expire" the active versions and then they're retained by the VERD/RETO parameters. So if, as Del sug; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-07/msg00683.html (14,185 bytes)
5. Re: TDP Domino and transaction logs (score: 1): Author: Del Hoobler <hoobler AT US.IBM DOT COM>; Date: Thu, 24 Jul 2003 09:34:59 -0400; Bill, The logs are uniquely named based on the log name and logger id. You are correct, they won't be "inactivated" (forced inactive) until you run the INACTIVATELOGS command. When you run the INACTI; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-07/msg00684.html (11,841 bytes)
6. Re: TDP Domino and transaction logs (score: 1): Author: Kent Monthei <Kent.J.Monthei AT GSK DOT COM>; Date: Thu, 24 Jul 2003 12:51:40 -0400; Won't running INACTIVATELOGS immediately after a full backup potentially break PIT restores from the prior full backups? To preserve PIT restore capability, it seems to me INACTIVATELOGS should be sc; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-07/msg00697.html (12,672 bytes)
7. Re: TDP Domino and transaction logs (score: 1): Author: Del Hoobler <hoobler AT US.IBM DOT COM>; Date: Thu, 24 Jul 2003 14:16:53 -0400; Kent, The normal procedure is to run the INACTIVATELOGS command after a full backup so that only the logs necessary to restore the active full backups, remain active. It will only "break" the PIT res; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-07/msg00702.html (12,301 bytes)

Current List: 1 - 7
Page: [1]