53 lines
2.5 KiB
Markdown
53 lines
2.5 KiB
Markdown
# Zerto AI Rewind - demo narration (v3, rewritten against the jp-voice profile)
|
|
# Edit any line, then tell Claude to re-read this file.
|
|
# Blank line separates beats. Lines starting with # are ignored.
|
|
|
|
## PART 1 - INTRO (architecture diagram on screen, builds as each beat lands)
|
|
|
|
[i1] Hello, and welcome to the Zerto AI Rewind demo.
|
|
|
|
[i2] AI agents are acting on production systems faster than ever, and a lot faster
|
|
than backup was ever designed to keep up with. Zerto's continuous data
|
|
protection is a good fit for that, because the journal is always running.
|
|
|
|
[i3] In this demo an AI agent makes a change to a production system. But before it
|
|
does, it checks whether that VM is protected by Zerto, and if it is, it inserts
|
|
a tagged checkpoint into the journal first.
|
|
|
|
[i4] That gives the agent something to fall back on. If the change breaks the
|
|
application, and the agent can't fix it on its own, it can use file level or
|
|
full system recovery to get back to the moment before it touched anything.
|
|
|
|
## PART 2 - THE DEMO (audience: a customer, not an engineer)
|
|
|
|
[d1] This is the agent connecting to Zerto. Everything from here runs against a live
|
|
Zerto environment.
|
|
|
|
[d2] The machine is a production Windows server, and Zerto is already protecting it.
|
|
The agent has been asked to change a configuration file on that server.
|
|
|
|
[d3] Before it changes anything, it asks Zerto a simple question. Is this machine
|
|
protected, and which protection group is it in?
|
|
|
|
[d4] It is, so Zerto puts a tagged checkpoint into the journal, and the agent waits
|
|
until Zerto confirms that checkpoint is really there before it goes any further.
|
|
|
|
[d5] Now the change goes in, and it breaks the file. The version that was there is
|
|
gone from the server. Backup has a copy from last night, so that's hours old
|
|
already. Zerto has one from seconds before the change.
|
|
|
|
[d6] The agent can't just recover on its own. Recovery has to be approved by a
|
|
person, so at this point it stops and asks.
|
|
|
|
[d7] With approval, Zerto goes back to the checkpoint from just before the change,
|
|
and hands back the original file exactly as it was.
|
|
|
|
[d8] Putting that file back onto the server is an ordinary copy. Zerto's job was
|
|
keeping the data in the first place.
|
|
|
|
[d9] This was a single file, so file level recovery was enough. That same checkpoint
|
|
would let you bring back the entire machine if the damage were bigger.
|
|
|
|
[d10] And that's the point. The recovery point is the journal, seconds before the
|
|
change, instead of last night's backup window.
|