Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*scheduling\s+questions\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*scheduling\s+questions\s*$/: 7 ]

Total 7 documents matching your query.

1. scheduling questions (score: 1): Author: David Soucy <dsoucy AT DIGITAS DOT COM>; Date: Wed, 23 Feb 2005 16:31:44 -0500; Hi all. Hope you are well. I was wondering if some of you could share your scheduling strategies. For most nodes, I just use a standard daily incremental schedule. The problem is that we have to keep; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-02/msg00667.html (11,292 bytes)
2. Re: scheduling questions (score: 1): Author: "Stapleton, Mark" <mark.stapleton AT BERBEE DOT COM>; Date: Wed, 23 Feb 2005 15:49:23 -0600; Piece of cake. Use archives for your long-term backups. Create a weekly archive client schedule with a six-month retention, and a monthly archive schedule with a year's retention. You'll end up with; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-02/msg00669.html (11,831 bytes)
3. Re: scheduling questions (score: 1): Author: "Mark D. Rodriguez" <mark AT MDRCONSULT DOT COM>; Date: Thu, 24 Feb 2005 23:11:01 -0600; David, Mark's suggestions below will certainly work, but as in all things TSM there are many ways to accomplish what you need. I have a customer with a similar requirements. He needs daily incrementa; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-02/msg00721.html (14,008 bytes)
4. Re: scheduling questions (score: 1): Author: David Soucy <dsoucy AT DIGITAS DOT COM>; Date: Sun, 27 Feb 2005 20:29:02 -0500; Sounds good. I have just been getting into experimenting with image backups. My only problem is how do I schedule these so they're not a manual process? The reason I thought I might need multiple nod; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-02/msg00771.html (14,841 bytes)
5. Re: scheduling questions (score: 1): Author: "Mark D. Rodriguez" <mark AT MDRCONSULT DOT COM>; Date: Mon, 28 Feb 2005 11:27:56 -0600; David, I don't see why you would need multiple nodes on a single system. You can simply run a separate schedule that does image backup. Then you can use include.image statements to control the manage; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-02/msg00782.html (15,958 bytes)
6. Re: scheduling questions (score: 1): Author: David Soucy <dsoucy AT DIGITAS DOT COM>; Date: Mon, 28 Feb 2005 13:21:18 -0500; Mark, I guess I'm just wondering how I could have daily, weekly, and monthly backups automated under a single node name. What I'm gathering is that you would have to schedule dailys (M-F) a weekly im; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-02/msg00785.html (17,560 bytes)
7. Re: scheduling questions (score: 1): Author: "Mark D. Rodriguez" <mark AT MDRCONSULT DOT COM>; Date: Mon, 28 Feb 2005 13:21:20 -0600; I think you got the idea now. What you propose would work just fine. Now the only thing you have to consider is the type of image backup you will do. Please read the manual on this since you will hav; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-02/msg00787.html (20,518 bytes)

Current List: 1 - 7
Page: [1]