PACEMAKER(8)

🌸 NAME 🌸

Pacemaker — literally part of the Pacemaker cluster resource manager, bestie. That's the whole vibe.

---

✨ SYNOPSIS ✨

crm_shadow <query>|<command> [options]

---

💖 DESCRIPTION 💖

Okay so the tea is: this command lets you do Pacemaker configuration changes in a sandbox. Like a little play area. A test kitchen. 🧚

It sets up an environment where your config tools (cibadmin, crm_resource, etc.) work offline instead of against a live cluster — so you can preview your changes and test them for side effects before they touch anything real. No cap, it's giving "rehearse before the main character moment." 👑

---

🎀 OPTIONS 🎀

💅 Help Options:

• -h, --help — Shows the help options. The classic.
• --help-all — Shows, like, all of the help options. Everything. The whole menu.
• --help-output — Shows output help.
• --help-queries — Shows query help.
• --help-commands — Shows command help.
• --help-additional — Shows additional options.

🌈 Output Options:

• --output-as=FORMAT — Pick your output format, one of: text (that's the default, btw) or xml.
• --output-to=DEST — Say where the output goes — a file name, or - for stdout. 🫶

🦋 Queries:

• -w, --which — Tells you which shadow copy is currently active.
• -p, --display — Displays what's actually inside the active shadow copy.
• -d, --diff — Displays the changes in the active shadow copy. The glow-up report. ✨
• -F, --file — Displays the location of the active shadow copy's file.

🔥 Commands:

• -c, --create=name — Creates the named shadow copy of the active cluster configuration.
• -e, --create-empty=name — Creates the named shadow copy with an empty cluster configuration. Optional add-on: --validate-with
• -C, --commit=name — Uploads the contents of the named shadow copy to the cluster. Sending it, fr.
• -D, --delete=name — Deletes the contents of the named shadow copy. Bye bestie. 💀
• -E, --edit — Edits the contents of the active shadow copy with your favorite $EDITOR.
• -r, --reset=name. Required: --force. — Recreates the named shadow copy from the active cluster configuration. And yes, --force is required, it's literally in the name. 🙈
• -s, --switch=name — (Advanced) Switches to the named shadow copy.

👑 Additional Options:

• -f, --force — (Advanced) Forces the action to be performed. Like, makes it happen.
• -b, --batch — (Advanced) Don't spawn a new shell.
• -a, --all — (Advanced) Uploads the entire CIB, including status, with --commit.
• -v, --validate-with — (Advanced) Creates an older configuration version.

🍓 Application Options:

• -$, --version — Displays the software version and exits.
• -V, --verbose — Increases debug output. You can specify this multiple times, so go off. 🔥

---

⭐ EXAMPLES ⭐

Create a blank shadow configuration:

# crm_shadow --create-empty myShadow

Create a shadow configuration from the running cluster:

# crm_shadow --create myShadow

Display the current shadow configuration:

# crm_shadow --display

Discard the current shadow configuration (named myShadow):

# crm_shadow --delete myShadow --force

Upload current shadow configuration (named myShadow) to running cluster:

# crm_shadow --commit myShadow

---

💜 AUTHOR 💜

Written by Andrew Beekhof and the Pacemaker project contributors. Icons. Legends. 🫶

---

And that's the whole page, bestie! This one's from Pacemaker 3.0.3+20260728.7052..., dated September 2026 — so you know it's fresh. Go forth and sandbox responsibly. 💖✨🎀🦋