IT Service Continuity (Disaster Recovery Plan)

1. Identify hosting Site which needs to be available Active/ Standby in both of the DataCenters.
2. Understand and Identity replication method between the sites.
3. DNS failover multiple options : 
load balancer GSLB
dynamic DNS : publically available 


http://dyn.com/dns/ or http://www.dnsdynamic.org/
​register domain name, then under domain name configure both the sides.

what we did in our organisation was register companies domain name to dyndns and ask clients to do cname. You need to configure two public IPs which dyndns will track processes.

Let me explain Vmware replication, Vmware site recovery Manager and later what is Dynamic DNS and how to setup.

VMware vSphere Replication 5.5

vSphere Replication is a feature of the VMware vSphere platform. It copies a 
virtual machine to another location, within or between clusters, and makes that
copy available for restoration through the VMware vSphere Web Client or through 
the orchestration of a full disaster recovery product such as VMware vCenter Site 
​Recovery Manager. 

How does it work?

vSphere Replication is a deeply integrated component of the vSphere platform. 
​It is the only true “hypervisor-level” replication engine available today.

Changed blocks in the virtual machine disk(s) for a running virtual machine are 
sent to a secondary location, where they are received by a virtual appliance that 
writes them to an on-disk redo log. Only when that redo log is complete and all 
blocks in a given replication are received is that set of data applied to the virtual 
machine disks for the offline (protection) copy of the virtual machine.

​Configuring replication for as many as 500 virtual machines through the same management interface that is used for all VMware vCenter operations is an easy process of right-clicking a virtual machine and selecting the destination for its replica.

vSphere Replication performs an initial, full synchronization of the source virtual machine and its replica copy. 

After baseline synchronization is complete, vSphere Replication switches to transferring only the blocks of data that have changed. This ensures that a minimal amount of data is sent over the network to the target, and it enables aggressive RPOs. After unique data has been sent, there is no need that it be sent again. Only changes are replicated, and those blocks are sent to the target location’s vSphere Replication Appliance.

​

There are lot more interesting topics under Vmware Replication;

*​Simplicity Without Sacrificing Functionality

*Protected site replicating to Target Site 1 and Target Site 2.

*Replication between multiple Remote Sites managed by Different Vcenter

  server system instances.

*Recovering a Virtual Machine.

*Retention of Multiple Points in Time.

We cover all these topics with Live examples during our Vmware and Datacenter Classes.

Now Lets Discuss "VMware vCenter Site Recovery Manager - Automated Disaster Recovery Orchestration"

What Is vCenter Site Recovery Manager?

vCenter Site Recovery Manager is the industry-leading disaster recovery (DR) management solution. Site Recovery Manager provides automated orchestration and non-disruptive testing of centralized recovery plans for all virtualized applications.

Site Recovery Manager can integrate natively with vSphere Replication.

How Does It Work?
VMware vCenter Server™. Site Recovery Manager instances 
deployed at both production and recovery sites integrate directly 
with local vCenter Server instances.
​Replication. Site Recovery Manager requires an underlying replication
technology to copy ​virtual machine (VM) data to the recovery site.

*vSphere replication

*Array-based replication

Key Benefits

​*Lower Cost for DR

*Hardware and APP independence

*Simplified setup

*Centralized recovery plan

*Non-Disruptive testing

*Automated disaster recovery Failover

*Automated Failback

There are lot more new features and technologies incorporated in VMware vCenter Site Recovery Manager 5.0 which we will cover in our Trainings and test all of them in our LAB setup. 

Lets Discuss Dynamic DNS now..

The main differences between regular DNS and dynamic DNS are:
1)How often an IP address is updated
2)How the IP is updated
3)And the speed at which the new address is communicated to the rest of 
the internet.

Dynamic DNS updates a DNS server with new or changed records for IP addresses
without the need for human intervention. This allows a fully qualified domain name
(FQDN) that never changes to be associated with a dynamically assigned IP address 
​that can change quite often.

Static DNS:

​When a computer is connected to the internet with a static IP address, setting up the DNS for the domain is a relatively simple matter of adding an A record to the domain name's zone file.
​A zone file is just a special text file describing everything about a domain name, where to send email for the domain, and where the website is located for example.
​The A record is that section of a zone file that specifies the name and the IP address where the appropriate server is located. 

Here is an example of an A record:
www.example.com.   IN A  192.168.1.2 

​Zone files are stored on a computer called a nameserver. A nameserver is a computer that is designated to answer all questions from other computers about specific domain names.

For all the queries and explanations please contact helpdesk @ +91-9643459703 or write to us at helpdesk@itechglide.com

VMWARE and CLOUD classes are already going on. Please contact on above details for Registeration.