Free guides, interview Q&As, and job responsibility breakdowns — curated by industry veterans to help you crack MNC interviews
Figure 1: Incremental vs. Differential backup growth across a week
Figure 2: The 3-2-1 Backup Rule
Backup
Definition: A copy of important data stored separately from the original so it can be restored after loss or failure.
Day-to-Day Example: Like photocopying an important original document and storing the copy in a different drawer, in case the original gets damaged.
Recovery
Definition: The process of restoring data, files, applications, or systems from a backup after a failure or data loss event.
Day-to-Day Example: Like pulling out that photocopy and using it to replace the original document once it's lost or destroyed.
Business Continuity (BC)
Definition: The broader practice of keeping essential business operations running during and after a disruption.
Day-to-Day Example: Like a restaurant having a backup generator and a manual paper order system ready, so it can keep serving customers even during a power outage.
Disaster Recovery (DR)
Definition: The process specifically focused on restoring IT systems, applications, and data after a major failure or disaster.
Day-to-Day Example: Like the specific plan a hotel follows to rebuild and reopen after a fire, rather than its everyday operational routine.
Full Backup
Definition: A backup that copies all selected data in its entirety every time it runs.
Day-to-Day Example: Like re-photocopying an entire filing cabinet from scratch every week, even the documents that haven't changed.
Incremental Backup
Definition: A backup that copies only the data changed since the last backup, whether that was a full or another incremental backup.
Day-to-Day Example: Like only photocopying the pages you edited today, rather than the whole notebook, and doing this fresh each day.
Differential Backup
Definition: A backup that copies all data changed since the last Full Backup, growing larger each day until the next full backup.
Day-to-Day Example: Like keeping a running photocopy of every page you've changed since your last big full copy, no matter how many days have passed.
Mirror/Clone Backup
Definition: A backup that keeps an exact, continuously updated copy of the source data in real time.
Day-to-Day Example: Like a live video feed of a room instead of a photograph — it always shows the current state, including if something in the room disappears.
Windows Server Backup (WSB)
Definition: A built-in Windows Server tool used to back up and restore files, System State, and entire servers.
Day-to-Day Example: Like a hotel's in-house maintenance crew that can patch a single room or rebuild the entire hotel, all using the same toolkit.
System State Backup
Definition: A backup of critical Windows components like the Active Directory database, SYSVOL, registry, and boot files, without backing up the whole server.
Day-to-Day Example: Like backing up just a building's blueprints and utility connections, not every piece of furniture inside it.
Bare Metal Recovery (BMR)
Definition: A recovery method that rebuilds an entire server from scratch, including OS, applications, and configuration, onto new or empty hardware.
Day-to-Day Example: Like reconstructing an entire house from architectural plans on an empty plot of land, not just repairing one damaged room.
Recovery Time Objective (RTO)
Definition: The maximum acceptable amount of downtime a system can experience after a disaster before it must be restored.
Day-to-Day Example: Like a restaurant deciding it can afford to stay closed for at most 4 hours after a kitchen fire before it must reopen.
Recovery Point Objective (RPO)
Definition: The maximum acceptable amount of data loss, measured in time, that an organization can tolerate.
Day-to-Day Example: Like deciding you're comfortable losing at most the last 30 minutes of a document's edits if your computer crashes right now.
Hot Site
Definition: A fully operational secondary recovery site with real-time synchronization, ready for near-instant failover.
Day-to-Day Example: Like keeping a second, fully staffed and stocked restaurant running at all times, ready to serve customers the instant the first one closes.
Warm Site
Definition: A partially configured recovery site that needs some additional setup before it can take over operations.
Day-to-Day Example: Like having a second restaurant space with the kitchen installed but no staff or food stocked yet — usable, but not instantly.
Cold Site
Definition: A backup location with only basic infrastructure in place, requiring significant setup before it becomes operational.
Day-to-Day Example: Like having an empty rented space with just electricity and plumbing — everything else has to be brought in and set up from scratch.
3-2-1 Backup Rule
Definition: A backup strategy recommending 3 copies of data, on 2 different storage media, with 1 copy kept offsite.
Day-to-Day Example: Like keeping your passport's original, a photocopy in your home safe, and another photocopy at a relative's house in a different city.
Backup Testing
Definition: The practice of regularly verifying that backup data can actually be restored successfully.
Day-to-Day Example: Like periodically test-driving your spare car in the garage, instead of assuming it'll start the one day you actually need it.
Backup Retention Policy
Definition: A rule defining how long backup data is kept before it's deleted, balancing storage space against historical recovery needs.
Day-to-Day Example: Like a company policy on how many years of old paper invoices to keep in storage before shredding them.
Backup Monitoring
Definition: The ongoing practice of tracking backup jobs to detect failures, low storage, or corrupted backups early.
Day-to-Day Example: Like a manager checking every morning that last night's security cameras actually recorded footage, instead of finding out only when it's needed.
Figure 3: RTO and RPO plotted on a recovery timeline
Figure 4: Hot, Warm, and Cold Disaster Recovery sites compared
1. Backup vs. Recovery
Feature Backup Recovery Nature Preventive process Corrective process When performed Done regularly Done during/after failure Purpose Creates a copy of data Restores data from that copy Goal Protects against data loss Brings systems back online
2. Full Backup vs. Incremental Backup vs. Differential Backup
Feature Full Backup Incremental Backup Differential Backup Backup speed Slow Fast Medium Storage usage High Low Medium Restore speed Fast Slow Medium Complexity Simple Complex Moderate
3. Incremental Backup vs. Differential Backup
Feature Incremental Backup Differential Backup Copies Changes since the last backup (full or incremental) Changes since the last Full Backup only Backup size over the week Stays small each day Grows larger each day Restore requirement Full backup + every incremental since Full backup + latest differential only Restore complexity More complex Simpler
4. Local Disk vs. NAS vs. Cloud Backup
Aspect Local Disk NAS Cloud Backup Speed Fastest Fast (network-dependent) Depends on internet speed Disaster protection None — same site Limited — same site Strong — offsite by nature Scalability Limited Good Very high Cost pattern One-time hardware cost One-time + maintenance Recurring subscription
5. Full Server Backup vs. System State Backup vs. File and Folder Backup
Feature Full Server Backup System State Backup File and Folder Backup Scope Entire server (OS + apps + data) Core system components only (AD, SYSVOL, registry) Selected files/folders only Backup size Largest Small Smallest to moderate Typical use Major disaster recovery Restoring AD/config without full rebuild Recovering individual user files
6. RTO vs. RPO
Feature RTO (Recovery Time Objective) RPO (Recovery Point Objective) Focus System recovery time Data loss tolerance Measures Downtime duration Amount of data that can be lost Example target Restore within 2 hours Maximum 30 minutes of data loss What lowers it Fast recovery systems, hot sites Frequent backups, real-time replication
7. Hot Site vs. Warm Site vs. Cold Site
Feature Hot Site Warm Site Cold Site Readiness Fully operational Partially configured Basic infrastructure only Recovery speed Fastest Moderate Slowest Cost Highest Medium Lowest
8. File & Folder Recovery vs. Bare Metal Recovery vs. Complete Server Recovery
Recovery Method Purpose Recovery Scope File & Folder Recovery Recover individual files Selected data only Bare Metal Recovery (BMR) Rebuild a server from scratch Full server onto new/empty hardware Complete Server Recovery Restore the full server environment OS + applications + data + settings
9. Backup-Based Recovery vs. Replication-Based Recovery
Feature Backup-Based Recovery Replication-Based Recovery Method Restores from stored backup files Data continuously copied to another site Cost Lower Higher Recovery speed Slower Faster Data loss risk Higher (since last backup) Lower (near real-time copy)
10. Common Backup Failure Causes Compared
Cause Typical Symptom Typical Fix Insufficient disk space "Disk Full" error, incomplete backup Delete old backups, adjust retention, add storage Network connectivity issues Backup to NAS/network share fails Check connectivity, DNS, firewall rules Corrupted backup files Verification/restore errors Use healthy storage, test restores regularly Permission issues "Access Denied" during backup/restore Verify NTFS/share permissions and service account rights
Q1. What is the difference between Backup and Recovery?
Answer: Backup is a preventive process that creates a copy of data on a regular basis, while Recovery is a corrective process that restores that data after a failure occurs.
Q2. What is Business Continuity, and how does it relate to Disaster Recovery?
Answer: Business Continuity is the broader goal of keeping operations running during and after a disruption; Disaster Recovery is the more specific process of restoring IT systems and data after a major failure, and it supports overall business continuity.
Q3. What are the advantages and disadvantages of a Full Backup?
Answer: A Full Backup offers fast, simple recovery since everything is in one backup set, but it requires large storage space and takes longer to complete each time it runs.
Q4. Why does an Incremental Backup have slower recovery than a Full Backup?
Answer: Because Incremental Backups only store daily changes, restoring requires the last full backup plus every incremental backup since, making the restore process longer and more complex.
Q5. Why is Differential Backup generally easier to restore than Incremental Backup?
Answer: A Differential Backup only requires the last Full Backup plus the most recent Differential Backup to restore, while Incremental requires the full backup plus every incremental in the chain.
Q6. What is a Mirror/Clone Backup, and what is its main risk?
Answer: A Mirror Backup keeps an exact, real-time copy of source data; its main risk is that if a file is deleted from the source, it may also be deleted from the mirror, since there's no version history.
Q7. Why is storing backups only on the same server being backed up considered risky?
Answer: If that server suffers hardware failure, ransomware, or a disaster, both the original data and its only backup could be lost together, defeating the purpose of having a backup.
Q8. What is System State Backup used for, and why not just take a Full Server Backup instead?
Answer: System State Backup protects critical components like Active Directory and SYSVOL without backing up the entire server, allowing faster, smaller backups when only system configuration recovery is needed.
Q9. What is Bare Metal Recovery, and when is it used?
Answer: Bare Metal Recovery rebuilds an entire server from scratch — OS, applications, and configuration — onto new or empty hardware, and is used when a server becomes completely unusable due to severe hardware failure or corruption.
Q10. What questions do RTO and RPO each answer?
Answer: RTO answers "how quickly must the system be restored?" (acceptable downtime), while RPO answers "how much recent data can be lost?" (acceptable data loss).
Q11. Why would a lower RTO or RPO increase implementation cost?
Answer: A lower RTO requires faster recovery infrastructure like hot sites and failover systems, and a lower RPO requires more frequent backups or real-time replication — both of which demand more advanced (and costly) technology.
Q12. What is the difference between a Hot Site, Warm Site, and Cold Site?
Answer: A Hot Site is fully operational with real-time sync for near-instant failover; a Warm Site is partially configured and needs some setup; a Cold Site has only basic infrastructure and takes the longest to become operational.
Q13. What does the 3-2-1 Backup Rule recommend, and why?
Answer: It recommends keeping 3 copies of data on 2 different storage types with 1 copy offsite, which protects against hardware failure, ransomware, and site-wide disasters all at once.
Q14. Why is backup testing considered essential rather than optional?
Answer: Without testing, corrupted or incomplete backups may go unnoticed until an actual emergency, at which point the organization discovers too late that recovery isn't possible.
Q15. What role does Event Viewer play in backup troubleshooting?
Answer: Event Viewer records backup errors, service failures, and disk-related warnings, helping administrators identify the exact cause and timing of backup failures.
Q1. A company performs a Full Backup every Sunday and wants fast daily backups with minimal storage use, and can tolerate a slightly longer restore process. Which strategy fits best?
Answer: An Incremental Backup strategy fits best — daily incrementals are fast and storage-efficient, at the cost of a more involved restore process using the full backup plus every incremental since.
Q2. A ransomware attack encrypts both the production server and its only backup, which was stored on an attached external drive left connected. What best practice was violated?
Answer: The 3-2-1 Backup Rule was violated — there was no truly offline or offsite copy, so when ransomware spread, it reached the backup as well as the original data.
Q3. An online shopping company says even a few minutes of downtime during a festival sale would be very costly, but they can tolerate losing a bit of non-critical browsing data. Which DR metric should be prioritized, and what site type fits?
Answer: RTO (Recovery Time Objective) should be prioritized and kept very low; a Hot Site with real-time failover fits, since fast recovery matters more here than perfect data preservation.
Q4. A bank requires that no more than 5 minutes of transaction data can ever be lost. Which DR concept is most critical, and how would they achieve it?
Answer: RPO (Recovery Point Objective) is most critical here; achieving a 5-minute RPO requires real-time or near-real-time replication and very frequent backups rather than infrequent nightly backups.
Q5. A Domain Controller's Group Policy Objects become corrupted, but the rest of the server is working fine. What recovery method should be used instead of rebuilding the whole server?
Answer: System State Recovery should be used, since it restores Active Directory and related system configuration without requiring a full server rebuild.
Q6. A backup job to a NAS device fails every night with a network-related error. What should be checked first?
Answer: Check network connectivity and DNS resolution to the NAS, confirm the NAS device is online, verify the shared folder path, and check whether a firewall is blocking backup traffic.
Q7. A backup completes successfully every night, but when the company finally needs to restore, the files turn out to be corrupted and unusable. What could have prevented this?
Answer: Regular backup testing/restoration drills would have caught the corruption earlier — a backup that has never been test-restored isn't verified as actually usable.
Q8. A physical server's motherboard fails completely, making the hardware unusable. What recovery approach lets the organization rebuild everything on new hardware?
Answer: Bare Metal Recovery (BMR) should be performed — it rebuilds the entire server, including the OS, applications, and configuration, onto new or replacement hardware from backup.
