Hello everyone. My name is Chushing Chen and I'm a technical marketing engineer with NetApp. Today I'd like to give you an overview of the Flexpot data center with NetApp SnapMir business continuity and ant 9.10 solution. Let's first take a look at the ONAP snap mirror business continuity solution or SMBC solution. It includes two untapped clusters peered together to enable synchronous replication of data for disaster recovery and business continuity purposes.Consistency group relationships or CG relationships are created to protect the volumes and lungs containing the volumes by synchronously mirroring the data between the clusters. From the perspectives of an application such as the Microsoft SQL server, database transactions pause briefly when a disaster strikes and then they quickly resume when the data services automatically continue from the surviving side. Flex pod data center with NetApp SMBC solution utilizes tier one storage network and compute components from NetApp and Cisco. It protects fiber channel and ICE sand data services against single point of failure scenarios as well as a site disaster. The solution can be deployed between two sites with up to 10 millisecond network latency to achieve zero recovery point objective and very low recovery time objective. You can build a flex pod SMBC solution by utilizing two existing flex pods, adding a new flex pod to an existing flex pod or deploying two new flex pods. The two flex pots can form activedata center and use SMBC to ensure the continuity of business critical data services for both sides. For storage, you could either use all fresh fast storage systems at both sites or use the all send array systems at both sites. The untapped mediator deploy at the surf site monitors the solution and facilitates automated failover in case of a disaster. You will also need a multi-sight network fabric for the connectivity between the sites. Flex by SMBC solution can also be deployed to protect critical data services of multiple branch offices in a metro area. You will create CG relationships for each branch office to protect its critical data services. For this use case, be sure to carefully plan the CG relationships to make sure that the total object counts at the data center do not exceed the supported limits. VMware high availability can be configured on the solution. It can allow VMs to be restarted at the other site when there is a complete compute failure at the site. The AMAB SMBC is used to implement a symmetric VMware via metro storage cluster solution to overcome a safe storage failure scenario. The VMs and workloads can be spread out into the two data centers based on requirements and they should normally utilize local data stores to optimize storage access and performance. The two sites deployed for the solution validation have similar flex configurations except for using different Nexus switches. The site connectivity is provided by connecting the flex path switches at the two sides together to extend VLANs across the sides. As a result, the ESXi host at each site can access storage at both sites. After deploying the flex paths, according to CVD best practices, the onep storage clusters appear together by using Antip system manager. Then an ONEP mediator is deployed at the SE site for solution monitoring and to facilitate automated failover in case of a site disaster. After the infrastructure and applications are deployed, it is time to protect the business critical data volumes by creating CG relationships between the two storage clusters. For this solution validation, all volumes utilized are crossprotected with site A data stores and post boot ls protected by site B and vice versa. From an ESXi host perspective, it is configured to utilize both SAM fabrics to access its LUNs from both storage clusters. Under normal situation, the lungs are accessed from the primary site. When the primary site is not available, IO's are serviced from the secondary site. You can start a CG relationship failover from the ANTP system manager to perform failover testing and to validate the deploy configuration. As failover is granular at the CG level, you can test a specific application without impacting other applications. An automatic failover happens when there is a site storage disaster. As shown in the performance pane, the additional IOPS and throughput near the end of those graphs indicate that the surviving cluster picked up additional workloads in the CG relationships. Microsoft SQL Server and Hammer DB database testing tools are included as part of the validation. During the implant failover testing, the database transactions paused briefly when the site where the SQL server database resides failed. After the automatic failover of data services to the surviving site, the database transactions resumed as shown in the Hammer DB tools transaction counter view. For more information about FlexPath solutions, please visit flexpath.com. Thank you very much.