NATs is still relevant and will be installed on the VB365 server locally to be used.
@Spencer
For smaller deployments ( <2000 users) you should be fine with a next, next, finish installation with an all-in-one setup. NATS is still necessary and relevant, without NATS, the system will not work.
Apply the GOMEMLIMIT to keep memory consumption of the NATS server under control (75% of available memory as a maximum)
Thank you for the replies.
@kristofpoppe
Are you saying that I don’t need to bother configuring TLS and just leave it how Veeam configures it during the installation process?
@Chris.Childerhose
I tried following the instructions from the NATS website, but I’m not familiar with NATS. Am I supposed to edit the nats-server.conf file in ProgramData? I can create a separate NATS server and connect to it just fine, but I can’t figure out how to configure the one that Veeam already set up upon installation. Would you be able to point me in the right direction for this?
I believe that is the file you need to edit. I have deployed VB365 V8 but with external NATs versus the built-in one so not 100% sure. There has to be a conf file though somewhere on the controller.
I would like to take up this topic again.
You will find the config at
"C:\ProgramData\NATS\nats-server.conf"
tls: {
cert_file: "./server-cert.pem"
key_file: "./server-key.pem"
}
but I am also struggling with the NATS SSL integration.
I am unsure whether I have to use a new certificate or the certificate that is also stored in the general options under Security.
i created a new certificate. The NATS server accepts the certificate, but Veeam reports in the proxy log that the certificate cannot be validated. Proxy server will be disconnected.
NATS server and client are one and the same server, do I need to store the certificate somewhere else?
Unfortunately, there are no more detailed instructions, although this is an important issue with v8. Maybe I'm just being too stupid.
Hi @Jan.B. ,
what is the error you see in the log?
I don’t know if can help, but this is the official doc for NATS TLS https://docs.nats.io/running-a-nats-service/configuration/securing_nats/tls
The remote certificate is invalid according to the validation procedure: RemoteCertificateNameMismatch
the official doc doesn’t help.
I will open a case at veeam support.
Have you already tried to restart both Veeam M365 and NATS services?
Sure, how else could the config have been reloaded?
ive found the problem. Certificate was created for FQDN - Veeam is using just the hostname at "C:\ProgramData\Veeam\Backup365\Proxy.xml"
Glad to hear you found the issue. Nice to know where to check this.