VMware AirWatch Database Migration Guide
VMware AirWatch Database Migration Guide
Have documentation feedback? Submit a Documentation Feedback support ticket using the Support Wizard on
support.air-watch.com.
Copyright © 2016 VMware, Inc. All rights reserved. This product is protected by copyright and intellectual property laws in the United States and other countries as well as by
international treaties. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and other jurisdictions. All other marks and names mentioned herein may be trademarks of their
respective companies.
1
Table of Contents
Chapter 1: Overview 3
Introduction to Database Migration 4
Migration Checklist 4
2
Chapter 1:
Overview
Introduction to Database Migration 4
Migration Checklist 4
3
Chapter 1: Overview
Migration Checklist
Status (Mark Complete as Needed) Task
Pre Migration Steps
Verify number of application servers
Verify connectivity to new database server
Meet the basic minimum requirements
Plan for downtime (submit change request, alert management)
Migration Procedure
Stop all AirWatch applications and services
Perform a back up of your data
Restore the data on the new database server
Note user permissions of old database's AirWatch SQL Service
Account
Delete AirWatch SQL Service Account from the new database
that was created when you restored
Create new user account in new database and give permissions
Migrate any AirWatch-related jobs
Perform a test query to verify functionality
Update applications servers so they are pointing to the new
database
Re-install AirWatch Reports
Restart IIS and AirWatch services
Log in to AirWatch and ensure you can perform basic device
functions (device query, lock device command, etc.)
Test reporting functionality by running the Device Summary
Report
4
Chapter 2:
Pre Migration Steps
Overview 6
Verify Number of Application Servers 6
Verify Connectivity to New Database Server 6
Meet the Basic Prerequisites 6
Plan for Downtime 9
5
Chapter 2: Pre Migration Steps
Overview
Perform the following pre migration steps to ensure you are prepared to perform a database migration.
2. Telnet to your new database server and verify connectivity by using the following command:
telnet <database_instance> <port>
Note that the default port for a SQL database instance is 1433. If you have manually changed the port then you
should use that value instead to verify connectivity.
If the connection is successful the command prompt window shows an empty screen.
If unsuccessful, you will receive a connect failed message. If the connection fails then ensure the database server is
configured to listen on the port you entered.
3. Verify that Full-Text Search is installed. The Global search function of the AirWatch Console uses full text search
indexes and requires the appropriate service to be running on the SQL server. Ensure this component is running on
your SQL instance by performing the following steps:
a. Click New Query.
6
Chapter 2: Pre Migration Steps
7
Chapter 2: Pre Migration Steps
On Windows Server 2008, the default account assigned to the SQL Full-text Filter Daemon Launcher service is the
Local Service account. SQL Server uses security features available in Windows Server 2008 to provide a high level of
security and isolation for the service. For enhanced security, you should not configure the SQL Full-text Filter
Daemon Launcher service to run under any other account.
8
Chapter 2: Pre Migration Steps
9
Chapter 3:
Migration Procedure
Overview 11
Performing the Migration 11
Post Migration Steps 26
10
Chapter 3: Migration Procedure
Overview
Perform the following steps to migrate your AirWatch database to another database server.
l Stopping the World Wide Web Publishing Services on each AirWatch Console and Device Services servers.
l Disabling any monitoring services (for example, Nagios) that could manually restart the AirWatch services or IIS.
From each AirWatch Console and Device Services Server do the following:
a. Open the Server Manager.
c. You will see all AirWatch Services at the top of the services list in alphabetical order. Each of these services start
with AirWatch in the name. For each of these services, right-click and choose Stop.
11
Chapter 3: Migration Procedure
d. Continue to repeat this process until all AirWatch services have been stopped and your services pane looks like
the following.
Now that all services have been stopped, you can stop Internet Information Services (IIS) to stop the AirWatch
Websites.
2. On your old database: Open Microsoft SQL Server Management Studio and log in using your system administrator
account.
3. On your old database: Perform a test query. For example, one for device count, to ensure proper functioning. To do
this:
12
Chapter 3: Migration Procedure
a. Right-click on the AirWatch database under Databases and select New Query.
c. Select Execute.
13
Chapter 3: Migration Procedure
c. Under the Options tab on the left, make sure Back up to the existing media set is selected, along with
Overwrite all existing backup sets.
d. Under the General tab on the left, navigate to the Destination header near the bottom of the window. Remove
any existing filepaths, and then select Add. Select the ellipses ('...') button, select the filepath where you want to
store the backup, then select OK. You are taken back to the Select Backup Destination screen, where you should
name the file in the following form: AirWatch{Version}_{Date}.bak., as shown below. For example,
AirWatch7.3.1.1_20150120.bak.
14
Chapter 3: Migration Procedure
The backup file should be saved in the file path specified in the step above. Navigate to that file and move it to
the new database server that the old database is being migrated to.
15
Chapter 3: Migration Procedure
5. On your new database: Restore the data on the new server you are migrating data to. To do this:
a. Open Microsoft SQL Server Management Studio, right-click on Databases and select Restore Database.
b. Under the General tab on the left and within the Source for restore section, select From device, then select the
ellipses ('...') button.
16
Chapter 3: Migration Procedure
17
Chapter 3: Migration Procedure
d. Under Destination for restore, select the To database drop-down list and select the AirWatch database name.
Note: This should be the last database in the list, in the event you have multiple backups all named AirWatch
and are unsure of which one to select.
18
Chapter 3: Migration Procedure
6. On the old database: Next you need to note the user permissions of the old database’s AirWatch SQL Service
Account. To do this:
a. Navigate to Security > Logins > <Your DB User> to locate your DB User in the Object Explorer, and then right-
click and choose Properties.
b. Navigate to the Server Roles tab. Note the roles listed. Your roles may differ from what is shown below. Copy
19
Chapter 3: Migration Procedure
c. Select User Mapping. Note the user mappings listed and the role membership permissions. Your user mappings
may differ from what is shown below. Copy or save a screenshot of your permissions.
While the screenshot below only shows the AirWatch role memberships, you should take note of all of the role
memberships for AirWatch, master, model, msdb, and tempdb.
7. On your new database: Delete the AirWatch SQL Service Account, which was created when you restored.
20
Chapter 3: Migration Procedure
8. On your new database: Create the new AirWatch SQL Service Account. To do this navigate to Security > Logins,
right-click, and select New Login.
21
Chapter 3: Migration Procedure
e. For User Mapping, enter the user mappings and permissions you noted previously.This procedure is only for the
main AirWatch SQL Service Account If you had any other custom-created SQL accounts you will need to perform
this procedure for each of them.
This should include all of the permissions that you copied for AirWatch, master, model, msdb, and tempdb.
9. Next you need to migrate any AirWatch-related jobs. The steps below are for the purge job, but any other AirWatch-
related jobs need to be similarly migrated using the procedure below.
a. From the old database, navigate to SQL Server Agent > Jobs, right-click <AirWatch_DB> - Purge Expired Sample
Data, and select Script Job as > CREATE To > New Query Editor Window.
22
Chapter 3: Migration Procedure
23
Chapter 3: Migration Procedure
c. Select Execute.
24
Chapter 3: Migration Procedure
12. Next you need to update each of your application servers (e.g. Console, Device Services) so they are pointing to the
new database.
Dedicated API and AWCM servers are considered application servers, similar to the AirWatch Console and Device
Services. You should therefore perform the steps below regarding re-pointing app servers on these servers if you
have dedicated servers for these components.
EIS, SEG, AirWatch Tunnel and ACC are considered auxiliary components and you do not need to perform this step
for these components.
a. Navigate to AirWatch Root Folder on the application server.
c. Launch UpdateSQLServerInfo.exe.
13. At this time you should re-install AirWatch Reports. See the appendix, Perform Reports Installation, for more
information. Note that you will lose any report subscriptions you configured through AirWatch.
14. On your application server(s), open cmd.exe and perform an IIS reset by simply typing iisreset and pressing Enter.
25
Chapter 3: Migration Procedure
15. While IIS is restarting, go to the Start menu, select Administrative Tools > Services. For each of the AirWatch
services that are currently running, right-click and select Restart.
16. Once each of the AirWatch services have been restarted, verify that the IIS reset is complete.
26
Chapter 4:
Reports Installation
Overview 28
Connect the Database to Reports Server 28
Configure the Service Account for SSRS 29
Configure the Web Service URL 30
Set up the Reporting Database 31
Verify the Report Manager URL and Web Service URL 33
Set up the AirWatch SSRS User 34
Add the SSRS User to IIS_IUSRS 35
Run the AirWatch Reporting Installer 37
Integrate Reports with the AirWatch Console 42
27
Chapter 4: Reports Installation
Overview
This chapter walks you through the process of installing AirWatch Reports to enable report configuration, report
subscription, and data driven email for your AirWatch deployment.
Important: While your reports server can be installed on the same server as the database, a dedicated SSRS instance
is required for reports installations. Installing AirWatch Reports on an existing production reporting instance may
cause reporting failures.
2. Provide the Server Name to select the name of the Server that SSRS runs on.
3. Select Report Server Instance from the drop-down menu to choose where to install AirWatch Reports.
4. Click Connect.
5. Ensure that the Report Server status is Started. If it is not, start the server from the Configuration Manager
Window, or navigate to the SQL Server Configuration Manager (Start > Microsoft SQL Server > Configuration
28
Chapter 4: Reports Installation
Tools > SQL Server Configuration Manager), and start the service.
2. Navigate to Security > Logins > <Your DB User> to locate your DB User in the Object Explorer, and then right-click
and choose Properties.
29
Chapter 4: Reports Installation
l If you are running the reports installer using Windows Authentication, include the following permissions:
o Select the AirWatch database, then select the public role.
o Select the master database, then select the public role.
o Select the msdb database, then select the public role.
5. After confirming these permissions, enter your service account details on the Service Account tab.
30
Chapter 4: Reports Installation
Note: If both IIS 7.0 and SQL Server are running on the same machine (that is, Appliance Type installs), set the SQL
Server endpoint to listen on a port other than 80. This problem does not exist for IIS 6.0.
If there are multiple instances of reporting on the same SQL Server, give the new Web Service URL a unique name, for
example, ReportServer_AirWatch.
31
Chapter 4: Reports Installation
2. Specify the database used for reporting. The default name is ReportServer. If this name is already in use, change it to
create a reporting database.
32
Chapter 4: Reports Installation
4. Use the report server credentials to connect to the Report Server Database.
2. Access the Web Service URL using the URL listed in the Web Service URL page.
33
Chapter 4: Reports Installation
l Set up a local user with the same Username and Password on both the Console Server and the Report Server and
add this user to the IIS user groups on both Servers.
The steps below cover creating a local user. If you are using a domain service account, you can skip to Add the SSRS User
to IIS_IUSRS.
34
Chapter 4: Reports Installation
2. Choose any user name and password, if they are the same on both the Console and SQL Reporting Server.
Remember these credentials for use in the AirWatch Console as the user name and password.
3. Clear the User must change password at next logon check box, and select the User cannot change password and
the Password never expires check boxes.
35
Chapter 4: Reports Installation
1. Click the Member Of tab for the user, and add the user to the IIS_IUSRS Group.
2. Ensure the SSRS_USER is also created on the AirWatch Console Server using the same steps. The password must be
same.
Next you must add the SSRS_USER to the Content Manager Role.
3. On the SQL Server, navigate back to the Reporting Services Configuration Manager, select Report Manager URL.
4. Click Folder Settings > Security > New Role Assignment, from the home screen.
5. Enter the created SSRS User and select the Content Manager option.
6. Ensure that the SSRS_USER presents as a Content Manager in the Home folder.
36
Chapter 4: Reports Installation
l Log in as the Windows account you are using to authenticate, if you have not already.
Perform the following steps to install AirWatch Reports:
1. On the SQL Reporting Services server (typically on the SQL server), open the 9.0 Reports folder, right-click the
AirWatch_Reports executable, and Run as an administrator.
3. Choose a folder in which to download all installation files. After the download is complete, the installer uploads
report files to the Report Server.
37
Chapter 4: Reports Installation
4. Complete the database connection information text boxes. A best practice is to connect using the local SQL account
you used to install the AirWatch database, because it already has the correct permissions.
l Connect using Windows authentication credentials.
5. Provide Report Server and SMTP information, as shown. Confirm that the Report Server URL and Report Services
Location are correct.
l rs.exe location - The installer automatically populates this text box. If it is not populated, the typical path for this
file is C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\rs.exe.
l Report Server URL - This URL is the Web Service URL you configured in the step 1.
l Report Service Location - Navigate to Server Manager or go to Services.msc and open the Services tab to locate
Report Services. Right-click "SQL Server Reporting Services" service and choose properties to view the path to
executable. You only need the root directory. If you are running multiple instances of SSRS, then select the one
38
Chapter 4: Reports Installation
l SMTP Port - Pull the SMTP information from the rsReportServer.config file, located under
E:\DirectoryAbove\Reporting Services\ReportServer\rsreportserver.config.
6. For Only Windows authentication credentials: From the SSRS, update the AirWatchDS information in the Connect
using area.
a. Locate and access the AirWatch Data Source in your SSRS instance:
39
Chapter 4: Reports Installation
c. Enter a user name. This user name is the same user name you use to run the SSRS.
e. Select the Use as Windows credentials when connecting to the data source check box and apply your settings.
40
Chapter 4: Reports Installation
41
Chapter 4: Reports Installation
l Domain Name – Enter the domain name of your active directory. This is only needed if you are using a Domain
Service Account.
42
Chapter 4: Reports Installation
43