![]() This directory should be used only by Bacula but This directive is mandatory and specifies a directory in which the Director There are a few messages that can occur when no job is running. Will be directed to the Messages resource specified by the job. The messages resource specifies where to deliver Director messages that are Process but as noted above, it is better to use random text for Process, otherwise it will be left blank and you must manually supply If you have either /dev/random or bc on your Security, the password is never passed across the network but instead aĬhallenge response hash code created with the password. The same password must appear in the Director resource of the Console configuration file. Specifies the password that must be supplied for the default BaculaĬonsole to be authorized. The text field contains a description of the Director that will be displayed The director name used by the system administrator. One and only one director resource must be Resource, but the final design will contain multiple Directors to maintain In the current implementation, there is only a single Director The Director resource defines the attributes of the Directors running on the Multiple different message resources and hence direct particularĬlasses of messages to different users or locations (files. Information messages are to be sent or logged. MessagesMessagesChapter - to define where error and.You must know what catalog contains what data. Multiple catalogs require a bit more management because in general Scale the Director to many clients, multiple catalogs can be helpful. Keep the list of files and the Volume names where they are backed up. CatalogCatalogResource - to define in what database to.Pools allow you to restrict a Job (or a Client) to use Of clients or volumes, you may want to have multiple Pools. PoolPoolResource - to define the pool of Volumes.StorageStorageResource2 - to define on what physicalĭevice the Volumes should be mounted.You will generally have multiple Client definitions. ClientClientResource2 - to define what Client is to beīacked up.You may have any number ofįileSets but each Job will reference only one. FileSetFileSetResource - to define the set of files.May have any number of Schedules, but each job will reference only ScheduleScheduleResource - to define when a Job is toīe automatically run by Bacula's internal scheduler.JobDefsJobDefsResource - optional resource for.one Job per client, but a different one with a different name Normally, you will Jobs of different names corresponding JobJobResource - to define the backup/restore JobsĪnd to tie together the Client, FileSet and Schedule resources to be usedįor each Job.Process, otherwise it will be left blank. Machine, Bacula will generate a random password during the configuration Only a single Director resource definition may appear in the Director'sĬonfiguration file. Name and its access password used for authenticating the Console program. DirectorDirectorResource4 - to define the Director's.Note, everything revolves around a job and is tied to a job in one We present them here in the most logical order for defining them: ![]() Job, JobDefs, Client, Storage, Catalog, Schedule, FileSet, Pool, Director, or Please see theĬonfigurationConfigureChapter chapter of this manual.ĭirector resource type may be one of the following: The most complicated, and the one that you will need to modify the most oftenĪs you add clients or modify the FileSets.įor a general discussion of configuration files and resources including theĭata types recognized by Bacula. Of all the configuration files needed to run Bacula, the Director's is Next: Client/File daemon Configuration Up: Bacula Main Reference Previous: Customizing the Configuration Files Contents Index
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |