Dave, On Tuesday 21 November 2006 15:43, DAve wrote: > Martin Simmons wrote: > >>>>>> On Mon, 20 Nov 2006 15:07:27 -0500, DAve said: > >> > >> I've read through the following portions of the manual and I think I > >> might not be able to do what I need. > >> > >> http://bacula.org/rel-manual/Automatic_Volume_Recycling.html > >> http://bacula.org/rel-manual/Basic_Volume_Management.html > >> http://bacula.org/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0003 > >>430000000000000000 > >> http://bacula.org/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0003 > >>425000000000000000 > >> > >> I am trying to backup a simple disaster recovery set, kept for a single > >> day (there is local tape making routine backups), and then reused 24 > >> hours later. The backup set is for off site emergencies only. This all > >> works, just fine. > >> > >> Now I want to generate a report for the past thirty days to show the > >> backups were made. Currently I can't get my job information to stay in > >> the DB so I can query it for reporting. > >> > >> I have the following set, > >> Client { > >> Name = alli-fd > >> Address = fd.alli.com > >> FDPort = 49101 > >> Catalog = DataVault > >> Password = "o/hEQs5oQgO103AfF1cvrmhW21BuodfrzN" > >> File Retention = 2 days > >> Job Retention = 30 days > >> AutoPrune = yes > >> } > >> > >> Pool { > >> Name = Daily-Alli-Pool > >> Pool Type = Backup > >> Recycle = yes > >> AutoPrune = yes > >> Volume Retention = 1 day > >> Accept Any Volume = yes > >> LabelFormat = "Daily-alli-" > >> Maximum Volume Jobs = 1 > >> Maximum Volumes = 2 > >> } > >> > >> I think I can change my Maximum Volume Jobs to 30 and get the result I > >> want which is, 30 days of jobs in the catalog, only two Volumes in use. > >> I am trying it tonight. If I am misunderstanding something, smack me. > > > > It will be confusing if you still have Volume Retention = 1 day. > > > > Also, it is overkill for the goal of "disaster recovery set kept for a > > single day ... and then reused 24 hours later." It implies keeping 30-60 > > days of backups in the 2 volumes. > > > > I think the problem you have is that the job information must be removed > > from the catalog before the volume can be recycled. Therefore, if you > > want to keep only 1-2 days of backups then the catalog can only contain > > 1-2 jobs. > > That is how I read the docs as well, and the test showed the same. So I > understand it correctly, good. > > I understand the problem with what they requested, but I don't so sales > and I am not the IT manager for the client (This is for a client within > our building). They believe they just need to to get fresh copies of > certain files into our NOC every night for DR purposes. There is only > one current copy of the files in each volume, the previous volume is > purged shortly after. > > Doesn't make sense to me, but it pays the same as a strategy that does. > > DAve
I imagine you've already thought of this, but it sounds like the solution to this dilema is to have a run-after-job which will execute an sql query on the database to extract the necessary information and save it in another database or text file. Then, once a month you can generate your report from this file, purge it and start over. Cheers! cmr -- Debian 'Etch': Registered Linux User #241964 ---- "More laws, less justice." -- Marcus Tullius Ciceroca, 42 BC -------- ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
