Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

Server+ > Disaster Recovery Planning > Flashcards

Disaster Recovery Planning Flashcards

(60 cards)

Start Studying
1
Q

RTO

A
  • recovery time objective
  • maximum amount of time an IT service can be down before it has a negative impact on business
  • ensure all parties know their roles in disaster recovery plan
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

BIA

A
  • business impact analysis

- RTO is important component

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

alternate sites

A
  • enable business to continue when disruption occurs at primary site
  • require high-speed communication links between sites
  • IT infrastructure must be in place
  • data replication between sites must be configured
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

failing over IT services to alternate site

A
  • DHCP/DNS
  • hosted web site
  • VMs
  • line of business applications
  • ensure notifications are sent to stakeholders
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

ensure network address changes don’t affect IT service consumers

A

dynamic DNS updates for changed IP addresses

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

failover clustering

A
  • provides high availability
  • multiple servers (cluster nodes) use same shared storage/configured identically
  • redundancy
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

MRU

A
  • most recently used
  • MRU path normally used when cluster node connects to shared storage
  • server will attempt other paths if current path fails
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

active/active clustered services

A
  • clustered service is running simultaneously on multiple cluster nodes
  • zero downtime
  • live failover
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

active/passive clustered services

A
  • service fails over/starts up on another cluster node if node where service is running fails
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

rolling cluster updates

A
  • staggered process of applying cluster node updates

- ensure some cluster nodes are always running

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

periodic heartbeat transmission

A
  • used by clustering solutions
  • sent from each node to ensure nodes haven’t failed
  • use dedicated network adapter for cluster heartbeats
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

hot site

A
  • alternate location that can actively continue business operations
  • disaster recovery (DR) sites commonly used as hot sites by cloud providers
  • continuous data protection (CDP) replication between sites
  • most expensive to maintain
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

cold site

A
  • alternate location with power/communication links in place
  • don’t have IT equipment/software/data/staff
  • software incompatibility
  • must restore data from backups
  • must fit within RTO/business continuity plan (BCP)
  • least expensive
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

warm site

A
  • alternate location with power/communication links
  • some equipment in place
  • bare-metal server restoration
  • application patching
  • data restoration
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

bare-metal server restoration

A
  • performs full system recovery
  • including OS
  • can be configured even when hardware configuration is different from the software configured when system backup/image was taken
  • external bootable drives/PXE
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

data replication

A

can immediately provide data without requiring restoration procedure

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

synchronous data replication

A

writes to primary/alternate location simultaneously

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

asynchronous data replication

A

slight delay before alternate write completes

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

disk-to-disk data replication

A
  • RAID 1 (disk mirroring) storage
  • second copy of data is written to disk other than primary disk
  • automatically fails over to redundant disk
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Linux tar command

A

create compressed archives for backup purposes

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

tar -c

A

create archive

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

tar -v

A

display verbose output

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

tar -z

A

compress archive with gzip

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

tar -f

A

specify path/filename of archive file

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
tar -x
extract specified archive
26
tar -C (uppercase)
change to directory for extraction of archive
27
Linux dd command
back up specific disk blocks/entire partitions
28
server-to-server data replication
- host-to-host replication - uses software in server OS to replicate data between 2 or more servers - consumes server processing workload
29
Windows DFSR
- distributed file system replication - Windows server role service - synchronize folder contents between servers - only file block changes are synchronized - changes compressed before being sent over network - replication can be scheduled - servers can be configured for continuous replication - can be configured with bandwidth throttling to preserve network resources - asynchronous replication - configured 1 or more servers in replication group as read-only to prevent changes from that host
30
rsync
- tool to replicate data between hosts in UNIX/Linux - variants work on Windows - synchronized 2 or more local folders over network - only file changes are synchronized
31
site-to-site data replication
- primary/hot site - between cloud provider datacenters - network links must be able to accommodate large data transfers quickly
32
active/active copies of data
data copies from synchronous replication solution
33
who/what affected (BIA)
- personal safety - critical data - network hardware/software - critical database servers - front-end applications
34
RTO (BIA)
significant factor when determining what type of failures can be tolerated/how long
35
disaster recovery (DR) plan
- prepares organization for potential negative incidents that can affect IT systems - simulations - includes step-by-step procedures to recover failed systems - proper role documentation
36
DR plan contents
- table of contents - scope of DR document - contact information for escalation/outsourcing - recovery procedures - document revision history - glossary
37
MTTR
- mean time to repair - on average how long it takes to restore failed components - helps in planning equipment life cycle/restore failed equipment
38
MTBR
- mean time between failures - manufacturer provided - estimate on how much time before failure - usually associated with hardware
39
BCP
- business continuity plan - ensures business operations can continue/resume quickly during/after a failure - should include preventative measures - continuity of operations (COOP)
40
creating/using BCP
- assemble BCP team - identify/prioritize critical systems/data - determine if required skills available internally/outsourced - determine if alternate sites will be used - create DR plan for each IT service - review BCP with BCP team - run periodic drills
41
selective backups
- enable only restoring files that are required | - instead of overwriting all files/restoring to an alternate path from original backup location
42
SQL server log shipping
- uses primary/secondary SQL server - primary SQL supports read/write access - secondary SQL updated via transaction log updates from primary - side-by-side backup
43
archive bit
- used in file systems to indicate that a file has been changed/needs to be backed up - used by most backup solutions - cleared by full backup - turned on by OS when new file is created
44
full backup
- copies all data specified in backup set - take longer to complete/restore - commonly only performed periodically - clears archive bit when performed
45
differential backup
- copies only files that have changed since the last full backup (not since last differential backup) - more time to restore than full backups (full restore + restore of differential) - archive bit is not normally cleared
46
incremental backup
- copies only files that have changed since the last incremental/full backup - normally clears archive bit - least amount of time to take - most amount of time to restore
47
synthetic full backups
- take incremental backup | - combine with older full backup in same location
48
snapshots
- VMs - capture settings/data in vdisk files - should not be relied upon as sole backup (don't replace backups) - can also apply to disk volumes/storage arrays/LUNs/hypervisors/databases
49
storage snapshots
snapshots used in SAN environments
50
Windows VSS
- volume shadow service - configured for each disk volume - enable scheduled snapshots (volume shadow copies) - only contain changed disk blocks (don't consume much space)
51
bare-metal backup
- data included in recovery image - can be used to deploy new servers quickly - use snapshots (recovery points) - require boot device
52
linear access tape
- linear tape-open (LTO) - magnetic storage media that uses linear tape file system (LTFS) - large capacities - fast data seeks - streaming - commonly used with tape backup systems/archiving - XML file used as catalog of backed-up content
53
AIT
- advanced intelligent tape - magnetic tape storage used with tape backup/archiving systems - each data cartridge contains a chip with metadata
54
DLT
- digital linear tape - industry standard - used for long-term archiving - should be placed in protective cases - superDLT (SDLT) supports larger capacities/transfer rates - can use SDLT in DLT systems with only read access
55
tape library
management solution for multiple tape devices/backup media used for backups
56
cloud backup security
- connect network to cloud provider with site-to-site VPN - connect network to cloud provider with private network connection - encrypt data before backing up to cloud (if server side encryption isn't provided)
57
GFS tape rotation strategy
- grandfather-father-son - most common - uses 3 backup sets (i.e. daily/weekly/monthly) - each tape rotated on a schedule
58
GFS example
- son = daily backup - father = weekly backup - grandfather = monthly backup - day 7 = son tape becomes a father/used for next weekly backups - other daily tapes keep getting reused as cycle continues - week 4 = father becomes grandfather/used for next monthly backups - monthly backups can be stored offsite
59
backup best practices
- clear/concise backup media labeling - data retention policy - integrity verification - backup media offsite storage - backup media encryption - backup media environmental controls - periodic data restoration tests
60
RAID variant that can tolerate 2 disk failures
RAID 6

Server+ (7 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions