Re: [Bacula-users] Quantum LTO-7 HH

2017-07-11 Thread John Drescher
Thanks.

John

On Mon, Jul 10, 2017 at 1:42 PM, Jim Richardson  wrote:
> I am using one successfully in a Dell TL1000 tape library. Be sure to use
> the latest version of Bacula, factory reset your drive and library when you
> receive it, and use the LTO-4 configuration at the bottom of the
> Bacula-SD.conf
>
>
>
> Sent from my Android phone using TouchDown (www.symantec.com)
>
>
> -Original Message-
> From: John Drescher [dresche...@gmail.com]
> Received: Monday, 10 Jul 2017, 8:06AM
> To: Bacula Users [Bacula-users@lists.sourceforge.net]
> Subject: [Bacula-users] Quantum LTO-7 HH
>
> Anyone using a Quantum LTO-7 HH drive with bacula? I am looking to
> purchase one soon at work.
>
> Thanks,
> John
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
> CONFIDENTIALITY: This email (including any attachments) may contain
> confidential, proprietary and privileged information, and unauthorized
> disclosure or use is prohibited. If you received this email in error, please
> notify the sender and delete this email from your system. Thank you.



-- 
John M. Drescher

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Problem labeling tapes dir and sd on different machines

2017-07-11 Thread Kern Sibbald

  
  
Hello,
First, I don't think you really want to do the add command,
  unless you are going to manually label all those volumes.
Normally, if I remember correctly, when automatic labeling works,
  Bacula will not only create a new volume, but it will label it,
  and put the entry in the catalog.  You should confirm this.
One thing you are definitely doing incorrectly is giving volumes
  in two pools the same prefix.  Bacula cannot have the same volume
  in two pools.  So you need to have different prefixes (other than
  just "Vol-") for each pool.  One suggestion would be to use the
  MediaType as the prefix.  That way, you would also know by the
  Volume name, what pool it belongs to.
It is not clear why you have two pools, because the Volumes are
  all mixed in the same physical directory.  There is no problem
  with that, but what is the purpose of two pools ?

An "llist Volumes" may give you a better idea of what is going
  on.

Best regards,
Kern


On 07/11/2017 04:13 PM, Jose Alberto
  wrote:


  

  

  

  Hi. 

  
  When i use SD with Disk (SD, USB, NAS, SAN, etc).  
  

I add volumen with the command:   add    

  
  And i add for example   50 volumen. 
  
  

Because (i view) the  command label only add 1 volumen. 

  
  i use Label only when my SD is a Tape Library. 
  
  

Note:  you have 2 Autochanger:  FileChgr2 and  FileChgr2

  

  

  

You must add volumen you should  on the 2
  Autochanger. 
  



Sorry for my English. 





  

  

  
  
On Tue, Jul 11, 2017 at 3:44 AM, bacula
  
  wrote:
  

  

  Hi
  all,

  my
  current setup is director on a vm and sd is
  running on a qnap nas. Everything
  went fine runing all daemons on a single virtual
  machine writing to an nfs mount of the qnap.

  To
  improve performance in particualr for the bigger
  jobs we installed bacula directly on qnap to have
  the sd running there. Now we got the follwing
  problem.

  Autolabeling
  doesn't work anymore. After starting a job I got
  the following message:

  

  From:
  root@bacula
  
 Sent:
  Mon Jul 10 00:05:19 2017

  To: admin
 Cc: 

  Subject: Bacula: Intervention needed for
  shares.2017-07-09_23.05.00_13
 Auto
  forwarded by a rule


  10-Jul 00:05 qnap4-sd JobId 1: Job
  shares.2017-07-09_23.05.00_13 is waiting. Cannot
  find any appendable volumes.

  Please use the "label" command to create a new
  Volume for:
    
  Storage:  "FileChgr1-Dev2" (/opt/bacula/tapes)
    
  Pool: File
    
  Media type:   File1
  

  That
  message never apperead on the single machine
  setup. The labels were properly autolabeled.
Nevertheless
  I tried to label a tape. 


  user@bacula:~#
  bconsole
Connecting
  to Director localhost:9101
  1000 OK: 1 bacula-dir Version: 7.0.5 (28 July
  2014)
Enter
  a period to cancel a command.
*label
Automatically
   

Re: [Bacula-users] Problem labeling tapes dir and sd on different machines

2017-07-11 Thread Jose Alberto
Hi.

When i use SD with Disk (SD, USB, NAS, SAN, etc).

I add volumen with the command:   add

And i add for example   50 volumen.


Because (i view) the  command label only add 1 volumen.

i use Label only when my SD is a Tape Library.


Note:  you have 2 Autochanger:  FileChgr2 and  FileChgr2


You must add volumen you should  on the 2 Autochanger.


Sorry for my English.



On Tue, Jul 11, 2017 at 3:44 AM, bacula  wrote:

> Hi all,
>
> my current setup is director on a vm and sd is running on a qnap nas. 
> Everything
> went fine runing all daemons on a single virtual machine writing to an nfs
> mount of the qnap.
>
> To improve performance in particualr for the bigger jobs we installed
> bacula directly on qnap to have the sd running there. Now we got the
> follwing problem.
>
> Autolabeling doesn't work anymore. After starting a job I got the
> following message:
>
>
> From: root@bacula   >
> Sent: Mon Jul 10 00:05:19 2017
> To: admin
> Cc:
> Subject: Bacula: Intervention needed for shares.2017-07-09_23.05.00_13
> Auto forwarded by a rule
>
> 10-Jul 00:05 qnap4-sd JobId 1: Job shares.2017-07-09_23.05.00_13 is
> waiting. Cannot find any appendable volumes.
> Please use the "label" command to create a new Volume for:
> Storage:  "FileChgr1-Dev2" (/opt/bacula/tapes)
> Pool: File
> Media type:   File1
>
>
> That message never apperead on the single machine setup. The labels were
> properly autolabeled.
> Nevertheless I tried to label a tape.
>
> user@bacula:~# bconsole
> Connecting to Director localhost:9101
> 1000 OK: 1 bacula-dir Version: 7.0.5 (28 July 2014)
> Enter a period to cancel a command.
> *label
> Automatically selected Catalog: MyCatalog
> Using Catalog "MyCatalog"
> The defined Storage resources are:
>  1: File1
>  2: File2
> Select Storage resource (1-2): 1
> Enter new Volume name: TestVolume001
> Defined Pools:
>  1: Default
>  2: File
>  3: Scratch
> Select the Pool (1-3): 2
> Connecting to Storage daemon File1 at qnap4.jws.local:9103 ...
> Sending label command for Volume "TestVolume001" Slot 0 ...
> 3000 OK label. VolBytes=195 VolABytes=0 VolType=1 Volume="TestVolume001"
> Device="FileChgr1-Dev1" (/opt/bacula/tapes)
> Label command failed for Volume TestVolume001.
> Do not forget to mount the drive!!!
>
>
>
> SD creates the volume properly (as fare as I can see in the fielsystem)
> but director doesn't recognize it.
>
>
> Can someone please point me to the right direction how to get it work?
>
>
> cheers
>
> Holger
>
>
> xxx
>
> bacula-dir.conf
>
> xxx
>
> Director {# define myself
>   Name = bacula-dir
>   DIRport = 9101# where we listen for UA connections
>   QueryFile = "/etc/bacula/scripts/query.sql"
>   WorkingDirectory = "/var/lib/bacula"
>   PidDirectory = "/var/run"
>   Maximum Concurrent Jobs = 20
>   Password = "xyz" # Console password
>   Messages = Daemon
> }
>
> JobDefs {
>   Name = "DefaultJob"
>   Type = Backup
>   Level = Incremental
>   Client = bacula-fd
>   FileSet = "Full Set"
>   Schedule = "WeeklyCycle"
>   Storage = File1
>   Messages = Standard
>   Pool = File
>   SpoolAttributes = yes
>   SpoolData = yes
>   Priority = 10
>   Write Bootstrap = "/var/lib/bacula/working/%c.bsr"
> }
>
> Job {
>   Name = "BackupCatalog"
>   JobDefs = "DefaultJob"
>   Level = Full
>   FileSet="Catalog"
>   Schedule = "WeeklyCycleAfterBackup"
>RunBeforeJob = "/etc/bacula/scripts/make_catalog_backup.pl MyCatalog"
>RunAfterJob  = "/etc/bacula/scripts/delete_catalog_backup"
>   Write Bootstrap = "/etc/bacula/working/%n.bsr"
>   Priority = 11   # run after main backup
> }
>
> Job {
>   Name = "RestoreFiles"
>   Type = Restore
>   Client= bacula-fd
>   Storage = File1
> # The FileSet and Pool directives are not used by Restore Jobs
> # but must not be removed
>   FileSet="Full Set"
>   Pool = File
>   Messages = Standard
>   Where = /nonexistant/path/to/file/archive/dir/bacula-restores
> }
>
> Job {
>   Name = samba4
>   JobDefs = DefaultJob
>   Client = samba4-fd
>   FileSet = samba4
>   Storage = File1
>   Messages = Standard
>   Client Run Before Job = /root/bin/backups
>   Enabled = no
> }
>
> # List of files to be backed up
> FileSet {
>   Name = "Full Set"
>   Include {
> Options {
>   signature = MD5
> }
> File = /opt/sbin
>   }
>   Exclude {
> File = /opt/bacula/working
> File = /opt/bacula/tmp
> File = /proc
> File = /tmp
> File = /sys
> File = /.journal
> File = /.fsck
>   }
> }
>
> FileSet {
>   Name = samba4
>   Include {
>   File = /opt
>   File = /srv/home
>  File = /srv/profiles
>  File = /srv/backup
>  Options {
> Signature = MD5
> Compression = GZIP5
> }
>   }
> }
>
> Schedule {
>   Name = 

Re: [Bacula-users] Bacula largest installations ever

2017-07-11 Thread Simone Caronni
I had the chance to manage the following:

- Around 600 clients
- 15 different storage daemons with disk storage or automated tape libraries
- Automated laptop backups based on the site where they are connected
(basically triggering backups to the closest SD storage daemon based on
their DNS record as updated in Active Directory)
- Cross-datacenter consolidations for jobs
- All Red Hat/Fedora and Windows systems. 1 very old client on SCO UNIX.


Regards,
--Simone




On Mon, Jul 10, 2017 at 9:21 PM, Roberts, Ben 
wrote:

> I manage a sizeable Bacula installation:
>
> ~70 FD
>
> ~10,000 volumes
>
> ~2,000 jobs currently in catalog of 45,000 jobs (lifetime for this
> instance of director/catalog)
>
> ~4.8 PB currently tracked by jobs in catalog
>
> ~30.1TB largest single job (which took 3d 9h on last run)
>
>
>
> This workload previously served fine by a single director/catalog
> open-source edition for many years (running on mysql until the beginning of
> this year, since switched to postgres but not because of any performance
> issues)
>
> Maintaining this workload currently requires less than 1 person-day of
> effort per month (after a fair amount of tuning)
>
>
>
> Regards,
>
> Ben Roberts
>
>
>
> *From:* Jason Voorhees [mailto:jvoorhe...@gmail.com]
> *Sent:* 10 July 2017 17:18
> *To:* bacula-users@lists.sourceforge.net
> *Subject:* [Bacula-users] Bacula largest installations ever
>
>
>
> ** This is an external e-mail. Please treat attachments and links as
> potentially dangerous. **
>
>
> Hello bats:
>
> I was wondering if you can share any of your biggest Bacula
> deployments you ever made. I mean anything like "I use Bacula to
> backup thousands of desktops/servers", or "I have a backup
> infrastructure with Bacula for more than 30TB of data being backed
> up".
>
> It's just that I want to know how robust and scalable Bacula might be
> compared to other competitors such as TSM, HP Dataprotector, Backup
> Exec, among others.
>
> This is because one of my customer want to backup more than 2,000
> desktops and a backup software is under evaluation.
>
> Thanks in advance for your comments, if any.
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
> --
> This email and any files transmitted with it contain confidential and
> proprietary information and is solely for the use of the intended
> recipient. If you are not the intended recipient please return the email to
> the sender and delete it from your computer and you must not use, disclose,
> distribute, copy, print or rely on this email or its contents. This
> communication is for informational purposes only. It is not intended as an
> offer or solicitation for the purchase or sale of any financial instrument
> or as an official confirmation of any transaction. Any comments or
> statements made herein do not necessarily reflect those of GSA Capital. GSA
> Capital Partners LLP is authorised and regulated by the Financial Conduct
> Authority and is registered in England and Wales at Stratton House, 5
> Stratton Street, London W1J 8LA, number OC309261. GSA Capital Services
> Limited is registered in England and Wales at the same address, number
> 5320529.
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>


-- 
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).

http://xkcd.com/229/
http://negativo17.org/
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] Problem labeling tapes dir and sd on different machines

2017-07-11 Thread bacula
Hi all,

my current setup is director on a vm and sd is running on a qnap nas. 
Everything went fine runing all daemons on a single virtual machine writing to 
an nfs mount of the qnap.

To improve performance in particualr for the bigger jobs we installed bacula 
directly on qnap to have the sd running there. Now we got the follwing problem.

Autolabeling doesn't work anymore. After starting a job I got the following 
message:



From: root@bacula   >
 Sent: Mon Jul 10 00:05:19 2017
 To: admin
 Cc: 
 Subject: Bacula: Intervention needed for shares.2017-07-09_23.05.00_13
 Auto forwarded by a rule

 10-Jul 00:05 qnap4-sd JobId 1: Job shares.2017-07-09_23.05.00_13 is waiting. 
Cannot find any appendable volumes.
 Please use the "label" command to create a new Volume for:
     Storage:  "FileChgr1-Dev2" (/opt/bacula/tapes)
     Pool: File
     Media type:   File1



That message never apperead on the single machine setup. The labels were 
properly autolabeled.
Nevertheless I tried to label a tape. 


user@bacula:~# bconsole
Connecting to Director localhost:9101
1000 OK: 1 bacula-dir Version: 7.0.5 (28 July 2014)
Enter a period to cancel a command.
*label
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
The defined Storage resources are:
 1: File1
 2: File2
Select Storage resource (1-2): 1
Enter new Volume name: TestVolume001
Defined Pools:
 1: Default
 2: File
 3: Scratch
Select the Pool (1-3): 2
Connecting to Storage daemon File1 at qnap4.jws.local:9103 ...
Sending label command for Volume "TestVolume001" Slot 0 ...
3000 OK label. VolBytes=195 VolABytes=0 VolType=1 Volume="TestVolume001" 
Device="FileChgr1-Dev1" (/opt/bacula/tapes)
Label command failed for Volume TestVolume001.
Do not forget to mount the drive!!!

 

SD creates the volume properly (as fare as I can see in the fielsystem) but 
director doesn't recognize it.



Can someone please point me to the right direction how to get it work?



cheers

Holger



xxx

bacula-dir.conf

xxx

Director {    # define myself
  Name = bacula-dir
  DIRport = 9101    # where we listen for UA connections
  QueryFile = "/etc/bacula/scripts/query.sql"
  WorkingDirectory = "/var/lib/bacula"
  PidDirectory = "/var/run"
  Maximum Concurrent Jobs = 20
  Password = "xyz" # Console password
  Messages = Daemon
}

JobDefs {
  Name = "DefaultJob"
  Type = Backup
  Level = Incremental
  Client = bacula-fd
  FileSet = "Full Set"
  Schedule = "WeeklyCycle"
  Storage = File1
  Messages = Standard
  Pool = File
  SpoolAttributes = yes
  SpoolData = yes
  Priority = 10
  Write Bootstrap = "/var/lib/bacula/working/%c.bsr"
}

Job {
  Name = "BackupCatalog"
  JobDefs = "DefaultJob"
  Level = Full
  FileSet="Catalog"
  Schedule = "WeeklyCycleAfterBackup"
   RunBeforeJob = "/etc/bacula/scripts/make_catalog_backup.pl MyCatalog"
   RunAfterJob  = "/etc/bacula/scripts/delete_catalog_backup"
  Write Bootstrap = "/etc/bacula/working/%n.bsr"
  Priority = 11   # run after main backup
}

Job {
  Name = "RestoreFiles"
  Type = Restore
  Client= bacula-fd
  Storage = File1
# The FileSet and Pool directives are not used by Restore Jobs
# but must not be removed
  FileSet="Full Set"
  Pool = File
  Messages = Standard
  Where = /nonexistant/path/to/file/archive/dir/bacula-restores
}

Job { 
  Name = samba4
  JobDefs = DefaultJob
  Client = samba4-fd
  FileSet = samba4
  Storage = File1
  Messages = Standard
  Client Run Before Job = /root/bin/backups
  Enabled = no
}

# List of files to be backed up
FileSet {
  Name = "Full Set"
  Include {
    Options {
  signature = MD5
    }
    File = /opt/sbin
  }
  Exclude {
    File = /opt/bacula/working
    File = /opt/bacula/tmp
    File = /proc
    File = /tmp
    File = /sys
    File = /.journal
    File = /.fsck
  }
}

FileSet {
  Name = samba4
  Include {
  File = /opt
  File = /srv/home
 File = /srv/profiles
 File = /srv/backup
 Options {
    Signature = MD5
    Compression = GZIP5
    }
  }
}

Schedule {
  Name = "WeeklyCycle"
  Run = Full 1st sun at 23:05
  Run = Differential 2nd-5th sun at 23:05
  Run = Incremental mon-sat at 23:05
}

WeeklyCycle
Schedule {
  Name = "WeeklyCycleAfterBackup"
  Run = Full sun-sat at 23:10
}

FileSet {
  Name = "Catalog"
  Include {
    Options {
  signature = MD5
    }
    File = "/var/lib/bacula/bacula.sql"
  }
}

Client {
  Name = samba4-fd
  Password = "4711"
  Address = samba.local
  FDPort = 9102
  Catalog = MyCatalog
  File Retention = 30 days    # 30 days
  Job Retention = 6 months    # six months
  AutoPrune = yes
}

Storage {
  Name = File1
  Address = qnap.local # N.B. Use a fully qualified name here
  SDPort = 9103
  Password = "123"
  Device = FileChgr1
  Media Type =