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 may or may not 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 may or may not 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 may or may not 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. |