Speaker Murali KK
Business Continuity Challenges
Too many roadblocks out there:
- Too many complications, problems and mistakes.
- Too much data with insufficient protection
- Not enough data retention
- Time-intensive media management
- Untested DR & decreasing recovery confidence
- Increasing costs
Businesses need simpler and standardized DR. Costs are too high in terms of OPEX, CAPEX, time, and risk.
- Automate, automate, automate
- Tigther integration between systems availablity and data protection
- Increase bradth and depth of continuity protection
- Eliminate the tape problem. Object? You still using punch cards?
- Implement simple failover and testing
- Get predictable and lower costs and operations availability
Moving into Microsoft Solutions …
There is not one solution. There are multiple solutions in the MSFT portfolio.
- HA is built into clustering for on-premise availability on infrastructure
- Guest OS HA can be achieved with NLB, clustering, SQL, and Exchange
- Simple backup protection with Windows Server Backup (for small biz)
- DPM for scalable backup
- Integrate backup (WSB or DPM) into Azure to automate off-site backup to affordable tapeless and hugely scalable backup vaults
- Orchestrated physical, Hyper-V, and VMware replication & DR using Azure Site Recovery. Options include on-premises to on-premises orchestration, or on-premises to Azure orchestration and failover.
Covering physical servers and VMware virtual machines. This is a future scenario based on InMage Scout.
A process server is a physical or virtual appliance deployed in the customer site. An Image Scout data channel allows replication into the customers virtual network/storage account. A configuration server (central managemetn of scout) and master target (repository and retention) run in Azure. A multi-tenant RX server runs in Azure to manage InMage service.
How VMware to VMware Replication Works Now
This is to-on-premises replication/orchestration:
There are two vSphere environments. He is going to replicate from one to another. CS and RX VMs are running as VMs in the secondary site.
There is application consistency leveraging VSS. A bookmarking process (application tags) in VMs enables failover consistency of a group of servers, e.g. a SharePoint farm.
In Scout vContinuum he enters the source vSphere details and credentials. A search brings up the available VMs. Selecting a VM shows the details and allows you to select virtual disks (exclude temp/paging file disks to save bandwidth). Then he enters the target vSphere farm details. A master target (a source Windows VM) that is responsible for receiving the data is selected. The replication policy is configured. You can pick a data store. You can opt to use Raw Device Mapping for larger performance requirements. You can configure retention – the ability to move back to an older copy of the VM in the DR site (playback). This can be defined by hours, days, or a quote of storage space. Application consistency can be enabled via VSS (flushes buffers to get committed changes).
- Support to migrate heterogenous workloads to Azure. Physical (Windows), Virtual and AWS workloads to Azure
- Multi-tenant migration portal.
- And more I can’t type fast enough!
You require a site-to-site VPM or a NAT IP for the cloud gateway. You need to run the two InMage VMs (CS and MT) running in your subscription.
There was a little bit more, but not much. Seems like a simple enough solution.