PlateSpin Forge Guide Book. IT Business Continuity Planning and Management with PlateSpin Forge

Transcription

1 PlateSpin Forge Guide Book IT Business Continuity Planning and Management with PlateSpin Forge

2 IT Business Continuity Planning and Management with PlateSpin Forge

3 Introduction Information technology, or IT, is used on a day-to-day basis in many fields of business, and it is no exaggeration to describe IT as a key infrastructure without which corporate activities cannot continue. Improving the usability of IT systems while maintaining an environment that ensures stability is surely one of the most central roles of any IT department. Engagement in business is a make-or-break issue for many corporations. Strategies can be created from a number of different perspectives, by planning business in terms of management of corporate resources such as personnel, assets, capital and information. In this document we will specifically focus on IT business planning, or IT-BCP. A range of IT-BCP methods can be adopted to suit the importance of the data being stored or the importance of the system. A luxurious environment with unlimited resources is a rare thing indeed. So the main goal is to maintain an environment that ensures business while at the same time costs are being minimized as much as possible. In this document we introduce the PlateSpin Forge hardware appliance as the optimal strategy for such a business environment. Of all the approaches available in the field, PlateSpin Forge represents the business solution which is both the most practical and most economical to implement. The central feature of PlateSpin Forge is its full utilization of virtualization technology. It permits fast and straightforward failover, by switching a new system in as the production server with a simple click in the event of a disaster. Moreover, once the original unit has been repaired or replaced, PlateSpin Forge allows straightforward failback, by switching back to the fully recovered original environment. This document casts a fresh eye on various approaches to business being taken by corporations, and explains their distinct methodologies. In doing so, it will become clear why PlateSpin Forge is the optimal solution. We hope this document will help you plan appropriately for IT business in your corporation.

4 Approaches to business Contents Introduction 2 The cost of business chapter 01 Approaches to business 4 chapter 02 The cost of business 16 Merits and demerits of IT-BCP solutions chapter 03 Merits and demerits of IT-BCP solutions 26 chapter 04 PlateSpin Forge as IT-BCP solution 40 PlateSpin Forge as IT-BCP solution chapter 05 PlateSpin Forge usage 52 chapter 06 PlateSpin Forge GUI 70 PlateSpin Forge usage PlateSpin Forge GUI

5 chapter 01 Approaches to business 4

6 Approaches to business The cost of business The importance of business 6 Required approaches for business 8 Merits and demerits of IT-BCP solutions Historical and current guidelines for business 10 Tuning IT systems components 12 The power of virtualization technology for business 14 PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI 5

7 chapter 01 Approaches to business The importance of business Creating an environment capable of enabling business to continue despite disaster or breakdown is an essential part of risk management and cannot be ignored by corporations. Even where an interruption to operations is inevitable, it is essential that they are back up and running as quickly as possible. For this reason, corporations world-wide invest in business planning (BCP), which seeks to protect the corporation from reduced market share or reduced corporate value by recovering from interruptions to operations, or avoiding them all together. A number of approaches can be taken to define BCP, but in its document PAS56 Guide to Business Continuity Management, the British Standards Institution (BSI) defines it as " planning which recognizes impacts due to potential losses, establishes and implements an enforceable strategy, and ensures business in the event of an emergency. Business outcomes which document procedures and information, developed, compiled and maintained for use in the event of an emergency." Efforts to establish, operate, simulate and continuously improve BCP are generally known as business management (BCM). Information technology (IT) systems are already extensively deployed by corporations, and the importance of IT systems as business infrastructure is increasing. For this reason, IT infrastructure presents a very real risk to the continuous operation of corporations and to the provisioning of services. This is why we think of IT business planning (IT-BCP) as a separate field of BCP, focused on IT. Ordinarily, BCP initiatives include measures such as maintaining backup systems and ensuring a backup office, accelerating safety confirmation procedures, ensuring staff and arranging alternative production facilities. This document however focuses particularly on issues within IT-BCP, concerned with maintaining backup systems. When considering BCP initiatives, it is necessary to think about the recovery point objective (RPO), the point in the data record and the age thereof at which recovery is acceptable, the recovery time objective (RTO), the amount of time it takes to restore services, as well as the recovery level objective (RLO), the level of operations to be recovered. Additionally, day-to-day training for business should consider the test time objective (TTO) metric, which asks how easy the system is to test. 6

8 PlateSpin Forge guide book Approaches to business Level of operation (quantity of product supplied, etc.) Before 3 Enables business to continue at a level above a set threshold 100% Restoration Target Current expected recovery curve After (initial and BCP response) Recovery curve after implementing BCP 2 Enables restoration of operations within a set time frame Threshold 1 Difference between target and actual recovery time Target Threshold Time The cost of business Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution Ref: Keywords for business RPO: Recovery Point Objective How recent should the recovered data be? RTO: Recovery Time Objective How much time should be allowed for recovery? RLO: Recovery Level Objective What level of granularity should be recovered? TTO: Test Time Objective How easily can testing be carried out? Conceptual diagram of BCP measures Service level 100% under normal conditions Status of data at time of provisional recovery RLO RPO Disaster occurs RTO Provisional recovery Full recovery Time PlateSpin Forge usage PlateSpin Forge GUI Ref: Definition of BCP: 7

9 chapter 01 Approaches to business Required approaches for business When considering business risk as a factor in business, several perspectives must be incorporated. These perspectives cover a broad range of topics including exchange fluctuation risks, recall risks associated with quality assurance, litigation risks and production equipment related risks such as plant fires. Some of these could be included in IT related business risk. But in particular, both breakdown risks and disaster risks must be considered as factors in IT risk. Breakdown risks are risks arising primarily due to machine, equipment or human errors, and include hardware breakdown, primarily concerning server or network equipment, and communication services breakdown such as services provided by contracted telecommunication operators or data center services. By precautionary, we mean measures to avoid encountering damage. Specifically, these would be measures such as seeking to improve reliability of systems such as through load distribution or redundancy, or migrating to a robust and secure data center capable of handling disasters. Recovery means providing an environment capable of implementing rapid failover, e.g. by implementing backups and having alternative servers as an emergency precaution. Providing day-to-day training in preparation for an emergency is another effective means of achieving rapid recovery. Disaster risks are risks that are likely to arise due to a natural disaster such as an earthquake or typhoon, and include large-scale systems breakdowns such as loss of or interruption to communication lines to data centers. Handling these risks requires consideration of BCP measures from both a precautionary and a recovery perspective. 8

10 PlateSpin Forge guide book Approaches to business The very real IT risk to business, and countermeasures IT risk Preventative countermeasures Recovery countermeasures The cost of business Minimizing risk (threat avoidance and reduction of vulnerability) Loss/damage minimization on realization of risk Failure risk Internal factors Disaster risk External factors (unavoidable) Hardware failure Failure of communication services Processing overload Software bugs Operational error Computer crime Local disaster Widespread disaster Earthquakes Power failure/ restrictions Tsunami/flood Loss of data services Improving system reliability Redundancy, load balancing, QA, SPOF avoidance, etc. Data center ruggedization Favorable location, seismic isolation, redundancy in equipment / circuits, etc. Backup and recovery Backup acquisition, preparation of alternative devices, failover, training, etc. Primarily on-site control Remote site control Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI * QA: Quality assurance, SPOF: Single point of failure, Exhibit: ITR 9

11 chapter 01 Approaches to business Historical and current guidelines for business Originally, BCP existed as a concept from the 1960s called disaster recovery (DR) and set out disaster recovery countermeasures to cope with host computer breakdown. The term BCM emerged as a management concept in the 1999 British Standards Institution (BSI) standard on Information Security Management Systems (BS7799). This was later developed into Business Continuity Management Systems (BS25999) to handle a wide range of organizations, and BCM is now applied by an increasing number of corporations at the management level. in March 2005, and the Business Continuity Guidelines Ver. 1 by the Central Disaster Prevention Council of the Cabinet Office in August of the same year. In February 2006 the Small and Medium Enterprise Agency published an introductory examination and a range of templates for BCP policy formation under the title Small and Medium Enterprise BCP: Guidelines for Formulation and Application. Then, in November 2009 the document Business Continuity Guidelines Ver. 2 was published to simplify the application of Business Continuity Guidelines Ver. 1. The requirements of BS25999 were later turned into an ISO standard, the International Standard for Business Continuity Management Systems (BCMS) ISO 22301, issued in May These standards are applied to all organizations, including corporations, public bodies, not-for-profit organizations and NGOs, whatever the scale or activities of the organization. They are set out as standard requirements explicitly identifying the control items that need to be implemented. In contrast, the process of establishing guidelines in Japan involved the publication of the Business Continuity Policy Formation Guidelines by METI In terms of guidelines on the subject of IT-specific issues (IT-BCP), METI provided the IT Service Continuity Guidelines in September 2008, and the Information-technology Promotion Agency (IPA) provided documents including the well known Highly Resilient System Infrastructure Guidelines (Summary, Planning) in May Finally, the National Information Security Center is due to release guidelines looking at IT-BCP including the Operational Continuity Planning Guidelines for Information Systems in Central Government and the supplementary IT-BCP Formulation Model. 10

12 PlateSpin Forge guide book Approaches to business Business Continuity Guidelines Version 2 Contents Key Points 1. What are business initiatives? 1 2. Features of business initiatives 3 3. Features of these guidelines 3 4. Aims of and issues promoted by initiatives Estimating damage to key activities Extracting key elements Establishing a business plan Defining the command structure Standpoint of these guidelines Ensuring functionality at key corporate sites Adopting a checklist External data transmission and data sharing IT system backup 20 I. Basic approach to business requirements Product-service supply relationship Issues to be derived in conjunction with 1.1 Requirements and key points in business The need to make business work in times of emergency Key points in the approach to business Features of business planning in Japan: being ready for widespread natural disasters 7 business Safety assurance and safety confirmation Disaster damage mitigation for offices/places of work and equipment Prevention of secondary disasters Community cooperation and contribution Cooperation and mutual aid Basic approach Other matters to consider Hypothetical disaster risk Issues to be derived in conjunction with business Standpoint of each item provided in these guidelines Implementation and operation Implementation of measures under business plan Preparation of documents Preparation of protocols and manuals Continuous improvement Preparation of checklists Financial allowances 25 II. Content of business plans and initiatives Confirming the plan works in practice Requirement for business decisions in event of 2.1 Policy Planning 12 emergency Implementation of education and training Identifying relevant disasters Evaluation of impact Inspections and corrective action Estimating stoppage time and responsiveness Management level estimates Determining key activities Setting RPO and RLO 14 III. Proposals for managers, the economy and society 28 The cost of business Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI IT systems operation planning guidelines for central government: 11

13 chapter 01 Approaches to business Tuning IT systems components When thinking about IT-BCP, a major prerequisite is that we understand the resources required to continuously operate IT systems. It is essential for business that a strategy is developed for every such resource. Specifically, required resources might be hardware to run systems, system-based resources such as applications or system configurations, data-based resources including management of backup data, facilities to house systems, and an uninterruptable communication network. In practice, additional resources are required such as a non-emergency testing system and an on-site operational system to investigate IT-BCP, and even business partners who also have business capabilities and alternative procedures to restart activities, should a disaster happen. We clearly see that a vast number of resources are needed to achieve operational of IT systems. Taking hardware as an example, for hardware with a low recovery priority, the countermeasure objective may be considered as entering into contracts for hardware maintenance and having the ability to obtain repaired or replacement parts. As the recovery priority increases, the objective might be keeping a backup unit on hand at a remote site away from the system operations site, and ensuring hardware is available on cold standby for setup in the event of an emergency. For hardware with the highest levels of recovery priority, the objective could be to provide an exclusive replacement unit at a remote site with synchronized data, and ensuring an environment capable of rapid recovery by switching to the replacement unit in the event of an emergency. It is crucial to have a clear idea of the recovery priorities and countermeasure objectives for each IT system resource. Setting a priority for recovery of each of these resources enables us to understand practical recovery level objectives. Understanding recovery level objectives provides information on where current measures are lacking, and helps to define future measures. 12

14 PlateSpin Forge guide book Approaches to business Example IT system components Component Explanation of component 1 Hardware Role, quantity and location of hardware such as servers (including for replacement units) The cost of business 2 System-related Location and status of data required for recovery of IT systems, such as applications and system configuration data (external storage of backup media, etc.) 3 Data-related Location and status of key data (external storage of backup media, etc.) 4 Facilities 5 Data communication network Environmental aspects for IT system equipment (location, robustness, presence of on-site generator and presence of backup center within buildings or at data center, redundancy of electricity system, water supply, etc.) Arrangement of data communication networks (within buildings and externally such as between sites) required for use of IT systems (carrier, type, route diversification, etc.) 6 IT-BCP analysis system (* Item added in this study) System for constant analysis of IT-BCP content Merits and demerits of IT-BCP solutions 7 System operational structure Ensuring operational human resource and role allocation to achieve rapid confirmation of damage to systems and appropriate responses, and ensuring maintenance of standard operating procedures and means of communication. 8 Business capabilities of vendors 9 Fallback system Support and collaboration structures with IT system vendors in case of an emergency (capturing of vendors' business capabilities, maintenance of service assurance contracts, etc.) (* Item added in this study) Hardware Countermeasure Objectives Level Alternative procedures for recovery of operations where IT systems are suspended in case of an emergency PlateSpin Forge as IT-BCP solution Recovery Priority Rank S A Countermeasure Objective Ensuring hardware for hot standby Provision of exclusive replacement units in locations which will not be simultaneously subject to the same disasters as production units. Recovery is performed through backup systems by switching in an replacement unit in case of an emergency. Provision of alternative client PCs for use in case of emergency. Countermeasure Level 3 PlateSpin Forge usage B C D E Ensuring hardware for cold standby Provision of a backup unit in a state requiring setup at a location which will not be simultaneously subject to the same disasters as the current location. Utilize thin clients to avoid impact on client environments due to damage to the working environment. Elimination of end-of-maintenance parts through hardware maintenance contracts (recovery at damaged sites) Ensuring that hardware which cannot be confirmed after sale is not used. Enter into maintenance contracts to ensure parts repair and replacement parts are available when damage is incurred to hardware. Regular saving of data on client PC operating systems. 2 1 PlateSpin Forge GUI Ref: 13

15 chapter 01 Approaches to business The power of virtualization technology for business Let us now think about specific strategies for business in the IT field, i.e. IT-BCP measures. We often hear about efforts to increase redundancy in IT systems and improving fault tolerance through the use of clusters. For high priority tasks, it is obvious that a backup environment is required at a different location to the production site, but it is important above all to create a highly flexible system that allows operations to be rapidly redeployed. The key benefit of providing a remote environment is that even if the production site is knocked offline by a natural disaster, there is no loss of data. Additionally, in the event of a large-scale natural disaster that renders the production site inoperable, it provides an additional service as a backup site for re-initiating the systems in a short period of time. This is also where virtualization technology comes in. Virtualization technology enables physical environments to be deployed as virtual machines, and allows systems to be designed and built freely using a hypervisor, with no hardware platform dependence. This technology not only enables migration to different environments, but is also ideal when used as a system infrastructure for BCP, enabling the automation of the operational management of system. The key features of virtualization technology are increased reliability and availability, while making efficient use of computing resources. Considering the prerequisite that the IT environment should be fully recoverable, it is clear that systems that are dependent on a specific hardware environment should be avoided as far as possible. Where possible, systems should be built to be quickly recoverable, without depending on infrastructure such as hardware. This is why it is so important to make sure that operating systems and applications are not platform-dependent and are structured with flexibility. 14

16 PlateSpin Forge guide book Approaches to business Difference between physical environments and virtualized environments Virtual Machine Application Application Application Application The cost of business Physical Machine Guest OS Guest OS Guest OS Guest OS Application Application Operating System x86 Hardware Physical Machine Virtualization platform x86 Hardware Merits and demerits of IT-BCP solutions CPU Memory Disk NIC CPU Memory Disk NIC PlateSpin Forge as IT-BCP solution Conventional IA server One OS on one server Inefficient use of resources Close integration of software and hardware Virtualized platform Virtualized hypervisor High performance Flexible resource management Independent from software and hardware PlateSpin Forge usage Unlike physical environments, virtualization technology transfers the close connection to the hardware to the virtualization platform. This enables the virtual machine to operate flexibly, with no specific platform dependence. PlateSpin Forge GUI 15

17 chapter 02 The cost of business 16

18 Approaches to business The cost of business Cost considerations for business : hardware 18 Cost considerations for business : software 20 Cost considerations for business : personnel 22 Cost considerations for business : other 24 Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI 17

19 chapter 02 The cost of business Cost considerations for business : hardware In this chapter we will look in more detail at the costs of IT-BCP. Firstly, we have to ask what hardware elements are required. provider, or another alternative would be to build a customized environment using robust remote data center facilities. The first thing to understand is that it is somewhat difficult to generally predict what hardware is required, as the recovery time objectives (RTOs) and recovery point objectives (RPOs) differ depending on the type and priority of system. The biggest differences in hardware configurations arise from the necessity for rapid recovery and the necessity for recovered data to be perfectly up-to-date. For example, if the RTO and RPO are set to a short period or time, then system redundancy is the key premise. In this case, the backup site has to be ready with the same system environment as the production environment. In practice, this requires new storage such as a storage server or SAN, network devices such as routers and switches, load balancers and application delivery controllers (ADCs) as required to distribute load, and web application firewalls (WAFs) to handle security. For low priority systems allocated a medium or long RTO and RPO of several days to one month, the general method would be to restore data once the new environment would be ready, having prepared a backup of data and system parameters on portable media such as tape. In this case we use a tape device such as an autoloader or tape library for backup of production environment data, requiring storage on multiple volumes of tape media such as LTO tape drives. However, it must not be forgotten that to finally recover the original state, the hardware for operating the production environment must be redeployed or repaired. One option would be to use a public cloud rather than setting up the environment internally, but this raises the difficult issue of configuring it in exactly the same way as the production environment. One method would be to use a private cloud environment outsourced to a systems integrator or service 18

20 PlateSpin Forge guide book Approaches to business DB server AP server LAN switch The cost of business If the RTO and RPO are relatively short SAN switch Router ADC/WAF periods, less than 24 hours, either hot or cold standby methods may be used in a remote installation mirroring the production environment. Merits and demerits of IT-BCP solutions SAN storage PlateSpin Forge as IT-BCP solution If the RTO and RPO are relatively long periods, a backup of production environment data and system parameters is PlateSpin Forge usage Tape media Tape library made to a portable media such as tape. PlateSpin Forge GUI 19

21 chapter 02 The cost of business Cost considerations for business : software The software that is required will naturally differ depending on the hardware configuration. If the RTO and RPO are set to short periods, under 24 hours, some sort of replication tool will be required to make regular copies of data to a backup site. When a method using an intrinsic replication function of SAN storage or some similar technology is adopted, then this requires advanced hardware. Additionally, in order to maintain the backup site as an equivalent environment, this method generates a requirement for software licenses that mirror the production server, including server operating systems and applications, antivirus software, and server virtualization software to act as the hypervisor needed for the virtual environment. As some vendors have license terms allowing use of software at backup sites, the calculation is not as simple as just doubling the cost. est backup tools, a growing number of products support virtual environments, and incorporate the functions necessary for IT-BCP. Some backup tools include options with replication functionality, but as many backup appliance products have their own internal software functionality, this software may not be required, depending on the environment. Systems for which a one week to a one month recovery timescale is appropriate do not require real-time data copying. A data backup may be made according to a schedule to portable media such as tape, and restored once the hardware is ready for recovery. The software required in this case is a backup tool to be used when performing backup and restoration to tape. Amongst the lat- 20

22 PlateSpin Forge guide book Approaches to business Data backup System backup Key functions of legacy backup software Complete backup Incremental backup Differential backup Single file backup Deduplication Open file backup Disk image RAW backup The cost of business Merits and demerits of IT-BCP solutions Backup devices Tape backup (D2T) Disk backup (D2D) D2D2T Cloud backup PlateSpin Forge as IT-BCP solution Recovery Single file Bare metal Virtual machine PlateSpin Forge usage Application agent SQL Server Oracle Database Lotus Domino Exchange Server PlateSpin Forge GUI 21

23 chapter 02 The cost of business Cost considerations for business : personnel Now let s examine the cost of tasks that are likely to arise during the day-to-day operation of infrastructure at a backup site. First and foremost, if RTO and RPO are defined to be short, then a state of the art replication infrastructure will have to be provided at the backup site. If there are plans to rebuild the production environment, the opportunity should be taken to setup both sites concurrently, while incorporating data copying techniques such as replication into the design. This is an efficient way to build a backup site. When a backup site is built to support an operational production environment, it is important to ensure the hardware infrastructure and software are as similar to the production environment as possible. If an unavailable CPU type or an older version of the software is used, it may be necessary to update the backup site, which may require considerable time and effort in verification and testing. Once the backup site is set up, thought must also be given to labor costs for routine operational and maintenance tasks. If a hot standby unit is already operational, the same monitoring solution that is used at the production environment will be necessary, and any software upgrades and server operating system security patches must also be applied. Cold standby units will also require regular operating system and application upgrades. Maintaining the backup system in the same way as the production system ensures that work can proceed without a glitch in the event of an emergency. If the RTO and RPO are not quite as aggressive, the routine backups as described earlier would still apply as a strategy. Where backup is performed to tape or similar, the tapes would need to be transferred to a remote location, and their storage would require careful management. Another cost that arises, regardless of the timescale, is regular testing and training to confirm that recovery would be possible in any event. A strict schedule should be prepared and the switching process verified, showing that the backup site could be setup under conditions where the production environment is offline. This element also incurs a labor cost. 22

24 PlateSpin Forge guide book Approaches to business The cost of business Network setup Routine monitoring Upgrades Merits and demerits of IT-BCP solutions Backups Security patching PlateSpin Forge as IT-BCP solution Recovery testing PlateSpin Forge usage In addition to building the initial environment, routine operations such as monitoring and upgrade operations must also be considered. Recovery verification testing is another essential. PlateSpin Forge GUI 23

25 chapter 02 The cost of business Cost considerations for business : other In addition to the hardware, software and personnel costs already addressed, there are a number of other costs associated with IT-BCP that cannot be ignored. If a rapid recovery is sought, routine online backups are required, but for high volume backups this requires a dedicated broadband connection. Even if incremental and differential backups or deduplication is being used, it may be impossible to run the backups on the same connection as ordinary tasks. In these cases, a duplicate connection would definitely aid IT-BCP. It is important to review the bandwidth available on existing network connections. Alternatively, if the backup site is always in operation, there would need to be a calculation of the costs associated with the backup, such as electricity costs. Options for power outages such as UPS or on-site power generation should also not be ignored. On-site power generation would also incur costs related to ensuring a source of fuel as well as storage costs. Thinking about IT-BCP in this way, we can easily see the wide range of associated costs. Corporations must ensure optimal BCP countermeasures while keeping these cost issues in mind. The installation of the backup site would require new personnel, and would naturally generate costs associated with day-to-day operations and management. While routine monitoring tasks can be performed remotely, it is important to recognize the setup effort that would be required at the backup site in the event of an emergency. The costs associated with these efforts should also be considered. This system setup process would need to include a review of operational rules, such as how data is returned to the main site and how services are reinitiated once circumstances return to normal. 24

26 PlateSpin Forge guide book Approaches to business The cost of business Power strategy (cost of power, UPS, self-generating devices) Merits and demerits of IT-BCP solutions Training costs Securing human resources PlateSpin Forge as IT-BCP solution Network costs PlateSpin Forge usage IT-BCP countermeasures come with a variety of unavoidable costs, in addition to hardware and software. The optimal solution is found by estimating and preparing for these costs. PlateSpin Forge GUI 25

27 chapter 03 Merits and demerits of IT-BCP solutions 26

28 Approaches to business The cost of business Potential solutions and comparison thereof 28 Characteristics of tape backup 30 Merits and demerits of IT-BCP solutions Characteristics of storage replication 32 Characteristics of system redundancy 34 Key points for selecting the optimal IT-BCP solution 36 Example cost calculation 38 PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI 27

29 chapter 03 Merits and demerits of IT-BCP solutions Potential solutions and comparison thereof IT-BCP solutions can take various forms depending on the scale and structure of the system and the type of business. Earlier we introduced RPO (recovery point objective) and RTO (recovery time objective), and the options available differ depending on how these are set for each system. But let us first look at general BCP measures. Here, we will introduce tape backup, storage replication and system redundancy methods. Firstly, the key feature of tape backup systems using portable tape media has to be the low cost of the environment. For example, the latest tape standard, LTO-6 (2.5TB) can be obtained for a little over $50. A drive to run LTO tapes can also be purchased for around $2,000. This is the recommended method for organizations seeking to constrain initial costs. However, whatever the RPO or RTO, restoration using this method takes time, and there are additional running costs related to tape replacement and storage. Next we have storage replication, which maintains the same storage baseline as the production environment, giving it the key feature that data at the backup site represents the situation just prior to any incident, so the backup data is up-to-date and the RPO is very aggressive. However, the procedure for switching systems in, such as changing environmental settings of the installed operating system and applications, as well as changing over networks, is complex, and requires technicians with adequate training to be present at the backup site. Additionally, the initial installation costs tends to be high, as a high-end storage array is needed to handle the remote replication. The key feature of system redundancy then, where a backup site is maintained with the same infrastructure as the production environment, is rapid system recovery. System redundancy is the optimal method for mission critical operations that must not fail. There is, of course, a very high cost associated with the installation of a mirror environment, and the need for maintenance to match the production environment adds a considerable running cost. A stable network is also required for real-time data copying. Some implementations will also require a broadband network, making this a method requiring a considerable investment. All three methods have their merits and demerits, but the optimal IT-BCP approach can be found by selecting the appropriate target recovery point and recovery time. 28

30 PlateSpin Forge guide book Approaches to business Low cost Only data can be recovered Restoration takes time OS and applications need to be re-installed High daily operational load (replacement, storage and rotation of tapes) Tape Backup TCO: RPO: RTO: Insufficient for BCP The cost of business Merits and demerits of IT-BCP solutions Storage Replication Data very up-to-date Only data can be recovered OS and applications need to be re-installed Switching process is complex A technician is needed at the disaster recovery site TCO: RPO: RTO: Not cost-effective PlateSpin Forge as IT-BCP solution Installation costs are high (reconstruction of storage infrastructure) System Redundancy PlateSpin Forge usage System can be recovered in a short time High installation costs (at least doubles system installation cost) High-speed connection needed Expensive to operate (maintenance of backup systems) TCO: RPO: RTO: Highly effective, but also highly expensive PlateSpin Forge GUI 29

31 chapter 03 Merits and demerits of IT-BCP solutions Characteristics of tape backup Let us look again at the characteristics of tape backup. Magnetic tapes used for backup enable information to be recorded by magnetizing a large number of minuscule particles. While various standards have existed in the past, including DDS, DTL and AIT, the current mid-range leading product is LTO (Linear Tape-Open), with some DDS still in use. There are also additional high-end standards designed by individual vendors. The present version of LTO is Generation 6 (LTO-6: without compression 2.5TB, with compression 6.25TB), and a roadmap exists up to Generation 8. Tape backup uses a backup tool to backup and restore data. The backup method is capable of backing up individual files, as well as images, where the whole system including the operating system and applications is stored block-by-block as an image file. There also exists a system called CDP (Continuous Data Protection) that is installed as an agent on the device to be protected, where it constantly monitors its status and performs backup in real time in the event of any change or addition. stores only the parts that have changed since the previous backup, and differential backup, which stores only the parts which have changed since the previous full backup. Recently it has become the norm to employ deduplication, which optimizes the number of backup tapes and storage capacity by excluding duplicate data. Although tape backup can significantly constrain initial installation costs compared to other methods, there is a considerable cost associated with routine management such as magnetic tape replacement and storage. Furthermore, in the event of recovery, the process involves finding the appropriate magnetic tape and performing the restoration manually. So while via scheduling the backup process itself can be automated, recovery requires a lot of time and effort. A product similar to magnetic tapes that offers high capacity and portability is RDX. RDX is a hard drive based solution and is used for rapid data access. An RDX drive uses a USB connection, and when a cartridge is inserted it is recognized as a local drive, allowing simple data copying. As well as full backup of all data, there are a number of methods for reducing the time required for backup, such as incremental backup, which 30

32 PlateSpin Forge guide book Approaches to business Disc redundancy (RAID board, GDS) Operating site The cost of business A Mirror Built in Business for minor disasters Integrated backup environment Tape library Merits and demerits of IT-BCP solutions B Mirror Built-in Backup server A B PlateSpin Forge as IT-BCP solution Data storage site PlateSpin Forge usage A B Backup data Transportation PlateSpin Forge GUI 31

33 chapter 03 Merits and demerits of IT-BCP solutions Characteristics of storage replication Next, let us look at storage replication. Storage replication is a technology for real-time copying of the computer data to be protected, and is an effective way of mitigating the breakdown risk of continuous services. A storage replication system constantly acquires data, allowing restoration to the point just prior to the breakdown, and can, from a business perspective, provide excellent RPOs (recovery point objectives). There are two types of storage replication: synchronous, where the computer to be protected and the replication storage media are written to simultaneously, and asynchronous, where the replication storage is written to according to a defined schedule. Synchronous replication completes the I/O writing process when it is confirmed that the write to the protected computer and the replication storage media was successful. This means adequate network bandwidth to the remote site is required, as well as a low-delay latency. Asynchronous replication writes data to be protected to the storage media, exports data to be replicated to memory, and performs copying to the replication device in accordance to a schedule. Storage hardware enabled for replication can usually handle both synchronous and asynchronous replication processes. If synchronous replication is selected, restoration can be performed using data from immediately prior to the breakdown, giving an optimal RPO, although an operating system and environment would have to be arranged first. Setting a short RTO (recovery time objective) is not sufficient in itself. Skilled technical support would be required at the remote site to achieve rapid recovery in the event of an emergency. Replication solutions that come as a black box from a storage vendor require a network that can handle the load as well as a system for transferring data to the remote site. While the initial data transfer requires a full copy of all data stored at the time, once this is completed, the data transfer volume can be reduced by employing functions to transfer only those blocks in a snapshot which have changed, and by making use of deduplication to identify duplicate data block-by-block. These methods provide a system for minimizing data transfer volume on the network, while achieving high speed data copying. 32

34 PlateSpin Forge guide book Approaches to business Synchronous Replication Application server The cost of business Write I/O ACK 1 4 Local An I/O complete message (ACK) is returned to the server upon completion of transfer to the remote site 2 3 Remote Merits and demerits of IT-BCP solutions Zero data loss in event of disaster Additional delay for transfer to remote site Asynchronous Replication PlateSpin Forge as IT-BCP solution Application server Write I/O ACK An I/O complete message (ACK) is returned to the server before transfer to the remote site PlateSpin Forge usage Local Remote No delayed I/O to server Some data loss in event of disaster PlateSpin Forge GUI 33

35 chapter 03 Merits and demerits of IT-BCP solutions Characteristics of system redundancy Now let us look at some ways of achieving system redundancy. System redundancy, as the name suggests, involves the construction of a backup site with the exact same environment as the production environment, and that is capable of handling hardware breakdown by duplicating the computer itself using clustering, as well as coping with disaster by copying data to a remote site in real-time using replication. As mentioned above, transfer of data to a remote site is achieved by replication. To ensure the shortest RPO and RTO while maximizing availability, synchronous replication is required, but this does come with an additional cost, as a low latency broadband network is needed. Although asynchronous replication is available as an option, mission critical systems requiring system redundancy are generally better suited with the synchronous model. As this system enables instant recovery to a state immediately prior to the breakdown, in IT-BCP terms it enables RPO and RTO to be set at will. It is ideal for mission critical operations that require high business performance. Clustering is most often achieved using failover clustering, which for Windows environments is available in Windows Server 2012, but uses specific clustering software under non-windows platforms or virtualized environments. The reason for this is that clustering functions in a virtualized environment are unable to monitor every application, and therefore cannot detect when a breakdown occurs. Using clustering functions incorporated into the hardware allows a higher precision of fault detection, as a separate network is provided for fault detection. However, providing a system environment at two sites has a considerable impact on system installation costs, and a broadband connection is essential to achieve real-time information processing and instantaneous switching. Furthermore, day-to-day maintenance would be required at the backup site in the same manner as the production environment, adding to the maintenance costs. Operations that require continuous system availability demand infallible protection through system redundancy regardless of cost. 34

36 PlateSpin Forge guide book Approaches to business Primary site (data center) Secondary site (data center) Currently in use Backup server A A B B B Backup server Active (reference system) A B Cluster Standby Storage area network (SAN) Storage area network (SAN) Standby Cluster A Currently in use Active (reference system) A A AB B Cluster Standby Wide Area Ethernet RAID device Standby Cluster Mirror between RAID devices Remote mirror The cost of business Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI 35

37 chapter 03 Merits and demerits of IT-BCP solutions Key points for selecting the optimal IT-BCP solution We have seen how each of the IT-BCP solutions discussed so far has its own merits and demerits. Preventing system interruptions in the event of a breakdown can be costly, and while low cost methods of avoiding operational difficulties are available, these require patience. Essentially, the key is to determine the recovery priority of all existing systems. Although the approach will differ from corporation to corporation, we should seek to minimize the RTO of those systems that, if interrupted, would have a significant impact on business. The operations that require rapid recovery are those that have a considerable impact on business, such as accepting orders or shipping instructions. Such issues have a direct impact on customers. Important systems such as call centers handling customer inquiries should also be considered. monthly accounts could be missed, so the level of protection should perhaps be of the order of a few hours. Difficulties would also arise if core sales systems were to fail, such as plant production control or invoice issuing. Internal communication infrastructure such as mail servers and groupware servers represent another field where the impact on business due to a loss of service could be significant, but it may be possible to overcome this by adopting alternative means of communication such as cellphones, smartphones or social network services like Facebook. The RTO could well be set to be a little more flexible in this case. On the other hand there are systems that have little impact externally, such as file servers. For such systems a low cost recovery method such as tape backup may be selected, rather than implementing an expensive IT-BCP solution. Some core systems such as financial accounting are also of key importance, but it must be determined whether immediate recovery is a necessity. If the financial accounting system were to fail it is possible that 36

38 PlateSpin Forge guide book Approaches to business The cost of business File server Communication system Merits and demerits of IT-BCP solutions RTO Financial accounting system Call center system PlateSpin Forge as IT-BCP solution Sales management system Ordering system PlateSpin Forge usage Impact on operations PlateSpin Forge GUI 37

39 chapter 03 Merits and demerits of IT-BCP solutions Example cost calculation An unavoidable key concern when considering IT-BCP solutions is cost. Seeking recovery as rapidly as possible implies significant investment and organization, and deters some corporations from adopting measures. The reason for this is the high cost of maintaining the backup site or environment, due to the dependence of the system on the hardware. However, the latest virtualization technology is now delivering solutions that enable standby environments to be built flexibly, with no dependence on the physical environment. These backup methods use customized infrastructures such as cloud services or backup appliances to allow a mirror of the production environment to sit in standby. In other words, to address both low cost and rapid recovery, the approach must now consider the recovery level objective (RLO), or the level of business that should be recovered. As a recovery level of 100% would require considerable maintenance costs for the standby environment, a flexible approach is needed, whereby, for example, 30% of operations are initially recovered, leaving the remainder to be recovered once the required environment is deployed. While this leads to some reduction in system responsiveness, it ensures business with minimum impact. Therefore, the focus is now on installing a customized appliance running a virtual environment at a remote site, as a backup standby environment. In the event of an emergency the appliance is capable of continuing operations in the same way as the production environment. One such backup appliance product is PlateSpin Forge from Netiq. Real-use cost calculations show this approach to be exceedingly efficient. Let us compare storage replication with a backup appliance, both running storage synchronization. If we assume the corporation's production environment runs 15 physical servers and five virtual servers, we would expect a typical cost reduction of 44.8% for a TCO period of four years from installation. This backup appliance option has gained considerable attention as a solution that satisfies the principles of business while keeping costs to a minimum. 38

40 PlateSpin Forge guide book Approaches to business $ 700K 600K Breakdown of total costs (normal operations): "Inter-storage transfer vs. Backup appliance" The cost of business 500K 400K 300K 200K 100K 0 Service Testing A: Inter-storage transfer $53,240 $41,917 B: Backup appliance $53,240 $16,765 Merits and demerits of IT-BCP solutions Permanent operation Construction $201,204 $43,104 $0 $8,714 $ 700K Product $179,715 $154,354 Change in TCO (normal operations): "Inter-storage transfer vs. Backup appliance" PlateSpin Forge as IT-BCP solution 600K 500K 400K 300K 200K PlateSpin Forge usage 100K 0 A: Inter-storage transfer B: Backup appliance Year 1 $162,145 $51,223 Year 2 $281,192 $111,850 Year 3 $400,195 $172,435 Year 4 $519,229 $233,047 PlateSpin Forge GUI From the ITR document, "Investment efficiency in business solutions using virtual environments: low cost disaster recovery". 39

41 chapter 04 PlateSpin Forge as IT-BCP solution 40

42 Approaches to business The cost of business PlateSpin solution 42 Optimal virtualization planning: PlateSpin Recon 44 Migrating to a virtual environment: PlateSpin Migrate 46 PlateSpin Forge as IT-BCP solution 48 Overview of business using PlateSpin Forge 50 Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI 41

43 chapter 04 PlateSpin Forge as IT-BCP solution PlateSpin solution We have talked about how virtualization technology can be useful for IT-BCP. The PlateSpin product line from NetIQ offers a solution for each stage (phase) of virtualization, with virtualization technology-enabled solutions to support all efforts on the journey to a fully virtualized environment. Essentially, the four phases are situation capture, planning, migration and backup/bcp. In order to achieve a virtualized environment, the first essential phase is to capture the current state of affairs, such as capturing internal servers, preparing an inventory and gathering data on workloads (whole environments to run on the virtual machine hosts). Before making the switch to a virtual environment, assuming the purpose is to develop a backup environment for IT-BCP at the same time, it is important to ascertain which servers are handling important workloads, as well as creating the schedule for implementation. Once the situation has been captured, the next phase is the planning phase, which involves migration planning to determine the sizing of virtual servers according to the size of the new environment and the schedule for migration according to prioritization, as well as careful measurement of effectiveness following migration. The required resources for the migration environment must be calculated accurately during the migration planning, so that they match the actual workloads. The PlateSpin Recon virtualization planning tool is ideal for these capturing and planning phases. Once migration planning has been done, the migration phase begins, to eventually migrate from the current environment to the new environment. Generally, if the existing environment runs on physical infrastructure, this is a P2V (physical to virtual) migration. If a workload is to be developed on a virtual platform using an on-premise environment, a V2V (virtual to virtual) migration is required. PlateSpin Migrate is a useful solution for migration of data and systems between various environments, and is capable of freely migrating workloads between physical and virtual environments. Its key feature is the ability to handle all major virtualization platforms such as VMware, Microsoft Hyper-V, SUSE Linux Enterprise with Xen and Citrix XenServer. The final phase is the IT-BCP solution: backup/ BCP. When specifying any environment for backup, whether physical or virtual, it is important to integrate backup while mitigating operational load. In the event of an emergency, the solution should be capable of implementing provisional recovery using flexible failover, and supporting rapid busi- 42

44 PlateSpin Forge guide book Approaches to business ness. A failback function should also be available for use when an environment matching the production environment is again ready for use. The PlateSpin backup appliance PlateSpin Forge, with its software component PlateSpin Protect, meets the needs of this phase. The cost of business Route to virtualization and the cloud Virtual/Cloud Merits and demerits of IT-BCP solutions Phase Capturing current situation Planning Migration Backup / BCP Key Tasks Capture internal servers Compile inventory Monitoring Compile workload Identifying targets for virtualization Sizing of virtualized servers Migration planning Measurement of overall effectiveness P2V (physical to virtual) V2V (virtual to virtual) V2P (virtual to physical) P2P (physical to physical) P2I (physical to image) V2I (virtual to image) I2P (image to physical) I2V (image to virtual) BCP Solution Backup of physical servers Backup of virtual servers Failover Backup integration Disaster recovery appliance PlateSpin Forge/PlateSpin Protect PlateSpin Forge as IT-BCP solution PlateSpin Forge usage Product PlateSpin Recon PlateSpin Migrate PlateSpin Forge GUI 43

45 chapter 04 PlateSpin Forge as IT-BCP solution Optimal virtualization planning: PlateSpin Recon Next we will take a closer look at the product in the PlateSpin solution portfolio for planning the optimal virtual environment, PlateSpin Recon. business changes and improved planning. Efficient sizing is achieved by constantly maintaining an optimal environment. PlateSpin Recon is a virtualization planning tool to assist you in achieving optimal resource planning for your virtual environment. In addition to tracking CPU, memory, HDD and network use on all existing servers on the network in both physical and virtual environments, PlateSpin Recon enables remote capture of inventories and performance data. The workloads are then analyzed in detail leading to automated creation of a server integration and consolidation plan. PlateSpin Recon is designed to automatically handle up to 10,000 server data points. All operations are performed agent-less. Creation of server integration and consolidation scenarios can also be automated by configuring settings for the hardware or virtual platform to be used, as well as resource allocation following consolidation. Another key feature is the simulation function for estimating operational status up to 12 months ahead, enabling potential issues with the virtualization process to be identified in advance. At the same time, tracking of resource usage can be set to continue after migration to capture changes to the environment, enabling a flexible response to When considering an IT-BCP solution, it is only by setting the level at which business needs to be recovered, the RLO (the fallback level required for recovery), that a plan suited to the required performance can be created. PlateSpin Recon can help in creating such a plan. It also includes a function for analysis of cost reductions and investment efficiencies compared to the existing environment, which even calculates hypothetical electricity and cooling costs under the created plan. So as well as with IT-BCP, the software also helps with corporate social responsibility (CSR) efforts for CO 2 emission reduction. 44

46 PlateSpin Forge guide book Approaches to business The cost of business Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI 45

47 chapter 04 PlateSpin Forge as IT-BCP solution Migrating to a virtual environment: PlateSpin Migrate Next in the PlateSpin solution portfolio is PlateSpin Migrate, which enables workloads to be freely migrated. PlateSpin Migrate is a virtualization and migration tool that enables migration of servers running on virtual or physical environments, called workloads, to other physical or virtual environments. Because workloads can be migrated as they are, without altering the existing environment, PlateSpin Migrate is able to migrate a physical server to a test virtual environment to verify application functionality. Conversely, a system that has been developed and tested in a virtual machine can be deployed in a single step to a physical server to become the production environment. Ordinarily, P2V migration requires complex procedures such as the setup of the virtual machine, but with PlateSpin Migrate this operation is simplified via automation. The entire process, from creation of the virtual machine on the destination server to adjusting the system and copying data, can be automated using the GUI drag and drop functionality. The bandwidth throttling function enables migration of workloads in a short time period without impacting the network too much. The software can handle all major virtualization platforms including VMware ESX, VMware ESXi, Microsoft Hyper-V, SUSE Linux Enterprise with Xen and Citrix XenServer, and is designed to enable simple migration between different virtualization platforms, such as from VMware to Hyper-V or the other way around. This means virtual environments can be created with no dependence on a specific vendor, allowing the virtualization platform to be changed in the event of new trends in virtualization platforms or new evaluations of cost efficiency. Because PlateSpin Migrate is capable of returning virtualized workloads back to a physical environment, there is always peace of mind that a V2P operation can be implemented in the event of application incompatibilities leading to issues with the virtual environment. All in all, PlateSpin Migrate is a powerful solution supporting end-to-end virtual environment migrations. 46

48 PlateSpin Forge guide book Approaches to business The cost of business Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI 47

49 chapter 04 PlateSpin Forge as IT-BCP solution PlateSpin Forge as IT-BCP solution The next item in the PlateSpin portfolio is NetIQ s IT-BCP solution: the PlateSpin Forge backup appliance and its software element PlateSpin Protect. Let us focus more closely on the appliance product PlateSpin Forge. PlateSpin Forge is a backup appliance product which provides business functionality via a provisional recovery environment in the event of an emergency, through integrated backup of multiple servers, whether physical and virtual environments, on a single unit. Because PlateSpin Forge is an appliance server preloaded with the hardware environment required for business as well as virtualization and recovery software, it can start providing value as soon as it is connected to the network, and vastly simplifies the process of managing BCP environments. While business for production environments usually involves a performance reduction, the level of fallback operation can be adjusted to allow considerable improvements in RTO. If a network is provided to remotely access PlateSpin Forge, the provisional recovery process can be simply implemented without the need for staff to be deployed at the remote site. Even if the new failback environment has hardware from a different vendor than the one used in the initial environment, or uses a different virtual environment, the system can handle it. PlateSpin Forge comes equipped out-of-the-box with a broad set of drivers for multiple virtual and physical platforms, and is capable of flawlessly restoring from e.g. Microsoft Hyper-V to VMware ESX, or to Citrix XenServer. When using PlateSpin Forge, recovery, including different system settings for each and every data backup, is simply a matter of a few clicks. As well as being useful as a routine backup environment, PlateSpin Forge excels at operating as a failover environment for provisional recovery in the event of an emergency. It can also perform failback back to the original environment, once the infrastructure is ready, to achieve full recovery. It also incorporates a failover test function that allows failover testing to be performed using different network settings than the production environment. PlateSpin Forge can be set up to run its own test environment, so failover testing can be performed with no impact on the production environment, allowing it to be used as a verification environment for security patches and application upgrades. Once testing is completed, all updates 48

50 PlateSpin Forge guide book Approaches to business are deleted and the system automatically reverts to a synchronized state, meaning you can freely change, add or delete test environments and always have the option to immediately reset. Forge is thin provisioning-enabled, meaning it is capable of virtualizing storage volumes to support flexible storage operations. The cost of business Finally, as well as offering recovery point management on a workload-by-workload basis, PlateSpin PlateSpin Forge Dashboard Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI 49

51 chapter 04 PlateSpin Forge as IT-BCP solution Overview of business using PlateSpin Forge Now let us look again at how PlateSpin Forge can be of use from a business perspective. Because it is a backup appliance, PlateSpin Forge excels across a range of scenarios, for routine backup use as well as for business and restoration in emergencies. Firstly, during routine use in a production environment, PlateSpin Forge functions as a device to collectively backup multiple servers. It implements replication for both data and system settings, and applies internal recovery point management. In the event of data loss such as due to a deletion made in error, even if this error is replicated, PlateSpin Forge can still recover the environment by returning to one of the multiple previous recovery points. It also employs incremental backup, so backup time is kept to a minimum by avoiding backup of the same data again and again. In the event of a disaster or breakdown, the workload can be booted up using PlateSpin Forge's internal virtual environment, providing dramatic improvements to RTO. As you only need to boot up the backup virtual server, there is no need to carry out restoration procedures as with an ordinary backup tool. Because multiple server environments are housed in a single unit, the service level will not be 100%, but it will provide business at a fallback level. As in practice often a network switchover is required, PlateSpin Forge can automatically convert the backup system's IP address to match the failover network before booting. This means the system will have network access as soon as it is switched on. This eliminates the task of changing network addresses following restoration, as often required with system backup tools. Once the hardware and the software that are to be used for the full recovery are ready, PlateSpin Forge's internal virtual workload can be restored to the production environment. The new environment options can be simply selected using the GUI, providing a secure failback route without multiple complex steps. As well as failback to a physical environment, PlateSpin Forge is also designed to handle failback to virtual environments, and restoration can proceed even when different hardware is used in the new system. Restoration can also be performed to a different virtualization platform than the original one. 50

52 PlateSpin Forge guide book Approaches to business Service level 100% Overview of business using PlateSpin Forge Under normal operation In event of disaster / failure Full recovery The cost of business RLO Final backup Provisional recovery RPO RTO Time Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution Implementation of integrated backup Reduced-level operation using Forge's internal backup system Restoration to production server once prepared PlateSpin Forge usage PlateSpin Forge GUI 51

53 chapter 05 PlateSpin Forge usage 52

54 Approaches to business The cost of business Key feature of PlateSpin Forge: simple and user-friendly setup 54 Key feature of PlateSpin Forge: easy-to-use GUI with low overhead 56 Two methods for initial workload replication 58 Merits and demerits of IT-BCP solutions Routine operations example 1 60 Routine operations example 2 62 Routine operations example 3 system recovery training 64 Failover 66 PlateSpin Forge as IT-BCP solution Failback 68 PlateSpin Forge usage PlateSpin Forge GUI 53

55 chapter 05 PlateSpin Forge usage Key feature of PlateSpin Forge: simple and user-friendly setup One key feature of PlateSpin Forge is its simple setup. This is because as a product it includes all the elements required for business : hardware such as a server and storage, recovery software with replication and backup functionality, and a virtual environment. All of this is provided in one unit, as a single package. When we think about ordinary business we think of having servers and storage ready at a backup site, and of synchronization settings such as replication to a storage mirror. As well as setting up the environment we also have to implement backup of the production environment, along with complex system settings. In practice there are also a number of other requirements before we have a functioning backup site, such as stationing a technician on site and scheduling copying of data and system settings from the production environment to the backup environment. Setting the levels for RPO and RTO will depend on the specific organization, but it is easy to imagine a significant time and effort required to setup each system. With PlateSpin Forge, all the essential backup site equipment including the server, the storage and the recovery software is provided in one unit, making it possible to build a backup environment for business simply by placing it on the network and making simple configuration changes using the GUI. Of course, the performance will not be equal to the production environment, but it is powerful enough to implement business at an excellent fallback level. System building with PlateSpin Forge is easy. Ordinarily the integration costs are considerable due to the range of tasks to be completed, such as the installation of an operating system in preparation for applications, and creating the virtual environment. With PlateSpin Forge, you simply remove the unit from its box, connect it to the network, assign an IP address and password, and select the servers to be protected. Backup is handled automatically simply by setting the synchronization policies, such as the schedule and compression level, and clicking execute. The initial backup will complete within one to two days, depending on the number of servers to be protected, and thereafter the incremental backup system will proceed automatically. This means a considerable reduction in time and effort needed for setup. 54

56 PlateSpin Forge guide book Approaches to business Backup target server Typical disaster recovery site setup Operating environment 1. Application setup The cost of business 2. OS installation Backup Production site Local storage (critical) Synchronous Large system integration cost and effort Mount Remote storage (critical) Backup site 3. Construction of virtual environment 4. Preparation of server 5. Preparation of storage 6. Software replication 7. Storage replication Merits and demerits of IT-BCP solutions Backup target server Production site Simplicity of PlateSpin Forge infrastructure Synchronous Simple disaster recovery site setup Operating environment Backup site Using Forge: 1. Remove from box 2. Configure IP address and password 3. Select servers for protection 4. Set synchronization timing PlateSpin Forge as IT-BCP solution PlateSpin Forge usage A single PlateSpin Forge unit enables IT-BCP with no requirement for additional equipment or technical staff PlateSpin Forge GUI 55

57 chapter 05 PlateSpin Forge usage Key feature of PlateSpin Forge: easy-to-use GUI with low overhead Even more than simplicity of setup and system building, PlateSpin Forge offers excellent controllability for day-to-day backup operations. The same applies to recovery, all the while ensuring business. Information backup is performed incrementally in accordance with the synchronization policies set at the time of install, so there is no need for any specific routine maintenance. Any changes, including changes to system settings, are part of the incremental backup. So if, for example, there is an operating system patch for a protected server, the patch will be automatically installed to the server operating system on the workload as part of the backup process. Recovery point management is also implemented, so the required environment can be selected and restored in the event of a mistake on the protected server. One task that should be performed periodically is a failover test, to determine whether the environment can be correctly restored in the event of an emergency. This task simply requires a recovery point to be selected and executed using the Test Failover button on the control screen. A test network is created as a virtual network, so that when the virtual machine is booted for testing it connects to the test network rather than to a network with external access. This allows testing to be carried out in a way that ensures switching works in practice, with no impact on the production environment. The test outcomes are shown on the GUI, allowing any problems to be eliminated in advance. Once testing is complete, temporary settings for the workload used in the test are discarded, and PlateSpin Forge automatically reverts to the pre-test environment. Should a protected server suffer a breakdown, rapid recovery is needed. With PlateSpin Forge, failover optimized for business can be executed with a single button. All that is required is selecting the workload for recovery and selecting the recovery point. While performance will not be equal to the production environment, PlateSpin Forge provides a fallback version of the production environment. If just a single workload is to be recovered this can be done in a few minutes, while simultaneous recovery of multiple workloads can be brought to provisional recovery in up to a few hours. Once hardware, etc. is prepared for full recovery, a failback operation is required to move from the provisional recovery environment to the full recovery environment. The failback function works by configuring how failback will be executed, for example by selecting which transfer method and which volumes are to be used, and then executing failback to the full recovery environment. 56

58 PlateSpin Forge guide book Approaches to business The full recovery environment created through PlateSpin Forge's failback function can then be set for replication to ensure future protection. Restart- ing replication following recovery ensures that system protection for business is once again maintained. The cost of business Backup Tools Failure is detected on the production system Prepare new server Exchange HDDs Reinstall OS and applications (including backup tool agents) Start backup tool and select restore point Implement restoration Start applications and verify operation Storage Replication (non-synchronous) Failure is detected on production system Switch networks to standby system Suspend storage replication Mount the storage LUN in standby system Start standby system and verify operation Apply OS updates and the latest patches to the standby system Prepare new server Prepare new storage products Exchange storage Reinstall OS and applications (including replication software) Test and verify storage replication Implement reverse replication Full recovery Provisional recovery Using Forge Failure detected on production system Select restore point using data stored in Forge Implement failover in Forge, start up Forge environment and verify operation Prepare new server product Implement failback in Forge Confirm operation Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution PlateSpin Forge usage Several days are needed before business can start Work can begin after several hours under provisional recovery Work can begin after several hours under provisional recovery System maintenance and personnel needed at backup site Provisional recovery can be implemented remotely using Forge, enabling minimum cost business PlateSpin Forge GUI 57

59 chapter 05 PlateSpin Forge usage Two methods for initial workload replication Installing PlateSpin Forge initially requires the entire workload of the target server that is to be protected to be copied, including operating system and other system settings and data. This process is called replication. There are two main methods of performing the initial full replication upon install. If, however, the volume of data for backup is small or the servers to be protected are distributed nationwide, it would be problematic to host a PlateSpin Forge unit at each site. Therefore, the second option would be to install it at the backup site and perform the initial full replication over the network. If the server to be protected holds a large quantity of data or there is no broadband network to the backup site, the first option would be to copy all data and system settings within the local environment. PlateSpin Forge is installed within the same LAN segment as the server to be protected, and the entire workload is copied over. If there are multiple servers, workloads from multiple units can be copied simultaneously, up to the limit supported by the network bandwidth, and PlateSpin Forge will integrate these as a single backup environment. Although this method requires more time to complete than full replication using the first option, the targets to be protected can be assigned from the backup site, and the IT-BCP environment can be achieved by scheduling replication of workloads in sequence. Detailed settings are available including network bandwidth, compression level and bandwidth limits, so replication can be managed without significant impact on existing networks. Once the initial full replication is complete, a continuous process of incremental backup is initiated. Next, PlateSpin Forge is transported to the backup site and powered up. PlateSpin Forge's own IP address is then changed, which changes the replication IP addresses in the backup settings of workloads to be protected, allowing data protection to be implemented passing only incremental data from the local environment across the network. Performing the initial full replication in the local environment means the backup environment can be prepared as a rapid IT-BCP solution. 58

60 PlateSpin Forge guide book Approaches to business Copy the production environment locally and transport it, for example by truck, to a backup site where it can be installed The cost of business Production site Backup site Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution Install at backup site and copy the production environment across the network PlateSpin Forge usage Production site Production site Production site Production site PlateSpin Forge GUI 59

61 chapter 05 PlateSpin Forge usage Routine operations example 1 Here we will look at a specific example of adopting PlateSpin Forge. Let us say the intention is to migrate around 20 physical servers with integrated backup to tape to a private cloud as an IT-BCP solution. Firstly, the workloads of the 20 physical servers should be consolidated onto a single PlateSpin Forge unit using its virtual environment, so all workloads are copied using a P2V migration process. At this stage, the production environment is usable and IT-BCP enabled, and can be rapidly recovered to the provisional recovery state on PlateSpin Forge in the event of any problems with the physical servers. At the same time, the private cloud environment can be built for future use as the production environment. In this case, we assume that the environment will run 20 workload units as virtual machines on a single physical server. Once the workloads of the 20 existing environments are copied to PlateSpin Forge, the PlateSpin Forge unit is moved and installed at the site where the private cloud environment is to be built. A V2V migration process enables migration from the PlateSpin Forge environment into the private cloud environment. After the migration of the production environment to a private cloud, PlateSpin Forge is configured to protect the workloads that are now running in the private cloud. Once the initial replication is performed, PlateSpin Forge is installed at a remote backup site, and functions as an IT-BCP solution providing remote backup for the production environment in the cloud. PlateSpin Forge enables a simple migration to a private cloud, as well as making a valuable contribution to IT-BCP in the private cloud environment. Configuring replication settings in advance means that the environment is capable of rapidly switching to provisional recovery mode for business even when the party responsible is not present. As a result, not only does PlateSpin Forge provide a level of business infrastructure that was unavailable in the past, it also succeeds in reducing the hardware cost and complex operational burden associated with 20 physical servers. In case of an emergency, PlateSpin Forge provides valuable functionality as a provisional recovery infrastructure. 60

62 PlateSpin Forge guide book Approaches to business Problem: PlateSpin Forge: Case Study 1 1. A business solution cannot be implemented without ensuring countermeasures in the event of a failure. 2. Downtime during failure can run into days. 3. Plans must be made to switch out old equipment as well as looking ahead to virtualization. The cost of business Before PlateSpin Forge solves this problem 12 physical servers Two virtual servers (8 instances) Merits and demerits of IT-BCP solutions After Tape Phase 1: Backup existing physical production environment to Forge. Phase 1 : Backup virtual environment to Forge. PlateSpin Forge as IT-BCP solution Phase 2: Virtual environment on Forge is migrated as a whole to become a virtual environment on the new server. One virtual server (12 instances) Phase 3: The newly constructed virtual environment is synchronized and backed up to Forge, providing a disaster recovery solution when sited remotely. Virtual environment is backed up on Forge. Two virtual servers (8 instances) PlateSpin Forge usage PlateSpin Forge GUI 61

63 chapter 05 PlateSpin Forge usage Routine operations example 2 Next, we will discuss how PlateSpin Forge can help at sites that will unavoidably continue to use multiple backup tools, by breaking down each system into silos. Organizations with different systems at each site or plant may find it difficult to establish respective backup environments. This is because in many cases backup is left to the technician onsite, meaning that backup software and tape media may differ for each system, and that rationalization of usage methods and backup policies may not occur. With a wide distribution of operations and environments, it can be difficult to assign priorities to systems, making rapid recovery for business in the event of an emergency an unlikely prospect. no longer any requirement to perform tape backups at each site. Unlike with simple replication, this system provides recovery point management, allowing the system to be reverted precisely to any recovery point. Backup operations are also integrated, reducing on-site operational load, and allowing human resources to be diverted to other operations. This P2V process provides full integration of cross-site backup environments, and enables organizations to switch away from tape backup environments that can require several days for recovery. PlateSpin Forge delivers dramatic improvements in RPO and RTO compared to such legacy technologies. The most efficient solution for such a mixed backup environment is PlateSpin Forge. Firstly, all workloads running on the various systems should be migrated to PlateSpin Forge's virtual environment using P2V. Specifically, the physical environments running at each site are selected for protection, and the workloads are replicated to PlateSpin Forge. Once the initial full replication is complete, the workloads are kept synchronized using incremental backup at a predefined schedule, meaning there is 62

64 PlateSpin Forge guide book Approaches to business Problem: PlateSpin Forge: Case Study 2 1. Each site has its own backup system. Different plants have different systems and information capture cannot be implemented using information systems. 2. Backup policies are disparate. 3. Only operational staff members understand the systems, confounding system handover. 4. The system is not periodically backed up. The cost of business Before PlateSpin Forge solves this problem Site A backup tool Merits and demerits of IT-BCP solutions Site B backup tool Site C backup tool PlateSpin Forge as IT-BCP solution Site D backup tool After PlateSpin Forge usage Different vendor systems, different sites and different operation methods can all be combined. Only one or two staff members are required, meaning only a simple manual is required for handover. PlateSpin Forge GUI 63

65 chapter 05 PlateSpin Forge usage Routine operations example 3 system recovery training Here we will discuss the failover test process, which is easy to be carried out routinely when using PlateSpin Forge. The failover process to be performed at the backup site in the event of an emergency should be routinely tested. Despite this, many organizations omit such verification in their routine operations in an attempt to avoid impact on the production environment. For proper implementation, however, failover capability should be checked on a monthly basis, at the minimum. This factor is quantified using the TTO (Test Time Objective) metric, which asks how easy it is to test the system as part of day-to-day training for business. Often several days have to be devoted to verifying the system, so that you know whether your IT-BCP solution will function correctly when it comes to the crunch. Daily verification can even be essential to ensure rapid and reliable IT-BCP countermeasures. PlateSpin Forge was designed from the outset to allow failover testing to be performed simply, and without interrupting operations. It is capable of running a test environment internally that has no impact on the production environment, enabling failover testing to be performed simply by select- ing the backup workload to be verified. Indeed, the process simply involves selecting the workload to be verified and clicking on the failover test button. This makes shorter-term TTOs achievable. A traditional failover test often requires personnel to be stationed at the backup site, and must be performed on a non-working day in order to avoid impacting the existing environment. In some cases, the test can only be performed with the production environment temporarily offline, to simulate an incident, making the impact of the failover testing considerable. With PlateSpin Forge, however, the test can be performed with no impact on the production environment whatsoever. PlateSpin Forge provides its own test environment on a custom internal network, which can be used to perform a wide range of verification tasks such as pre-verification of security patches or application upgrades. Moreover, PlateSpin Forge is designed to automatically revert to the original synchronized environment once testing is complete, by undoing the configuration changes used for testing. This means peace of mind, no matter how many changes or deletions you make to the system or data in the test environment. 64

66 PlateSpin Forge guide book Approaches to business PlateSpin Forge The cost of business Standby server Test environment Test environment setup in Forge Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI 65

67 chapter 05 PlateSpin Forge usage Failover Now let us look at how PlateSpin Forge can be used in the event of an actual emergency to provide a failover service. Under normal operation, users access specific servers and make use of business applications. For servers subject to the backup process, these applications are running within workloads, and PlateSpin Forge draws down data on a day-to-day or hour-tohour basis for incremental backup of workloads in accordance with a predefined schedule. Let us assume that a server breakdown occurs. Straight away the server connection enabling users to access the server is cut, as is the connection to PlateSpin Forge. The server has lost its online status and further backup is no longer possible. Users who have lost access will be aware that some issue has arisen on the server or network, but before they are able to deliver this message to their manager, PlateSpin Forge will promptly detect the breakdown and deliver an to the address of the relevant manager. involves selecting the workload to place in failover mode from the PlateSpin Forge dashboard, and pressing the execute button next to the desired recovery point. Doing so boots up the backup workload within PlateSpin Forge, and recovers the server state from the selected recovery point. If settings for switching the IP address of the booted workload and the IP address of the offline server have been configured in the Active Directory or DNS server in advance, users will be able to access the server as soon as PlateSpin Forge has booted the workload, providing a temporary provisional recovery state. However, as this failover state operates on a workload within PlateSpin Forge, performance will not be at the same level as the production environment. Users should be aware that this state offers a fallback level of service. The manager, having received the , can then access PlateSpin Forge from a device such as a smartphone or notebook, and initiate the recovery process for business. Specifically, this 66

68 PlateSpin Forge guide book Approaches to business Normal operation Production PlateSpin Forge The cost of business Users In event of breakdown Offline PlateSpin Forge Merits and demerits of IT-BCP solutions Forge sends breakdown alert or cellphone/tabletnotice, instruction to switch over is provided using cellphone/tablet PlateSpin Forge Dashboard Users PlateSpin Forge PlateSpin Forge as IT-BCP solution PlateSpin Forge usage Forge's internal standby server boots and continues operations Offline PlateSpin Forge Users PlateSpin Forge GUI 67

69 chapter 05 PlateSpin Forge usage Failback While PlateSpin Forge can be used to provide a failover service, the environment offers only a certain fallback performance level, and does not reach the stage of complete recovery. Therefore, let us now look at the failback process for moving workloads back to a full recovery environment, once the original infrastructure has been repaired or rebuilt. While business continues in a provisional recovery state under PlateSpin Forge, the system manager will have the damaged server repaired or, if it cannot be repaired, will arrange for it to be replaced. At this replacement stage, it may be unavoidable that the same hardware as was used in the previous model cannot be ensured. It may also be the case that the business environment has altered and a different virtualized platform is now sought for full recovery. Once the new full recovery environment has been deployed, manual adjustments can be made to make it a virtualized platform, if so desired. Next, the failback target is selected, and settings similar to the initial replication are configured for failback, such as compression level and transfer method. When failback is executed on the configured system, failback is performed to provide a system and data environment with a 100% recovery level, achieving full recovery. Once full recovery has been achieved, PlateSpin Forge replication can be once again set to execute, to provide an IT-BCP solution for the now recovered environment. This is possible because PlateSpin Forge is a dual functionality appliance, providing a running environment for provisional recovery, as well as a day-to-day backup function. PlateSpin Forge is loaded with functionality to allow recovery of workloads to physical servers from various vendors and to different virtualization platforms. PlateSpin Forge has tens of thousands of drivers available for operating systems and virtualized platforms, and is preloaded with the ability to automatically switch drivers to suit any new hardware on the restoration target. PlateSpin Forge accommodates for the differences between physical environments and virtual environments seamlessly. 68

70 PlateSpin Forge guide book Approaches to business Forge synchronizes with original server Original Server PlateSpin Forge The cost of business Users Switch back to original server occurs once synchronization is complete Original Server PlateSpin Forge Merits and demerits of IT-BCP solutions Users PlateSpin Forge as IT-BCP solution Original Server PlateSpin Forge New Server PlateSpin Forge usage No need to worry about original server spec! - Data can be migrated between different machine specs - NetIQ's conversion technology allows recovery to machines from different vendors and using different hypervisors. The drivers in Forge / Protect are installed automatically to enable data migration. PlateSpin Forge GUI 69

71 chapter 06 PlateSpin Forge GUI 70

72 Approaches to business The cost of business Addition of a workload 72 Initial configuration, including scheduling 74 Configuration for failover and failover testing 76 Failover procedure under PlateSpin Forge 78 Failback procedure under PlateSpin Forge 80 Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI 71

73 chapter 06 PlateSpin Forge GUI Addition of workload A key feature of PlateSpin Forge is its easy to use WebUI. It provides a data protection and business system that is easy for managers to navigate. Here we will look at the actual WebUI and introduce some of the configuration processes. 01 Firstly, when you open up the PlateSpin Forge web interface you are presented with the Dashboard screen. To the left of the screen is the PlateSpin Forge usage summary, which will show the number of configurable workloads. 72

74 PlateSpin Forge guide book Approaches to business 02 Workloads are added by selecting Add workload at the bottom of the left-hand panel, then selecting the IP address of the workload to be protected and the workload type according to the operating system it is running, and then clicking Execute. The cost of business Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution 03 Addition of the workload is now complete. Note that as the initial full replication has yet to complete, the workload status will show as Unprotected. PlateSpin Forge usage PlateSpin Forge GUI 73

75 chapter 06 PlateSpin Forge GUI Initial configuration, including scheduling Now that a new workload has been added let us look at the settings for the initial synchronization. Here we can set the synchronization timing and method. 01 Firstly, full replication must be selected on the options screen for the initial replication method. 02 Next come the settings for Tiers or synchronization groups. The protection tier can be set to a specific recurrence such as Weekly, Nightly, or Hourly, or a Custom option can be selected. In addition to the incremental replication schedule, compression level and bandwidth throttling can be specified. The section Recovery points to keep allows version management to be configured for backups as required, and is capable of managing up to 32 recovery points. 74

76 PlateSpin Forge guide book Approaches to business 03 Now that the tier is defined, we can move on to replication settings. A range of settings is available, including transfer method settings such as file or block level replication, data encryption, the network to be used during the transfer, volumes to be protected, and services to be suspended during replication. The cost of business Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI 75

77 chapter 06 PlateSpin Forge GUI Configuration for failover and failover testing With routine replication settings configured, the next task is to make further configurations to ensure smooth failover in the event of an emergency. As soon as the failover settings are complete, protection of the workload added earlier is initiated. 04 Failover settings specify the amount of memory to allocate to the virtual machine running on PlateSpin Forge, as well as other settings such as changes to the domain or workgroup following failover, and network settings to be used when failover is executed. This is where details should be entered to ensure the IP address is changed to match that of the backup site network. 05 Similar settings should be configured for failover testing. The details of these settings can be the same as those for failover, or they can be different settings altogether. Once configuration is complete, clicking on the Save and prepare button at the bottom of the screen prepares the workload for replication. 76

78 PlateSpin Forge guide book Approaches to business 06 Next, the workload to be replicated should be selected followed by a click on the "Run Replication" button. The cost of business 07 While replication is executing, a detailed progress report is displayed for each step. When replication is complete, the word Completed is displayed in the status bar. Now, initial replication of the designated workload is complete, and incremental replication will be performed according to the designated schedule. Merits and demerits of IT-BCP solutions PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI 77

79 chapter 06 PlateSpin Forge GUI Failover procedure under PlateSpin Forge Having already looked at the initial settings screen, we shall now discuss the procedure for putting a workload on PlateSpin Forge into failover mode in the event of an emergency. Because detailed failover settings have been configured in the initial setup, the failover procedure is as simple as selecting the workload for failover and clicking Run Failover. 01 As soon as a problem arises with a protected server, simply click the workload to be restored and press the Run Failover button. 02 If recovery point management is enabled, simply select which recovery point to be used for failover and press Execute. 78

80 PlateSpin Forge guide book Approaches to business 03 A status report can be checked while failover is running. Clicking on the phrase Running Failover on the Workloads screen will display the following screen. The cost of business Merits and demerits of IT-BCP solutions 04 Once the status shows as "Completed", the failover process is completed. The workload status will show as Live. PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI 79

81 chapter 06 PlateSpin Forge GUI Failback procedure under PlateSpin Forge After failover is complete, and once an environment for full recovery has been prepared, it is time to configure settings for failback, to restore the workload to the new environment. A 100% restoration is achievable by configuring this process in the same way as the initial replication and failover. 01 Firstly, select Failback from the Workloads tab. Next, follow the prompts to configure failback target settings such as the failover workload settings and replication method. 02 Once the failback process is prepared, press the Failback button. Here we have the same set of configuration fields for failback as we had for replication, such as data transfer method and compression level. 80

82 PlateSpin Forge guide book Approaches to business 03 As part of the failback configuration, settings can be configured to once again protect the workload using PlateSpin Forge after the failback is done. Selecting Save and failback will execute failback. The cost of business Merits and demerits of IT-BCP solutions 04 The status will show as Completed to indicate that failback has completed without problems. The status of the workload displayed by PlateSpin Forge will change to Ready For Reprotect. PlateSpin Forge as IT-BCP solution PlateSpin Forge usage PlateSpin Forge GUI 81