IT Business Continuity Planning and Management with

Transcription

PlateSpin Forge
Guide Book
IT Business Continuity Planning
and Management with PlateSpin Forge
and Management with PlateSpin Forge
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 continuity is a make-or-break issue for many corporations. Strategies can be created
from a number of different perspectives, by planning business continuity in terms of management of corporate
resources such as personnel, assets, capital and information. In this document we will specifically focus on IT
business continuity 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 continuity 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
continuity 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 continuity 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 continuity in your corporation.
Approaches to business
continuity
Contents
2
The cost of business
continuity
Introduction………………………………………………………………………
chapter 01
Approaches to business continuity………………………………………
4
The cost of business continuity…………………………………………… 16
Merits and demerits of
IT-BCP solutions
chapter 02
chapter 03
chapter 04
PlateSpin Forge as IT-BCP solution……………………………………… 40
PlateSpin Forge as IT-BCP
solution
Merits and demerits of IT-BCP solutions………………………………… 26
chapter 05
chapter 06
PlateSpin Forge GUI overview……………………………………………
70
PlateSpin Forge usage
overview
PlateSpin Forge usage overview………………………………………… 52
PlateSpin Forge GUI
overview
chapter
01
4
continuity
continuity
continuity
IT-BCP solutions
The importance of business continuity ……………………………………………… 6
Required approaches for business continuity………………………………………… 8
Historical and current guidelines for business continuity…………………………… 10
The power of virtualization technology for business continuity…………………… 14
solution
Tuning IT systems components……………………………………………………… 12
overview
PlateSpin Forge GUI
overview
5
chapter
01
Approaches to business continuity
The importance of
business continuity
Creating an environment capable of enabling
Information technology (IT) systems are already
business to continue despite disaster or breakdown
extensively deployed by corporations, and the
is an essential part of risk management and
importance of IT systems as business infrastructure
cannot be ignored by corporations. Even where
is increasing. For this reason, IT infrastructure
an interruption to operations is inevitable, it is
presents a very real risk to the continuous operation
essential that they are back up and running as
of corporations and to the provisioning of services.
quickly as possible.
This is why we think of IT business continuity
planning (IT-BCP) as a separate field of BCP, focused
For this reason, corporations world-wide invest
on IT. Ordinarily, BCP initiatives include measures
in business continuity planning (BCP), which seeks
such as maintaining backup systems and ensuring
to protect the corporation from reduced market
a backup office, accelerating safety confirmation
share or reduced corporate value by recovering
procedures, ensuring staff and arranging alternative
from interruptions to operations, or avoiding them
production facilities. This document however
all together. A number of approaches can be taken
focuses particularly on issues within IT-BCP,
to define BCP, but in its document PAS56 Guide
concerned with maintaining backup systems.
to Business Continuity Management, the British
Standards Institution (BSI) defines it as "continuity
When considering BCP initiatives, it is necessary
planning which recognizes impacts due to poten-
to think about the recovery point objective (RPO),
tial losses, establishes and implements an enforce-
the point in the data record and the age thereof
able continuity strategy, and ensures business
at which recovery is acceptable, the recovery time
continuity in the event of an emergency. Business
objective (RTO), the amount of time it takes to
continuity outcomes which document procedures
restore services, as well as the recovery level objec-
and information, developed, compiled and main-
tive (RLO), the level of operations to be recovered.
tained for use in the event of an emergency." Efforts
Additionally, day-to-day training for business conti-
to establish, operate, simulate and continuously
nuity should consider the test time objective (TTO)
improve BCP are generally known as business con-
metric, which asks how easy the system is to test.
tinuity management (BCM).
6
guide book
② Enables restoration of
operations within a set
time frame
After (initial and BCP response)
100%
Restoration
IT-BCP solutions
Target
Threshold
Target
Current expected recovery curve
Recovery curve after implementing BCP
Threshold
Time
solution
Level of operation (quantity of product supplied, etc.)
Before
Enables business
to continue at a level
above a set threshold
continuity
③
continuity
PlateSpin Forge
① Difference between target
and actual recovery time
Ref: http://www.bousai.go.jp/kyoiku/kigyou/keizoku/hajimete.html
RPO: Recovery Point Objective
→ How recent should the recovered data be?
RTO: Recovery Time Objective
→ How much time should be allowed for recovery?
TTO: Test Time Objective
→ How easily can testing be carried out?
Conceptual diagram of BCP measures
Service level
100%
under
normal
conditions
Full
recovery
Disaster
occurs
Status of data
at time of
provisional
recovery
Provisional
recovery
RLO
RPO
RTO
Time
PlateSpin Forge GUI
overview
RLO: Recovery Level Objective
→ What level of granularity should be recovered?
overview
Keywords for business continuity
Ref: Definition of BCP: http://www.meti.go.jp/policy/netsecurity/downloadfiles/BCPguide.pdf
7
chapter
01
Required approaches for
business continuity
When considering business risk as a factor in busi-
By precautionary, we mean measures to avoid
ness continuity, several perspectives must be incor-
encountering damage. Specifically, these would
porated. These perspectives cover a broad range of
be measures such as seeking to improve reliability
topics including exchange fluctuation risks, recall
of systems such as through load distribution or
risks associated with quality assurance, litigation
redundancy, or migrating to a robust and secure
risks and production equipment related risks such
data center capable of handling disasters. Recov-
as plant fires. Some of these could be included in
ery means providing an environment capable of
IT related business continuity risk. But in particular,
implementing rapid failover, e.g. by implementing
both breakdown risks and disaster risks must be
backups and having alternative servers as an emer-
considered as factors in IT risk.
gency precaution. Providing day-to-day training in
preparation for an emergency is another effective
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.
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
means of achieving rapid recovery.
guide book
continuity
Thejeopardize
very real ITbusiness
risk to business
continuity,
and countermeasures
IT risks that
continuity
and countermeasures
IT risk
Internal factors
Recovery
countermeasures
Minimizing risk
(threat avoidance and
reduction of vulnerability)
Loss/damage
minimization on
realization of risk
Hardware failure
Failure of
communication services
Software bugs
Improving
system
reliability
Redundancy,
load balancing, QA,
SPOF avoidance, etc.
Operational error
Backup and
recovery
Computer crime
Local disaster
External factors
(unavoidable)
Widespread disaster
Power failure/
restrictions
Loss of
data services
Favorable location,
seismic isolation,
redundancy in
equipment / circuits,
etc.
PlateSpin Forge GUI
overview
Tsunami/flood
Data center
ruggedization
Remote site control
Earthquakes
overview
Disaster risk
Backup acquisition,
preparation of
alternative devices,
failover, training, etc.
solution
Primarily on-site control
Processing overload
IT-BCP solutions
Failure risk
Preventative
countermeasures
continuity
PlateSpin Forge
* QA: Quality assurance, SPOF: Single point of failure, Exhibit: ITR
9
chapter
01
Historical and current guidelines
for business continuity
Originally, BCP existed as a concept from the
in March 2005, and the Business Continuity Guide-
1960s called disaster recovery (DR) and set out
lines Ver. 1 by the Central Disaster Prevention Coun-
disaster recovery countermeasures to cope with
cil of the Cabinet Office in August of the same year.
host computer breakdown. The term BCM emerged
In February 2006 the Small and Medium Enterprise
as a management concept in the 1999 British
Agency published an introductory examination
Standards Institution (BSI) standard on Information
and a range of templates for BCP policy formation
Security Management Systems (BS7799). This
under the title Small and Medium Enterprise BCP:
was later developed into Business Continuity
Guidelines for Formulation and Application.
Management Systems (BS25999) to handle a wide
Then, in November 2009 the document Business
range of organizations, and BCM is now applied
Continuity Guidelines Ver. 2 was published to sim-
by an increasing number of corporations at the
plify the application of Business Continuity Guide-
management level.
lines Ver. 1.
The requirements of BS25999 were later turned
In terms of guidelines on the subject of IT-specific
into an ISO standard, the International Standard for
issues (IT-BCP), METI provided the IT Service Con-
Business Continuity Management Systems (BCMS)
tinuity Guidelines in September 2008, and the
ISO 22301, issued in May 2012. These standards are
Information-technology Promotion Agency (IPA)
applied to all organizations, including corporations,
provided documents including the well known
public bodies, not-for-profit organizations and
Highly Resilient System Infrastructure Guide-
NGOs, whatever the scale or activities of the orga-
lines (Summary, Planning) in May 2012. Finally,
nization. They are set out as standard requirements
the National Information Security Center is due to
explicitly identifying the control items that need to
release guidelines looking at IT-BCP including the
be implemented.
Operational Continuity Planning Guidelines for
Information Systems in Central Government and
In contrast, the process of establishing guidelines
in Japan involved the publication of the Business
Continuity Policy Formation Guidelines by METI
10
the supplementary IT-BCP Formulation Model.
guide book
Key Points
1. What are business continuity initiatives?……………………1
2.2.3 Estimating damage to key activities……………… 15
2. Features of business continuity initiatives…………………3
2.2.4 Extracting key elements…………………………… 17
3. Features of these guidelines………………………………3
2.2.5 Establishing a business continuity plan…………… 18
2.2.5.1 Defining the command structure……………… 18
5. Standpoint of these guidelines……………………………5
2.2.5.2 Ensuring functionality at key corporate sites…… 19
6. Adopting a checklist………………………………………5
2.2.5.3 External data transmission and data sharing…… 19
2.2.5.4 IT system backup……………………………… 20
I. Basic approach to business continuity requirements…………6
2.2.5.5 Product-service supply relationship…………… 20
2.2.6 Issues to be derived in conjunction with
1.1 Requirements and key points in business continuity……6
1.1.1 The need to make business continuity work
in times of emergency…………………………………6
1.1.2 Key points in the approach to business continuity……6
1.1.3 Features of business continuity planning in Japan:
2.2.6.1 Safety assurance and safety confirmation……… 21
2.2.6.2 Disaster damage mitigation for offices/places
of work and equipment……………………… 21
2.2.6.3 Prevention of secondary disasters…………… 22
2.2.6.4 Community cooperation and contribution…… 23
2.2.6.5 Cooperation and mutual aid…………………… 24
1.2 Basic approach……………………………………………7
2.2.6.6 Other matters to consider……………………… 24
1.2.1 Hypothetical disaster risk………………………………7
1.2.2 Issues to be derived in conjunction with business
continuity………………………………………………8
1.2.3 Standpoint of each item provided in these
guidelines………………………………………………9
2.3 Implementation and operation………………………… 24
2.3.1 Implementation of measures under business
solution
being ready for widespread natural disasters…………7
business continuity………………………………… 21
IT-BCP solutions
4. Aims of and issues promoted by initiatives…………………4
continuity
Business Continuity Guidelines Version 2 Contents
continuity
PlateSpin Forge
continuity plan……………………………………… 24
2.3.2 Preparation of documents………………………… 25
2.3.2.1 Preparation of protocols and manuals………… 25
2.3.2.2 Preparation of checklists……………………… 25
2.3.3 Financial allowances……………………………… 25
II. Content of business continuity plans and initiatives……… 11
2.3.4 Confirming the plan works in practice…………… 26
2.3.5 Requirement for business decisions in event of
2.1 Policy…………………………………………………… 12
emergency………………………………………… 26
2.2 Planning………………………………………………… 12
2.4 Implementation of education and training…………… 26
overview
1.3 Continuous improvement……………………………… 10
2.2.1 Identifying relevant disasters……………………… 12
2.2.2 Evaluation of impact……………………………… 13
2.5 Inspections and corrective action……………………… 27
2.2.2.1 Estimating stoppage time and
2.6 Management level estimates…………………………… 27
2.2.2.3 Setting RPO and RLO…………………………… 14
III. Proposals for managers, the economy and society……… 28
PlateSpin Forge GUI
overview
responsiveness………………………………… 13
2.2.2.2 Determining key activities……………………… 13
IT systems operation continuity planning guidelines for central government: http://www.nisc.go.jp/active/general/itbcp-guideline.html
11
chapter
01
Tuning IT systems components
When thinking about IT-BCP, a major prerequisite
Taking hardware as an example, for hardware with
is that we understand the resources required to
a low recovery priority, the countermeasure objec-
continuously operate IT systems. It is essential for
tive may be considered as entering into contracts
business continuity that a strategy is developed for
for hardware maintenance and having the ability
every such resource.
to obtain repaired or replacement parts. As the
recovery priority increases, the objective might be
Specifically, required resources might be hardware
keeping a backup unit on hand at a remote site
to run systems, system-based resources such as
away from the system operations site, and ensuring
applications or system configurations, data-based
hardware is available on cold standby for setup in
resources including management of backup data,
the event of an emergency. For hardware with the
facilities to house systems, and an uninterruptable
highest levels of recovery priority, the objective
communication network. In practice, additional
could be to provide an exclusive replacement unit
resources are required such as a non-emergency
at a remote site with synchronized data, and ensur-
testing system and an on-site operational system
ing an environment capable of rapid recovery by
to investigate IT-BCP, and even business partners
switching to the replacement unit in the event of
who also have business continuity capabilities and
an emergency.
alternative procedures to restart activities, should a
disaster happen. We clearly see that a vast number
It is crucial to have a clear idea of the recovery pri-
of resources are needed to achieve operational
orities and countermeasure objectives for each IT
continuity of IT systems.
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
guide book
continuity
Example IT system components
Component
Explanation of component
1
Hardware
2
System-related
3
Data-related
4
Facilities
5
Data communication
network
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
7
System operational
structure
Ensuring operational human resource and role allocation to achieve rapid confirmation of damage to systems and
8
Business continuity
capabilities of vendors
9
Fallback system
Role, quantity and location of hardware such as servers (including for replacement units)
Location and status of data required for recovery of IT systems, such as applications and system configuration
data (external storage of backup media, etc.)
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)
appropriate responses, and ensuring maintenance of standard operating procedures and means of communication.
(* Item added in this study)
Alternative procedures for recovery of operations where IT systems are suspended in case of an emergency
Countermeasure Objective
Ensuring hardware for hot standby
A
• Recovery is performed through backup systems by switching in an replacement unit in case of an emergency.
• Provision of exclusive replacement units in locations which will not be simultaneously subject to the same
disasters as production units.
3
• Provision of alternative client PCs for use in case of emergency.
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.
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
E
2
• Utilize thin clients to avoid impact on client environments due to damage to the working environment.
incurred to hardware.
• Regular saving of data on client PC operating systems.
1
PlateSpin Forge GUI
overview
D
overview
S
Countermeasure
Level
solution
Support and collaboration structures with IT system vendors in case of an emergency (capturing of vendors'
business continuity capabilities, maintenance of service assurance contracts, etc.)
Recovery
Priority
Rank
C
IT-BCP solutions
Location and status of key data (external storage of backup media, etc.)
Hardware Countermeasure Objectives Level
B
continuity
PlateSpin Forge
Ref: http://www.nisc.go.jp/active/general/pdf/IT-BCP.pdf
13
chapter
01
The power of virtualization
technology for business continuity
Let us now think about specific strategies for
This is also where virtualization technology
business continuity in the IT field, i.e. IT-BCP
comes in. Virtualization technology enables
measures. We of ten hear about ef for ts to
physical environments to be deployed as virtual
increase redundancy in IT systems and improving
machines, and allows systems to be designed and
fault tolerance through the use of clusters. For
built freely using a hypervisor, with no hardware
high priority tasks, it is obvious that a backup
platform dependence. This technology not only
environment is required at a different location
enables migration to different environments, but is
to the production site, but it is important above
also ideal when used as a system infrastructure for
all to create a highly flexible system that allows
BCP, enabling the automation of the operational
operations to be rapidly redeployed.
management of system continuity. The key features
of virtualization technology are increased reliability
The key benefit of providing a remote environ-
and availability, while making efficient use of com-
ment is that even if the production site is knocked
puting resources.
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.
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
guide book
Vir tual Machine
Application
Application
Application
Application
Guest
OS
Guest
OS
Guest
OS
Guest
OS
continuity
Difference between physical environments and virtualized environments
continuity
PlateSpin Forge
Physical Machine
Physical Machine
Operating System
Vir tualization platform
x86 Hardware
x86 Hardware
Memory
Disk
NIC
CPU
Memory
Disk
Virtualized platform
• One OS on one ser ver
• Vir tualized hyper visor
• Inefficient use of resources
• High per formance
• Close integration of software and hardware
• Flexible resource management
• Independent from software and hardware
virtualization platform.
This enables the virtual machine to operate flexibly, with no specific platform dependence.
PlateSpin Forge GUI
overview
Unlike physical environments, virtualization technology transfers the close connection to the hardware to the
overview
Conventional IA ser ver
NIC
solution
CPU
Application
IT-BCP solutions
Application
15
chapter
02
16
continuity
continuity
continuity
IT-BCP solutions
Cost considerations for business continuity: hardware……………………………… 18
Cost considerations for business continuity: software……………………………… 20
Cost considerations for business continuity: personnel……………………………… 22
solution
Cost considerations for business continuity: other…………………………………… 24
overview
PlateSpin Forge GUI
overview
17
chapter
02
The cost of business continuity
Cost considerations for business
continuity: hardware
In this chapter we will look in more detail at the
provider, or another alternative would be to build a
costs of IT-BCP. Firstly, we have to ask what hard-
customized environment using robust remote data
ware elements are required.
center facilities.
The first thing to understand is that it is some-
For low priority systems allocated a medium or
what difficult to generally predict what hardware
long RTO and RPO of several days to one month,
is required, as the recovery time objectives (RTOs)
the general method would be to restore data once
and recovery point objectives (RPOs) differ depend-
the new environment would be ready, having pre-
ing on the type and priority of system. The biggest
pared a backup of data and system parameters on
differences in hardware configurations arise from
portable media such as tape. In this case we use a
the necessity for rapid recovery and the necessity
tape device such as an autoloader or tape library
for recovered data to be perfectly up-to-date.
for backup of production environment data, requiring storage on multiple volumes of tape media
For example, if the RTO and RPO are set to a short
such as LTO tape drives. However, it must not be
period or time, then system redundancy is the
forgotten that to finally recover the original state,
key premise. In this case, the backup site has to be
the hardware for operating the production environ-
ready with the same system environment as the
ment must be redeployed or repaired.
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.
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
guide book
continuity
DB ser ver
continuity
PlateSpin Forge
AP ser ver
LAN switch
If the RTO and RPO are relatively short
Router
With a relatively
RTO and
RPOhot or
periods,
less thanshor
24 thours,
either
of less than 24 hours, a mirror production
cold
standby ismethods
beonused
environment
installed may
locally
hot in a
or cold installation
standby
remote
mirroring the producADC/ WAF
tion environment.
solution
SAN storage
IT-BCP solutions
SAN switch
periods,
a backup
production
With a relatively
longofRTO
and RPO, enviproduction
network
data andparameters
system
ronment
data
and system
is
overview
If the RTO and RPO are relatively long
settings are backed up on por table
Tape media
Tape librar y
made
a portable
mediato
such
as tape media such as tape.
PlateSpin Forge GUI
overview
19
chapter
02
continuity: software
The software that is required will naturally differ
est backup tools, a growing number of products
depending on the hardware configuration. If the
support virtual environments, and incorporate the
RTO and RPO are set to short periods, under 24
functions necessary for IT-BCP.
hours, some sort of replication tool will be required
to make regular copies of data to a backup site.
Some backup tools include options with replica-
When a method using an intrinsic replication func-
tion functionality, but as many backup appliance
tion of SAN storage or some similar technology is
products have their own internal software function-
adopted, then this requires advanced hardware.
ality, this software may not be required, depending
on the environment.
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.
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
guide book
• Complete backup
continuity
Key functions of legacy backup software
continuity
PlateSpin Forge
• Incremental backup
Data backup
• Differential backup
• Single file backup
• Deduplication
• Disk image
• RAW backup
Backup devices
• Tape backup (D2T)
• Disk backup (D2D)
• D2D2T
• Cloud backup
Application agent
• SQL Server
• Oracle Database
• Lotus Domino
• Exchange Server
PlateSpin Forge GUI
overview
• Single file
• Bare metal
• Virtual machine
overview
Recovery
solution
System backup
IT-BCP solutions
• Open file backup
21
chapter
02
continuity: personnel
Now let’s examine the cost of tasks that are likely
operating system security patches must also be
to arise during the day-to-day operation of infra-
applied. Cold standby units will also require regular
structure at a backup site.
operating system and application upgrades. Maintaining the backup system in the same way as the
First and foremost, if RTO and RPO are defined to
production system ensures that work can proceed
be short, then a state of the art replication infra-
without a glitch in the event of an emergency.
structure will have to be provided at the backup
site. If there are plans to rebuild the production
If the RTO and RPO are not quite as aggressive,
environment, the opportunity should be taken to
the routine backups as described earlier would still
setup both sites concurrently, while incorporating
apply as a strategy. Where backup is performed to
data copying techniques such as replication into the
tape or similar, the tapes would need to be trans-
design. This is an efficient way to build a backup site.
ferred to a remote location, and their storage would
require careful management.
When a backup site is built to support an operational production environment, it is important to
Another cost that arises, regardless of the time-
ensure the hardware infrastructure and software
scale, is regular testing and training to confirm that
are as similar to the production environment as
recovery would be possible in any event. A strict
possible. If an unavailable CPU type or an older
schedule should be prepared and the switching
version of the software is used, it may be necessary
process verified, showing that the backup site
to update the backup site, which may require con-
could be setup under conditions where the produc-
siderable time and effort in verification and testing.
tion environment is offline. This element also incurs
a labor cost.
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
22
guide book
continuity
PlateSpin Forge
continuity
Routine
monitoring
Upgrades
overview
Recovery
testing
solution
Security
patching
Backups
IT-BCP solutions
Network
setup
In addition to building the initial environment, routine operations such as monitoring and
Recovery verification testing is another essential.
PlateSpin Forge GUI
overview
upgrade operations must also be considered.
23
chapter
02
continuity: other
In addition to the hardware, software and personnel
Alternatively, if the backup site is always in oper-
costs already addressed, there are a number of other
ation, there would need to be a calculation of the
costs associated with IT-BCP that cannot be ignored.
costs associated with the backup, such as electricity costs. Options for power outages such as UPS
If a rapid recovery is sought, routine online back-
or on-site power generation should also not be
ups are required, but for high volume backups this
ignored. On-site power generation would also incur
requires a dedicated broadband connection. Even if
costs related to ensuring a source of fuel as well as
incremental and differential backups or deduplica-
storage costs.
tion is being used, it may be impossible to run the
backups on the same connection as ordinary tasks.
Thinking about IT-BCP in this way, we can easily
In these cases, a duplicate connection would defi-
see the wide range of associated costs. Corpora-
nitely aid IT-BCP. It is important to review the band-
tions must ensure optimal BCP countermeasures
width available on existing network connections.
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
guide book
continuity
PlateSpin Forge
continuity
IT-BCP solutions
Power strategy
(cost of power, UPS,
self-generating devices)
Training costs
overview
Network costs
solution
Securing human resources
IT-BCP countermeasures come with a variety of unavoidable costs, in addition to hardware
and software.
PlateSpin Forge GUI
overview
The optimal solution is found by estimating and preparing for these costs.
25
chapter
03
26
IT-BCP solutions
continuity
continuity
Characteristics of tape backup……………………………………………………… 30
IT-BCP solutions
Potential solutions and comparison thereof………………………………………… 28
Characteristics of storage replication………………………………………………… 32
Key points for selecting the optimal IT-BCP solution………………………………… 36
Example cost calculation……………………………………………………………… 38
solution
Characteristics of system redundancy……………………………………………… 34
overview
PlateSpin Forge GUI
overview
27
chapter
03
Merits and demerits of IT-BCP solutions
Potential solutions and
comparison thereof
IT-BCP solutions can take various forms depend-
However, the procedure for switching systems
ing on the scale and structure of the system and
in, such as changing environmental settings of the
the type of business. Earlier we introduced RPO
installed operating system and applications, as well
(recovery point objective) and RTO (recovery time
as changing over networks, is complex, and requires
objective), and the options available differ depend-
technicians with adequate training to be present at
ing on how these are set for each system. But let
the backup site. Additionally, the initial installation
us first look at general BCP measures. Here, we will
costs tends to be high, as a high-end storage array
introduce tape backup, storage replication and
is needed to handle the remote replication.
system redundancy methods.
The key feature of system redundancy then,
Firstly, the key feature of tape backup systems
where a backup site is maintained with the same
using portable tape media has to be the low cost
infrastructure as the production environment, is
of the environment. For example, the latest tape
rapid system recovery. System redundancy is the
standard, LTO-6 (2.5TB) can be obtained for a little
optimal method for mission critical operations that
over $50. A drive to run LTO tapes can also be pur-
must not fail. There is, of course, a very high cost
chased for around $2,000. This is the recommended
associated with the installation of a mirror envi-
method for organizations seeking to constrain
ronment, and the need for maintenance to match
initial costs. However, whatever the RPO or RTO,
the production environment adds a considerable
restoration using this method takes time, and there
running cost. A stable network is also required for
are additional running costs related to tape replace-
real-time data copying. Some implementations will
ment and storage.
also require a broadband network, making this a
method requiring a considerable investment.
Next we have storage replication, which maintains
the same storage baseline as the production envi-
All three methods have their merits and demerits,
ronment, giving it the key feature that data at the
but the optimal IT-BCP approach can be found by
backup site represents the situation just prior to
selecting the appropriate target recovery point and
any incident, so the backup data is up-to-date and
recovery time.
the RPO is very aggressive.
28
guide book
continuity
Tape Backup
● Low
●
cost
Only data can be recovered
● Restoration
OS and applications need to be re-installed
● High
daily operational load
(replacement, storage and rotation of tapes)
RPO:
RTO:
Insufficient
for BCP
IT-BCP solutions
●
TCO:
takes time
continuity
PlateSpin Forge
Storage Replication
very up-to-date
● Only
data can be recovered
● OS
and applications need to be re-installed
● Switching
●A
process is complex
technician is needed at the disaster recovery site
TCO:
RPO:
RTO:
Not
cost-effective
solution
● Data
● Installation
costs are high (reconstruction of
storage infrastructure)
overview
System Redundancy
●
System can be recovered in a short time
installation costs (at least doubles
system installation cost)
TCO:
● High-speed
RPO:
● Expensive
connection needed
to operate (maintenance of
backup systems)
RTO:
Highly
effective, but
also highly
expensive
PlateSpin Forge GUI
overview
● High
29
chapter
03
Characteristics of tape backup
Let us look again at the characteristics of tape
stores only the parts that have changed since the
backup.
previous backup, and differential backup, which
stores only the parts which have changed since the
Magnetic tapes used for backup enable informa-
previous full backup. Recently it has become the
tion to be recorded by magnetizing a large number
norm to employ deduplication, which optimizes
of minuscule particles. While various standards have
the number of backup tapes and storage capacity
existed in the past, including DDS, DTL and AIT, the
by excluding duplicate data.
current mid-range leading product is LTO (Linear
Tape-Open), with some DDS still in use. There are
Although tape backup can significantly con-
also additional high-end standards designed by
strain initial installation costs compared to other
individual vendors. The present version of LTO is
methods, there is a considerable cost associated
Generation 6 (LTO-6: without compression 2.5TB,
with routine management such as magnetic tape
with compression 6.25TB), and a roadmap exists up
replacement and storage. Furthermore, in the event
to Generation 8.
of recovery, the process involves finding the appropriate magnetic tape and performing the restora-
Tape backup uses a backup tool to backup and
tion manually. So while via scheduling the backup
restore data. The backup method is capable of
process itself can be automated, recovery requires
backing up individual files, as well as images, where
a lot of time and effort.
the whole system including the operating system
and applications is stored block-by-block as an
A product similar to magnetic tapes that offers
image file. There also exists a system called CDP
high capacity and portability is RDX. RDX is a hard
(Continuous Data Protection) that is installed as an
drive based solution and is used for rapid data
agent on the device to be protected, where it con-
access. An RDX drive uses a USB connection, and
stantly monitors its status and performs backup in
when a cartridge is inserted it is recognized as a
real time in the event of any change or addition.
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
guide book
continuity
Operating site
Disc redundancy
(R AID board, GDS)
Mirror
Business continuity
for minor disasters
IT-BCP solutions
A
Integrated backup
environment
Built in
continuity
PlateSpin Forge
Tape library
Backup server
Mirror
Built-in
B
solution
A
B
overview
Data storage site
A
Transportation
Backup data
PlateSpin Forge GUI
overview
B
31
chapter
03
Characteristics of storage
replication
Next, let us look at storage replication.
in accordance to a schedule. Storage hardware
enabled for replication can usually handle both syn-
Storage replication is a technology for real-time
chronous and asynchronous replication processes.
copying of the computer data to be protected, and
is an effective way of mitigating the breakdown risk
If synchronous replication is selected, restoration
of continuous services. A storage replication sys-
can be performed using data from immediately
tem constantly acquires data, allowing restoration
prior to the breakdown, giving an optimal RPO,
to the point just prior to the breakdown, and can,
although an operating system and environment
from a business continuity perspective, provide
would have to be arranged first. Setting a short RTO
excellent RPOs (recovery point objectives).
(recovery time objective) is not sufficient in itself.
Skilled technical support would be required at the
There are two types of storage replication:
remote site to achieve rapid recovery in the event
synchronous, where the computer to be protected
of an emergency.
and the replication storage media are written to
simultaneously, and asynchronous, where the
Replication solutions that come as a black box
replication storage is written to according to a
from a storage vendor require a network that can
defined schedule.
handle the load as well as a system for transferring data to the remote site. While the initial data
32
Synchronous replication completes the I/O writ-
transfer requires a full copy of all data stored at
ing process when it is confirmed that the write to
the time, once this is completed, the data transfer
the protected computer and the replication stor-
volume can be reduced by employing functions to
age media was successful. This means adequate
transfer only those blocks in a snapshot which have
network bandwidth to the remote site is required,
changed, and by making use of deduplication to
as well as a low-delay latency. Asynchronous rep-
identify duplicate data block-by-block. These meth-
lication writes data to be protected to the storage
ods provide a system for minimizing data transfer
media, exports data to be replicated to memory,
volume on the network, while achieving high
and performs copying to the replication device
speed data copying.
guide book
Application server
ACK
①
④
②
③
Local
IT-BCP solutions
Write I/O
An I/O complete message
(ACK) is returned to the
server upon completion of
transfer to the remote site
continuity
Synchronous Replication
continuity
PlateSpin Forge
Remote
Zero data loss in event of disaster
Asynchronous Replication
solution
Additional delay for transfer to remote site
Application server
ACK
①
overview
Write I/O
An I/O complete message
(ACK) is returned to the
server before transfer to
the remote site
②
③
④
Remote
No delayed I/O to server
Some data loss in event of disaster
PlateSpin Forge GUI
overview
Local
33
chapter
03
Characteristics of system
redundancy
Now let us look at some ways of achieving system
As mentioned above, transfer of data to a
redundancy.
remote site is achieved by replication. To ensure
the shortest RPO and RTO while maximizing
System redundancy, as the name suggests,
availability, synchronous replication is required,
involves the construction of a backup site with the
but this does come with an additional cost, as
exact same environment as the production envi-
a low latency broadband network is needed.
ronment, and that is capable of handling hardware
Although asynchronous replication is available as
breakdown by duplicating the computer itself using
an option, mission critical systems requiring system
clustering, as well as coping with disaster by copying
redundancy are generally better suited with the
data to a remote site in real-time using replication.
synchronous model.
As this system enables instant recovery to a state
However, providing a system environment at two
immediately prior to the breakdown, in IT-BCP
sites has a considerable impact on system installa-
terms it enables RPO and RTO to be set at will. It
tion costs, and a broadband connection is essential
is ideal for mission critical operations that require
to achieve real-time information processing and
high business continuity performance.
instantaneous switching. Furthermore, day-to-day
maintenance would be required at the backup site
Clustering is most often achieved using failover
in the same manner as the production environ-
clustering, which for Windows environments
ment, adding to the maintenance costs.
is available in Windows Server 2012, but uses
specific clustering software under non-Windows
Operations that require continuous system avail-
platforms or virtualized environments. The reason
ability demand infallible protection through system
for this is that clustering functions in a virtualized
redundancy regardless of cost.
environment are unable to monitor ever y
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.
34
guide book
A
A
Cluster
Cluster
Currently in use
Currently in use
Standby
Standby
Mirror between
R AID devices
A
IT-BCP solutions
Storage
area
network
(SAN)
Backup server
continuity
Primary site (data center)
B
B
continuity
PlateSpin Forge
B
solution
Remote mirror
Wide Area
Ethernet
R AID device
Storage
area
network
(SAN)
overview
B
Backup server
A
Standby
Standby
Cluster
Active
(reference
system)
B
A
B
Standby
Cluster
PlateSpin Forge GUI
overview
Active
(reference
system)
AA
Secondary site (data center)
A
35
chapter
03
Key points for selecting the
optimal IT-BCP solution
We have seen how each of the IT-BCP solutions
monthly accounts could be missed, so the level of
discussed so far has its own merits and demerits. Pre-
protection should perhaps be of the order of a few
venting system interruptions in the event of a break-
hours. Difficulties would also arise if core sales sys-
down can be costly, and while low cost methods of
tems were to fail, such as plant production control
avoiding operational difficulties are available, these
or invoice issuing.
require patience. Essentially, the key is to determine
the recovery priority of all existing systems.
Internal communication infrastructure such as
mail servers and groupware servers represent
Although the approach will differ from corpora-
another field where the impact on business due
tion to corporation, we should seek to minimize
to a loss of service could be significant, but it may
the RTO of those systems that, if interrupted,
be possible to overcome this by adopting alterna-
would have a significant impact on business. The
tive means of communication such as cellphones,
operations that require rapid recovery are those
smartphones or social network services like Face-
that have a considerable impact on business, such
book. The RTO could well be set to be a little more
as accepting orders or shipping instructions. Such
flexible in this case.
issues have a direct impact on customers. Important systems such as call centers handling customer
inquiries should also be considered.
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
guide book
continuity
overview
Ordering
system
Sales
management
system
solution
Call
center
system
Financial
accounting
system
RTO
IT-BCP solutions
File
server
continuity
PlateSpin Forge
Communication
system
Impact on operations
PlateSpin Forge GUI
overview
37
chapter
03
Example cost calculation
An unavoidable key concern when considering
Therefore, the focus is now on installing a custom-
IT-BCP solutions is cost. Seeking recovery as rapidly
ized appliance running a virtual environment at a
as possible implies significant investment and orga-
remote site, as a backup standby environment. In
nization, and deters some corporations from adopt-
the event of an emergency the appliance is capable
ing measures. The reason for this is the high cost of
of continuing operations in the same way as the
maintaining the backup site or environment, due
production environment. One such backup appli-
to the dependence of the system on the hardware.
ance product is PlateSpin Forge from Netiq.
However, the latest virtualization technology is now
delivering solutions that enable standby environ-
Real-use cost calculations show this approach to
ments to be built flexibly, with no dependence on
be exceedingly efficient. Let us compare storage
the physical environment. These backup methods
replication with a backup appliance, both running
use customized infrastructures such as cloud ser-
storage synchronization. If we assume the corpo-
vices or backup appliances to allow a mirror of the
ration's production environment runs 15 physical
production environment to sit in standby.
servers and five virtual servers, we would expect a
typical cost reduction of 44.8% for a TCO period of
In other words, to address both low cost and
four years from installation.
rapid recovery, the approach must now consider
the recovery level objective (RLO), or the level of
This backup appliance option has gained consid-
business that should be recovered. As a recovery
erable attention as a solution that satisfies the prin-
level of 100% would require considerable main-
ciples of business continuity while keeping costs to
tenance costs for the standby environment, a
a minimum.
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 continuity with minimum impact.
38
guide book
continuity
Breakdown of total costs (normal operations):
"Inter-storage transfer vs. Backup appliance"
$
continuity
PlateSpin Forge
700K
600K
500K
400K
300K
100K
0
B: Backup appliance
Service
$53,240
$53,240
Testing
$41,917
$16,765
$201,204
$0
$43,104
$8,714
$179,715
$154,354
Permanent operation
Construction
Product
$
solution
A: Inter-storage transfer
IT-BCP solutions
200K
Change in TCO (normal operations):
"Inter- storage transfer vs. Backup appliance"
700K
600K
overview
500K
400K
300K
200K
100K
0
Year 2
Year 3
Year 4
$162,145
$281,192
$400,195
$519,229
B: Backup appliance
$51,223
$111,850
$172,435
$233,047
PlateSpin Forge GUI
overview
Year 1
A: Inter-storage transfer
From the ITR document, "Investment efficiency in business continuity solutions using virtual environments: low cost disaster recovery".
39
chapter
04
40
PlateSpin Forge as
IT-BCP solution
continuity
continuity
IT-BCP solutions
PlateSpin solution overview………………………………………………………… 42
Optimal virtualization planning: PlateSpin Recon…………………………………… 44
Migrating to a virtual environment: PlateSpin Migrate……………………………… 46
Overview of business continuity using PlateSpin Forge……………………………… 50
solution
PlateSpin Forge as IT-BCP solution…………………………………………………… 48
overview
PlateSpin Forge GUI
overview
41
chapter
04
PlateSpin Forge as IT-BCP solution
PlateSpin solution overview
We have talked about how virtualization tech-
calculated accurately during the migration plan-
nology can be useful for IT-BCP. The PlateSpin
ning, so that they match the actual workloads. The
product line from NetIQ offers a solution for each
PlateSpin Recon virtualization planning tool is ideal
stage (phase) of virtualization, with virtualization
for these capturing and planning phases.
technology-enabled solutions to support all efforts
on the journey to a fully virtualized environment.
Once migration planning has been done, the
Essentially, the four phases are situation capture,
migration phase begins, to eventually migrate from
planning, migration and backup/BCP.
the current environment to the new environment.
Generally, if the existing environment runs on phys-
In order to achieve a virtualized environment, the
ical infrastructure, this is a P2V (physical to virtual)
first essential phase is to capture the current state
migration. If a workload is to be developed on a
of affairs, such as capturing internal servers, prepar-
virtual platform using an on-premise environment,
ing an inventory and gathering data on workloads
a V2V (virtual to virtual) migration is required.
(whole environments to run on the virtual machine
hosts). Before making the switch to a virtual envi-
PlateSpin Migrate is a useful solution for migration
ronment, assuming the purpose is to develop a
of data and systems between various environ-
backup environment for IT-BCP at the same time, it
ments, and is capable of freely migrating workloads
is important to ascertain which servers are handling
between physical and virtual environments. Its key
important workloads, as well as creating the sched-
feature is the ability to handle all major virtualization
ule for implementation.
platforms such as VMware, Microsoft Hyper-V, SUSE
Linux Enterprise with Xen and Citrix XenServer.
Once the situation has been captured, the next
42
phase is the planning phase, which involves migra-
The final phase is the IT-BCP solution: backup/
tion planning to determine the sizing of virtual
BCP. When specifying any environment for backup,
servers according to the size of the new environ-
whether physical or virtual, it is important to inte-
ment and the schedule for migration according
grate backup while mitigating operational load.
to prioritization, as well as careful measurement
In the event of an emergency, the solution should
of effectiveness following migration. The required
be capable of implementing provisional recovery
resources for the migration environment must be
using flexible failover, and supporting rapid busi-
guide book
The PlateSpin backup appliance PlateSpin Forge,
available for use when an environment matching
with its software component PlateSpin Protect,
the production environment is again ready for use.
meets the needs of this phase.
Phase
Planning
Migration
Backup / BCP
• Capture internal
servers
• Sizing of virtualized
servers
• P2V (physical to virtual)
• BCP Solution
• Compile inventory
• Migration planning
• V2V (virtual to virtual)
• Backup of physical
servers
• Monitoring
• Measurement of
overall effectiveness
• V2P (virtual to physical)
• Compile workload
• Identifying targets
for virtualization
• P2P (physical to
physical)
• P2I (physical to image)
• V2I (virtual to image)
• I2V (image to virtual)
• Failover
• Backup integration
• Disaster recovery
appliance
PlateSpin Forge/PlateSpin Protect
Product
overview
• I2P (image to physical)
• Backup of virtual
servers
solution
Key
Tasks
Capturing
current situation
Virtual/Cloud
IT-BCP solutions
Route to virtualization and the cloud
continuity
ness continuity. A failback function should also be
continuity
PlateSpin Forge
PlateSpin Recon
PlateSpin Migrate
PlateSpin Forge GUI
overview
43
chapter
04
Optimal virtualization planning:
PlateSpin Recon
Next we will take a closer look at the product in
business changes and improved planning. Efficient
the PlateSpin solution portfolio for planning the
sizing is achieved by constantly maintaining an
optimal virtual environment, PlateSpin Recon.
optimal environment.
PlateSpin Recon is a virtualization planning tool to
When considering an IT-BCP solution, it is only
assist you in achieving optimal resource planning
by setting the level at which business needs to
for your virtual environment. In addition to tracking
be recovered, the RLO (the fallback level required
CPU, memory, HDD and network use on all existing
for recovery), that a plan suited to the required
servers on the network in both physical and virtual
performance can be created. PlateSpin Recon
environments, PlateSpin Recon enables remote
can help in creating such a plan. It also includes
capture of inventories and performance data. The
a function for analysis of cost reductions and
workloads are then analyzed in detail leading to
investment efficiencies compared to the existing
automated creation of a server integration and
environment, which even calculates hypothetical
consolidation plan. PlateSpin Recon is designed
electricity and cooling costs under the created plan.
to automatically handle up to 10,000 server data
So as well as with IT-BCP, the software also helps
points. All operations are performed agent-less.
with corporate social responsibility (CSR) efforts for
CO2 emission reduction.
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
44
guide book
continuity
PlateSpin Forge
continuity
IT-BCP solutions
solution
overview
PlateSpin Forge GUI
overview
45
chapter
04
Migrating to a virtual environment:
PlateSpin Migrate
Next in the PlateSpin solution portfolio is
The software can handle all major virtualization
PlateSpin Migrate, which enables workloads to be
platforms including VMware ESX, VMware ESXi,
freely migrated.
Microsoft Hyper-V, SUSE Linux Enterprise with Xen
and Citrix XenServer, and is designed to enable
PlateSpin Migrate is a virtualization and migration
simple migration between different virtualization
tool that enables migration of servers running on
platforms, such as from VMware to Hyper-V or the
virtual or physical environments, called workloads,
other way around. This means virtual environments
to other physical or virtual environments. Because
can be created with no dependence on a specific
workloads can be migrated as they are, with-
vendor, allowing the virtualization platform to be
out altering the existing environment, PlateSpin
changed in the event of new trends in virtualization
Migrate is able to migrate a physical server to a test
platforms or new evaluations of cost efficiency.
virtual environment to verify application functionality. Conversely, a system that has been developed
Because PlateSpin Migrate is capable of returning
and tested in a virtual machine can be deployed
virtualized workloads back to a physical environ-
in a single step to a physical server to become the
ment, there is always peace of mind that a V2P
production environment.
operation can be implemented in the event of
application incompatibilities leading to issues with
Ordinarily, P2V migration requires complex proce-
the virtual environment. All in all, PlateSpin Migrate
dures such as the setup of the virtual machine, but
is a powerful solution supporting end-to-end vir-
with PlateSpin Migrate this operation is simplified
tual environment migrations.
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.
46
guide book
continuity
PlateSpin Forge
continuity
IT-BCP solutions
solution
overview
PlateSpin Forge GUI
overview
47
chapter
04
The next item in the PlateSpin portfolio is NetIQ’s
While business continuity for production environ-
IT-BCP solution: the PlateSpin Forge backup appli-
ments usually involves a performance reduction,
ance and its software element PlateSpin Protect.
the level of fallback operation can be adjusted
Let us focus more closely on the appliance product
to allow considerable improvements in RTO. If a
PlateSpin Forge.
network is provided to remotely access PlateSpin
Forge, the provisional recovery process can be sim-
PlateSpin Forge is a backup appliance product
ply implemented without the need for staff to be
which provides business continuity functionality
deployed at the remote site.
via a provisional recovery environment in the event
48
of an emergency, through integrated backup of
Even if the new failback environment has
multiple servers, whether physical and virtual envi-
hardware from a different vendor than the one
ronments, on a single unit. Because PlateSpin Forge
used in the initial environment, or uses a different
is an appliance server preloaded with the hardware
virtual environment, the system can handle it.
environment required for business continuity as
PlateSpin Forge comes equipped out-of-the-box
well as virtualization and recovery software, it can
with a broad set of drivers for multiple virtual and
start providing value as soon as it is connected to
physical platforms, and is capable of flawlessly
the network, and vastly simplifies the process of
restoring from e.g. Microsoft Hyper-V to VMware
managing BCP environments.
ESX, or to Citrix XenServer.
When using PlateSpin Forge, recovery, including
It also incorporates a failover test function that
different system settings for each and every data
allows failover testing to be performed using
backup, is simply a matter of a few clicks. As well
different network settings than the production
as being useful as a routine backup environment,
environment. PlateSpin Forge can be set up to run
PlateSpin Forge excels at operating as a failover
its own test environment, so failover testing can
environment for provisional recovery in the event
be performed with no impact on the production
of an emergency. It can also perform failback back
environment, allowing it to be used as a verification
to the original environment, once the infrastructure
environment for security patches and application
is ready, to achieve full recovery.
upgrades. Once testing is completed, all updates
guide book
Forge is thin provisioning-enabled, meaning it is
to a synchronized state, meaning you can freely
capable of virtualizing storage volumes to support
change, add or delete test environments and
flexible storage operations.
continuity
are deleted and the system automatically reverts
continuity
PlateSpin Forge
always have the option to immediately reset.
Finally, as well as offering recovery point manage-
PlateSpin Forge Dashboard
IT-BCP solutions
ment on a workload-by-workload basis, PlateSpin
solution
overview
PlateSpin Forge GUI
overview
49
chapter
04
Overview of business continuity
using PlateSpin Forge
Now let us look again at how PlateSpin Forge can
be 100%, but it will provide business continuity
be of use from a business continuity perspective.
at a fallback level. As in practice often a network
Because it is a backup appliance, PlateSpin Forge
switchover is required, PlateSpin Forge can auto-
excels across a range of scenarios, for routine
matically convert the backup system's IP address
backup use as well as for business continuity and
to match the failover network before booting. This
restoration in emergencies.
means the system will have network access as
soon as it is switched on. This eliminates the task of
Firstly, during routine use in a production envi-
changing network addresses following restoration,
ronment, PlateSpin Forge functions as a device to
as often required with system backup tools.
collectively backup multiple servers. It implements
replication for both data and system settings, and
Once the hardware and the software that are to
applies internal recovery point management. In the
be used for the full recovery are ready, PlateSpin
event of data loss such as due to a deletion made in
Forge's internal virtual workload can be restored
error, even if this error is replicated, PlateSpin Forge
to the production environment. The new environ-
can still recover the environment by returning to
ment options can be simply selected using the GUI,
one of the multiple previous recovery points. It also
providing a secure failback route without multiple
employs incremental backup, so backup time is
complex steps. As well as failback to a physical
kept to a minimum by avoiding backup of the same
environment, PlateSpin Forge is also designed to
data again and again.
handle failback to virtual environments, and restoration can proceed even when different hardware
In the event of a disaster or breakdown, the
is used in the new system. Restoration can also be
workload can be booted up using PlateSpin Forge's
performed to a different virtualization platform
internal virtual environment, providing dramatic
than the original one.
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
50
guide book
In event of disaster / failure
Service level
Under normal
operation
continuity
Overview of business continuity using PlateSpin Forge
continuity
PlateSpin Forge
Full recovery
100%
RLO
RPO
RTO
Time
IT-BCP solutions
Provisional recovery
Final backup
solution
Implementation of integrated
backup
Reduced-level operation
Restoration to production
using Forge's internal
server once prepared
backup system
overview
PlateSpin Forge GUI
overview
51
chapter
05
52
overview
continuity
continuity
Key feature of PlateSpin Forge: easy-to-use GUI with low overhead………………… 56
Two methods for initial workload replication………………………………………… 58
IT-BCP solutions
Key feature of PlateSpin Forge: simple and user-friendly setup……………………… 54
Routine operations example 1……………………………………………………… 60
Routine operations example 3 – system recovery training…………………………… 64
Failover……………………………………………………………………………… 66
solution
Routine operations example 2……………………………………………………… 62
Failback……………………………………………………………………………… 68
overview
PlateSpin Forge GUI
overview
53
chapter
05
PlateSpin Forge usage overview
Key feature of PlateSpin Forge:
simple and user-friendly setup
One key feature of PlateSpin Forge is its simple
for business continuity simply by placing it on the
setup. This is because as a product it includes all
network and making simple configuration changes
the elements required for business continuity:
using the GUI. Of course, the performance will not
hardware such as a server and storage, recovery
be equal to the production environment, but it is
software with replication and backup functionality,
powerful enough to implement business continuity
and a virtual environment. All of this is provided in
at an excellent fallback level.
one unit, as a single package.
System building with PlateSpin Forge is easy. Ordi When we think about ordinary business continu-
narily the integration costs are considerable due
ity we think of having servers and storage ready at
to the range of tasks to be completed, such as the
a backup site, and of synchronization settings such
installation of an operating system in preparation
as replication to a storage mirror. As well as setting
for applications, and creating the virtual environ-
up the environment we also have to implement
ment. With PlateSpin Forge, you simply remove the
backup of the production environment, along with
unit from its box, connect it to the network, assign
complex system settings. In practice there are also
an IP address and password, and select the servers
a number of other requirements before we have a
to be protected. Backup is handled automatically
functioning backup site, such as stationing a tech-
simply by setting the synchronization policies, such
nician on site and scheduling copying of data and
as the schedule and compression level, and clicking
system settings from the production environment
execute. The initial backup will complete within one
to the backup environment. Setting the levels for
to two days, depending on the number of servers
RPO and RTO will depend on the specific organiza-
to be protected, and thereafter the incremental
tion, but it is easy to imagine a significant time and
backup system will proceed automatically. This
effort required to setup each system.
means a considerable reduction in time and effort
needed for setup.
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
54
guide book
Backup target
ser ver
Operating environment
continuity
Typical disaster recovery site setup
continuity
PlateSpin Forge
1. Application setup
2. OS installation
Backup
4. Preparation of server
Remote storage
(critical)
Local storage
(critical)
3. Construction of virtual environment
Backup site
5. Preparation of storage
6. Software replication
Large system integration cost and effort
7. Storage replication
Backup target
ser ver
solution
Simplicity of PlateSpin Forge infrastructure
IT-BCP solutions
Production site
Mount
Synchronous
Operating environment
Using Forge:
Production site
1. Remove from box
Backup site
2. Configure IP address
and password
3. Select servers for protection
Simple disaster recovery site setup
4. Set synchronization timing
PlateSpin Forge GUI
overview
A single PlateSpin Forge unit enables IT-BCP with no
requirement for additional equipment or technical staff
overview
Synchronous
55
chapter
05
Key feature of PlateSpin Forge:
easy-to-use GUI with low overhead
Even more than simplicity of setup and system
to be carried out in a way that ensures switching
building, PlateSpin Forge of fers excellent
works in practice, with no impact on the production
controllability for day-to-day backup operations.
environment. The test outcomes are shown on
The same applies to recovery, all the while ensuring
the GUI, allowing any problems to be eliminated
business continuity.
in advance. Once testing is complete, temporary
settings for the workload used in the test are
Information backup is performed incrementally
discarded, and PlateSpin Forge automatically
in accordance with the synchronization policies
reverts to the pre-test environment.
set at the time of install, so there is no need for
any specific routine maintenance. Any changes,
Should a protected server suffer a breakdown,
including changes to system settings, are part of
rapid recovery is needed. With PlateSpin Forge,
the incremental backup. So if, for example, there is
failover optimized for business continuity can be
an operating system patch for a protected server,
executed with a single button. All that is required is
the patch will be automatically installed to the
selecting the workload for recovery and selecting
server operating system on the workload as part of
the recovery point. While performance will not be
the backup process. Recovery point management
equal to the production environment, PlateSpin
is also implemented, so the required environment
Forge provides a fallback version of the produc-
can be selected and restored in the event of a mis-
tion environment. If just a single workload is to be
take on the protected server.
recovered this can be done in a few minutes, while
simultaneous recovery of multiple workloads can be
One task that should be performed periodically
brought to provisional recovery in up to a few hours.
is a failover test, to determine whether the
56
environment can be correctly restored in the
Once hardware, etc. is prepared for full recov-
event of an emergency. This task simply requires a
ery, a failback operation is required to move from
recovery point to be selected and executed using
the provisional recovery environment to the full
the Test Failover button on the control screen. A
recovery environment. The failback function works
test network is created as a virtual network, so that
by configuring how failback will be executed, for
when the virtual machine is booted for testing
example by selecting which transfer method and
it connects to the test network rather than to a
which volumes are to be used, and then executing
network with external access. This allows testing
failback to the full recovery environment.
guide book
ing replication following recovery ensures that
PlateSpin Forge's failback function can then be set
system protection for business continuity is once
for replication to ensure future protection. Restart-
again maintained.
Backup Tools
Using Forge
• Failure is detected on production
system
• Failure detected on production
system
• Switch networks to standby system
• Select restore point using data
stored in Forge
• Suspend storage replication
• Mount the storage LUN in standby
system
• Start standby system and verify
operation
• Implement failover in Forge, start
up Forge environment and verify
operation
Provisional recovery
• Prepare new ser ver
• Prepare new ser ver
• Prepare new ser ver product
• Exchange HDDs
• Prepare new storage products
• Implement failback in Forge
• Reinstall OS and applications
(including backup tool agents)
• Exchange storage
• Confirm operation
• Implement restoration
• Reinstall OS and applications
(including replication software)
• Test and verify storage replication
overview
• Start backup tool and select
restore point
• Implement reverse replication
• Start applications and verify operation
Full recover y
Several days are needed before
business can start
solution
• Apply OS updates and the latest
patches to the standby system
IT-BCP solutions
• Failure is detected on the
production system
Storage Replication
(non-synchronous)
continuity
The full recovery environment created through
continuity
PlateSpin Forge
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 continuity
PlateSpin Forge GUI
overview
Work can begin after several hours
under provisional recovery
57
chapter
05
Two methods for initial
workload replication
Installing PlateSpin Forge initially requires the
If, however, the volume of data for backup is small
entire workload of the target server that is to be
or the servers to be protected are distributed nation-
protected to be copied, including operating system
wide, it would be problematic to host a PlateSpin
and other system settings and data. This process is
Forge unit at each site. Therefore, the second option
called replication. There are two main methods of
would be to install it at the backup site and perform
performing the initial full replication upon install.
the initial full replication over the network.
If the server to be protected holds a large quantity
Although this method requires more time to com-
of data or there is no broadband network to the
plete than full replication using the first option, the
backup site, the first option would be to copy all
targets to be protected can be assigned from the
data and system settings within the local environ-
backup site, and the IT-BCP environment can be
ment. PlateSpin Forge is installed within the same
achieved by scheduling replication of workloads in
LAN segment as the server to be protected, and the
sequence. Detailed settings are available including
entire workload is copied over. If there are multiple
network bandwidth, compression level and band-
servers, workloads from multiple units can be cop-
width limits, so replication can be managed with-
ied simultaneously, up to the limit supported by
out significant impact on existing networks. Once
the network bandwidth, and PlateSpin Forge will
the initial full replication is complete, a continuous
integrate these as a single backup environment.
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
guide book
continuity
PlateSpin Forge
continuity
Copy the production environment
locally and transport it, for example
by truck, to a backup site where it
can be installed
Backup site
IT-BCP solutions
Production site
solution
Production site
Production site
Production site
PlateSpin Forge GUI
overview
Production site
overview
Install at backup site and copy the production
environment across the network
59
chapter
05
Routine operations example 1
Here we will look at a specific example of
After the migration of the production environ-
adopting PlateSpin Forge. Let us say the intention
ment to a private cloud, PlateSpin Forge is config-
is to migrate around 20 physical servers with
ured to protect the workloads that are now running
integrated backup to tape to a private cloud as an
in the private cloud. Once the initial replication is
IT-BCP solution.
performed, PlateSpin Forge is installed at a remote
backup site, and functions as an IT-BCP solution
Firstly, the workloads of the 20 physical servers
providing remote backup for the production envi-
should be consolidated onto a single PlateSpin
ronment in the cloud.
Forge unit using its virtual environment, so all workloads are copied using a P2V migration process. At
PlateSpin Forge enables a simple migration
this stage, the production environment is usable
to a private cloud, as well as making a valuable
and IT-BCP enabled, and can be rapidly recovered
contribution to IT-BCP in the private cloud
to the provisional recovery state on PlateSpin Forge
environment. Configuring replication settings in
in the event of any problems with the physical
advance means that the environment is capable
servers. At the same time, the private cloud envi-
of rapidly switching to provisional recovery mode
ronment can be built for future use as the produc-
for business continuity even when the party
tion environment. In this case, we assume that the
responsible is not present.
environment will run 20 workload units as virtual
machines on a single physical server.
As a result, not only does PlateSpin Forge provide
a level of business continuity infrastructure that
Once the workloads of the 20 existing environ-
was unavailable in the past, it also succeeds
ments are copied to PlateSpin Forge, the PlateSpin
in reducing the hardware cost and complex
Forge unit is moved and installed at the site where
operational burden associated with 20 physical
the private cloud environment is to be built. A
servers. In case of an emergency, PlateSpin Forge
V2V migration process enables migration from
provides valuable functionality as a provisional
the PlateSpin Forge environment into the private
recovery infrastructure.
cloud environment.
60
guide book
Problem:
1. A business continuity 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.
Before
12 physical servers
Phase 1:
Backup existing physical production
environment to Forge.
Phase 1′:
Backup vir tual environment
to Forge.
After
Phase 3:
The newly constructed vir tual
environment is synchronized and
backed up to Forge, providing a disaster
recover y solution when sited remotely.
One virtual server (12 instances)
Vir tual environment is
backed up on Forge.
overview
Phase 2:
Vir tual environment on Forge
is migrated as a whole to
become a vir tual environment
on the new ser ver.
solution
Tape
Two virtual servers (8 instances)
IT-BCP solutions
PlateSpin Forge solves this problem
continuity
PlateSpin Forge: Case Study 1
continuity
PlateSpin Forge
Two virtual servers (8 instances)
PlateSpin Forge GUI
overview
61
chapter
05
Routine operations example 2
Next, we will discuss how PlateSpin Forge can
no longer any requirement to perform tape back-
help at sites that will unavoidably continue to use
ups at each site. Unlike with simple replication,
multiple backup tools, by breaking down each sys-
this system provides recovery point management,
tem into silos.
allowing the system to be reverted precisely to
any recovery point. Backup operations are also
Organizations with different systems at each site
integrated, reducing on-site operational load, and
or plant may find it difficult to establish respective
allowing human resources to be diverted to other
backup environments. This is because in many
operations.
cases backup is left to the technician onsite, meaning that backup software and tape media may
This P2V process provides full integration of
differ for each system, and that rationalization of
cross-site backup environments, and enables
usage methods and backup policies may not occur.
organizations to switch away from tape backup
With a wide distribution of operations and environ-
environments that can require several days
ments, it can be difficult to assign priorities to sys-
for recovery. PlateSpin Forge delivers dramatic
tems, making rapid recovery for business continuity
improvements in RPO and RTO compared to such
in the event of an emergency an unlikely prospect.
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
guide book
1. Each site has its own backup system. Different plants have different systems and
information capture cannot be implemented using information systems.
Problem:
continuity
PlateSpin Forge: Case Study 2
continuity
PlateSpin Forge
2. Backup policies are disparate.
3. Only operational staff members understand the systems, confounding system handover.
4. The system is not periodically backed up.
Before
IT-BCP solutions
PlateSpin Forge solves this problem
Site A backup tool
solution
Site B backup tool
Site C backup tool
Site D backup tool
overview
After
PlateSpin Forge GUI
overview
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.
63
chapter
05
Routine operations example 3 – system
recovery training
Here we will discuss the failover test process,
ing the backup workload to be verified. Indeed, the
which is easy to be carried out routinely when
process simply involves selecting the workload to
using PlateSpin Forge.
be verified and clicking on the failover test button.
This makes shorter-term TTOs achievable.
The failover process to be performed at the
backup site in the event of an emergency should be
A traditional failover test often requires personnel
routinely tested. Despite this, many organizations
to be stationed at the backup site, and must be
omit such verification in their routine operations
performed on a non-working day in order to avoid
in an attempt to avoid impact on the production
impacting the existing environment. In some cases,
environment. For proper implementation, however,
the test can only be performed with the production
failover capability should be checked on a monthly
environment temporarily offline, to simulate an
basis, at the minimum.
incident, making the impact of the failover testing
considerable. With PlateSpin Forge, however, the
This factor is quantified using the TTO (Test Time
test can be performed with no impact on the pro-
Objective) metric, which asks how easy it is to
duction environment whatsoever.
test the system as part of day-to-day training for
business continuity. Often several days have to be
PlateSpin Forge provides its own test environment
devoted to verifying the system, so that you know
on a custom internal network, which can be used
whether your IT-BCP solution will function correctly
to perform a wide range of verification tasks such
when it comes to the crunch. Daily verification
as pre-verification of security patches or application
can even be essential to ensure rapid and reliable
upgrades. Moreover, PlateSpin Forge is designed to
IT-BCP countermeasures.
automatically revert to the original synchronized
environment once testing is complete, by undo-
PlateSpin Forge was designed from the outset to
ing the configuration changes used for testing.
allow failover testing to be performed simply, and
This means peace of mind, no matter how many
without interrupting operations. It is capable of
changes or deletions you make to the system or
running a test environment internally that has no
data in the test environment.
impact on the production environment, enabling
failover testing to be performed simply by select-
64
guide book
Test environment
Standby ser ver
IT-BCP solutions
Test environment
setup in Forge
continuity
PlateSpin Forge
continuity
PlateSpin Forge
solution
overview
PlateSpin Forge GUI
overview
65
chapter
05
Failover
Now let us look at how PlateSpin Forge can be
involves selecting the workload to place in failover
used in the event of an actual emergency to pro-
mode from the PlateSpin Forge dashboard, and
vide a failover service.
pressing the execute button next to the desired
recovery point. Doing so boots up the backup
Under normal operation, users access specific
workload within PlateSpin Forge, and recovers the
servers and make use of business applications. For
server state from the selected recovery point.
servers subject to the backup process, these applications are running within workloads, and PlateSpin
If settings for switching the IP address of the
Forge draws down data on a day-to-day or hour-to-
booted workload and the IP address of the offline
hour basis for incremental backup of workloads in
server have been configured in the Active Direc-
accordance with a predefined schedule.
tory or DNS server in advance, users will be able to
access the server as soon as PlateSpin Forge has
Let us assume that a server breakdown occurs.
booted the workload, providing a temporary provi-
Straight away the server connection enabling users
sional recovery state.
to access the server is cut, as is the connection to
PlateSpin Forge. The server has lost its online status
However, as this failover state operates on a
and further backup is no longer possible. Users who
workload within PlateSpin Forge, performance will
have lost access will be aware that some issue has
not be at the same level as the production environ-
arisen on the server or network, but before they
ment. Users should be aware that this state offers a
are able to deliver this message to their manager,
fallback level of service.
PlateSpin Forge will promptly detect the breakdown and deliver an email to the email address of
the relevant manager.
The manager, having received the email, can then
access PlateSpin Forge from a device such as a
smartphone or notebook, and initiate the recovery
process for business continuity. Specifically, this
66
guide book
Normal operation
Production
PlateSpin Forge
continuity
�
continuity
PlateSpin Forge
Users
In event of breakdown
Offline
PlateSpin Forge
Forge sends breakdown alert
or cellphone/tabletnotice,
instruction to switch over is
provided using cellphone/tablet
�
Forge's internal standby
server boots and continues
operations
PlateSpin Forge
PlateSpin Forge Dashboard
overview
�
solution
Users
IT-BCP solutions
�
Offline
PlateSpin Forge
PlateSpin Forge GUI
overview
Users
67
chapter
05
Failback
While PlateSpin Forge can be used to provide a
Once the new full recovery environment has been
failover service, the environment offers only a cer-
deployed, manual adjustments can be made to
tain fallback performance level, and does not reach
make it a virtualized platform, if so desired. Next,
the stage of complete recovery. Therefore, let us
the failback target is selected, and settings similar
now look at the failback process for moving work-
to the initial replication are configured for failback,
loads back to a full recovery environment, once the
such as compression level and transfer method.
original infrastructure has been repaired or rebuilt.
When failback is executed on the configured system, failback is performed to provide a system
While business continues in a provisional
and data environment with a 100% recovery level,
recovery state under PlateSpin Forge, the system
achieving full recovery.
manager will have the damaged server repaired
or, if it cannot be repaired, will arrange for it to
Once full recovery has been achieved, PlateSpin
be replaced. At this replacement stage, it may be
Forge replication can be once again set to execute,
unavoidable that the same hardware as was used
to provide an IT-BCP solution for the now recovered
in the previous model cannot be ensured. It may
environment. This is possible because PlateSpin
also be the case that the business environment has
Forge is a dual functionality appliance, providing a
altered and a different virtualized platform is now
running environment for provisional recovery, as
sought for full recovery.
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
guide book
Forge synchronizes with
original server
PlateSpin Forge
Original Server
continuity
�
continuity
PlateSpin Forge
Users
Switch back to original server
occurs once synchronization
is complete
PlateSpin Forge
Original Server
IT-BCP solutions
�
solution
Users
PlateSpin Forge
Original Server
overview
New Server
No need to worry about original server spec!
vendors and using different hyper visors. The drivers in Forge / Protect are
installed automatically to enable data migration.
PlateSpin Forge GUI
overview
- Data can be migrated between different machine specs NetIQ's conversion technology allows recover y to machines from different
69
chapter
06
70
PlateSpin Forge GUI overview
continuity
continuity
IT-BCP solutions
Addition of a workload……………………………………………………………… 72
Initial configuration, including scheduling…………………………………………… 74
Configuration for failover and failover testing……………………………………… 76
Failback procedure under PlateSpin Forge…………………………………………… 80
solution
Failover procedure under PlateSpin Forge…………………………………………… 78
overview
PlateSpin Forge GUI
overview
71
chapter
06
Addition of workload
A key feature of PlateSpin Forge is its easy to use WebUI. It provides a data protection and business continuity
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
guide book
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”.
continuity
02
continuity
PlateSpin Forge
IT-BCP solutions
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”.
overview
PlateSpin Forge GUI
overview
73
chapter
06
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
02
74
Firstly, full replication must be selected on the options screen for the initial replication method.
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.
guide book
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.
continuity
03
continuity
PlateSpin Forge
IT-BCP solutions
solution
overview
PlateSpin Forge GUI
overview
75
chapter
06
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
05
76
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.
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.
guide book
Next, the workload to be replicated should be selected followed by a click on the "Run Replication"
button.
continuity
06
continuity
PlateSpin Forge
IT-BCP solutions
07
solution
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.
overview
PlateSpin Forge GUI
overview
77
chapter
06
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
02
78
As soon as a problem arises with a protected server, simply click the workload to be restored and
press the “Run Failover” button.
If recovery point management is enabled, simply select which recovery point to be used for failover
and press “Execute”.
guide book
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.
continuity
03
continuity
PlateSpin Forge
IT-BCP solutions
Once the status shows as "Completed", the failover process is completed. The workload status will
show as “Live”.
solution
04
overview
PlateSpin Forge GUI
overview
79
chapter
06
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
02
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.
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
guide book
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.
continuity
03
continuity
PlateSpin Forge
IT-BCP solutions
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”.
solution
04
overview
PlateSpin Forge GUI
overview
81
and Management with
PlateSpin Forge
April 2015
Issued by: NetIQ
•About PlateSpin Forge
Product URL: https://www.netiq.com/products/forge/
•About other PlateSpin products
PlateSpin Recon
Product URL: https://www.netiq.com/products/recon/
PlateSpin Migrate
Product URL: https://www.netiq.com/products/migrate/
PlateSpin Protect
Product URL: https://www.netiq.com/products/protect/
Copyright 2015 NetIQ
Authors: Toshiki Iida and Ichiro Kai

IT Business Continuity Planning and Management with

Transcription

Similar documents

University of Valley forge Campus – Krempels theater 1401

ClarksBeach.com 315.369.3026

scanticon hotel and conference center

Manage - Avnet Technology Solutions

(C) Engine - Automotriz En Video

The Bookmark - Old Forge Library

Giggles and Good Times Pigeon Forge, Tennessee

Children`s Activity Guide - Valley Forge Park Alliance

NOTICE OF BID The City of Pigeon Forge Department of Tourism is

Valley Forge, PA - Military Locator and Reunion Service