Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. IT Analytics Data Collector Notes and Troubleshooting
  3. CRON Expressions for Policy and Report Schedules
  4. CRON expressions for scheduling reports
IT Analytics Data Collector Notes and Troubleshooting

CRON expressions for scheduling reports

Many reports and dashboards may require a email or export schedule. Native CRON expressions are supported for fine-tuning a email or schedule. The format for scheduling reports and dashboard email and exports follows string with six single space-separated time and date fields:

*

second

 

*

minute

 

*

hour

 

*

day of the month

 

*

month

 

*

day of the week

The following are the general guidelines when using special characters during the CRON expressions.

Table: Probe Schedule Allowed Values and Allowed Special Characters

Field

Allowed Values

second

0-59 in string with six single space-separated time and date fields

minutes

0-59 (0 is "on the hour")

hours

0-23

day of month

1-31

month

1-12

day of week

0-6 (0 is Sunday)

  • IT Analytics supports a maximum of 80 characters in a CRON expression.

Special Characters:

  • A field may be an asterisk (*), which means the full range - i.e., "first" to "last". However, a * in the seconds and minutes position is not permitted, as this would excessively trigger the probe - every second or minute.

  • A forward slash (/) can be used to specify intervals.

  • Use a dash (-) to specify a range.

  • Use ? ("no specific value") when you need to specify something in one of the two fields in which the character is allowed, but not the other.

    For example, to schedule the trigger on a particular day of the month (the 10th), but irrespective of the day-of-the-week that happens to be, specify "10" in the day-of-month field, and "?" in the day-of-week fie

  • You can use forward slash (/) can be used to specify increments.

    For example, "0/15" in the seconds field means "the seconds 0, 15, 30, and 45". And "5/15" in the seconds field means "the seconds 5, 20, 35, and 50". You can also specify '/' after the '' character - in this case '' is equivalent to having '0' before the '/'. '1/3' in the day-of-month field means "fire every 3 days starting on the first day of the month".

  • The CRON expression for the last day of the month, denoted by the letter L, is not supported.

Table: Report Schedule field examples of string with six single space-separated time and date fields

Report Schedule Examples

Schedule Run Time

0 0 * * * *

the top of every hour of every day.

*/10 * * * * *

every ten seconds.

0 0 8-10 * * *

8, 9 and 10 o'clock of every day.

0 0 6,19 * * *

6:00 AM and 7:00 PM every day.

0 0/30 8-10 * * *

8:00, 8:30, 9:00, 9:30, 10:00 and 10:30 every day.

0 0 0 25 12 ?

every Christmas Day at midnight.

0 15 10 * * ? 2010

run at 10:15 AM every day during the year 2010.

0 0 12 1/5 * ?

run at 12 PM (noon) every 5 days every month, starting on the first day of the month.

0 0 0 1W * *

first weekday of the month at midnight

0 11 11 11 11 ?

run every November 11th at 11:11 AM.

0 0-5 14 * * ?

run every minute starting at 2 PM and ending at 2:05 PM, every day.

Feedback

Was this page helpful?
Previous

CRON expressions for policy probe schedules

Next

Clustering Data Collectors with VCS and Veritas NetBackup (RHEL)

Feedback

Was this page helpful?