we ran into problems when launching an immediate backup via nfs:
server is windows (nfs share), ACS is 126.96.36.199
windows log files show successful nfs mount/unmount when we try to save the ACS backup to a nfs repository but ACS reports that the backup could not be written after sucessfully generating the .gpg archive.
show repository for a nfs repository always returns errors on the ACS console, either "could not mount" or "invalid directory" - in both cases the windows log file report a successful nfs mount (we turned on nfs logs on the windows server).
the same operations, backing up and show repository, are sucessful with a test ftp-server (we just changed the protocol and adjusted the credentials in the repository config).
I have carefully read throug the available documention and the sucessful nfs mount/unmount on the windows logs show that basically everything is configured correctly and no restrictions on the server block access to the nfs.
any idea on that?
PS the url used for nfs follows the syntax:
the colon has to be there, according to the documentation
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...