Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Schedule\s+for\s+the\s+last\s+day\s+of\s+the\s+month\.\.\.every\s+month\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Schedule\s+for\s+the\s+last\s+day\s+of\s+the\s+month\.\.\.every\s+month\s*$/: 8 ]

Total 8 documents matching your query.

1. Schedule for the last day of the month...every month (score: 1): Author: Bill Boyer <bill.boyer AT VERIZON DOT NET>; Date: Thu, 19 Jun 2003 13:14:17 -0400; I have a client that wants to do monthly backups on the last day of the month. A co-worker did some testing and creating a schedule for say 5/31/3002 with PERU=MONTH. The June event gets scheduled fo; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-06/msg00650.html (11,720 bytes)
2. Re: Schedule for the last day of the month...every month (score: 1): Author: "Ford, Phillip" <phillip.ford AT SPCORP DOT COM>; Date: Thu, 19 Jun 2003 13:27:18 -0400; If you are doing it inside TSM I can give you an approach. I am not good with SQL so you or someone on this list could help. You could run a schedule everyday and have a select statement in it like t; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-06/msg00652.html (13,032 bytes)
3. Re: Schedule for the last day of the month...every month (score: 1): Author: Eddie Jones <Eddie_Jones AT CANADALIFEUS DOT COM>; Date: Thu, 19 Jun 2003 13:29:37 -0400; I have some of my month end archives running on the last day of the month also. I have a start date of 05/31/2003 or any previous month that contains 31 days. When a month end falls on the 30th the m; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-06/msg00653.html (12,942 bytes)
4. Re: Schedule for the last day of the month...every month (score: 1): Author: Kent Monthei <Kent.J.Monthei AT GSK DOT COM>; Date: Thu, 19 Jun 2003 13:54:05 -0400; You might be able to develop & schedule a little script which a) does a 'delete schedule' b) goes through a loop that performs a 'define schedule' for the 31st/30th/29th/28th (in that order) c) after; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-06/msg00656.html (12,628 bytes)
5. Re: Schedule for the last day of the month...every month (score: 1): Author: Curtis Stewart <curtis.stewart AT ATTBI DOT COM>; Date: Thu, 19 Jun 2003 22:10:03 -0500; We've just decided to get rid of the whole TSM scheduler for the most part and go with an external schedular for TSM backups (AutoSys). It fixes the whole "last day of the month, or quarter or whatev; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-06/msg00670.html (13,320 bytes)
6. Re: Schedule for the last day of the month...every month (score: 1): Author: "Mr. Lindsay Morris" <lmorris AT SERVERGRAPH DOT COM>; Date: Fri, 20 Jun 2003 03:24:41 -0400; Curtis, if I may ask: how can you monitor backup status (ie success or failure of all your nodes) if you use autosys? -- Mr. Lindsay Morris Lead Architect www.servergraph.com 512-482-6138 ext 105; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-06/msg00674.html (14,761 bytes)
7. Re: Schedule for the last day of the month...every month (score: 1): Author: Alex Paschal <AlexPaschal AT FREIGHTLINER DOT COM>; Date: Fri, 20 Jun 2003 09:24:59 -0700; Hi, Lindsay. I would suggest also monitoring backup status using a select statement to pull out filespaces that didn't complete backup within x amount of time, even if you use the TSM scheduler. This; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-06/msg00689.html (15,826 bytes)
8. Re: Schedule for the last day of the month...every month (score: 1): Author: "Mr. Lindsay Morris" <lmorris AT SERVERGRAPH DOT COM>; Date: Fri, 20 Jun 2003 14:53:46 -0400; Thanks, Alex - brilliant idea - and that's how Servergraph already does it. We give the TSM admins visibility into the status, checked daily, fo how old the backups are. So they need not care about s; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-06/msg00696.html (17,723 bytes)

Current List: 1 - 8
Page: [1]