Citrix XenMobile 10.x Disaster Recovery architecture Design

Mobile devices are rapidly changing traditional modes of operation, making it an unstoppable emerging trend for employees to bring their own devices (BYOD), but in terms of IT management, security controls are a new challenge. Citrix launches Citrix Xenmobile solutions from desktops to mobile devices and becomes one of the leaders in the field.

As each solution grows and matures, there is a need for a corresponding solution architecture for large-scale deployments and disaster recovery, or scenarios where disaster recovery should be considered at the beginning of product design. Starting with the product version of Xenmobile 10.x, this article uses a separate Citrix product NetScaler to integrate the architecture and design a disaster recovery architecture based on the Xenmobile 10.x version.

The disaster recovery architecture designed in this article is designed based on two data, and considers high-availability patterns at the server and software levels in each datacenter. The product knowledge is mainly related to the following:

• Windows AD

• Dns

• NetScaler LB

• NetScaler GSLB

• XenMobile

• Windows SQL Server

The basic framework of its disaster recovery architecture is as follows:

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M00/7C/6D/wKiom1bQHKCSDgZpAAKTVVa7iCA003.png "title=" 001. PNG "width=" 610 "height=" 341 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:610px;height:341px; "alt=" Wkiom1bqhkcsdgzpaaktvva7ica003.png "/>

Frame Description:

1. This architecture uses NetScaler's GSLB technology to carry out disaster tolerance. In two data centers, each data center sends a hardware device that places Citrix NetScaler, building a global load balancing gslb. GSLB in the data center to build a DNS resource pool, under normal circumstances, Site1 Primary Data center, SITE2 for Disaster preparedness Center, all the business will be netscaler to Site1, when Site1 failure, GSLB network switchover, Switch traffic to the disaster Recovery data Center Site2.

The network between 2 and two data centers is interconnected, which facilitates network switchover and synchronization of data configuration. and each data center needs to provide 4 public IP address for configuration use.

3, the mobile device in the public network Unified registration domain name for enroll.silitone.com, and through the public domain name nsg.silitone.com to establish the application level of MVPN.

Data center internal software level xenmobile component design

In a production environment, Citrix recommends deploying the XenMobile solution in a cluster configuration for scalability and server redundancy purposes. To deploy the Xenmobile component:

• NetScaler: Use the NetScaler device to load the Xenmobile clustered server, and to use a VPN for the channels established between the mobile device and the back-end server. To ensure high availability of the NetScaler, use at least 2 NetScaler devices to build an HA or cluster.

• XenMobile. The Xenmobile server is a packaged VM, which is a virtual machine that is directly imported to the underlying server virtualization platform after download and configured with a basic IP address and a subset of initialization information to function properly. After initialization, you can configure policies and settings in the XenMobile console to allow users to enroll their mobile devices. You can also configure mobile applications, WEB applications, and SaaS applications. Mobile apps can include apps from the Apple app Store or Google Play. Users can also connect to mobile applications that you package and upload to the console through MDX Toolkit. To ensure high availability of the Xenmobile server itself, the cluster is built with 2 xenmobile servers.

• Active Directory: Certified with Windows Active Directory. To ensure high availability, build 2 ad servers in two data centers, respectively. Designed with a dual-master approach, each of the 2 ad controllers placed in each data center, each with one ad primary domain controller and one standby controller.

• Information such as the configuration and policies of SQL Server:xenmobile is stored in the database, supports SQL Server databases, and is based on the SQL Server 2014 version. To ensure high availability we use always on technology to ensure that SQL is highly available. A SQL Server 2014 server is placed in each data center, and a total of 2 units make up the always on cluster. If the scale is large, in order to concurrency and load, you can place 2 SQL Servers, a total of 4 SQL Server composed always on cluster.

• License: One in each data center, where the disaster preparedness Center License do cold standby.

The cluster deployment pattern is as follows:

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M00/7C/6C/wKioL1bQHUPQwPwBAADjDedNMN4830.png "title=" 1.png " Width= "603" height= "280" border= "0" hspace= "0" vspace= "0" style= "width:603px;height:280px;" alt= " Wkiol1bqhupqwpwbaadjdednmn4830.png "/>

So the planning table for Site1 is as follows:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/7C/6D/wKiom1bQHS2AQrf5AACcZPyA-SM599.png "title=" 1.png " alt= "Wkiom1bqhs2aqrf5aacczpya-sm599.png"/>

Site2 's planning table:

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M00/7C/6C/wKioL1bQHaighivAAACjx3LMyF4953.png "title=" 2.png " alt= "Wkiol1bqhaighivaaacjx3lmyf4953.png"/>

Data center internal Software service level integration NetScaler high-availability design

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/7C/6D/wKiom1bQHVaQSHxYAABTHWnLV4I170.png "title=" 1.png " alt= "Wkiom1bqhvaqshxyaabthwnlv4i170.png"/>

At the service level, we need to install regular deployments within the datacenter, set up load balancing for MDM and Mam, and set up the NSG

Site1 of the Netscale vserver settings:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7C/6C/wKioL1bQHe3yxe_IAABkhAL4V8A045.png "title=" 1.png " alt= "Wkiol1bqhe3yxe_iaabkhal4v8a045.png"/>

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M01/7C/6E/wKiom1bQHYaQVpYrAAC0Q-32zRk369.png "title=" 1.png " Width= "686" height= "239" border= "0" hspace= "0" vspace= "0" style= "WIDTH:686PX;HEIGHT:239PX;" alt= " Wkiom1bqhyaqvpyraac0q-32zrk369.png "/>

Settings on NetScaler on Site2

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M01/7C/6C/wKioL1bQHiPz_pJMAABpOXiCvHs873.png "title=" 2.png " alt= "Wkiol1bqhipz_pjmaabpoxicvhs873.png"/>

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M02/7C/6C/wKioL1bQHjCjVpU9AAC4GD_DI_w372.png "title=" 2.png " Width= "682" height= "258" border= "0" hspace= "0" vspace= "0" style= "width:682px;height:258px;" alt= " Wkiol1bqhjcjvpu9aac4gd_di_w372.png "/>

Configuring NETSCALERGSLB Design Xenmobile Disaster recovery

If the SITE1 site has the following 4 public network IP address can:

• 50.97.93.43

• 50.97.93.44

• 50.97.93.45

• 50.97.93.46

GSLB Design of Site1

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M00/7C/6C/wKioL1bQHnPxyGMEAAC9e-Qfp4k720.png "title=" 1.png " alt= "Wkiol1bqhnpxygmeaac9e-qfp4k720.png"/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7C/6E/wKiom1bQHguh9NXdAACd1c5vO3M260.png "title=" 2.png " alt= "Wkiom1bqhguh9nxdaacd1c5vo3m260.png"/>

If the Site2 site has the following 4 public network IP address can:

• 75.126.153.43

• 75.126.153.44

• 75.126.153.45

• 75.126.153.46

GSLB Design of Site2

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7C/6C/wKioL1bQHtuQ7Pz2AAC9bfO6e5U214.png "title=" 1.png " alt= "Wkiol1bqhtuq7pz2aac9bfo6e5u214.png"/>

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M01/7C/6E/wKiom1bQHnSSBKmaAACd1DUIv9M683.png "title=" 2.png " alt= "Wkiom1bqhnssbkmaaacd1duiv9m683.png"/>

After the above configuration design is complete, set up a backup server GSLB vServer enroll on Sitei1 NS1, which points to Enroll_dr. Also set up a backup server for the GSLB vServer NSG , which points to Nsg_dr.

Similarly, on the Site2 is the NS1 gslb vServer enroll_dr set up a backup server that points to Enroll. also set the GSLB vServer nsg_dr to a backup server that points to the NSG.

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M01/7C/6C/wKioL1bQHvry3_-IAAEdRVq-JHw238.png "title=" 1.png " Width= "696" height= "233" border= "0" hspace= "0" vspace= "0" style= "width:696px;height:233px;" alt= "wkiol1bqhvry3_- Iaaedrvq-jhw238.png "/>

This article is from "I take fleeting chaos" blog, please be sure to keep this source http://tasnrh.blog.51cto.com/4141731/1745374

Citrix XenMobile 10.x Disaster recovery architecture design