Re: [Bacula-users] Windows client backup error
| | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive t:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive u:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive v:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive w:\ failed. | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): System Writer, State: 0x1 backslashes look also wrong. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] concurrent jobs not working?
On 06/01/2015 01:18 PM, Ana Emília M. Arruda wrote: I have this working here. With automatic labeling. When you submit the jobs, which messeges do you see for the jobs in the status dir command A-ha, it says one job is running and 10 is waiting on max Storage jobs. Just for checking: have you enabled the storage concurrency both on bacula-sd.conf and bacula-dir.conf? Yes of course. ... but it turns out I had it in Storage and Device blocks in bacula-sd.conf and in Director block in bacula-dir.conf. I was missing it from the Storage block in bacula-dir.conf. We'll see if that was it, I'll let you know after the next run. Thanks for the pointer, -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Perl 5.20 upgrade breaks make_catalog_backup.pl?
Recently FreeBSD announced that its default Perl version is now 5.20 and urged all users to upgrade to that version. I did so. Now make_catalog_backup.pl doesn't run. The first indication was as follows: 30-May 09:05 pisces-dir JobId 15770: shell command: run BeforeJob /usr/local/share/bacula/make_catalog_backup1.pl MyCatalog 30-May 09:05 pisces-dir JobId 15770: BeforeJob: Statement unlikely to be reached at /usr/local/share/bacula/make_catalog_backup1.pl line 40. 30-May 09:05 pisces-dir JobId 15770: BeforeJob: (Maybe you meant system() when you said exec()?) 30-May 09:05 pisces-dir JobId 15770: BeforeJob: Statement unlikely to be reached at /usr/local/share/bacula/make_catalog_backup1.pl line 67. 30-May 09:05 pisces-dir JobId 15770: BeforeJob: (Maybe you meant system() when you said exec()?) 30-May 09:05 pisces-dir JobId 15770: BeforeJob: Statement unlikely to be reached at /usr/local/share/bacula/make_catalog_backup1.pl line 97. 30-May 09:05 pisces-dir JobId 15770: BeforeJob: (Maybe you meant system() when you said exec()?) 30-May 09:05 pisces-dir JobId 15770: BeforeJob: cannot create /backup/bacula.sql: Permission denied 30-May 09:05 pisces-dir JobId 15770: Error: Runscript: BeforeJob returned non-zero status=2. ERR=Child exited with code 2 30-May 09:05 pisces-dir JobId 15770: Error: Bacula pisces-dir 7.0.5 (28Jul14): Build OS: i386-portbld-freebsd9.3 freebsd 9.3-RELEASE-p5 JobId: 15770 Job:BackupCatalog.2015-05-30_09.05.00_22 Backup Level: Full Client: pisces-fd 7.0.5 (28Jul14) i386-portbld-freebsd9.3,freebsd,9.3-RELEASE-p5 FileSet:Catalog 2010-10-06 06:00:00 Pool: BackupCatalog (From Run Pool override) Catalog:MyCatalog (From Client resource) Storage:FileStorageBackupCatalog (From Job resource) Scheduled time: 30-May-2015 09:05:00 Start time: 30-May-2015 09:05:02 End time: 30-May-2015 09:05:03 Elapsed time: 1 sec Priority: 30 FD Files Written: 0 SD Files Written: 0 FD Bytes Written: 0 (0 B) SD Bytes Written: 0 (0 B) Rate: 0.0 KB/s Software Compression: None VSS:no Encryption: no Accurate: no Volume name(s): Volume Session Id: 0 Volume Session Time:0 Last Volume Bytes: 0 (0 B) Non-fatal FD errors:1 SD Errors: 0 FD termination status: SD termination status: Termination:*** Backup Error *** Okay, so I changed all three instances of the 'exec' string to 'system'. I tested the script manually and it succeeded. The next time it ran unattended, an error message was produced as follows: 02-Jun 06:00 pisces-dir JobId 15778: shell command: run BeforeJob /usr/local/share/bacula/make_catalog_backup1.pl MyCatalog 02-Jun 06:03 pisces-dir JobId 15778: BeforeJob: Error while executing postgres dump 02-Jun 06:03 pisces-dir JobId 15778: Error: Runscript: BeforeJob returned non-zero status=1. ERR=Child exited with code 1 02-Jun 06:03 pisces-dir JobId 15778: Error: Bacula pisces-dir 7.0.5 (28Jul14): Build OS: i386-portbld-freebsd9.3 freebsd 9.3-RELEASE-p5 JobId: 15778 Job:BackupCatalog.2015-06-02_06.00.00_32 Backup Level: Full Client: pisces-fd 7.0.5 (28Jul14) i386-portbld-freebsd9.3,freebsd,9.3-RELEASE-p5 FileSet:Catalog 2010-10-06 06:00:00 Pool: BackupCatalog (From Run Pool override) Catalog:MyCatalog (From Client resource) Storage:FileStorageBackupCatalog (From Job resource) Scheduled time: 02-Jun-2015 06:00:00 Start time: 02-Jun-2015 06:03:34 End time: 02-Jun-2015 06:03:34 Elapsed time: 0 secs Priority: 30 FD Files Written: 0 SD Files Written: 0 FD Bytes Written: 0 (0 B) SD Bytes Written: 0 (0 B) Rate: 0.0 KB/s Software Compression: None VSS:no Encryption: no Accurate: no Volume name(s): Volume Session Id: 0 Volume Session Time:0 Last Volume Bytes: 0 (0 B) Non-fatal FD errors:1 SD Errors: 0 FD termination status: SD termination status: Termination:*** Backup Error *** Checking the backup location of the SQL dump shows that the dump was successful: root@pisces:/usr/local/share/bacula# ll /backup total 5718218 .. snip .. -rw--- 1 bacula bacula 5852490083 Jun 2 06:03 bacula.sql .. snip .. root@pisces:/usr/local/share/bacula# I'm not sure what needs to be done next in order to avoid the error
Re: [Bacula-users] Windows client backup error
Hi Fabio, Most of windows client are Virtual machine (Hyper-V). Don’t run any command before job. Thank you, Ankush From: Fábio R. Medeiros [mailto:fab...@unicamp.br] Sent: 02 June 2015 20:05 To: bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] Windows client backup error Hi Ankush, Is this Windows a virtual machine? Most virt. technologies requires special drivers and/or agents. Are you running any command before the job? Regards, Fábio On 02-06-2015 10:57, More, Ankush wrote: Hi Heitor/Ana Few windows client backup successfully with same fileset. So I don’t think wrong in fileset. Thank you, Ankush From: Heitor Faria [mailto:hei...@bacula.com.br] Sent: 01 June 2015 17:23 To: More, Ankush; Ana Emília M. Arruda Cc: bacula-users@lists.sourceforge.netmailto:bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] Windows client backup error Ankush: windows filesets should be with regular dash and usually with capital letters. It is on the Bacula Config. Manual. -- Heitor Medrado de Faria +55 61 82684220 Precisa de treinamento Bacula presencial, telepresencial ou online? Acesse: http://www.bacula.com.br Em 1 de junho de 2015 06:19:32 BRT, More, Ankush ankush.m...@capgemini.commailto:ankush.m...@capgemini.com escreveu: Hi Ana, I have created single file set from drives C: to W: for all windows client. Drives which are failed not present. Please find log: | bacula-dir JobId 1569: No prior Full backup Job record found. | | bacula-dir JobId 1569: No prior or suitable Full backup found in catalog. Doing FULL backup. | | bacula-dir JobId 1569: Start Backup JobId 1569, Job=CTPTSTWIN04-W-BkpTape.2015-05-28_13.50.02_21 | | bacula-dir JobId 1569: Using Device Drive-4 to write. | | ctptstwin04-fd JobId 1569: Generate VSS snapshots. Driver=Win32 VSS, Drive(s)=CDEFGHIJKLMNOPQRSTUVW | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive e:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive f:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive g:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive h:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive i:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive j:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive k:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive l:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive m:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive n:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive o:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive p:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive q:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive r:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive s:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive t:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive u:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive v:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive w:\ failed. | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): System Writer, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): MSDEWriter, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): Registry Writer, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): Event Log Writer, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): COM+ REGDB Writer, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): WMI Writer, State: 0x1 (VSS_WS_STABLE) | | bacula-sd JobId 1569: Elapsed time=00:00:14, Transfer rate=0 Bytes/second | | bacula-dir JobId 1569: Error: Bacula bacula-dir 7.0.5 (28Jul14): Build OS: x86_64-redhat-linux-gnu redhat Enterprise release JobId: 1569 Thank you, Ankush From: Ana Emília M. Arruda [mailto:emiliaarr...@gmail.com] Sent: 30 May 2015 21:28 To: More, Ankush Cc:
Re: [Bacula-users] Windows client backup error
Am 02.06.2015 um 20:35 schrieb More, Ankush: Hi Fabio, Most of windows client are Virtual machine (Hyper-V). Don’t run any command before job. Thank you, Ankush *From:*Fábio R. Medeiros [mailto:fab...@unicamp.br] *Sent:* 02 June 2015 20:05 *To:* bacula-users@lists.sourceforge.net *Subject:* Re: [Bacula-users] Windows client backup error Hi Ankush, Is this Windows a virtual machine? Most virt. technologies requires special drivers and/or agents. Are you running any command before the job? Regards, Fábio On 02-06-2015 10:57, More, Ankush wrote: Hi Heitor/Ana Few windows client backup successfully with same fileset. So I don’t think wrong in fileset. Thank you, Ankush *From:*Heitor Faria [mailto:hei...@bacula.com.br] *Sent:* 01 June 2015 17:23 *To:* More, Ankush; Ana Emília M. Arruda *Cc:* bacula-users@lists.sourceforge.net mailto:bacula-users@lists.sourceforge.net *Subject:* Re: [Bacula-users] Windows client backup error Ankush: windows filesets should be with regular dash and usually with capital letters. It is on the Bacula Config. Manual. -- Heitor Medrado de Faria +55 61 82684220 Precisa de treinamento Bacula presencial, telepresencial ou online? Acesse: http://www.bacula.com.br http://www.bacula.com.br Em 1 de junho de 2015 06:19:32 BRT, More, Ankush ankush.m...@capgemini.com mailto:ankush.m...@capgemini.com escreveu: Hi Ana, I have created single file set from drives C: to W: for all windows client. Drives which are failed not present. Please find log: | bacula-dir JobId 1569: No prior Full backup Job record found. | | bacula-dir JobId 1569: No prior or suitable Full backup found in catalog. Doing FULL backup. | | bacula-dir JobId 1569: Start Backup JobId 1569, Job=CTPTSTWIN04-W-BkpTape.2015-05-28_13.50.02_21 | | bacula-dir JobId 1569: Using Device Drive-4 to write. | | ctptstwin04-fd JobId 1569: Generate VSS snapshots. Driver=Win32 VSS, Drive(s)=CDEFGHIJKLMNOPQRSTUVW | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive e:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive f:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive g:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive h:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive i:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive j:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive k:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive l:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive m:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive n:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive o:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive p:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive q:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive r:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive s:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive t:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive u:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive v:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive w:\ failed. | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): System Writer, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): MSDEWriter, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): Registry Writer, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): Event Log Writer, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): COM+ REGDB Writer, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): WMI Writer, State: 0x1 (VSS_WS_STABLE) | | bacula-sd JobId 1569: Elapsed time=00:00:14, Transfer rate=0 Bytes/second | | bacula-dir JobId 1569: Error: Bacula bacula-dir 7.0.5 (28Jul14): Build OS: x86_64-redhat-linux-gnu redhat
Re: [Bacula-users] Perl 5.20 upgrade breaks make_catalog_backup.pl?
On 06/02/2015 02:01 PM, Doug Sampson wrote: I'm not sure what needs to be done next in order to avoid the error from occurring. Can someone shed light on what I need to do next? Running Bacula 7.0.5 on FreeBSD 9.3. I have in my BackupCatalog job RunBeforeJob = /usr/bin/pg_dump -c -U bacula -f /var/spool/bacula/bacula.sql bacula No perl errors here. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula not recycling all volumes
Hello Marc, Could you post a list media output? Bacula will just recycle a volume when there is no one available for append and it is not possible to create a new one (and you have automatic labeling configured). Best regards, Ana On Tue, Jun 2, 2015 at 5:04 PM, Marc van Houtum m...@dutchsecurity.net wrote: I don't have any jobs with long retention times. Both file and job retention are set at 14 days for every client, while the LastWritten date on the oldest volume is May 10th. The catalog is showing the oldest backup to be from May 19th and according to the JobMedia table in the bacula database there aren't any jobs that use the unused volumes. Would this mean that all the volumes with a LastWritten date older then May 19th should've been recycled by Bacula? I'm really wondering why this hasn't happend. On 2-6-2015 16:28, Josh Fisher wrote: Chances are that one or more jobs on those full volumes has a long retention time, causing them to not be recycled. If only one job is configured with the wrong retention time, then only the volumes that job's data gets written to ceases to recycle, making it appear to be random volumes. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula not recycling all volumes
I don't have any jobs with long retention times. Both file and job retention are set at 14 days for every client, while the LastWritten date on the oldest volume is May 10th. The catalog is showing the oldest backup to be from May 19th and according to the JobMedia table in the bacula database there aren't any jobs that use the unused volumes. Would this mean that all the volumes with a LastWritten date older then May 19th should've been recycled by Bacula? I'm really wondering why this hasn't happend. On 2-6-2015 16:28, Josh Fisher wrote: Chances are that one or more jobs on those full volumes has a long retention time, causing them to not be recycled. If only one job is configured with the wrong retention time, then only the volumes that job's data gets written to ceases to recycle, making it appear to be random volumes. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula not recycling all volumes
Hi Ana, Does this mean that Bacula prefers to create new volumes over recycling old ones? Here's the output, Vol-0001 for example isn't used by any backup jobs looking at the bacula database, as are 15 others: *list media Pool: File +-++---+-++--+--+-+--+---+---+-+ | MediaId | VolumeName | VolStatus | Enabled | VolBytes | VolFiles | VolRetention | Recycle | Slot | InChanger | MediaType | LastWritten | +-++---+-++--+--+-+--+---+---+-+ | 72 | Vol-0001 | Full | 1 | 53,687,079,572 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-17 16:34:38 | | 73 | Vol-0073 | Full | 1 | 53,687,079,571 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-17 23:48:02 | | 74 | Vol-0074 | Full | 1 | 53,687,051,357 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-22 01:09:10 | | 83 | Vol-0083 | Full | 1 | 53,687,079,336 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-29 02:07:13 | | 84 | Vol-0084 | Full | 1 | 53,687,079,650 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-29 04:02:07 | | 85 | Vol-0085 | Full | 1 | 53,687,038,466 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-30 00:20:19 | | 86 | Vol-0086 | Full | 1 | 53,687,072,062 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-31 00:43:51 | | 87 | Vol-0087 | Full | 1 | 53,687,078,955 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-31 03:31:16 | | 88 | Vol-0088 | Full | 1 | 53,687,079,760 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-31 05:46:51 | | 89 | Vol-0089 | Full | 1 | 53,687,079,537 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-31 07:12:04 | | 99 | Vol-0099 | Full | 1 | 53,687,035,899 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-14 00:56:20 | | 100 | Vol-0100 | Full | 1 | 53,687,079,400 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-31 08:30:19 | | 101 | Vol-0101 | Full | 1 | 53,687,079,499 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-31 09:50:03 | | 102 | Vol-0102 | Full | 1 | 53,687,079,535 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-31 11:24:41 | | 103 | Vol-0103 | Full | 1 | 53,687,079,562 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-31 13:12:54 | | 106 | Vol-0104 | Full | 1 | 53,687,079,466 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-10 19:35:51 | | 107 | Vol-0107 | Full | 1 | 53,687,061,994 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-17 00:28:01 | | 108 | Vol-0108 | Full | 1 | 53,687,033,748 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-17 03:09:56 | | 109 | Vol-0109 | Full | 1 | 53,687,079,058 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-17 06:36:13 | | 110 | Vol-0110 | Full | 1 | 53,687,079,593 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-17 07:44:40 | | 111 | Vol-0111 | Full | 1 | 53,687,079,599 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-17 08:53:21 | | 112 | Vol-0112 | Full | 1 | 53,687,079,515 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-17 10:07:45 | | 113 | Vol-0113 | Full | 1 | 53,687,079,470 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-17 11:35:35 | | 114 | Vol-0114 | Full | 1 | 53,687,079,758 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-17 13:34:05 | | 115 | Vol-0115 | Full | 1 | 53,687,079,672 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-17 15:03:29 | | 116 | Vol-0116 | Full | 1 | 53,687,028,512 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-19 00:32:57 | | 117 | Vol-0117 | Full | 1 | 53,687,079,451 | 12 |1,209,600 | 1 |0 | 0 | Disk | 2015-05-24 16:16:57 | | 118 | Vol-0118 | Full | 1 | 53,687,079,355 | 12 |1,209,600 | 1 |0 |
Re: [Bacula-users] Use multiple HDDs to backup files to
On 6/1/2015 5:21 PM, Ana Emília M. Arruda wrote:
Hello,
Maybe you could use the virtual autochanger resource:
This will not work as expected. If the ArchiveDevice in the two Device
resources specifies different directories (mountpoints), then the two
Device resources cannot have the same MediaType. This is because Bacula
expects to be able to load any volume that has MediaType=File into any
Device having that same MediaType, and a volume in /sdb1/bacula/backup
cannot be loaded into Device vDrive-1, not can a volume in
/bacula/backup be loaded into vDrive-2.
To use multiple HDDs as a single autochanger, you must:
Define each Device resource to have a unique MediaType, if using the
native virtual autochanger
or
Use vchanger, which is designed for using multiple removable HDDs (See
http://sourceforge.net/projects/vchanger/)
or
Combine the HDD partitions using LVM2 or md so that there is only a
single mountpoint
.
bacula-sd.conf:
Autochanger {
Name = VChanger
Changer Device = /dev/null
Changer Command = # versão 5.2.6. For 7.0.5 version, use /dev/null
Device = vDrive-1, vDrive-2
}
Device {
Name = vDrive-1
Drive Index = 0
Device Type = File
Media Type = File
Archive Device = /bacula/backup
...
}
Device {
Name = vDrive-2
Drive Index = 1
Device Type = File
Media Type = File
Archive Device = /sdb1/bacula/backup # is this your mount point?
...
}
In your bacula-dir.conf (or wherever you have your storage definiton
for director):
Storage {
Name = MyVirtualAutochanger
Address = X.X.X.X
SDPort = 9103
Password = xx
Device = VChanger
Media Type = File
Maximum Concurrent Jobs = XX
Autochanger=yes
}
Best regards,
Ana
On Wed, May 20, 2015 at 1:32 PM, SPQR bacula-fo...@backupcentral.com
mailto:bacula-fo...@backupcentral.com wrote:
I would like to set up bacula - well, my first steps have been
successful.
All my backups are written to /bacula/backup. But / has only
900GB. So I want bacula to write to /sdb1/bacula/backup, too.
/sdb1 has another 950GB of space. The sum of available
backup-space should be 1850GB HDD:
Well, I got the following config of /etc/bacula/bacula-sd.conf:
Storage { # definition of myself
Name = backup-sd
SDPort = 9103 # Director's port
WorkingDirectory = /var/lib/bacula
Pid Directory = /var/run/bacula
Maximum Concurrent Jobs = 20
SDAddress = backup.example.com http://backup.example.com
}
Director {
Name = backup-dir
Password = doyoureallywanttoknow
}
Device {
Name = FileStorage
Media Type = File
Archive Device = /bacula/backup
LabelMedia = yes; # lets Bacula label
unlabeled media
Random Access = Yes;
AutomaticMount = yes; # when device opened, read it
RemovableMedia = no;
AlwaysOpen = no;
}
Okay - now I would like to add another device. I guess I could
just add a second entry like this:
Device {
Name = FileStorage
Media Type = File
Archive Device = /sdb1/bacula/backup
LabelMedia = yes; # lets Bacula label
unlabeled media
Random Access = Yes;
AutomaticMount = yes; # when device opened, read it
RemovableMedia = no;
AlwaysOpen = no;
}
?
Do I have to change something else so that bacula is able to write
more than 900GB - if the first 900GB are full it should switch
to the second hdd.
Thank you very much :-)
+--
|This was sent by r...@ehrenwert.it mailto:r...@ehrenwert.it via
Backup Central.
|Forward SPAM to ab...@backupcentral.com
mailto:ab...@backupcentral.com.
+--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
mailto:Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Windows client backup error
Hi Heitor/Ana Few windows client backup successfully with same fileset. So I don’t think wrong in fileset. Thank you, Ankush From: Heitor Faria [mailto:hei...@bacula.com.br] Sent: 01 June 2015 17:23 To: More, Ankush; Ana Emília M. Arruda Cc: bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] Windows client backup error Ankush: windows filesets should be with regular dash and usually with capital letters. It is on the Bacula Config. Manual. -- Heitor Medrado de Faria +55 61 82684220 Precisa de treinamento Bacula presencial, telepresencial ou online? Acesse: http://www.bacula.com.br Em 1 de junho de 2015 06:19:32 BRT, More, Ankush ankush.m...@capgemini.com escreveu: Hi Ana, I have created single file set from drives C: to W: for all windows client. Drives which are failed not present. Please find log: | bacula-dir JobId 1569: No prior Full backup Job record found. | | bacula-dir JobId 1569: No prior or suitable Full backup found in catalog. Doing FULL backup. | | bacula-dir JobId 1569: Start Backup JobId 1569, Job=CTPTSTWIN04-W-BkpTape.2015-05-28_13.50.02_21 | | bacula-dir JobId 1569: Using Device Drive-4 to write. | | ctptstwin04-fd JobId 1569: Generate VSS snapshots. Driver=Win32 VSS, Drive(s)=CDEFGHIJKLMNOPQRSTUVW | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive e:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive f:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive g:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive h:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive i:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive j:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive k:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive l:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive m:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive n:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive o:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive p:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive q:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive r:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive s:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive t:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive u:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive v:\ failed. | | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive w:\ failed. | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): System Writer, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): MSDEWriter, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): Registry Writer, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): Event Log Writer, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): COM+ REGDB Writer, State: 0x1 (VSS_WS_STABLE) | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): WMI Writer, State: 0x1 (VSS_WS_STABLE) | | bacula-sd JobId 1569: Elapsed time=00:00:14, Transfer rate=0 Bytes/second | | bacula-dir JobId 1569: Error: Bacula bacula-dir 7.0.5 (28Jul14): Build OS: x86_64-redhat-linux-gnu redhat Enterprise release JobId: 1569 Thank you, Ankush From: Ana Emília M. Arruda [mailto:emiliaarr...@gmail.com] Sent: 30 May 2015 21:28 To: More, Ankush Cc: bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] Windows client backup error Hi Ankush, On Sat, May 30, 2015 at 9:32 AM, More, Ankush ankush.m...@capgemini.commailto:ankush.m...@capgemini.com wrote: Hi Ana, Yes, we have few windows client 32bit. Do you mean 32 bit clients will not support on Bacula server with 64 bit? No. I thought that you had bacula client 32-bit installed on windows 64-bit. Do you get results for status client from bconsole? From the job output, It seems that your storage daemon do not receive response from the client and the job is cancelled because of an error in the client
Re: [Bacula-users] Bacula not recycling all volumes
Chances are that one or more jobs on those full volumes has a long retention time, causing them to not be recycled. If only one job is configured with the wrong retention time, then only the volumes that job's data gets written to ceases to recycle, making it appear to be random volumes. On 6/2/2015 9:17 AM, Marc van Houtum wrote: On 2-6-2015 14:43, Marc van Houtum wrote: If i compare the resultst to the volume files on the filesystem, I can see that there are currently 16 volume files not in use at the moment. Does anyone have any idea as to why these aren't being recycled? I've attached my bacula-dir.conf. Forgot to add, but the unused volumes are listed under 'list volumes' in the console with VolStatus 'full'. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Windows client backup error
Few windows client backup successfully with same fileset. So I don’t think wrong in fileset. Hello Ankush: can you output a estimate listing for this job? Do this volumes really exist at this Windows Server? If your FileSet is right it maybe indicate a VSS Windows service problem. You can try to restart it or make verifications like it's correctness on Windows Register files. Your Windows Bacula client architeture should maches OS one. A thing to consider is if this Home ServerEnterprise Edition Service VSS really exists and if its limited in comparison to other Windows Server distributions. Anyway you can also disable Bacula VSS usage at the FileSet, for contingency purposes. Regards, === Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems Certified Administrator II 15 a 26 de junho: Treinamento Telepresencial Bacula: http://www.bacula.com.br/?p=2174 61 8268-4220 Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk: heitorfa...@gmail.com Thank you, Ankush From: Heitor Faria [mailto:hei...@bacula.com.br] Sent: 01 June 2015 17:23 To: More, Ankush; Ana Emília M. Arruda Cc: bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] Windows client backup error Ankush: windows filesets should be with regular dash and usually with capital letters. It is on the Bacula Config. Manual. -- Heitor Medrado de Faria +55 61 82684220 Precisa de treinamento Bacula presencial, telepresencial ou online? Acesse: http://www.bacula.com.br Em 1 de junho de 2015 06:19:32 BRT, More, Ankush ankush.m...@capgemini.com escreveu: Hi Ana, I have created single file set from drives C: to W: for all windows client. Drives which are failed not present. Please find log: | bacula-dir JobId 1569: No prior Full backup Job record found. | bacula-dir JobId 1569: No prior or suitable Full backup found in catalog. Doing | FULL backup. | bacula-dir JobId 1569: Start Backup JobId 1569, | Job=CTPTSTWIN04-W-BkpTape.2015-05-28_13.50.02_21 | bacula-dir JobId 1569: Using Device Drive-4 to write. | ctptstwin04-fd JobId 1569: Generate VSS snapshots. Driver=Win32 VSS, | Drive(s)=CDEFGHIJKLMNOPQRSTUVW | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive e:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive f:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive g:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive h:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive i:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive j:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive k:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive l:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive m:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive n:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive o:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive p:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive q:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive r:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive s:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive t:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive u:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive v:\ | failed. | ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot of drive w:\ | failed. | | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): System Writer, State: | 0x1 (VSS_WS_STABLE) | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): MSDEWriter, State: 0x1 | (VSS_WS_STABLE) | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): Registry Writer, | State: 0x1 (VSS_WS_STABLE) | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): Event Log Writer, | State: 0x1 (VSS_WS_STABLE) | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): COM+ REGDB Writer, | State: 0x1 (VSS_WS_STABLE) | ctptstwin04-fd JobId 1569: VSS Writer (BackupComplete): WMI Writer, State: 0x1 | (VSS_WS_STABLE) | bacula-sd JobId 1569: Elapsed time=00:00:14, Transfer rate=0 Bytes/second | bacula-dir JobId 1569: Error: Bacula bacula-dir 7.0.5 (28Jul14): Build OS: x86_64-redhat-linux-gnu redhat Enterprise release JobId: 1569 Thank you, Ankush From: Ana Emília M. Arruda
[Bacula-users] Bacula not recycling all volumes
Hello,
We seem to be having an issue with our Bacula enviroment where some
volumes are not being recycled properly. This is causing our disk based
storage to fill up with unused volume files. Some volumes are being
recycled though which is why I'm having a hard time wrapping my head
around this issue.
I'm using the following SQL query in the bacula database to check which
Volumes are in use:
select DISTINCT(Media.VolumeName) AS VolumeName FROM JobMedia, Media
WHERE JobMedia.MediaID=Media.MediaID ORDER BY VolumeName;
If i compare the resultst to the volume files on the filesystem, I can
see that there are currently 16 volume files not in use at the moment.
Does anyone have any idea as to why these aren't being recycled? I've
attached my bacula-dir.conf.
Many thanks in advance.
Best regards,
Marc
#
# Director configuration
#
Director {# define myself
Name = file1.mycompany.net-dir
DIRport = 9101# where we listen for UA connections
QueryFile = /usr/local/share/bacula/query.sql
WorkingDirectory = /var/db/bacula
PidDirectory = /var/run
Maximum Concurrent Jobs = 20
Password = No32vQp0JxdXx4r4PgRus5vnhj4JTD1eDPrRRAsUzyUw # Console
password
Messages = Daemon
}
#
# Job definition templates
#
JobDefs {
Name = DefaultJob
Type = Backup
Level = Incremental
Client = file1.mycompany.net-fd
FileSet = OwnCloud
Schedule = WeeklyCycle
Storage = File1
Messages = Standard
Pool = File
Spool Data = no
Spool Attributes = yes
Priority = 10
Write Bootstrap = /var/db/bacula/%c.bsr
Reschedule On Error = yes
Reschedule Interval = 1 hour
Reschedule Times = 2
}
#
# Backup jobs
#
Job {
Name = File1
JobDefs = DefaultJob
Level = Full
FileSet=File1
Schedule = WeeklyCycleAfterBackup
RunBeforeJob = /usr/local/share/bacula/make_catalog_backup.pl MyCatalog
RunAfterJob = /bin/rm /usr/local/var/lib/bacula/bacula.sql
Write Bootstrap = /var/db/bacula/%n.bsr
Priority = 11 # run after main backup
}
Job {
Name = BBM
Client = bbm.mycompany.net-fd
JobDefs = DefaultJob
ClientRunBeforeJob = /usr/local/sbin/dump_db.sh
ClientRunAfterJob = /usr/local/sbin/delete_db.sh
}
Job {
Name = Cloud1
Client = cloud1.mycompany.net-fd
JobDefs = DefaultJob
ClientRunBeforeJob = /usr/local/sbin/dump_db.sh
ClientRunAfterJob = /usr/local/sbin/delete_db.sh
}
Job {
Name = RestoreFiles
Type = Restore
Client=file1.mycompany.net-fd
FileSet=OwnCloud
Storage = File1
Pool = File
Messages = Standard
Where = /tmp/bacula-restores/
}
#
# Fileset definitions
#
FileSet {
Name = OwnCloud
Include {
Options {
signature = MD5
compression = LZO
}
File = /root/
File = /etc/
File = /usr/local/
File = /var/www/
File = /data1/
File = /tmp/mysql.all-databases.sql.gz
}
}
FileSet {
Name = File1
Include {
Options {
signature = MD5
compression = LZO
}
File = /usr/local/var/lib/bacula/bacula.sql
File = /var/db/bacula/
File = /usr/local/etc/
File = /etc/
File = /root/
}
}
#
# Schedules
#
Schedule {
Name = WeeklyCycle
Run = Full sun at 00:00
Run = Differential mon-sat at 00:00
}
Schedule {
Name = WeeklyCycleAfterBackup
Run = Full sun-sat at 01:00
}
#
# Client definitions
#
Client {
Name = file1.mycompany.net-fd
Address = file1.mycompany.net
FDPort = 9102
Catalog = MyCatalog
Password = 43Ugukt7sM9z8IYC3D0QhcssdYzseipF/qLpsn8YEJnE
File Retention = 14 days# 14 days
Job Retention = 14 days # 14 days
AutoPrune = yes # Prune expired Jobs/Files
}
Client {
Name = bbm.mycompany.net-fd
Address = bbm.mycompany.net
FDPort = 9102
Catalog = MyCatalog
Password = 43Ugukt7sM9z8IYC3D0QhcssdYzseipF/qLpsn8YEJnE2
File Retention = 14 days
Job Retention = 14 days
AutoPrune = yes
}
Client {
Name = cloud1.mycompany.net-fd
Address = cloud1.mycompany.net
FDPort = 9102
Catalog = MyCatalog
Password = Fki1Lu/2eVq0tTbstY1uhYvSNgSEypw4MmHQJoyDwcKJ
File Retention = 14 days
Job Retention = 14 days
AutoPrune = yes
}
#
# Definition of file Virtual Autochanger device
#
Storage {
Name = File1
Address = file1.mycompany.net# N.B. Use a fully qualified
name here
SDPort = 9103
Password = FNOqO5C3h9QGMnJhQtVSebJjabCQ5GjgEzwd8dKj9Cy4
Device = File1-Disk1
Media Type = Disk
Maximum Concurrent Jobs = 10
}
#
# Catalog service
#
Catalog {
Name = MyCatalog
dbname = bacula; dbuser = bacula; dbpassword = qskjf8wjdjdxj4
}
# Reasonable message delivery -- send most everything to email address
# and to the console
Messages {
Name = Standard
#
# NOTE! If you send to two email or more email addresses, you will need
# to replace the %r in the from field (-f part) with a single valid
# email address in both the mailcommand and the operatorcommand.
# What this does is, it sets the email address that emails would display
Re: [Bacula-users] Bacula not recycling all volumes
On 2-6-2015 14:43, Marc van Houtum wrote: If i compare the resultst to the volume files on the filesystem, I can see that there are currently 16 volume files not in use at the moment. Does anyone have any idea as to why these aren't being recycled? I've attached my bacula-dir.conf. Forgot to add, but the unused volumes are listed under 'list volumes' in the console with VolStatus 'full'. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Use multiple HDDs to backup files to
Do you have some specific reason to need to have these two volumes separate?
You might be best off using LVM to create a single logical drive. That
would certainly be a more flexible solution long term.
Bryn
On 2015-05-20 09:32 AM, SPQR wrote:
I would like to set up bacula - well, my first steps have been successful.
All my backups are written to /bacula/backup. But / has only 900GB. So I want
bacula to write to /sdb1/bacula/backup, too. /sdb1 has another 950GB of
space. The sum of available backup-space should be 1850GB HDD:
Well, I got the following config of /etc/bacula/bacula-sd.conf:
Storage { # definition of myself
Name = backup-sd
SDPort = 9103 # Director's port
WorkingDirectory = /var/lib/bacula
Pid Directory = /var/run/bacula
Maximum Concurrent Jobs = 20
SDAddress = backup.example.com
}
Director {
Name = backup-dir
Password = doyoureallywanttoknow
}
Device {
Name = FileStorage
Media Type = File
Archive Device = /bacula/backup
LabelMedia = yes; # lets Bacula label unlabeled media
Random Access = Yes;
AutomaticMount = yes; # when device opened, read it
RemovableMedia = no;
AlwaysOpen = no;
}
Okay - now I would like to add another device. I guess I could just add a
second entry like this:
Device {
Name = FileStorage
Media Type = File
Archive Device = /sdb1/bacula/backup
LabelMedia = yes; # lets Bacula label unlabeled media
Random Access = Yes;
AutomaticMount = yes; # when device opened, read it
RemovableMedia = no;
AlwaysOpen = no;
}
?
Do I have to change something else so that bacula is able to write more than
900GB - if the first 900GB are full it should switch to the second hdd.
Thank you very much :-)
+--
|This was sent by r...@ehrenwert.it via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Use multiple HDDs to backup files to
I particularly do not like the idea of having separate volumes of the same
media type into two different mount points, but I know people that are
configuring this way. So I decided to do some tests and see what really was
happening. No issues. Instead I prefer the LVM solution.
On Tue, Jun 2, 2015 at 2:12 PM, Bryn Hughes li...@nashira.ca wrote:
Do you have some specific reason to need to have these two volumes
separate?
You might be best off using LVM to create a single logical drive. That
would certainly be a more flexible solution long term.
Bryn
On 2015-05-20 09:32 AM, SPQR wrote:
I would like to set up bacula - well, my first steps have been
successful.
All my backups are written to /bacula/backup. But / has only 900GB. So I
want bacula to write to /sdb1/bacula/backup, too. /sdb1 has another 950GB
of space. The sum of available backup-space should be 1850GB HDD:
Well, I got the following config of /etc/bacula/bacula-sd.conf:
Storage { # definition of myself
Name = backup-sd
SDPort = 9103 # Director's port
WorkingDirectory = /var/lib/bacula
Pid Directory = /var/run/bacula
Maximum Concurrent Jobs = 20
SDAddress = backup.example.com
}
Director {
Name = backup-dir
Password = doyoureallywanttoknow
}
Device {
Name = FileStorage
Media Type = File
Archive Device = /bacula/backup
LabelMedia = yes; # lets Bacula label unlabeled
media
Random Access = Yes;
AutomaticMount = yes; # when device opened, read it
RemovableMedia = no;
AlwaysOpen = no;
}
Okay - now I would like to add another device. I guess I could just add
a second entry like this:
Device {
Name = FileStorage
Media Type = File
Archive Device = /sdb1/bacula/backup
LabelMedia = yes; # lets Bacula label unlabeled
media
Random Access = Yes;
AutomaticMount = yes; # when device opened, read it
RemovableMedia = no;
AlwaysOpen = no;
}
?
Do I have to change something else so that bacula is able to write more
than 900GB - if the first 900GB are full it should switch to the second
hdd.
Thank you very much :-)
+--
|This was sent by r...@ehrenwert.it via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Use multiple HDDs to backup files to
I particularly do not like the idea of having separate volumes of the same
media
type into two different mount points, but I know people that are configuring
this way. So I decided to do some tests and see what really was happening. No
issues. Instead I prefer the LVM solution.
The point is to make sure severall disks are being write at the same time (load
balance) and more resiliency since a dead LVM is a terrible situation.
But I kind of agree with you: I don't know why to use different Media Types for
compatible media.
Regards,
===
Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems Certified
Administrator II
15 a 26 de junho: Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 8268-4220
Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk: heitorfa...@gmail.com
On Tue, Jun 2, 2015 at 2:12 PM, Bryn Hughes li...@nashira.ca wrote:
Do you have some specific reason to need to have these two volumes separate?
You might be best off using LVM to create a single logical drive. That
would certainly be a more flexible solution long term.
Bryn
On 2015-05-20 09:32 AM, SPQR wrote:
I would like to set up bacula - well, my first steps have been successful.
All my backups are written to /bacula/backup. But / has only 900GB. So I
want
bacula to write to /sdb1/bacula/backup, too. /sdb1 has another 950GB of
space.
The sum of available backup-space should be 1850GB HDD:
Well, I got the following config of /etc/bacula/bacula-sd.conf:
Storage { # definition of myself
Name = backup-sd
SDPort = 9103 # Director's port
WorkingDirectory = /var/lib/bacula
Pid Directory = /var/run/bacula
Maximum Concurrent Jobs = 20
SDAddress = backup.example.com
}
Director {
Name = backup-dir
Password = doyoureallywanttoknow
}
Device {
Name = FileStorage
Media Type = File
Archive Device = /bacula/backup
LabelMedia = yes; # lets Bacula label unlabeled media
Random Access = Yes;
AutomaticMount = yes; # when device opened, read it
RemovableMedia = no;
AlwaysOpen = no;
}
Okay - now I would like to add another device. I guess I could just add a
second
entry like this:
Device {
Name = FileStorage
Media Type = File
Archive Device = /sdb1/bacula/backup
LabelMedia = yes; # lets Bacula label unlabeled media
Random Access = Yes;
AutomaticMount = yes; # when device opened, read it
RemovableMedia = no;
AlwaysOpen = no;
}
?
Do I have to change something else so that bacula is able to write more than
900GB - if the first 900GB are full it should switch to the second hdd.
Thank you very much :-)
+--
|This was sent by r...@ehrenwert.it via Backup Central.
|Forward SPAM to ab...@backupcentral.com .
+--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
