Why Backup servers in Nginx? - Purpose & Use Cases

The Big Idea

What if your website never went down, even when servers fail?

The Scenario

Imagine you run a busy website with just one server handling all the visitors. One day, that server crashes or goes offline unexpectedly. Suddenly, your website is down, and visitors see error messages instead of your content.

The Problem

Relying on a single server means if it fails, your whole site stops working. Manually switching to a backup server takes time and can cause long outages. This leads to frustrated users and lost business.

The Solution

Backup servers automatically take over when the main server fails. This switch happens quickly and smoothly, keeping your website online without you lifting a finger.

Before vs After

✗ Before

server 192.168.1.10;
# Manually change to backup IP if main fails

✓ After

server 192.168.1.10 max_fails=3 fail_timeout=30s;
server 192.168.1.11 backup;

What It Enables

Backup servers let your website stay online and reliable, even when problems happen behind the scenes.

Real Life Example

A popular online store uses backup servers so customers can keep shopping even if one server crashes during a big sale.

Key Takeaways

Single servers can fail and cause downtime.

Manual switching is slow and error-prone.

Backup servers automatically keep services running smoothly.

Practice

1. What is the main purpose of marking a server as backup in an upstream block in nginx?

easy

A. To use it only if all main servers are unavailable

B. To prioritize it over main servers for all requests

C. To permanently disable the server

D. To balance load equally with main servers

Solution

1. Step 1: Understand the role of backup servers

   Backup servers are fallback servers used only when main servers fail.

2. Step 2: Analyze the backup keyword effect

   Marking a server as backup means it will receive traffic only if main servers are down.

3. Final Answer:

   To use it only if all main servers are unavailable -> Option A

4. Quick Check:

   Backup servers = fallback only [OK]

Hint: Backup servers handle traffic only when main servers fail [OK]

Common Mistakes:

• Thinking backup servers share load equally
• Assuming backup servers are always active
• Confusing backup with disabled servers

2. Which of the following is the correct syntax to define a backup server in an nginx upstream block?

easy

A. server 192.168.1.10;

B. server backup 192.168.1.10;

C. server 192.168.1.10 backup;

D. backup server 192.168.1.10;

Solution

1. Step 1: Recall nginx upstream server syntax

   The correct syntax is server [IP] [parameters]; with parameters like backup after IP.

2. Step 2: Identify correct placement of backup

   The backup keyword comes after the IP address in the server line.

3. Final Answer:

   server 192.168.1.10 backup; -> Option C

4. Quick Check:

   Backup keyword after IP = correct syntax [OK]

Hint: Put 'backup' after IP in server line [OK]

Common Mistakes:

• Placing 'backup' before IP address
• Using 'backup server' instead of 'server ... backup;'
• Omitting semicolon at line end

3. Given this nginx upstream block:

upstream backend {
    server 10.0.0.1;
    server 10.0.0.2 backup;
}

Which server will nginx send requests to if 10.0.0.1 is up?

medium

A. 10.0.0.1 only

B. 10.0.0.2 only

C. Both 10.0.0.1 and 10.0.0.2 equally

D. No server, error occurs

Solution

1. Step 1: Understand upstream with backup server

   Main server 10.0.0.1 handles requests first; backup 10.0.0.2 is fallback.

2. Step 2: Check server availability

   Since 10.0.0.1 is up, nginx sends all requests there, ignoring backup.

3. Final Answer:

   10.0.0.1 only -> Option A

4. Quick Check:

   Backup used only if main down [OK]

Hint: Backup server used only if main server fails [OK]

Common Mistakes:

• Assuming backup server shares load
• Thinking backup server is always active
• Believing nginx sends requests to both simultaneously

4. You have this nginx upstream configuration:

upstream backend {
    server 192.168.0.1 backup;
    server 192.168.0.2;
}

What is wrong with this configuration?

medium

A. Backup keyword is misspelled

B. No semicolon after server lines

C. IP addresses are invalid

D. Nothing is wrong with this configuration

Solution

1. Step 1: Validate syntax and parameters

   All server lines have correct syntax, valid IPs, proper semicolons, and correct backup usage.

2. Step 2: Check server order

   Position of backup servers does not matter; nginx ignores them unless all main servers fail.

3. Final Answer:

   Nothing is wrong with this configuration -> Option D

4. Quick Check:

   Backup position irrelevant [OK]

Hint: Backup servers can be listed anywhere [OK]

Common Mistakes:

• Thinking backup servers must be listed after main servers
• Believing server order causes failures
• Assuming 192.168.x.x IPs are invalid

5. You want nginx to send traffic to server1 and server2 normally, but use backup1 and backup2 only if both main servers fail. Which configuration correctly sets this up?

hard

A. upstream backend {
server backup1;
server backup2;
server server1;
server server2;
}

B. upstream backend {
server server1;
server server2;
server backup1 backup;
server backup2 backup;
}

C. upstream backend {
server server1 backup;
server server2 backup;
server backup1;
server backup2;
}

D. upstream backend {
server server1;
server backup1;
server server2;
server backup2;
}

Solution

1. Step 1: Identify main and backup servers

   Main servers are server1 and server2; backup servers are backup1 and backup2.

2. Step 2: Apply correct syntax and order

   Main servers listed first without backup, backups listed after with backup keyword.

3. Step 3: Verify options

   upstream backend { server server1; server server2; server backup1 backup; server backup2 backup; } correctly lists main servers first, backups with backup keyword after.

4. Final Answer:

   upstream backend { server server1; server server2; server backup1 backup; server backup2 backup; } -> Option B

5. Quick Check:

   Main servers first, backups last with 'backup' keyword [OK]

Hint: List main servers first, backups last with 'backup' keyword [OK]

Common Mistakes:

• Placing backup servers before main servers
• Missing 'backup' keyword on backup servers
• Marking main servers as backup by mistake