Powered by Zoomin Software. For more details please contactZoomin

Flowmon User Guide

Scheduling Examples

  • Last Updated: July 28, 2026
  • 2 minute read
    • Flowmon Products
    • Flowmon
    • Documentation

Example 1

Use case: Daily backup, scheduled for 2:00 AM every day.

Current time: July 13, 2020, at 1:59 AM  

Last backup: never

Next backup: July 13, 2020, at 2:00 AM

The backup process will start at 2:00 AM, back up the configuration present in the system at 2:00 AM, and all flow data up to July 12, 2020 (including). If the system has been running for a year, the process will attempt to back up flow data from the entire year, because there are no previous backups.

Example 2

Use case: Daily backup, scheduled for 2:00 AM every day.

Current time: July 14, 2020, at 1:59 AM  

Last backup: July 13, 2020, at 2:00 AM

Next backup: July 14, 2020, at 2:00 AM

The backup process will start at 2:00 AM, back up the configuration present in the system at 2:00 AM, and flow data from July 13, 2020. Since there is a previous backup, there is no need to copy more data, only one day has not yet been backed up.

Example 3

Use case: Weekly backup, scheduled for 2:00 AM every Saturday.

Current time: July 11, 2020, at 1:59 AM  

Last backup: never

Next backup: July 11, 2020, at 2:00 AM

The backup process will start at 2:00 AM, back up the configuration present in the system at 2:00 AM, and all flow data up to July 10, 2020 (including). If the system has been running for a year, the process will attempt to back up flow data from the entire year, because there are no previous backups.

Example 4

Use case: Weekly backup, scheduled for 2:00 AM every Saturday.

Current time: July 18, 2020, at 1:59 AM  

Last backup: July 11, 2020, at 2:00 AM

Next backup: July 18, 2020, at 2:00 AM

The backup process will start at 2:00 AM, back up the configuration present in the system at 2:00 AM, and all flow data from July 11, 2020 (including) to July 17, 2020 (including). Since there is a previous backup, there is no need to copy more data, only seven days have not yet been backed up.

Example 5

Use case: Hourly backup, scheduled for every hour of every day.

Current time: July 13, 2020, at 1:59 AM  

Last backup: never

Next backup: July 13, 2020, at 2:00 AM

The backup process will start at 2:00 AM, back up the configuration present in the system at 2:00 AM, and all flow data up to July 12, 2020 (including). If the system has been running for a year, the process will attempt to back up flow data from the entire year, because there are no previous backups.

Example 6

Use case: Hourly backup, scheduled for every hour of every day.

Current time: July 13, 2020, at 2:59 AM  

Last backup: July 13, 2020, at 2:00 AM

Next backup: July 13, 2020, at 3:00 AM

The backup process will start at 3:00 AM, back up the configuration present in the system at 3:00 AM, and no additional flow data. The smallest possible flow data backup is one day, everything up to July 12, 2020 (including) has already been backed up.

Alert