Hello.
I spent a few days with this error, but can't understand where is
mistake. Google tells, that this misconfiguration between sd.conf and
dir.conf, but it's identical.
This error at SD log. On the Dir log i can see next:
Storage daemon didn't accept Device "NULL" because:
Device "NULL" not in SD Device resources or no matching Media Type.
From bconsole:
*show Storage=NULL
Storage: name=NULL address=XX.XX.XX.XX SDport=9103 MaxJobs=1
DeviceName=NULL MediaType=NULL StorageId=7 Autochanger=0
Here sd.conf:
Storage {
Name = stor
SDPort = 9103
WorkingDirectory = "/var/bacula"
Pid Directory = "/var/bacula"
}
Director {
Name = backup-dir
Password = "XXX"
}
Device {
Name = NULL
Media Type = NULL
Device Type = Fifo
Archive Device = /dev/null
LabelMedia = yes
Random Access = no
AutomaticMount = no
RemovableMedia = no
MaximumOpenWait = 60
AlwaysOpen = no
}
Here dir.conf:
Storage {
Name = NULL
Address = XX.XX.XX.XX
SDPort = 9103
Password = "XXX"
Device = NULL
Media Type = NULL
}
Job {
Name = "Clien_NULL"
JobDefs = "DefaultJob_Backup"
Level = Full
FileSet = "configs"
Pool = Full-pool
Storage = NULL
Client = client1
}
Thanks.
PS. Device NULL a add for test, on real devices are the same.
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
