CHAP 8.1 Business Continuity Flashcards

1
Q

what is business continuity

A

set of related activities targeted to ensure:
- critical business functions will continue to operate despite major disruption
- ability to recover operation within short period of time after major incidents
objective is to MINIMIZE OUTAGE TIME

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

impacts of downtime

A
  • loss of revenue
  • damaged reputation
  • loss of productivity
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

key elements of business continuity

A
  • resilience
  • recovery
  • contingency
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

high availability

A
  • no downtime

- alw avail 24/7

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

loss of availability

A

outage/downtime
types:
- planned (eg maintenance)
- unplanned (eg offline, slow response)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

common threats to availability

A
  • disease
  • earthquake
  • fire
  • cyber attack
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

high availability requirements

A
  • no. of users affected
  • no. of external customers affected
  • available budget
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

HA technologies

A
  • fault-tolerant & redundancy: use fault-tolerant components to improve redundancy
  • network load balancing: distributes application requests among multiple nodes
  • failover clustering: migrates services from one server to another when the server fails
  • VM migration: moves a VM to a new host wo shutting it down
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

fault-tolerant components

A

fault-tolerant components IMPROVE REDUNDANCY
eg:
- SAN STORAGE w duplicate power supply unit, nwk cabling
- disk configured w RAID support hot-swap

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

RAID 0

A
  • striped set
  • data written across ALL disks in 64kb units (striped)
  • provides performance but not fault-tolerant
  • storage efficiency: 100%
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

RAID 1

A
  • disk mirroring
  • simultaneously writes data to two volumes on two physical disks
  • almost any volume can be mirrored, incl the system and boot volumes
  • storage efficiency: 50%
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

RAID 3

A
  • striped set w dedicated parity disks
  • parity data used to recover missing data if one disk is down
  • parity data is written on a dedicated disk
  • requires MINIMUM 3 DISKS
  • storage efficiency: (n-1)*100/n (n=no. of disks)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

RAID 5

A
  • striped set w distributed parity
  • requires MINIMUM 3 DISKS
  • storage efficiency: (n-1)*100/n (n=no. of disks)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

RAID 6

A
  • striped set w dual distributed parity
  • use parity to recover missing data from UP TO 2 FAILED DISKS
  • require MINIMUM 4 DISKS
  • storage efficiency: (n-2)*100/n (n=no. of disks)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

RAID 1+0

A
  • nested RAID
  • data is mirrored then striped
  • require MINIMUM 4 DISKS
  • storage efficiency= 50%
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

network load balancing

A
  • scalable HA technology
  • balances traffic based on node utilization
  • provides scalability as more servers can be added
  • provides availability when:
    - server failure is detected
    by other servers in the cluster
    - failed server load will be automatically distributed among other servers in the cluster
17
Q

requirements to implement NLB

A

all nodes must:

  • have the same configuration
  • data can be stored in a central location
  • data can be synchronized between servers
18
Q

failover clustering

A
  • provides fault-tolerance by ensuring availability of critical services
  • computers (nodes) are setup as a cluster
  • requires private nwk which is shared by the cluster nodes and is used to monitor each node’s status and communicate w each other
  • clustered services and resources are moved from one node to another when a node becomes inactive or fails
  • cluster service can fallback after the offline node becomes active again
  • usually implemented as part of a load balancing process
19
Q

when to use failover clustering?

A
  • when HA is required
  • scalability is not required
  • application uses IP-based protocols
  • client or protocol can automatically reconnect to the application
20
Q

hyper-v replica

A
  • allows for host-based replication of VMs wo the need for any shared cluster components
  • uses AD or certificate based authentication for security
  • once VM has been replicated, it can be powered off and powered on to carry out planned or unplanned failover
21
Q

live migration

A
  • moves running VMs from one physical server to another w no impact on availability for users
  • pre-copies the memory of the migrating VM to the destination server
  • no special configuration needed for the guest OS
  • provides HA
22
Q

DHCP service HA

A
  • dhcp servers share dhcp scope and lease info to ensure continuous availability
  • configured using dhcp failover
23
Q

DHCP service HA failover modes

A

hot standby mode:
- secondary server will take over when primary server is unavailable

load balance mode:

  • both servers dhcp clients
  • requests are load balanced between servers
24
Q

cold backup site

A
  • provides office space only
  • takes longer to get into full operation
  • least expensive
25
Q

hot site

A
  • fully staffed and includes all equipment, software and communications facility
  • can take over operations quickly
  • most expensive
26
Q

warm site

A
  • site may be installed w most of the equipment and facility preconfigured for operation
  • needs time to recover and start operation