Damn... I ran across an article this the other day, outlining how to do this, but not with amanda.
Let me look aroudnand I'll try and find something for you. Daryl. -----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de John R. Jackson Envoy� : dimanche 3 f�vrier 2002 03:47 � : Miquel Bonastre Cc : [EMAIL PROTECTED] Objet : Re: Home Backup on CDROM > Supposing we start from a 0 bytes occupied > disk, I have an idea about a backup policy: >... OK, I understand what you're saying, although I didn't think it through enough to decide if the algorithm would have any problems (other than the few things I note below). However, you're asking the wrong group. Amanda does not do backups. Amanda runs other programs that do backups. What you're describing is the algorithm an actual backup program (such as GNU tar) would use, which puts it outside the scope of Amanda. If you're interested in playing with this kind of thing, I'd start with the GNU tar source (1.13.19 or later). Eventually you'll have to make changes to Amanda to run your modified tar (or whatever program). For instance, it looks like you want essentially one (what Amanda thinks of as a) "level" for each run/CD because you need to keep an index (roughly like the current incremental files) for each CD. At the moment, Amanda does not go beyond level 9 (I don't think -- I'd have to look at that part of the code). And there will be some other changes, such as convincing it full dumps were not needed. But the first task will be building a backup program that implements your algorithm. What advantages will your algorithm have over the traditional levels? About the only one I can think of is that the backup media is fully utilized each run. I see some problems if there has to be a lot of data moved forward from the oldest CD before it is rewritten (I assume you're talking about CD-RW?). I think this can be resolved by having plenty more CD's than actual data, but I'd want to think through a lot more scenarios first. > Miquel John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
