“Acronis” and “Acronis Secure Zone” are registered trademarks of Acronis International GmbH.
"Acronis Compute with Confidence", “Acronis Startup Recovery Manager”, “Acronis Active Restore”,
“Acronis Instant Restore” and the Acronis logo are trademarks of Acronis International GmbH.
Linux is a registered trademark of Linus Torvalds.
VMware and VMware Ready are trademarks and/or registered trademarks of VMware, Inc. in the
United States and/or other jurisdictions.
Windows and MS-DOS are registered trademarks of Microsoft Corporation.
All other trademarks and copyrights referred to are the property of their respective owners.
Distribution of substantively modified versions of this document is prohibited without the explicit
permission of the copyright holder.
Distribution of this work or derivative work in any standard (paper) book form for commercial
purposes is prohibited unless prior permission is obtained from the copyright holder.
DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE
EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Third party code may be provided with the Software and/or Service. The license terms for such
third-parties are detailed in the license.txt file located in the root installation directory. You can
always find the latest up-to-date list of the third party code and the associated license terms used
with the Software and/or Service at http://kb.acronis.com/content/7696
Acronis patented technologies
Technologies, used in this product, are covered and protected by one or more U.S. Patent Numbers:
7,047,380; 7,275,139; 7,281,104; 7,318,135; 7,353,355; 7,366,859; 7,475,282; 7,603,533; 7,636,824;
7,650,473; 7,721,138; 7,779,221; 7,831,789; 7,886,120; 7,895,403; 7,934,064; 7,937,612; 7,949,635;
7,953,948; 7,979,690; 8,005,797; 8,051,044; 8,069,320; 8,073,815; 8,074,035; 8,145,607; 8,180,984;
8,225,133; 8,261,035; 8,296,264; 8,312,259; 8,347,137; 8,484,427; 8,645,748; 8,732,121 and patent
pending applications.
3.2.1 Group Policy ................................................................................................................................................... 33
3.3 On-boarding Mobile Devices ...................................................................................................43
3.3.1 Server-side Management Enrollment Process ........................................................................................... 44
3.3.2 User-side Management Enrollment Process .............................................................................................. 45
3.4 Managing Your Gateway Server ..............................................................................................48
3.4.1 Server Details ................................................................................................................................................. 50
10.8.3 New Relic ..................................................................................................................................................... 117
You must be logged in as an administrator before installing Acronis Access. Verify that you meet the
following requirements.
1.1.1 Operating System Requirements
Recommended:
Windows 2012 all flavors
Windows 2008 R2 64 bit
Supported:
Windows 2012 R2
Windows 2012, Standard and Datacenter editions
Windows 2008, all flavors, 32/64 bit
Note: For testing purposes, the system can be installed and runs on Windows 7 or later. These desktop class
configurations are not supported for production deployment.
1.1.2 Mobile Client requirements
The mobile client application is compatible with:
Supported devices:
Apple iPad 2nd, 3rd, 4th generation, Air, Air 2
Apple iPad Mini 1st, 2nd, 3rd generation
Apple iPhone 3GS, 4, 4S, 5, 5s, 5c, 6, 6 Plus
Apple iPod Touch 4th, 5th generation
Android Smartphones and Tablets (Devices with x86 processor architecture are not supported)
Android 2.2 or later (Devices with x86 processor architecture are not supported)
The Acronis Access app can be downloaded from:
For iOS http://www.grouplogic.com/web/meappstore
For Android https://play.google.com/store/apps/details?id=com.grouplogic.mobilecho
1.1.3 Minimum Hardware Recommendation
Processor: Intel/AMD
Note: Acronis Access server can be installed on virtual machines.
Memory:
Production environments: 8 GB minimum. More recommended.
Trial or Тest environments: 4 GB minimum. 8 GB or more recommended.
Disk Space:
The software installation requires 300MB of disk space.
Note: Please make sure that you have enough space to run the Acronis Access installer. 1GB of space is
required for the installer to run.
The file repository used by the Sync & Share features is installed on the local computer by
default.
Enough free space should be provided to meet testing parameters. 50 GB or more is
recommended.
1.1.4 Desktop Client Requirements
Supported operating systems:
Windows XP, Windows Vista, Windows 7, Windows 8 and 8.1
Note: In order to use the Acronis Access Desktop client on Windows XP, you will need to use relaxed SSL
cipher rules. For more information: Changing the Acronis Access Tomcat SSL Ciphers (p. 112).
Mac OS X 10.6.8 and higher with Mac compatible with 64-bit software.
Note: When installing the Acronis Access Desktop client, make sure that the sync-folder you create is not in
a folder synchronized by another software. For a list of known conflicts visit Conflicting Software (p. 110).
Supported web browsers:
Mozilla Firefox 6 and later
Internet Explorer 9 and later
Note: You can support an unsecure version of Internet Explorer 8 if necessary by following the Changing the
Acronis Access Tomcat SSL Ciphers (p. 112) article. Internet Explorer 8 is not supported for Server
Administration.
Note: When using Internet Explorer you have to make sure that Do not save encrypted pages to disk is
unchecked in order to be able to download files. This setting is found under Internet Options -> Advanced
1 Static IP Address.
Optional but recommended: DNS name matching the above IP address.
Network access to a Domain Controller if Active Directory will be used.
Network access to an SMTP server for email notifications and invite messages.
The address 127.0.0.1 is used internally by the Access Mobile Client and should not be routed
through any kind of tunnel (e.g. VPN).
The machine running Acronis Access needs to be bound to the Windows Active Directory.
Note: It is recommended to bind the server to the domain. Mobile clients will not be able to access Data sources
unless the server is bound to the domain.
If you want to allow mobile devices access from outside your firewall, there are several options:
Port 443 access: Acronis Access uses HTTPS for encrypted transport, so it fits in naturally with
common firewall rules allowing HTTPS traffic on port 443. If you allow port 443 access to your
Acronis Access server, authorized iPad clients can connect while inside or outside of your firewall.
Acronis Access can also be configured to use any other port you prefer.
VPN: The Access Mobile Client supports access through a VPN connection. Both the built in iOS
VPN client and third-party VPN clients are supported. iOS management profiles can optionally be
applied to devices using the Apple iPhone Configuration Utility to configure the certificate-based
iOS “VPN-on-demand” feature, giving seamless access to Acronis Access servers and other
corporate resources.
Reverse proxy server: If you have a reverse proxy server set up, iPad clients can connect without
the need for an open firewall port or a VPN connection. The Access Mobile Client app supports
reverse proxy pass-through authentication and username / password authentication.
Note: If you want to use a mobile device management like Good Dynamics or MobileIron, you will need to
upgrade to Acronis Access Advanced.
Certificates:
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.
1.2 Installing Acronis Access on your server
Installing Acronis Access
Please make sure you are logged in as an administrator before installing Acronis Access.
The Configuration Utility will launch automatically to complete the installation
1.3 Using the Configuration Utility
The Acronis Access installer comes with a configuration utility, which allows you to quickly and easily
set up the access to your Acronis Access Gateway server, File Repository and Acronis Access Server.
Note: See the Network Requirements (p. 7) section for more information on best practices for the IP address
configurations of Acronis Access.
Note: For information on adding your certificate to the Microsoft Windows Certificate Store, visit the Using
Certificates (p. 110) article.
Port - The port of your Web Interface and Gateway Server.
Certificate - SSL certificate for your Web Interface and Gateway Server. You can choose a
certificate from the Microsoft Windows Certificate Store.
Redirect requests from port 80 - When selected, Tomcat will listen for incoming traffic on the
unsecure port 80 and redirect it to the HTTPS port you have specified above. If you have another
program listening on port 80, do not check this box.
File Store Path - Local path to your File Store. If you change the File Store path, you MUST
manually copy any files that are already in the original File Store location to your new location.
Note: If you move the File Store to another location, you should upload a new file to make sure it is going
into the correct new location. Another thing is downloading a file that was already in the file store to make
sure all of the files that were in the original location can be accessed at the new location.
1.4 Using the Setup wizard
After installing the software and running the configuration utility to setup the network port and SSL
certificate, the administrator now needs to configure the Acronis Access server. The Setup Wizard
detects most of the necessary settings (LDAP, Server and SMTP) automatically to help you get the
basic functionality of the server working. You can still change all of these settings manually before
proceeding.
Note: After the configuration utility has run, it will take 30-45 seconds for the server to come up the first time.
Navigate to the Acronis Access's web interface using any of the available IP addresses and the port
specified in the configuration utility. You will be prompted to set the password for the default
administrator account.
Note: Administrators can be configured later on, for more information visit the Server Administration (p. 94)
section.
This wizard helps you setup the core settings for the functionality of your product.
General Settings cover settings of the web interface itself, like the language, the color scheme,
the server name used in admin notifications, licensing and administrators.
LDAP settings allow you to use Active Directory credentials, rules and policies with our product.
SMTP settings cover functionality in both Mobile Access features and Sync & Share features. For
Mobile Access, the SMTP server is used when sending enrollment invitations. Sync & Share
features use the SMTP server to send folder invitations, warnings, summaries of errors.
All of the settings you see in the Initial Configuration page will also be available after you complete it.
For more information on any of the settings, please visit the Server Administration (p. 94) articles.
Increasing the Acronis Access Tomcat Java Maximum Memory Pool ..... 29
To backup all of Acronis Access's elements and as part of your best practices and backup procedures, you may
want to read the Disaster Recovery guidelines (p. 18) article.
2.1 Disaster Recovery guidelines
High availability and fast recovery is of extreme importance for mission critical applications like
Acronis Access. Due to planned or unplanned circumstances ranging from local hardware failures to
network disruptions to maintenance tasks, it may be required to provision the means for restoring
Acronis Access to a working state in a very short period of time.
Introduction:
For mission critical applications like Acronis Access, high availability is of extreme importance. Due to
various circumstances ranging from local hardware failures to network disruptions to maintenance
tasks, it may be required to provision the means for restoring Acronis Access to a working state in a
very short period of time.
There are different ways to implement disaster recovery, including backup-restore, imaging,
virtualization and clustering. We will describe the backup-restore approach in the following sections.
Description of the Acronis Access elements:
Acronis Access is a solution composed of several discrete but interconnected elements:
Acronis Access Gateway Server
Note: Normally located here: C:\Program Files (x86)\Acronis\Access\Gateway Server
Acronis Access Server
Note: Normally located here: C:\Program Files (x86)\Acronis\Access\Access Server
Acronis Access Configuration Utility
Note: Normally located here: C:\Program Files (x86)\Acronis\Access\Configuration Utility
File Store
The location of the File Store is set during the installation when you first use the Configuration Utility.
Note: The FileStore structure contains user files and folders in encrypted form. This structure can be copied or
backed up using any standard file copy tool (robocopy, xtree). Normally this structure should be located in a
high availability network volume or NAS so the location may differ from the default.
PostGreSQL database. This is a discrete element running as a Windows service, installed and used by
Acronis Access. The Acronis Access database is one of the most critical elements because it maintains
all configurations, relationships between users and files, and file metadata.
All those components are needed in order to build a working instance of Acronis Access.
Resources needed to implement a fast recovery process
The resources needed to fulfill the disaster recovery process are:
Appropriate hardware to host the operating system, application and its data. The hardware must
meet the system and software requirements for the application.
A backup and restore process in place to ensure all software and data elements are available at
the time the switch is needed.
Network connectivity, including internal and external firewall and routing rules that permit users
to access the new node with no or minimal need to change client side settings.
Network access for Acronis Access to contact an Active Directory domain controller and SMTP
server.
Fast or automated DNS switching ability to redirect incoming request to the secondary node.
The process
Backup Setup
The recommended approach to provide a safe and fast recovery scenario can be described like this:
1. Have an installation of Acronis Access, including all elements in the secondary, restore, node. If
this is not possible, a full (source) machine backup or image is a good alternative. In virtualized
environments, periodic snapshots prove to be effective and inexpensive.
2. Backup the Acronis Access server software suite (all elements mentioned above, including the
entire Apache Software branch) regularly. Use any standard, corporate class backup solution for
the task.
3. Backup the FileStore as frequently as possible. A standard backup solution can be used, but an
automated differential copy tool is a good and sometimes preferred alternative due to the
amount of data involved. A differential copy minimizes the time this operation takes by updating
what is different between the source and target FileStores.
4. Backup the Acronis Access database as frequently as possible. This is performed by an automated
database dump script triggered by Windows Task Scheduler. The database dump should then be
backed up by a standard backup tool.
Recovery
Provided the conditions described in the section above have been met and implemented, the process
to bring online the backup resources is relatively simple:
1. Boot up the recovery node. Adjust any network configuration like IP Address, Host Name if
needed. Test Active Directory connectivity and SMTP access,
2. If needed restore the most recent Acronis Access software suite backup.
3. Verify that Tomcat is not running (Windows Control Panel/Services).
4. If needed, restore the FileStore. Make sure the relative location of the FileStore is the same as it
was in the source computer. If this is not the case, the location will need to be adjusted by using
the Configuration Utility.
5. Verify that the PostgreSQL service is running (Windows Control Panel/Services).
6. Restore the Acronis Access database.
7. Start the Acronis Access Tomcat service.
8. Migrate DNS to point to the new node.
9. Verify Active Directory and SMTP are working
2.2 Backing up and Restoring Acronis Access
In case you need to upgrade, update or maintain your Acronis Access server. This article will give you
the basics of backing up your database and restoring it.
Backing up your databases
Backing up your Acronis Access's database
The following method creates an *.sql file containing a text representation of the source database.
1. Open a Command Prompt window and navigate to the PostgreSQL\bin folder located in the
PostgreSQL installation directory.
e.g. cd "C:\Program Files (x86)\Acronis\Access\Common\PostgreSQL\bin"
2. Once your current Command Prompt directory is the bin folder, enter the following line:
pg_dump -U postgres -f mybackup.sql acronisaccess_production
where mybackup.sql is the desired file name for the produced backup file. It can include a full
path to the location where you want the backup file to be created, for instance:
D:\Backups\mybackup.sql
Note:acronisaccess_production must be entered exactly as shown as it is the name of the Acronis
Access database
3. A "Password: " line appears. Enter the postgres password that you set during the Acronis Access
installation process.
Note: Typing the password will not result in any visual changes in the Command Prompt window.
4. Your backup file will appear in the bin folder by default unless the output file specification
contains a full path to a different directory.
Note: If you want to backup the entire PostgreSQL database set you can use the following command:
pg_dumpall -U postgres > alldbs.sql
Where alldbs.sql will be the generated backup file. It can include a full path specification, for instance
D:\Backups\alldbs.sql
For full syntax on this command see: http://www.postgresql.org/docs/9.2/static/app-pg-dumpall.html
http://www.postgresql.org/docs/9.1/static/app-pg-dumpall.html
Info: For more information on PostgreSQL backup procedures and command syntax please read this:
http://www.postgresql.org/docs/9.2/static/backup.html
http://www.postgresql.org/docs/9.1/static/backup.html
Backing up your Gateway Server's database
1. Go to the server on which you have Acronis Access installed.
2. Navigate to the folder containing the database.
Note: The default location is: C:\Program Files (x86)\Acronis\Access\Gateway
Server\database
3.Copy the mobilEcho.sqlite3 file and paste it in a safe location.
Restoring Acronis Access
Restoring your Acronis Access's database
The database restore process is similar to the backup process.
1. Prior to executing the command to restore your database, make sure the source backup file is
located in a directory or location where it can be accessed by the logged in user.
2. Open a Command Prompt window and navigate to the PostgreSQL\bin folder located in the
PostgreSQL installation directory.
cd "C:\Program Files (x86)\Acronis\Access\Common\PostgreSQL\bin"
Note: This directory may be different if you installed PostgreSQL in a custom location.
3. You need to remove the old database first. To do so, stop the Acronis Access Tomcat service and
enter the following line:
Warning! Do not continue with this step unless you are certain you have made a successful backup.
Dropping the database is an irreversible process which deletes the entire database. All information is lost.
dropdb -U postgres acronisaccess_production
A "password for user postgres: " message may appear. If that happens, enter the postgres
password that you set during the Acronis Access installation process.
acronisaccess_production must be entered exactly as shown. This is the Acronis Access
database name.
4. Once the operation finishes, enter the following line:
createdb -U postgres acronisaccess_production
A "password for user postgres: " message may appear. If that happens, enter the postgres
password that you set during the Acronis Access installation process.
acronisaccess_production must be entered exactly as shown. This is the Acronis Access
database name.
5. To fill the newly created database with the information from your backup, enter the following
A "password for user postgres: " message may appear. If that happens, enter the postgres
password that you set during the Acronis Access installation process.
acronisaccess_production must be entered exactly as shown. This is the Acronis Access
database name.
6. Once the process has completed successfully, restart the postgres service and start the Acronis
Access Tomcat service.
Note: Typing the password will not result in any visual changes in the Command Prompt window.
Info: For full psql command syntax, please visit http://www.postgresql.org/docs/9.2/static/app-psql.html
1. Copy the mobilEcho.sqlite3 file you have backed up.
2. Go to the server on which you have Acronis Accessinstalled.
3. Navigate to the folder containing the database and paste the mobilEcho.sqlite3 file.
Note: The default location is: C:\Program Files (x86)\Acronis\Access\Gateway
Server\database
4.Restart the Acronis Access Gateway Server service.
Restoring Acronis Access to a new instance
1. Complete the Backup procedure explained above and move the alldbs.sql and mobilEcho.sqlite3
files to the new server.
2. On the new server, complete the Database restoration procedure explained above.
3. Start the Acronis Access services.
4. Complete the following procedure:
Configurations on the new instance
Note: It is highly recommended that you do not change the DNS names used by Acronis Access, only the IP
addresses they are pointing to. The following instructions assume you are re-using the DNS names of the
previous instance of Acronis Access
1. Open the Acronis Access web interface and login.
2. Navigate to Mobile Access -> Gateway Servers.
3. Press on the down arrow next to the Details button and select Edit.
4. Click on the SharePoint tab and enter the SharePoint administrator's credentials.
5. If the Address for administration is set as an IP address, change it to the new IP you set for the
Acronis Access Server.
6. Press Apply.
If you do not intend to use the same IP address as the previous instance, change the IP entries for the
DNS names used by the Acronis Access and Gateway Server.
As part of its normal operation Tomcat creates and writes information to a set of log files.
Unless periodically purged, these files accumulate and consume valuable space. It is commonly
accepted by the IT community that the informational value those logs provide degrades rapidly.
Unless other factors like regulations or compliance with certain policies play, keeping those log files
in the system a discrete number of days is what is required.
Introduction:
As part of its normal operation Tomcat creates and writes information to a set of log files. On
Windows, these files are normally located in the following directory:
“C:\Program Files (x86)\Acronis\Access\Common\apache-tomcat-7.0.34\logs”
Acronis Access saves it's own logs in the same directory as separate files.
Acronis Access's log files are named acronisaccess_date.
There are many tools capable of automating the task of deleting unneeded log files. For our example,
we will use a built-in Windows command called ForFiles.
Info: For information on ForFiles, syntax and examples visit
http://technet.microsoft.com/en-us/library/cc753551(v=ws.10).aspx
http://technet.microsoft.com/en-us/library/cc753551(v=ws.10).aspx
A sample process:
The sample process described below automates the process of purging log files older than a certain
number of days. Inside the sample batch file, this number is defined as a parameter so it can be
changed to fit different retention policies.
Info: The sample script (batch) file is designed to work on Windows 2008. Click here to download the script.
Optionally you could copy and paste the script code into an empty text document and save it as
“AASTomcatLogPurge.bat”
Click here for the full batch script code...
ECHO OFF
REM Script: aETomcatLogsPurge.bat
REM 2012-05-12: Version: 1.0: MEA: Created
ECHO This script will delete files older than a number of days from a directory
ECHO Run it from the command line or from a scheduler
ECHO Make sure the process has permissions to delete files in the target folder
REM ===== CONFIGURATIONS ===================================================
REM Note: all paths containing spaces must be enclosed in double quotes
REM Edit this file and set LogPath and NumDays below
REM Path to the folder where all Tomcat logs are
set LogPath="C:\Program Files (x86)\Group Logic\Common\apache-tomcat-7.0.34\logs"
Warning: We provide this example as a guideline so you can plan and implement your own process based on
the specifics of your deployment. The example is not meant nor tested to apply to all situations and
environments so use it as a foundation and at your own risk. Do not use it in production environments without comprehensive offline testing first.
Steps:
1. Copy the script to the computer running Acronis Access (Tomcat) and open it with Notepad or a
suitable plain text editor.
2. Locate the section illustrated in the picture below and edit the LogPath and NumDays variables
with your specific paths and retention settings:
In Acronis Access the log files are stored in the same folder as Tomcat's. (C:\Program Files
(x86)\Acronis\Access\Common\apache-tomcat-7.0.34\logs)
3. Select daily and select the time when the script will be run and how often the script should be
rerun (how often you want to backup your database).
4. Select Enabled from the Advanced settings and press OK.
On the Actions tab:
1. Click New.
2. Select Start a program for Action.
3. For Program/Script press Browse, navigate to and select the DatabaseBackup.bat file.
4. For Start in (optional), enter the path to the folder in which the script resides. e.g. If the path to
the script is C:\Program Files (x86)\Acronis\Access\Common\PostgreSQL\9.3\PSQL.bat enter C:\Program Files (x86)\Acronis\Access\Common\PostgreSQL\9.3\
5. Press OK.
Configure any additional settings on the other tabs and press OK.
You will be prompted for the credentials for the current account.
2.5 Increasing the Acronis Access Tomcat Java
Maximum Memory Pool
By default, the Acronis Access Tomcat's Java Maximum Memory Pool setting on a 64 bit operating
system is 4GBs. Depending on your deployment, you may need more.
Note: On a 32bit operating system, the maximum memory pool is 1GB.
To increase the maximum memory pool:
1.Click on the Start menu and navigate to All Programs -> Acronis Access.