Operation Manual

115 Copyright © Acronis International GmbH, 2002-2014
6. Download the New Relic script - newrelic.yml.
7. Open your Acronis Access web UI.
8. Go to Settings and click on Monitoring.
9. Enter the path to the newrelic.yml including the extension (e.g. C:\software\newrelic.yml).
We recommend you put this file in a folder outside of the Acronis Access folder so that it will not
be removed or altered on upgrade or uninstall.
10. Click Save and wait a couple of minutes or until the Active application(s) button becomes active
on the New Relic site.
11. If more than 10 minutes pass, restart your Acronis Access Tomcat service and wait a couple of
minutes. The button should be active now.
12. You should be able to monitor you Acronis Access server via the New Relic website.
All the information the Acronis Access server logs about trying to connect to New Relic and set up monitoring is
in a file called newrelic_agent.log found here - C:\Program Files
(x86)\Acronis\Common\apache-tomcat-7.0.34\logs. If you have any problems, you can find
information in the log file.
There is frequently a warning/error that starts like this:
WARN : DNS Error caching IP address: Errno::ENOENT: No such file or directory - C:/etc/hosts which
That's a side effect of the code used to patch another New Relic bug and is innocuous.
If you want to monitor the actual computer as well
1. Open http://newrelic.com/ http://newrelic.com/ and log in with your account.
2. Press Servers and download the New Relic installer for your operating system.
3. Install the New Relic monitor on your server.
4. The New Relic server monitor requires Microsoft .NET Framework 4. The link the New Relic
installer takes you to is only for the Microsoft .NET Framework 4 Client Profile. You will need to
go to the Microsoft Download Center and download the entire .NET 4 Framework from the
internet and install it before running the New Relic Server Monitor installer.
5. Wait until New Relic detects your server.
5.7 Using trusted server certificates with Acronis Access
This section explains how to configure Acronis Access with trusted server certificates. By default,
Acronis Access will use a self-generated SSL certificate. Using a certificate signed by a trusted
certificate authority will establish the identity of the server and allow browsers to connect without
displaying a warning message that the server is untrusted.
Note: Acronis Access ships and installs with self-signed certificates for testing purposes. Production
deployments should implement proper CA certificates.
Note: Certain web browsers will display warning messages when using self-signed certificates. Dismissing those
messages allows the system to be used without problems. Using self-signed certificates for production
conditions is not recommended.
Requirements
The certificate you are using must contain its private key. PFX certificates are highly recommended
but other types (CRT, CER) will work too, as long as they have their private key.