Data Continuity & Support

Understanding Data Continuity, Fault Tolerance, Redundancy, RAID, Power Protection, and Data Backups

Understanding Data Continuity

What Is Data Continuity?

Data continuity refers to the ability to keep data and systems available, reliable, and recoverable when problems occur.

Organizations depend heavily on computer systems for:

A failure involving hardware, software, or data can interrupt operations and cause significant losses.

Data continuity planning answers questions such as:

Two Major Concepts of Data Continuity

Data continuity is divided into two major areas:

  1. Fault tolerance
  2. Disaster recovery
Fault Tolerance

Fault tolerance is the ability of a system to continue operating even when a component or piece of data fails.

The goal is to prevent a single failure from causing a complete system outage.

Examples:

Fault tolerance reduces downtime and improves reliability.

Importance of Fault Tolerance

The amount of fault tolerance required depends on how important the system or data is.

For example:

Low Importance Data

A personal computer containing noncritical files may not require advanced protection.

A user may tolerate:

Critical Business Data

A business database or server may require:

Organizations must balance:

Redundancy

Redundancy means having duplicate components or systems available in case the primary component fails.

Redundancy improves reliability by eliminating single points of failure.

Examples include:

Types of Redundancy

Hardware Redundancy

Uses duplicate hardware components.

Examples:

If one component fails, another can continue operating.

Network Redundancy

Provides alternate communication paths.

Examples:

Network redundancy helps prevent communication failures.

Power Redundancy

Protects systems from electrical problems.

Examples:

Power redundancy prevents unexpected shutdowns.

Replication

Replication creates copies of data or systems.

Examples:

Benefits include:

Replication is commonly used in enterprise environments where downtime is unacceptable.

RAID (Redundant Array of Independent Disks)

RAID combines multiple storage drives to improve:

RAID is commonly used in servers and storage systems.

RAID protects against certain disk failures, but it does not replace backups.

RAID 1 – Mirroring

RAID 1 creates an exact copy of data on another drive.

Example:

Drive 1:

A B C D

Drive 2:

A B C D

If one drive fails, the other contains a complete copy.

Advantages:

Disadvantages:

RAID 5 – Striping With Parity

RAID 5 distributes data across multiple drives while storing parity information.

Parity allows data recovery if one drive fails.

Advantages:

Disadvantages:

RAID Limitations

RAID is not a complete backup solution.

RAID protects against:

RAID does not protect against:

Organizations should still maintain backups.

Power Protection

Computers require reliable electrical power.

Power problems can cause:

Power protection helps maintain system availability.

Common Power Problems

Power Outage

A complete loss of electrical power.

Effects:

Power Surge

A sudden increase in voltage.

Causes:

Can damage components.

Power Sag

A temporary decrease in voltage.

May cause:

Uninterruptible Power Supply (UPS)

A UPS (Uninterruptible Power Supply) provides temporary battery power when electrical power fails.

A UPS protects against:

UPS Benefits

A UPS can:

Many UPS devices can communicate with operating systems and automatically shut down computers safely.

UPS Maintenance

UPS batteries wear out over time.

Best practices:

Overloading a UPS can cause failures and may create safety risks.

Data Backups

Importance of Backups

A backup is a restorable copy of data.

Backups protect against:

Hardware can usually be replaced, but lost data may be impossible to recover.

Backup vs Archive

Although the terms are sometimes used incorrectly:

Backup

A copy of data used for restoration after loss.

Purpose:

Archive

A collection of data removed from regular use because it is no longer actively needed.

Purpose:

How Backups Work

Backup software commonly uses the archive bit.

The archive bit indicates whether a file has changed since the last backup.

Archive Bit Process

When a file is:

The archive bit is set.

This indicates:

The file needs to be backed up.

After backup:

This helps backup software identify changed files.

Backup Types

File Backup

A file backup copies selected user files.

Examples:

Advantages:

System Backup

A system backup copies:

Benefits:

Backup Storage Locations

Backups can be stored in several locations.

Local Storage

Examples:

Advantages:

Disadvantages:

Network Storage

Examples:

Advantages:

Cloud Storage

Examples:

Advantages:

Backup Scheduling

Backup frequency depends on:

Important data should be backed up more frequently.

Examples:

Backup Verification

A backup is not complete until it has been tested.

Organizations should:

A backup that cannot be restored is not useful.

Offsite Backups

Backups should not always remain in the same location as the original system.

Example:

If a server and backup drive are stored in the same building:

Offsite backups provide protection against major disasters.

Backup Best Practices

Key Terms

Exam Tips

Data Backups, Backup Types, Backup Locations, Scheduling, Verification, and Disaster Recovery

Data Backups

A backup is a restorable copy of data that is created so information can be recovered if the original data is lost, damaged, deleted, or corrupted.

Backups are one of the most important parts of data continuity because while hardware can usually be replaced, lost data is often impossible or very expensive to recover.

Why Are Backups Important?

Data is often the most valuable asset in a computer system.

Examples of important data include:

If these files are lost, they may never be recovered.

Hardware failures, malware, accidental deletion, ransomware, theft, or natural disasters can all result in permanent data loss if backups are not available.

Important Principle

Hardware can be replaced. Data often cannot.

For example:

RAID Is NOT a Backup

Many people mistakenly believe RAID eliminates the need for backups.

It does not.

RAID protects against hard drive failure, but it cannot protect against:

Therefore, backups are always necessary, even if RAID is used.

Creating a Backup Plan

Before choosing a backup method, several questions should be answered.

1. How often should backups be made?

This depends on how frequently the data changes.

Examples:

2. What should be backed up?

There are two major options:

File Backup

Backs up selected files or folders.

Examples:

System Backup

Backs up the entire computer system.

Includes:

3. How much data needs backing up?

Large files require:

Examples:

These may need different backup schedules than ordinary documents.

4. Which backup software will be used?

Possible choices include:

5. Should every backup copy everything?

Some backups copy:

Others copy only:

This decision greatly affects:

Importance of Data

The textbook gives an example of a doctoral student whose hard drive failed.

Unfortunately:

This story illustrates an important lesson:

Backups cost far less than professional data recovery.

How Backups Work

Most backup software uses the archive bit.

Archive Bit

The archive bit is a file attribute that indicates whether a file has been backed up.

Archive Bit = 1

Means:

Archive Bit = 0

Means:

Some backup types clear the archive bit after copying files, while others leave it unchanged.

Checking the Archive Bit

There are two common methods.

Method 1

Using Windows File Explorer

  1. Right-click the file.
  2. Select Properties.
  3. Click Advanced.
  4. Check whether File is ready for archiving is selected.

Method 2

Using Command Prompt

Use:

attrib

If the letter A appears beside the filename, the archive bit is set.

The attrib command can also be used to change archive attributes.

Backup Programs

Backup software may include features such as:

Examples include:

Five Types of File Backups

1. Normal (Full) Backup

Copies all selected files.

After copying:

Advantages

Disadvantages

2. Copy Backup

Copies selected files.

Does NOT clear the archive bit.

Advantages

Disadvantages

3. Incremental Backup

Copies only files that changed since the previous backup.

After copying:

Advantages

Disadvantages

Restoration is slower because:

You need:

Missing even one incremental backup can prevent full recovery.

4. Differential Backup

Copies files changed since the last Full Backup.

Archive bit is NOT cleared.

Advantages

Disadvantages

Backup size grows larger each day until another Full Backup is performed.

5. Daily Backup

Backs up files modified on the current day.

Does not use the archive bit.

Instead, it checks the file modification date.

Backup Type Comparison
Backup TypeCopiesClears Archive BitBackup SpeedRestore Speed
Full (Normal)All filesYesSlowestFastest
CopySelected filesNoMediumMedium
IncrementalChanged since last backupYesFastestSlowest
DifferentialChanged since last Full backupNoMediumFaster than Incremental
DailyToday’s modified filesNoFastMedium
System Image

A system image is an exact copy (snapshot) of an entire hard drive.

It includes:

Advantages

Disadvantages

Because of these limitations, system images are generally used less frequently than regular file backups.

Backup Locations

A backup should never be stored on the same drive as the original data.

If that drive fails, both the original and the backup are lost.

1. Local Storage

Examples:

Advantages

Disadvantages

2. Network Attached Storage (NAS)

A dedicated storage device connected to a network.

Advantages:

3. Cloud Storage

Examples include online backup services.

Advantages:

Disadvantages:

Local vs Cloud Backup
Local BackupCloud Backup
FastDepends on internet speed
No internet requiredInternet required
User manages storageProvider manages storage
Vulnerable to local disastersProtected from local disasters
One-time hardware costUsually recurring subscription
Off-Site Storage

Organizations should store at least some backups off-site.

Reasons include protection from:

Off-site storage ensures backups survive even if the primary location is destroyed.

Backup Frequency and Scheduling

Backups should occur regularly.

Factors affecting backup frequency include:

General rule:

The more valuable and frequently changing the data, the more often it should be backed up.

Scheduling Backups

Modern operating systems allow backups to run automatically.

Possible schedules include:

Automatic scheduling reduces the chance that users forget to perform backups.

Verifying and Testing Backups

Creating a backup does not guarantee it works.

Backups should always be tested.

Why Verification Is Important

A company once discovered after a server crash that their backup tape was unreadable.

Result:

The lesson:

Always verify backups before relying on them.

Methods of Testing

Possible verification methods include:

Best Practices for Local Backups

Rotate Backup Media

Instead of always using one flash drive:

Rotate between:

If one backup becomes corrupted, others remain available.

Store Backups Off-Site

Never keep every backup beside the computer being protected.

If the building is destroyed, both computer and backup may be lost.

Disaster Recovery

Disaster recovery is the process of restoring computer systems and data after a major failure.

Its purpose is to return operations to normal as quickly as possible.

Disaster Recovery Priorities

Recovery should occur in order of importance.

Typical sequence:

  1. Ensure the disaster has ended (e.g., fire is extinguished or cyberattack is contained).
  2. Repair or replace damaged hardware.
  3. Restore critical servers and network infrastructure.
  4. Restore operating systems.
  5. Restore backed-up data.
  6. Verify systems are functioning normally.
Restoring Files

Windows Backup allows users to:

This flexibility helps recover only the data that is needed instead of restoring the entire system.

Key Terms

Computer Support Concepts & The CompTIA Troubleshooting Methodology

Exploring Computer Support Concepts

Computer support (also called technical support or IT support) involves diagnosing, troubleshooting, and resolving computer-related problems. While users may not notice the design of a network or security system when everything works, they quickly rely on IT support when something fails. Therefore, effective troubleshooting is one of the most valuable skills an IT professional can have.

The Importance of a Structured Troubleshooting Process

Troubleshooting should never be random. Instead, technicians should follow a systematic process that identifies the root cause before attempting repairs.

A structured approach helps:

Even experienced technicians benefit from following a troubleshooting methodology because it prevents overlooking simple causes.

General Troubleshooting Principles

Before beginning any repair, remember these important guidelines:

1. Back Up Data First

Whenever possible, create a backup before making changes to a system. Hardware can usually be replaced, but important user data may be irreplaceable.

2. Establish Priorities

Not every problem has the same level of urgency.

For example:

Technicians should prioritize problems based on business impact.

3. Document Everything

Keep records of:

Good documentation improves future troubleshooting and helps other technicians resolve similar issues.

The Six-Step CompTIA Troubleshooting Methodology

CompTIA recommends the following six-step troubleshooting process:

StepDescription
1Identify the problem
2Establish a theory of probable cause (question the obvious)
3Test the theory to determine the cause
4Establish a plan of action and implement the solution
5Verify full system functionality and implement preventive measures if necessary
6Document findings, actions, and outcomes

These steps should be followed in order whenever possible.

Step 1 – Identify the Problem

Why This Step Is Important

A technician cannot solve a problem without first understanding exactly what the problem is.

Sometimes the issue reported by the user is actually a symptom rather than the real problem.

Example:

A user reports:

“I can’t access the Internet.”

Possible causes include:

The reported symptom alone does not reveal the root cause.

Four Major Sources of Computer Problems

Problems generally fall into one or more of these categories:

1. Hardware

Examples:

2. Operating System

Examples:

3. Software/Application

Examples:

4. User

Sometimes the computer works correctly, but the user:

Technicians should consider the user as part of the troubleshooting process, but avoid making assumptions or assigning blame.

Talking to the Customer

One of the best sources of information is the person who experienced the problem.

A technician should:

Remember:

Users often leave out important details—not because they are dishonest, but because they do not realize what information is relevant.

“Show Me the Problem”

Instead of asking vague questions, ask the user to demonstrate the issue.

For example:

“Can you show me what ‘not working’ looks like?”

Benefits include:

Sometimes the issue is simply that the user is performing the correct task in the wrong way or in the wrong order.

Important Questions to Ask

1. Can You Show Me the Problem?

Allows direct observation of:

2. How Often Does It Happen?

Determines whether the issue is:

Frequent or repeatable problems usually indicate deeper issues.

3. Has Any New Hardware or Software Been Installed?

Recently installed devices or applications may cause:

4. Has the Computer Been Moved or Dropped?

Moving equipment may:

Portable devices are especially vulnerable to physical damage.

5. Has Someone Else Used the Computer?

Another user may have:

6. Have Any Other Changes Been Made Recently?

If the timing of a recent change matches the appearance of the problem, that change may be responsible.

Always compare:

The Social Side of Troubleshooting

Technical skills alone are not enough.

Successful technicians also need strong communication skills.

Good practices include:

Example:

“What did you do to break it?”

Better:

“What was happening when the computer stopped working?”

This approach encourages users to share more information without becoming defensive.

Gathering Information

After speaking with the user, gather additional evidence by observing the computer.

Ask yourself:

The more precisely you identify the symptoms, the easier it becomes to locate the cause.

Handle Multiple Problems Separately

Sometimes users report several issues.

Example:

If the problems appear unrelated, troubleshoot each one separately.

However, if the issues share a common cause (e.g., network outage affecting Internet and file server access), solving one root problem may resolve both.

Hardware vs. Software Problems

One of the first goals is determining whether the issue is primarily hardware- or software-related.

Hardware Clues

Software Clues

This decision determines which troubleshooting tools and techniques to use.

Integrated Components

Modern computers often integrate components such as:

into the motherboard.

If one integrated component fails:

Step 2 – Establish a Theory of Probable Cause

After identifying the symptoms, develop one or more possible explanations.

Examples:

Problem:

“No display.”

Possible causes:

The goal is to create logical theories that can be tested.

Question the Obvious

A key troubleshooting principle is to check the simplest explanation first.

This idea is based on Occam’s Razor, which states that the simplest explanation is often the correct one.

Examples:

Before replacing hardware:

Many problems are caused by simple oversights.

Research Knowledge Sources

If the cause is not immediately obvious, consult reliable resources.

Recommended sources include:

Searching for a specific error message often leads directly to a solution.

Eliminating Possibilities

Rather than guessing, systematically eliminate potential causes.

Example:

A hard drive is not detected.

Possible causes:

Test each possibility one at a time until only the actual cause remains.

A useful troubleshooting technique is reducing the system to the minimum required components (“bare bones”) and then adding components back until the issue reappears. In software troubleshooting, Safe Mode can help isolate problems caused by drivers or startup programs.

Divide and Conquer

When multiple unrelated issues exist:

Trying to solve everything simultaneously often increases confusion and slows troubleshooting.

Step 3 – Test the Theory

Once a probable cause has been identified, perform tests to confirm or reject it.

If the test confirms the theory:

If the test disproves the theory:

This process continues until the root cause is found.

Check the Simple Stuff First

Many problems are caused by simple issues that technicians sometimes overlook.

Always check:

Is it plugged in?

Ensure cables are securely connected at both ends.

Is it turned on?

Verify power indicators are lit.

Is there physical damage?

Look for:

Is the system ready?

Confirm the operating system has fully loaded and the device is ready to accept input.

Do chips or cables need reseating?

Repeated heating and cooling can loosen:

Always power off the computer and use an antistatic wrist strap before opening the case to avoid electrostatic discharge (ESD).

Check for User Error

Not every problem is caused by faulty hardware or software.

Sometimes the user simply needs guidance.

Ask:

“Have you successfully performed this task before?”

If the answer is no, the issue may be incorrect usage rather than a technical failure.

When helping users:

Key Terms

Computer Support Concepts & The CompTIA Troubleshooting Methodology, and Technician Best Practices

Step 4 – Establish a Plan of Action and Implement the Solution

Once the root cause has been identified, the technician must determine the best way to fix the problem. The goal is not only to solve the issue but also to minimize risks, avoid unnecessary downtime, and protect the user’s data.

What Is a Plan of Action?

A plan of action is a step-by-step strategy for correcting the identified problem.

Before making changes, technicians should consider:

Planning first helps avoid making the situation worse.

Consider the Impact Before Making Changes

Even a correct repair can cause problems if performed carelessly.

For example:

Updating a device driver may fix one issue but create another if the new driver is incompatible with the operating system.

Similarly, replacing hardware without checking compatibility may prevent the computer from booting.

Technicians should always evaluate possible side effects before implementing a solution.

Protect User Data

Before making significant changes, create a backup whenever possible.

Examples include:

Backing up data ensures important files can be restored if something goes wrong.

Escalation

Sometimes a technician may not have enough experience, authority, or resources to solve a problem.

In these cases, the issue should be escalated to someone with more expertise.

Examples include:

Escalation is a normal part of technical support and helps ensure problems are resolved efficiently.

Implementing the Solution

Once the plan has been developed:

  1. Carry out the repair.
  2. Follow established procedures.
  3. Monitor the system carefully.
  4. Watch for unexpected behavior.
  5. Avoid making multiple changes at the same time.

Changing several things simultaneously makes it difficult to determine which action actually solved—or created—the problem.

Step 5 – Verify Full System Functionality

Repairing the original problem does not automatically mean the job is complete.

The technician must verify that:

This verification step ensures that the solution is complete rather than temporary.

Testing the Repair

Testing should include:

Reproduce the Original Problem

Attempt the same task that previously failed.

Example:

If a user could not print:

Check Related Features

Some repairs affect other system components.

Examples:

After replacing a network adapter:

Verify:

Ask the User to Test

The customer should verify that the repair solves the original issue.

The user may notice details the technician overlooked because they are familiar with their normal workflow.

Implement Preventive Measures

Good technicians try to prevent the same problem from occurring again.

Examples include:

Installing Updates

Update:

to eliminate known bugs.

Improving Security

If malware caused the issue:

Install or update:

Replacing Aging Hardware

If a hard drive shows signs of failure, replacing it before complete failure prevents future downtime.

User Education

Sometimes the best preventive measure is teaching the user the correct procedure.

Examples:

Step 6 – Document Findings, Actions, and Outcomes

Documentation is the final step in the troubleshooting methodology.

It provides a permanent record of:

Accurate documentation helps both the current technician and future technicians facing similar issues.

What Should Be Documented?

A service record should include:

Problem Description

Example:

“Computer displayed ‘No Boot Device Found’ during startup.”

Symptoms Observed

Examples:

Diagnostic Tests Performed

Examples:

Solution Implemented

Examples:

Final Verification

Examples:

Preventive Recommendations

Examples:

Why Documentation Is Important

Documentation benefits everyone.

It:

Organizations often maintain knowledge bases built from previous support tickets.

Troubleshooting Best Practices

Throughout the chapter, several best practices are emphasized.

1. Never Guess

Use evidence to identify the cause instead of making assumptions.

2. Start With Simple Possibilities

Check:

before replacing expensive hardware.

3. Change Only One Thing at a Time

If several changes are made simultaneously, it becomes difficult to determine which one solved the problem—or caused a new one.

4. Verify Before Finishing

Always confirm:

5. Keep Good Records

Good documentation improves future troubleshooting.

6. Be Professional

A technician should:

Good customer service is just as important as technical knowledge.

Common Troubleshooting Mistakes

Avoid these errors:

Putting It All Together: The Complete Troubleshooting Flow
  1. Identify the Problem
    • Gather information.
    • Interview the user.
    • Observe symptoms.
    • Determine whether the issue involves hardware, software, or user error.
  2. Establish a Theory of Probable Cause
    • Consider likely causes.
    • Check obvious issues first.
    • Research if necessary.
    • Eliminate possibilities systematically.
  3. Test the Theory
    • Perform tests to confirm or reject the suspected cause.
    • If incorrect, return to Step 2.
  4. Implement the Solution
    • Develop a repair plan.
    • Protect user data.
    • Escalate when necessary.
    • Apply the solution carefully.
  5. Verify Functionality
    • Confirm the original problem is solved.
    • Test related features.
    • Implement preventive measures.
    • Have the user verify the repair.
  6. Document Everything
    • Record the symptoms, diagnosis, repair, and outcome.
    • Include preventive recommendations.

This structured process helps technicians solve problems efficiently while minimizing risk and ensuring consistent results.

Exam Tips

These are among the most commonly tested concepts from this chapter: