Re: [Bacula-users] Volumes getting reused before meeting retention
I have tried the steps on test bed and found that it only applies to Pool resource. The Volume retention was same as previous. Update choice: 1: Volume parameters 2: Pool from resource 3: Slots from autochanger 4: Long term statistics Choose catalog item to update (1-4): 2 The defined Pool resources are: 1: Default 2: Pool_8 Select Pool resource (1-2): 2 Cross verified and it showed the changes: --- *llist Pool PoolId: 2 Name: Pool_8 NumVols: 1 MaxVols: 18 UseOnce: 0 UseCatalog: 1 AcceptAnyVolume: 0 *VolRetention: 1,036,800* <<< wrote: > 2009/12/15 vishal veerkar : > > Hi Timo. > > > > > > Thanks for quick response. > > > > Yes, the problem occurred because initial retention was changed and these > > volumes were present from start and hence using the same old config. > After > > goggling i came to know that whenever retention is configured, the first > > volume created is used as prototype for the next volumes and hence > inherits > > the same characteristics. > > > > For resolving the problem i have gone to bat and manually edited all the > > problematic volumes and set the retention to new configuration policy and > i > > think this will resolve my problem. > > > > If anyone else has this problem. There is a much easier solution. > > Open a bacula console window > > update > > then select "Pool from resource" > > and follow the menus. > > John > -- With regards, Vishal Veerkar -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] prune not working as expected
> -Original Message- > > I also checked: there are no jobs associated with these volumes. > > Yes, prune should mark those volumes are purged if there are no jobs. > It's a mystery. Is there a way to turn on something like verbose output for pruning so I can find out exactly what it does to troubleshoot that? -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] backing up to multiple hard drives
Hi, On Tue, 15 Dec 2009, Kendall Shaw wrote: > Do you have a recommendation? I'm backing up my home computers. The > point of doing the full backup only once, was to avoid transferring the > same files over and over again every week. Maybe it's not worth avoiding > doing the full backup every week. If you just want to avoid the data transfer, I'd suggest you take a look at virtualfull backups which were added in v3. It doesn't save you space particularly, but it saves the transfers. VirtualFull jobs "consolidate" a prior full backup and some subsequent differential and incremental backups into a new full backup. There are some tricks to getting it working though (you have to have your volumes on different "devices" as bacula won't read from and write to the same device at once. If you picture your devices as tape drives, that's easy to understand. You should also be using accurate backups for this to work right. Gavin -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] backing up to multiple hard drives
On Tue, 2009-12-15 at 09:46 +, Gavin McCullagh wrote: > Hi, > > On Mon, 14 Dec 2009, Kendall Shaw wrote: > > > I have a 300GB hard drive that I backup to a 600GB hard drive, but the > > initial full backup runs out of space (it takes almost twice as much > > space to hold the backup?). > > Something sounds wrong there. Are you saying that a single volume for a > single backup is more than twice the size of the data being backed up? Do > you have compression on? Perhaps you might want to post the log message > from the backup, the job config and the output of "df -h" on the computer. Yes, that's what I saw. I'll post the log later, I can't do it now. But, I wanted to ask a question: [...] > > An additional detail is that I use a scheme were I do a full backup > > once (ever) and then only incremental and differential after that, > > reusing volumes each week. > > It's up to you of course, but I'm not sure this is a wise scheme. How do > you ever free up space from old backups? You can't ever delete the > original full backup or all of the incrementals and differentials that > follow it will be useless. You can, I guess, have an ever growing > differential, but over time that will start to look like a full backup as > 30%,40%,50%, of the data you backup has changed since the original > full. Do you have a recommendation? I'm backing up my home computers. The point of doing the full backup only once, was to avoid transferring the same files over and over again every week. Maybe it's not worth avoiding doing the full backup every week. Kendall -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] logwatch
On Mon, 2009-12-14 at 08:22 -0700, Craig White wrote: > A relatively new bacula 3.0.3 installation on CentOS 5 > > I get an error every day from logwatch... > > > > obviously generated by > cron...run-parts /etc/cron.daily > > > /etc/cron.daily/0logwatch: > > Cannot find shared script applybaculadate > > Now I can find the script... > /usr/src/redhat/BUILD/bacula-3.0.3/scripts/logwatch/applybaculadate > > and I can see that... > > # cat /etc/logwatch/conf/services/bacula.conf > Title = "bacula" > > # Which logfile group... > LogFile = bacula > > *ApplyBaculaDate = > > What is it that I am supposed to do? with help from Steve Ellis... apparently the source rpm needs to do the following... mkdir /etc/logwatch/scripts/shared cp \ /usr/src/redhat/BUILD/bacula-3.0.3/scripts/logwatch/applybaculadate \ /etc/logwatch/scripts/shared chmod 755 /etc/logwatch/scripts/shared/applybaculadate and a terse bacula log is included with logwatch or otherwise, generates an error. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Solved] Re: Create new volume vs. recycle volume (with config)
On Tue, Dec 15, 2009 at 10:10 AM, Brian Clarkson wrote: > There were still volumes in my pool that were marked recycle=yes. > > Removing the recycle flag from all volumes triggered the creation of new > filenames for each server and backup job. > > Just changing the recycle flag to "no" in the configuration didn't solve > the problem. > The issue here is the pool resource in bacula-dir.conf is just a template for creating new volumes. It does not effect old volumes. So after modifying the pool resource you need to tell bacula to apply the changes to old volumes. John -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] [Solved] Re: Create new volume vs. recycle volume (with config)
There were still volumes in my pool that were marked recycle=yes.
Removing the recycle flag from all volumes triggered the creation of new
filenames for each server and backup job.
Just changing the recycle flag to "no" in the configuration didn't solve
the problem.
Thanks for the help!
Brian
On Thu, 2009-12-10 at 17:38 -0500, John Drescher wrote:
> On Thu, Dec 10, 2009 at 5:09 PM, Brian Clarkson wrote:
> > On Thu, 2009-12-10 at 16:11 -0500, John Drescher wrote:
> >> On Thu, Dec 10, 2009 at 3:53 PM, Brian Clarkson wrote:
> >> > On Thu, 2009-12-10 at 15:06 -0500, John Drescher wrote:
> >> >> >> Make the volume retention much longer. And then apply that to all of
> >> >> >> your volumes.
> >> >> >
> >> >> > Wouldn't the volume retention period need to be shorter?
> >> >> >
> >> >>
> >> >> Retention period is how long to keep the volume before it can be reused.
> >> >
> >> > So if I don't want to reuse volumes I should set the retention period to
> >> > zero?
> >> >
> >>
> >> Definitely not. I know telling bacula to keep your backup data for 0
> >> seconds is not what you want. Set this to the amount of time you want
> >> to keep your data after the backup is finished.
> >>
> >> > Reusing the files (a volume is just a collection of 512m files per my
> >> > configuration) is what I want to stop.
> >> >
> >>
> >> I got you there. As you mentioned you need to turn off automatic
> >> volume recycling. Please post your configs. Have you had bacula reload
> >> the config file after you have changed it?
> >
> > I restarted the bacula director after making the changes. Subsequent
> > backup jobs still re-used files.
> >
> > >From bacula-dir.conf
> >
> > Pool {
> > Name = Default
> > Label Format = "${JobName}-${Level}-${NumVols}"
> > Pool Type = Backup
> > Recycle = no
> > AutoPrune = yes # Prune expired volumes
> > Use Volume Once = yes
> > Volume Retention = 25 days
> > MaximumVolumeBytes = 512m
> > Maximum Volume Jobs = 1
> > }
> >
> > Client {
> > Name = client-fd
> > Address = server.com
> > FDPort = 9102
> > Catalog = MyCatalog
> > Password = "***"
> > File Retention = 21 days
> > Job Retention = 21 days
> > AutoPrune = yes
> > }
> >
> > Job {
> > Name = "Backup Server"
> > Type = Backup
> > Client = server-fd
> > FileSet = "Full Set"
> > Schedule = "WeeklyCycle"
> > Storage = Storage
> > Messages = Standard
> > Pool = Default
> > Write Bootstrap = "/usr/local/bacula/var/bacula/working/server.bsr"
> > }
> >
> > Storage {
> > Name = Storage
> > Address = storage.server.com
> > SDPort = 9103
> > Password = "***"
> > Device = StorageServer
> > Media Type = File
> > }
> >
> > >From bacula-sd.conf
> >
> > Device {
> > Name = StorageServer
> > Media Type = File
> > Archive Device = /home/bacula-data/
> > LabelMedia = yes; # lets Bacula label unlabeled
> > media
> > Random Access = Yes;
> > AutomaticMount = yes; # when device opened, read it
> > RemovableMedia = no;
> > AlwaysOpen = no;
> > }
> >
>
> I think I see why this is happening.
>
> Do the following
> list media pool=Default
>
> and see if Recycle=1 is set in any of the volumes.
>
> if so
>
> update
>
> and then select "Pool from resource"
>
> and follow the prompts.
>
> John
--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Crashing storage director. Need help getting trace.
> On Mon, 14 Dec 2009 16:47:00 +0800, Jim Barber said: > > Jim Barber wrote: > > > > Thanks Martin. > > > > I've compiled and installed version 3.1.6 from a git pull I did on 10th Dec. > > I'm not sure if this new version will crash or not. > > But I've manually attached a gdb session to it just in case it does. > > > > Thanks. > > I'm not having much luck with this. > When I attached to the process with gdb it seems to interfere with it. > It's like to stops running. > It no longer responds to status commands etc. > > I'm not familiar enough with gdb to resolve it. > I tried the 'c'ontinue command just in case attaching stops the process. > But it doesn't make any difference. Yes, you do need to use the continue command after attaching, but that should work. Possibly your version of gdb is broken, which might also explain the lack of email from btraceback. Did gdb print anything after you did that? It may be worth posting the whole gdb session. __Martin -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Volumes getting reused before meeting retention
2009/12/15 vishal veerkar : > Hi Timo. > > > Thanks for quick response. > > Yes, the problem occurred because initial retention was changed and these > volumes were present from start and hence using the same old config. After > goggling i came to know that whenever retention is configured, the first > volume created is used as prototype for the next volumes and hence inherits > the same characteristics. > > For resolving the problem i have gone to bat and manually edited all the > problematic volumes and set the retention to new configuration policy and i > think this will resolve my problem. > If anyone else has this problem. There is a much easier solution. Open a bacula console window update then select "Pool from resource" and follow the menus. John -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Volumes getting reused before meeting retention
Hi Timo.
Thanks for quick response.
Yes, the problem occurred because initial retention was changed and these
volumes were present from start and hence using the same old config. After
goggling i came to know that whenever retention is configured, the first
volume created is used as prototype for the next volumes and hence inherits
the same characteristics.
For resolving the problem i have gone to bat and manually edited all the
problematic volumes and set the retention to new configuration policy and i
think this will resolve my problem.
Regards,
Vishal Veerkar
On Tue, Dec 15, 2009 at 2:54 PM, Timo Neuvonen wrote:
> "vishal veerkar" kirjoitti viestissä
> news:d495389e0912142254u174d4e80h53c499b3379d6...@mail.gmail.com...
> > Hi All,
> >
> > I am using Bacula 2.2.8 and now in phase of migration for latest version
> > but in mean time i have to run the current setup. Recently i have noticed
> > that the Volumes are getting reused before the retention period is met.
> > The problem persist with some of the volumes and not all. The Job and
> File
> > retentions also set for 12days.
> >
>
> Are you aware that changing pool specs does NOT affect directly to the
> existing volumes? Sounds like your volumes had different retention periods,
> since some of them have this problem and the others don't.
>
> a) you may use "llist media" (note the double-l like 'long') to view
> current
> retention periods
>
> b) if necessary, use bconsole "update" command to update the existing
> volumes to follow the conf
>
> Also remember that after altering the conf file you'll need to either
> restart the director, or 'reload' the new conf before it takes control
>
>
> > Below is the example for illustrating the situation.
> >
> > 05-Dec 03:55 bacula-dir JobId 17183: There are no more Jobs associated
> > with Volume "Vol0048". Marking it purged.
> > 05-Dec 03:55 bacula-dir JobId 17183: All records pruned from Volume
> > "Vol0048"; marking it "Purged"
> >
> > 2009-12-14 10:10:35 bacula-dir JobId 17822: There are no more Jobs
> > associated with Volume "Vol0048". Marking it purged. 2009-12-14 10:10:35
> > bacula-dir JobId 17822: All records pruned from Volume "Vol0048"; marking
> > it "Purged"
> >
> >
> > Pool {
> > Name = Pool_8
> > Pool Type = Backup
> > Recycle = yes # Bacula can automatically
> recycle
> > Volumes
> > AutoPrune = yes # Prune expired volumes
> > Volume Retention = 12 days# 12 days
> > Maximum Volume Bytes = 32212254720#30GB
> > LabelFormat = "Vol"
> > }
>
>
>
>
> --
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
--
With regards,
Vishal Veerkar
--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] prune not working as expected
> On Fri, 11 Dec 2009 13:30:52 -0800, Kevin Keane said: > > > -Original Message- > > From: Martin Simmons [mailto:mar...@lispworks.com] > > Sent: Friday, December 11, 2009 12:44 PM > > To: bacula-users@lists.sourceforge.net > > Subject: Re: [Bacula-users] prune not working as expected > > > > > On Thu, 10 Dec 2009 13:11:38 -0800, Kevin Keane said: > > > > > > I have a couple older volumes that I expected to get pruned by now, > > but they > > > don't. I am using bacula 3.0.2 on OpenSuSE. > > > > > > Here is one example: > > > > > > | 244 | randamai_20091101223426_Full.bacula| > > Archive | 1 | 93,005,712,230 | 21 |2,851,200 | > > 0 |0 | 0 | File | 2009-11-02 02:11:00 | > > > > > > When I used the prune volume command, I saw the following (all as > > expected): > > > > > > Enter *MediaId or Volume name: > > > *244 > > > The current Volume retention period is: 1 month 3 days > > > Continue? (yes/mod/no): > > > yes > > > > > > But this volume remains unpruned even though it is older than 1 month > > and 3 days. > > > > > > One thing that might possibly be related: these volumes were created > > with > > > bacula 2.4.2. When I migrated to 3.0, I created a new database from > > scratch > > > and used bscan to import the volumes. That was about a week ago. > > Bacula > > > falsely assigned a retention time of 1 year; I corrected that with an > > update > > > pool command. > > > > The problem is that the volume has status Archive, which was probably > > set by > > bscan. You can only prune volumes with status Full or Used. > > Thanks! Yes, I discovered that right after I posted. But even after I updated > the volume status to Used, prune still does not do anything. > > I also checked: there are no jobs associated with these volumes. Yes, prune should mark those volumes are purged if there are no jobs. It's a mystery. __Martin -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] backing up to multiple hard drives
Hi, On Mon, 14 Dec 2009, Kendall Shaw wrote: > I have a 300GB hard drive that I backup to a 600GB hard drive, but the > initial full backup runs out of space (it takes almost twice as much > space to hold the backup?). Something sounds wrong there. Are you saying that a single volume for a single backup is more than twice the size of the data being backed up? Do you have compression on? Perhaps you might want to post the log message from the backup, the job config and the output of "df -h" on the computer. > So, I'd like to allow the backup to span more than one hard drive. I > read something like a solution on this list, involving creating files > for bacula to use as volumes, with symbolic links to the hard drive > that the fiel should be stored on. That's one way alright but it sounds a bit time consuming. Another way would be to use LVM to create a filesystem which spans the disks and use disk volumes normally on that. The trouble with either approach is that if you have a single full backup spanned across two disks and you lose either of your hard drives, you've lost some of your data. Spanning the backup over multiple volumes on multiple disks is probably easier to recover the remaining data than with LVM, but neither is a great backup. > An additional detail is that I use a scheme were I do a full backup > once (ever) and then only incremental and differential after that, > reusing volumes each week. It's up to you of course, but I'm not sure this is a wise scheme. How do you ever free up space from old backups? You can't ever delete the original full backup or all of the incrementals and differentials that follow it will be useless. You can, I guess, have an ever growing differential, but over time that will start to look like a full backup as 30%,40%,50%, of the data you backup has changed since the original full. Gavin -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Volumes getting reused before meeting retention
"vishal veerkar" kirjoitti viestissä
news:d495389e0912142254u174d4e80h53c499b3379d6...@mail.gmail.com...
> Hi All,
>
> I am using Bacula 2.2.8 and now in phase of migration for latest version
> but in mean time i have to run the current setup. Recently i have noticed
> that the Volumes are getting reused before the retention period is met.
> The problem persist with some of the volumes and not all. The Job and File
> retentions also set for 12days.
>
Are you aware that changing pool specs does NOT affect directly to the
existing volumes? Sounds like your volumes had different retention periods,
since some of them have this problem and the others don't.
a) you may use "llist media" (note the double-l like 'long') to view current
retention periods
b) if necessary, use bconsole "update" command to update the existing
volumes to follow the conf
Also remember that after altering the conf file you'll need to either
restart the director, or 'reload' the new conf before it takes control
> Below is the example for illustrating the situation.
>
> 05-Dec 03:55 bacula-dir JobId 17183: There are no more Jobs associated
> with Volume "Vol0048". Marking it purged.
> 05-Dec 03:55 bacula-dir JobId 17183: All records pruned from Volume
> "Vol0048"; marking it "Purged"
>
> 2009-12-14 10:10:35 bacula-dir JobId 17822: There are no more Jobs
> associated with Volume "Vol0048". Marking it purged. 2009-12-14 10:10:35
> bacula-dir JobId 17822: All records pruned from Volume "Vol0048"; marking
> it "Purged"
>
>
> Pool {
> Name = Pool_8
> Pool Type = Backup
> Recycle = yes # Bacula can automatically recycle
> Volumes
> AutoPrune = yes # Prune expired volumes
> Volume Retention = 12 days# 12 days
> Maximum Volume Bytes = 32212254720#30GB
> LabelFormat = "Vol"
> }
--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
