Sorry I do not know how to change the install script so I cannot test your new install. If you need someone to do this I am happy to act as a test case but you will need to tell me how to do it. You can PM me if you wish.
OK so I had a look at the README ( I will provide comments on it separately) and I then started a fresh openhabian install on my Rapberry PI 3B.
Now you stated that “There should not have been a backup user prior to running the Amanda installation menu option’. So to test this and after first boot had completed I executed sudo cat/etc/passwd to see if there was an existing ‘backup user”. There WAS a backup user
Details > backup:x:34:34:backup:/var/backups:/usr/sbin/nologin
I ignored this.
I then prepared a share on my NAS and created a /mnt/NAS folder on the pi. Went into fstab and added the line [192.168.1.37:/volume1/homes/Tom/Rpi301 /mnt/NAS nfs defaults 0 0]
Tested that with a sudo mount -a and then checked the directory to see if some test files had been shared. Everything OK so onto to an Amanda install. BTW I ignored all the intermediate set up steps such as setting up mail, samba adjusting locale and time zones etc.
Provided password, set containers to 15 and available space to 15000MB (three times the image size) chose not to backup SD card or use AWS
Everything seems to have worked so switch to backup user and do amcheck openhab-dir. Same problem as yesterday the installation does not seem to have granted permissions on the mounted share and it hangs with slot 0 volume “ “.
Ctrl C to exit and run an Amreport on openhab-dir and it says parse error; could not open config file “etc/Amanda/openhab-dir/Amanda.conf; No such file etc. I ran into this issue yesterday with the previous install. So while still backup user I tried to edit the Amanda.conf file and that generated a Security Exception “this will be reported”. OK change back to openhabian user and try to edit the Amanda config file. But it will not even let me CD into the directory (unless I use sudo -s). So to change Amanda config files I have to be root user not the normal openhabian. Is this how it’s supposed to work?
As I already have a working backup system (even though it may not optimised) I aborted the install. However despite what it told me on pi when I went to the NAS it HAD already created the required slots! Huh?
Yesterday, I fixed both of these issues by adding backup to the Sudoers group and granting permissions on the mount folder using “Sudo chmod -R 777 /mnt”. Now bearing in mind what you said about not needing to add backup to sudoer group would there have been alternative way of fixing these issues?
Anyway I know you have an updated installation script but I just though this might be useful info for you.