Stay organized with collections
Save and categorize content based on your preferences.
The previous topics provided definitions, detailed descriptions, and
best practices of how to set a schedule in a policy. The following table
summarizes the best practices and most often used policy schedules.
The production to snapshot policy defines when and how often production data is
captured and how many snapshots are retained.
Windowed Schedule, One Snapshot per Window. Window to open as needed, and
might span day boundary. Default is 19:00 to 07:00. Frequency: Once
per window. Retain for 2 days.
Windowed Schedule, Multiple Snapshots in a Window. Window to open as
needed, and might span day boundary. Default is 19:00 to 07:00.
Frequency: As needed, not to overlap with time to take a snapshot. Default is
every 8 hours. Retain for 2 days.
Continuous Schedule, Run Daily at Regular Intervals. Continuous schedule
spans a single 24 hour boundary. Frequency: As needed, not to overlap with time
to take a snapshot. Default is every 8 hours. Retain for 2 days.
Snapshot to OnVault Policy
StreamSnap Replication Policy
Send snapshot data to object storage defined by an OnVault Pool
Windowed Schedule -- One Snapshot per Window
Window to open as needed, and might span day boundary.
Default is 19:00 to 07:00.
Frequency: Once per window.
Retain as needed
Replicate snapshot data to a remote backup/recovery appliance,
over a high quality network, to provide RPOs as low as one hour.
A StreamSnap policy is always tied to a specific Snapshot policy,
and uses the schedule and frequency settings of that Snapshot policy.
Continuous Schedule -- Run Daily at Regular Intervals
Continuous schedule spans a single 24 hour boundary.
Frequency: As needed, not to overlap with time to take a snapshot.
Default is every 8 hours.
Retain for 2 days.
Can retain multiple point-in-time snapshot images at the remote site.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eThe content outlines best practices and common schedules for data snapshot policies, including production to snapshot, snapshot to OnVault, and StreamSnap replication policies.\u003c/p\u003e\n"],["\u003cp\u003eWindowed schedules allow for snapshots to be taken within a specified time frame, either once per window or multiple times, and can span across day boundaries.\u003c/p\u003e\n"],["\u003cp\u003eContinuous schedules run within a 24-hour period and are designed to capture snapshots at regular intervals, avoiding overlap.\u003c/p\u003e\n"],["\u003cp\u003eSnapshot to OnVault policies send snapshot data to object storage, while StreamSnap replication policies replicate data to a remote site for backup and recovery, following the schedule of an associated snapshot policy.\u003c/p\u003e\n"]]],[],null,["# Best scheduling practices at a glance\n\nThe previous topics provided definitions, detailed descriptions, and\nbest practices of how to set a schedule in a policy. The following table\nsummarizes the best practices and most often used policy schedules.\n\nThe production to snapshot policy defines when and how often production data is\ncaptured and how many snapshots are retained.\n\n- **Windowed Schedule, One Snapshot per Window.** Window to open as needed, and might span day boundary. Default is 19:00 to 07:00. Frequency: Once per window. Retain for 2 days.\n- **Windowed Schedule, Multiple Snapshots in a Window.** Window to open as needed, and might span day boundary. Default is 19:00 to 07:00. Frequency: As needed, not to overlap with time to take a snapshot. Default is every 8 hours. Retain for 2 days.\n- **Continuous Schedule, Run Daily at Regular Intervals.** Continuous schedule spans a single 24 hour boundary. Frequency: As needed, not to overlap with time to take a snapshot. Default is every 8 hours. Retain for 2 days."]]
