1.
Virtual Heterogeneous Database
Platform
Smith Yang 楊士岳
Trend Micro-Corp IT Technology Team DBA
7/19/2013
Version 0.1

2.
Agenda
 Project Background
 Project Objective
 Virtual Platform and Solutions
 DB Server Model Selection
 DB High Availability Solution
 Datakeeper vs Failover Clustering
 Operation Team’s Concern
 Monitoring Team’s Endorsement
7/19/2013 | Virtual Heterogeneous Database Platform2 |

3.
Project Background
Current physical DB server challenges
• Low utilization : High occupation of rack space
for physical servers
• Physical limitation: Difficulty to move services
in the rack
• High Cost : Hosting and maintenance of
physical servers dedicated for single projects
7/19/2013 | Virtual Heterogeneous Database Platform3 |

4.
Project Objective
 Support direction of Cloud Enablement by
moving 100% of Data Center Virtualization
 Provide a Virtualization Platform to host
multiple database platforms and solutions
requiring high performance
 Provide Security and Performance Isolation
for services while still achieving high degree of
Hardware Utilization
 Improve Efficiency of DB Service through
automated provisioning and management
7/19/2013 | Virtual Heterogeneous Database Platform4 |

5.
7/19/2013 | Virtual Heterogeneous Database Platform5 |
APP APP
SQL SQL
SSD/SAS
CPU
RAM
Hypervisors
SSD/SAS
CPU
RAM
SSD/SAS
CPU
RAM
SSD/SAS
CPU
RAM
Management Layer
APP APP
VIRTUAL SOLUTIONS
VIRTUAL PLATFORM
• Support Legacy DB Services (SQL2005,
2008, MySQL, etc..)
• Multiple HA Solutions depending on
Service Needs (DataKeeper, Replication,
AlwaysOn, Load Balancing Solutions etc..)
• Automated Deployment and Configuration
• Leveraging Application or Database HA
Solutions (not VMware HA)
• Platform to Support Cloud Design
• Utilize local SSD and Caching Technology
to improve IO capability by a factor of x10
• Segregation of Services into Different
Virtual Machines
• Compute Performance Isolated Per
Service
• Security Isolated per Service
• Platform to Support Package Apps (see
above)
• Full Utilization of Hardware
Orchestration
Virtual Platform and Solutions

6.
DB Server Model Selection
Consumption Low Medium High
CPU 1 v-CPU 2 v-CPU 4 v-CPU
Memory 8 GB 16 GB 32 GB
 Compute resource allocation for VM server
• VM local storage allocation base on service need
Model High
Performance
High
Capacity
Hard disk Pure SSD Hybrid SSD+SAS
Capacity Up to 2880 GB Up to 4860 GB
Note. Higher resource request would be exception only
Local Datastore

7.
DB High Availability Solution
Features Datakeeper Clustering Mirroring AlwaysOn
Log
Shipping
Replication
Software
Hardware
DKCE
Licenses
MS-SQL /
Storage
MS-SQL
MS-SQL
2012
MS-SQL MS-SQL
Auto
Failover
Yes Yes
Yes
(HA mode)
Yes No No
Units
Node
Server
Node
Server
DB
Group of
DB
DB
Table
Articles
Data
Replica
1 (*) 0 1 0-4 Unlimited Unlimited
Note (*) New version DKCE allow for snapshot at Mirror node,
offload the backup and reporting from Primary node
Our application level solutions can also utilized similar to physical DB servers.
7/19/2013 | Virtual Heterogeneous Database Platform7 |

8.
Datakeeper - Alternative Approach to Clustering
Traditional Clustering - Shared SAN Storage Clustering with Local Storage and Datakeeper
Challenges :
• No Persistent Shared Storage Options
in AWS – Not cloud ready
• Requirement for Shared SAN Storage
• Disaster Recovery Requires Expensive
SAN Replication Technology
• 1 Copy of the Data
• Complex Setup – Raw Device
Mappings
Benefits :
• Fully Supported HA Solution in AWS
Public Cloud – more here
• Local Storage – no SAN
• Low cost solution for keeping
Disaster Recovery site in synch.
• Mirror Copy of data can be used to
offload backups and reporting
• Simple to configure
7/19/2013 | Virtual Heterogeneous Database Platform8 |

9.
 Future Flexibility : DC OPs consider to reserve more resources
(HBA/Memory/HDD) in server.
 Multiple Cluster Nodes Design : We could have enough time to
recovery from any hardware failure.
 Standard SOP : Exercise and rebuild in pilot test servers.
 Parallel Pilot : P2V transformation from Production then test
together with service owners.
 Get Familiar With : Maintenance for Windows Cluster + SQL 2012
AlwaysOn AG + Datakeeper.
 Performance Impact : While multiple DB Instance running
together in one physical server.
 Network Loading : Monitor 1GB Ethernet Switch within
DataCenter and cross-site utilization.
Operation Team’s Concern
7/19/2013 | Virtual Heterogeneous Database Platform9 |

10.
The monitoring scope of new DB platform can be covered by
the following tools.
Monitoring Team’s Endorsement
Item Monitor Tools
Service availability PRTG, Quest Foglight
Performance Monitoring Quest Performance Analysis
Capacity Management PRTG, Quest Capacity Manager
Backup Quest LiteSpeed, Veeam, SQL Backup,
CommVault
Audit MS SQL Audit tool
7/19/2013 | Virtual Heterogeneous Database Platform10 |

11.
Q & A
7/19/2013 | Virtual Heterogeneous Database Platform11 |