VMware Site Recovery Manager overview August 30, 2009
Posted by Steve in BCP, Virtualization.Tags: BCP, virtualisation
add a comment
VMware Site Recovery Manager (SRM) is a disaster recovery technology that allows VMware ESX environments to be replicated to a secondary site. The ability to move protected virtual servers between sites quickly and easily takes away a lot of the difficulty associated with implementing a Disaster Recovery (DR) solution. SRM does require a significant investment in hardware and high performance links (fibre is recommended) between sites making it a solution for larger sites.
SRM leverages SAN to SAN replication technology to keep up to date copies of the production Virtual Servers at the recovery site. Any changes made to production servers are replicated in real-time to the recovery site. The recovery site has VMware host servers with Virtual Servers in a shutdown state, in even of a failure at the production site, these servers are started (manually or automatically). SRM uses plug-ins to manage the underlying SAN storage environment simplifying management of the total solution.
Testing and validation of the recovery site is often one of the most complexed and often difficult parts of managing a DR site. One of the best features of SRM is the testing functionality. This allows the recovery site to be tested without shutting down the production environment. VLAN’s are used to isolate the recovery site during the test. This lowers the risks and costs associated with testing the site.
Recovery time is essentially the time taken to boot up the recovery site. Multiple protection groups can be created and started in a predefined order. Within a protection group, servers can be give priorities e.g. Active Directory starts before Exchange servers which start before Citrix and Blackberry.
Basic requirements:
- Two VMware farms (a production farm and a recovery farm)
- Two VMware vCentre servers (one at each site)
- Two SAN’s with replication between sites (a wide range of SAN’s are supported)
SRM can fill a big part of the Disaster Recovery jigsaw and should be considered by any organisation with a VMware environment and DR needs. It is a competitive solution in terms of functionality and low on going management costs. It does require high performance data links between sites so ensure you can get and afford those services at the start of the planning process.
Business Continuity August 18, 2009
Posted by Steve in BCP.Tags: BCP
1 comment so far
Business Continuity is a popular topic at the moment and is high on the list of priorities for businesses around the globe. Business Continuity is about ensuring your business continues to function in event of a disruption (foreseen or unforeseen). Many people think about the stereotypical disasters e.g. building catches fire, earthquake or even terrorist attack. The reality is the around 80% of computer system downtime is actually the result of the people who run the computer system i.e. your IT people and not terrorists.
So what should you do to ensure business can continue in the event of an “IT disaster”?
Before you begin make sure the basics are right
- ensure you have good backups. This is your first line of defence.
- ensure your servers are in a protected environment. UPS, computer friendly environment, secure room etc
- ensure your IT staff know what they are doing and act in the interest of your business.
Develop a Business Continuity Plan
- identify and document your key business processes e.g. order processing, banking
- identify the things those processes identified in step 1 depend on
- work out your threshold for pain i.e. how long can you live without each process
- calculate the business cost if that business process is not available e.g. lost sales, delayed payments etc
- document what you will do if the process is disrupted e.g. manual processing, alternative process
Following these basic steps you will soon get an idea of where your business is vulnerable and how long you can continue before the pain threshold is reached. Businesses with large suppliers or customers should consider getting those partner organisations involved in the plan as they may also be affected if disaster strikes.
One size doesn’t fit all when it comes to Business Continuity, some businesses are happy to ride out a short outage and have manual processes while others require a duplication of IT infrastructure. Compliance with regulations is also an important consideration.
From a technical point of view, a number of technologies can be used to build the IT components of a Business Continuity solution. Virtualisation allows portability of servers and applications. Replication technologies allow data to be copied to a secondary location. Remote access technologies allow employees to work from outside the office. Backup technology can also be an important component of the solution.
Knowing what to do when a disaster occurs is a big part of BCP. Being prepared will reduce the time it takes to recover and reduces panic. It is important to test often and update your plan where necessary.