2 Chapter 32. Thoughts about a Strategy API
3 Prev Part VI. Historical files Next
5 -------------------------------------------------------------------------------
7 Chapter 32. Thoughts about a Strategy API
14 <oliva@dcc.unicamp.br>>
24 Refer to http://www.amanda.org/docs/strategy-api.html for the current version
27 Subject: STRATEGY API (was: Re: spelunking)
28 From: Alexandre Oliva <oliva@dcc.unicamp.br>
29 Date: 03 Oct 1998 02:44:47 -300
31 Doug Hughes <Doug.Hughes@Eng.Auburn.EDU> writes:
33 > I'm going to (try to) modify the amanda stuff such that there is a new
34 > parameter called dumplevel available in dumptype. That way I can fix
35 > the dump level at whatever I want (5 or 9 when I need to), without
36 > having to worry about whether it's going to try and skip a 0 and miss
37 > a dump, or try to do a 1, or whatever.
39 Now that you mention that, it comes to my mind that the current
40 mechanism to define backup strategies is too limited, and we could try
41 to improve it just like we are going to do with the DUMPER API.
43 We could define a STRATEGY API, that planner would use to:
45 1) define a set levels and/or dates for which estimates should be requested
47 2) select a subset of the estimate results that planner can choose
49 and driver would run to inform that a backup has succeeded, after
50 having updated the database.
52 I haven't fully analysed the implications of this choice, but it looks
53 quite feasible and very useful. Opinions? Requests of clarification?
56 Anyone willing to pursue this issue?
61 -------------------------------------------------------------------------------
64 Chapter 31. Multitape support in AMANDA 2.2 Home Chapter 33. Y2K Compliancy