Re: [Bacula-users] Problems with disk-based backup
On Wed, 04 May 2011 13:38:37 +1000, Philip Yarra said: On 03/05/11 00:00, John Drescher wrote: 2011/5/2 Philip Yarrapya...@radoncvic.com.au: My bacula now seems to be firmly wedged, with all jobs trying to use the same volume (and my config very definitely says to use each volume only once). Scheduled Jobs: Level Type Pri Scheduled Name Volume === IncrementalBackup10 02-May-11 22:00wd-server-user-shares Full-0179 IncrementalBackup10 02-May-11 22:00em-fap-user-shares Full-0179 IncrementalBackup10 02-May-11 22:00rg-server-user-shares Full-0179 IncrementalBackup10 02-May-11 22:00ep-server-user-shares Full-0179 IncrementalBackup10 02-May-11 22:00fr-server-user-shares Full-0179 IncrementalBackup10 02-May-11 22:00rov-impac-1-tshome Full-0179 IncrementalBackup10 02-May-11 22:00zevon-home Full-0179 IncrementalBackup10 02-May-11 22:00rov-citrix-cs-documents Full-0179 Can anyone advise on how bacula has got wedged like this, and how I can fix it? Help?? Bacula does not really know what volume it will use till it actually starts the backup so the display will not take into account Use volume once or any other condition that limits the volume usage. That's right - normally it displays *unknown* in the column for volume, and it gets a new volume allocated when the job runs. But in the case I showed above, the upcoming jobs had been pre-allocated a volume, which isn't normal. Also, they'd all been allocated the same one, which won't work, as each volume can be used once only. Hence why I'm asking how could this happen? and how do I fix it? It displays the first usable volume in the pool, without doing any pruning or creating any new volumes. It displays *unknown* when there are no usable volumes (e.g. they are all marked as Full or Used). So apparently Full-0179 was still available at that time. __Martin -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problems with disk-based backup
My bacula now seems to be firmly wedged, with all jobs trying to use the same volume (and my config very definitely says to use each volume only once). Scheduled Jobs: Level Type Pri Scheduled Name Volume === IncrementalBackup10 02-May-11 22:00wd-server-user-shares Full-0179 IncrementalBackup10 02-May-11 22:00em-fap-user-shares Full-0179 IncrementalBackup10 02-May-11 22:00rg-server-user-shares Full-0179 IncrementalBackup10 02-May-11 22:00ep-server-user-shares Full-0179 IncrementalBackup10 02-May-11 22:00fr-server-user-shares Full-0179 IncrementalBackup10 02-May-11 22:00rov-impac-1-tshome Full-0179 IncrementalBackup10 02-May-11 22:00zevon-home Full-0179 IncrementalBackup10 02-May-11 22:00rov-citrix-cs-documents Full-0179 Can anyone advise on how bacula has got wedged like this, and how I can fix it? Help?? Regards, Philip. On 28/04/11 15:10, Philip Yarra wrote: An update: after leaving it to run last night, it appears that incremental jobs are trying to use volume Incr-0017, which is already used (and not appendable). So why is bacula trying to re-use volumes it is not allowed to, and how can I stop it from doing so? I've pasted the debug output from the SD on rm-nas-1 below, you'll see it tries to use Incr-0017 for rg-server, fails, then tries to use it for fr-server. The Incr-0017 volume has already been used for wd-server - I can see it on disk. Here's the Storage Daemon debug output: 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: vol_mgr.c:352-295 enter reserve_volume=Incr-0017 drive=rm-nas-1-rg-server (/c/bacula/rg-server) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: vol_mgr.c:268-295 new Vol=Incr-0017 at 87048 dev=rm-nas-1-rg-server (/c/bacula/rg-server) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: vol_mgr.c:470-295 === set in_use. vol=Incr-0017 dev=rm-nas-1-rg-server (/c/bacula/rg-server) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: vol_mgr.c:211-295 List end new volume: Incr-0017 in_use=1 on device rm-nas-1-rg-server (/c/bacula/rg-server) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: askdir.c:293-295 dir_find_next_appendable_volume return true. vol=Incr-0017 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:126-295 After find_next_append. Vol=Incr-0017 Slot=0 Parts=0 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: autochanger.c:120-295 Device rm-nas-1-rg-server (/c/bacula/rg-server) is not an autochanger 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:150-295 autoload_dev returns 0 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:181-295 want vol=Incr-0017 devvol= dev=rm-nas-1-rg-server (/c/bacula/rg-server) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:360-295 open dev: type=1 dev_name=rm-nas-1-rg-server (/c/bacula/rg-server) vol=Incr-0017 mode=OPEN_READ_WRITE 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:369-295 call open_file_device mode=OPEN_READ_WRITE 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:2089-295 Enter mount 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:542-295 open disk: mode=OPEN_READ_WRITE open(/c/bacula/rg-server/Incr-0017, 0x2, 0640) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:549-295 open failed: dev.c:548 Could not open: /c/bacula/rg-server/Incr-0017, ERR=No such file or directory 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:557-295 open dev: disk fd=-1 opened, part=0/0, part_size=0 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:373-295 preserve=0x0 fd=-1 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:360-295 open dev: type=1 dev_name=rm-nas-1-rg-server (/c/bacula/rg-server) vol=Incr-0017 mode=OPEN_READ_WRITE 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:369-295 call open_file_device mode=OPEN_READ_WRITE 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:2089-295 Enter mount 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:542-295 open disk: mode=OPEN_READ_WRITE open(/c/bacula/rg-server/Incr-0017, 0x2, 0640) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:549-295 open failed: dev.c:548 Could not open: /c/bacula/rg-server/Incr-0017, ERR=No such file or directory 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:557-295 open dev: disk fd=-1 opened, part=0/0, part_size=0 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:373-295 preserve=0x0 fd=-1 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:199-295 open_device failed: ERR=dev.c:548 Could not open: /c/bacula/rg-server/Incr-0017, ERR=No such file or directory 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:222-295 set_unload 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:225-295 goto mount_next_vol 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:89-295 mount_next_vol retry=71
Re: [Bacula-users] Problems with disk-based backup
2011/5/2 Philip Yarra pya...@radoncvic.com.au: My bacula now seems to be firmly wedged, with all jobs trying to use the same volume (and my config very definitely says to use each volume only once). Scheduled Jobs: Level Type Pri Scheduled Name Volume === Incremental Backup 10 02-May-11 22:00 wd-server-user-shares Full-0179 Incremental Backup 10 02-May-11 22:00 em-fap-user-shares Full-0179 Incremental Backup 10 02-May-11 22:00 rg-server-user-shares Full-0179 Incremental Backup 10 02-May-11 22:00 ep-server-user-shares Full-0179 Incremental Backup 10 02-May-11 22:00 fr-server-user-shares Full-0179 Incremental Backup 10 02-May-11 22:00 rov-impac-1-tshome Full-0179 Incremental Backup 10 02-May-11 22:00 zevon-home Full-0179 Incremental Backup 10 02-May-11 22:00 rov-citrix-cs-documents Full-0179 Can anyone advise on how bacula has got wedged like this, and how I can fix it? Help?? Bacula does not really know what volume it will use till it actually starts the backup so the display will not take into account Use volume once or any other condition that limits the volume usage. John -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problems with disk-based backup
On 4/27/11 12:05 AM, Philip Yarra wrote: Hi, I'm having some troubles with bacula failing to perform automatic backups. The issue seems to be that the storage daemon is not automatically labelling a new volume. The setup looks like this: Director lives on an Intel server running Ubuntu 10.04.2 LTS, the installed version of bacula is from the packages for this release: 5.0.1 Storage daemons live on a pair of Netgear ReadyNAS NV+ (sparc-based NAS boxes) using 5.0.1 compiled natively on a ReadyNAS box. The NV+ is running Linux 2.6.17.14ReadyNAS and I believe this is a re-packaged Debian Sarge We have File daemons (version 5.0.3) deployed on a range of Windows 2003, 2000 and Ubuntu server boxes. We do a full backup each Saturday morning, then each weeknight we write an incremental. The director config has has custom schedules so that alternate weeks are written to different storage daemons. The problems seemed to start occurring when the volume names rolled over from Incr-0099 to Incr-0100 (that is the first instance I can find of this issue, anyway). I don't know if this is coincidence or not. When the problem occurred, we got this in the director's logs: [snip] My suspicion is that the issue is on the storage daemon. I've now set them to create debug level output (using-v -dt -d 200) which I have redirected to a file, so I hope to have more info in future. Regards, Philip. Philip, My first thought is that your fd, maybe, should not be more current than the dir or sd. Having an older fd worked for me. The second thing is there are no 'maximum' commands. Here are mine in the Pool section: Maximum Volume Bytes = 4GB Maximum Volumes = 115 Multiply 4 x 115 = 460 GB - bad things happen if the disk gets full The third thought is that you really should run a much simpler setup(conf files) till all issues are hashed out. You are doing things the hard way. Mehma -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problems with disk-based backup
An update: after leaving it to run last night, it appears that incremental jobs are trying to use volume Incr-0017, which is already used (and not appendable). So why is bacula trying to re-use volumes it is not allowed to, and how can I stop it from doing so? I've pasted the debug output from the SD on rm-nas-1 below, you'll see it tries to use Incr-0017 for rg-server, fails, then tries to use it for fr-server. The Incr-0017 volume has already been used for wd-server - I can see it on disk. Here's the Storage Daemon debug output: 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: vol_mgr.c:352-295 enter reserve_volume=Incr-0017 drive=rm-nas-1-rg-server (/c/bacula/rg-server) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: vol_mgr.c:268-295 new Vol=Incr-0017 at 87048 dev=rm-nas-1-rg-server (/c/bacula/rg-server) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: vol_mgr.c:470-295 === set in_use. vol=Incr-0017 dev=rm-nas-1-rg-server (/c/bacula/rg-server) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: vol_mgr.c:211-295 List end new volume: Incr-0017 in_use=1 on device rm-nas-1-rg-server (/c/bacula/rg-server) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: askdir.c:293-295 dir_find_next_appendable_volume return true. vol=Incr-0017 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:126-295 After find_next_append. Vol=Incr-0017 Slot=0 Parts=0 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: autochanger.c:120-295 Device rm-nas-1-rg-server (/c/bacula/rg-server) is not an autochanger 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:150-295 autoload_dev returns 0 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:181-295 want vol=Incr-0017 devvol= dev=rm-nas-1-rg-server (/c/bacula/rg-server) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:360-295 open dev: type=1 dev_name=rm-nas-1-rg-server (/c/bacula/rg-server) vol=Incr-0017 mode=OPEN_READ_WRITE 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:369-295 call open_file_device mode=OPEN_READ_WRITE 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:2089-295 Enter mount 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:542-295 open disk: mode=OPEN_READ_WRITE open(/c/bacula/rg-server/Incr-0017, 0x2, 0640) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:549-295 open failed: dev.c:548 Could not open: /c/bacula/rg-server/Incr-0017, ERR=No such file or directory 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:557-295 open dev: disk fd=-1 opened, part=0/0, part_size=0 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:373-295 preserve=0x0 fd=-1 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:360-295 open dev: type=1 dev_name=rm-nas-1-rg-server (/c/bacula/rg-server) vol=Incr-0017 mode=OPEN_READ_WRITE 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:369-295 call open_file_device mode=OPEN_READ_WRITE 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:2089-295 Enter mount 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:542-295 open disk: mode=OPEN_READ_WRITE open(/c/bacula/rg-server/Incr-0017, 0x2, 0640) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:549-295 open failed: dev.c:548 Could not open: /c/bacula/rg-server/Incr-0017, ERR=No such file or directory 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:557-295 open dev: disk fd=-1 opened, part=0/0, part_size=0 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: dev.c:373-295 preserve=0x0 fd=-1 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:199-295 open_device failed: ERR=dev.c:548 Could not open: /c/bacula/rg-server/Incr-0017, ERR=No such file or directory 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:222-295 set_unload 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:225-295 goto mount_next_vol 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:89-295 mount_next_vol retry=71 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: vol_mgr.c:594-295 === set not reserved vol=Incr-0017 num_writers=0 dev_reserved=1 dev=rm-nas-1-rg-server (/c/bacula/rg-server) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: vol_mgr.c:595-295 === clear in_use vol=Incr-0017 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: vol_mgr.c:623-295 === clear in_use vol=Incr-0017 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: vol_mgr.c:626-295 === remove volume Incr-0017 dev=rm-nas-1-rg-server (/c/bacula/rg-server) 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: askdir.c:640-297 Back from wait_for_sysop stat=3 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:101-297 Continue after dir_ask_sysop_to_mount. must_load=0 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: mount.c:346-297 Before dir_find_next_appendable_volume. 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: askdir.c:260-297 dir_find_next_appendable_volume: reserved=1 Vol=Incr-0017 28-Apr-2011 03:34:18 rm-nas-1.radoncvic.com.au: askdir.c:277-297 dird CatReq Job=fr-server-user-shares.2011-04-27_22.00.01_29 FindMedia=1 pool_name=Incremental
