 |
Looks to be a configuration problem. It triggers an ASSERT in the code that checks that the storage used is actually using the right password encoding which should be clear text not md5. You probably used the wrong storage e.g. you need to configure an extra NDMP storage which is paired with the native storage. We tried adding quite some ways to make sure a misconfiguration is found and reported but it seems this config bypasses the current available checks. The ASSERTS are there to make sure we don't continue with bogus information. How does your storage config look like ? |
|
|
in bareos-dir.conf: # my Storage Storage { Name = NDMPstoragefile Address = astrobkup # N.B. Use a fully qualified name here Password = "Kro4/r/e7odJfIO0XxVRpuBjuKiWPCQLqAjq5nL59fJ1" Media Type = nas26file Device = nas26sd Protocol = NDMPv4 Paired Storage = NDMPstoragepaired Media type = File } # my Storage paired Storage { Name = NDMPstoragepaired Address = astrobkup # Media Type = File Media Type = nas26file Password = "Kro4/r/e7odJfIO0XxVRpuBjuKiWPCQLqAjq5nL59fJ1" #Device = FileStorage Device = nas26sd } in bareos-sd.conf: NDMP { Name = nas1A Username = ndmpnas1A Password = ndmppassofnas1A Authtype = Clear } Device { Name = nas26sd Media Type = nas26file # Archive Device = /var/lib/bareos/storage Archive Device = /mnt/NAS26/__NDMP__ Device Type = file LabelMedia = yes; # lets Bareos label unlabeled media Random Access = yes; AutomaticMount = yes; # when device opened, read it RemovableMedia = no; AlwaysOpen = no; Requires Mount = no } |
|
|
I try to follow the guide: https://github.com/bareos/bareos/blob/master/README.NDMP but it isn't helped. regular backup works fine. |
|
|
You didn't follow the examples fully. Your problem is that you specify your password before you said what protocol the storage is using. As the config engine determines how to store a password according to the storage daemon protocol used it thinks it talking to a native storage daemon as you later on say its NDMP. Further more the password for NDMPstoragefile is wrong it should be ndmppassofnas1A as its the NDMP password used by the directors DMA to login into native SD using the NDMP protocol. The example says: Storage { Name = NDMPFile Address = ... # N.B. Use a fully qualified name here Port = 10000 Protocol = NDMPv4 Auth Type = Clear # Clear == Clear Text, MD5 == Challenge protocol Username = ndmp # username of the NDMP user on the TAPE AGENT e.g. the Bareos SD but accessed via the NDMP protocol. Password = test # password of the NDMP user on the TAPE AGENT e.g. the Bareos SD but accessed via the NDMP protocol. Device = FileStorage Media Type = File PairedStorage = File } # # This entry gives the DMA in the Director access to the bareos SD via the NDMP protocol. # This option is used via the NDMP protocol to open the right TAPE AGENT connection to your # Bareos SD via the NDMP protocol. The initialization of the SD is done via the native protocol # and is handled via the PairedStorage keyword. # Ndmp { Name = ...-ndmp-dma # Can be any name but normally you should use the name of the Director here. Username = ndmp # Same username as you specified in the NDMPFile storage definition. Password = test # Same password as you specified in the NDMPFile storage definition. AuthType = Clear # Clear == Clear Text, MD5 == Challenge protocol } |
|
|
Ok. This have fixed my problem. According to what i see the order inside each section is important. May be it will help other people if you could highlight this in your guide. (or may be you already did, but i have missed it ) mvwieringen, Thanks a lot for your help. |
|
|
Only the order of the protocol is important as that determines the password encoding. I added two patches one that updates the README.NDMP that the protocol has to come before the password and added a second patch that validates the password encoding so you get a fatal error instead of an ASSERT. |
|
|
Fix committed to bareos master branch with changesetid 2656. |
|
|
Fix committed to bareos bareos-14.2 branch with changesetid 2694. |
|
|
Fix committed to bareos2015 bareos-14.2 branch with changesetid 4456. |
|
|
Due to the reimport of the Github repository to bugs.bareos.org, the status of some tickets have been changed. These tickets will be closed again. Sorry for the noise. |
- Anonymous
