Change the Nightly Maintenance schedule times

KB Home   |   Change the Nightly Maintenance schedule times

Main.ChangeScheduleTime History

Hide minor edits - Show changes to output

April 25, 2019, at 12:17 PM by Jack Lawless - Grammar, formatting, added information regarding other schedule Config Keys
April 25, 2019, at 12:17 PM by Jack Lawless - Grammar, formatting, added information regarding other schedule Config Keys
April 25, 2019, at 12:17 PM by Jack Lawless - Grammar, formatting, added information regarding other schedule Config Keys
Changed lines 1-4 from:
(:title Change the schedule timing:)

You can change the time that PaperCut will perform it's nightly maintenance by using the Config Editor. By default these run at 12:55am (i.e. the config setting is @@0 55 0 * * ?@@).
to:
(:title Change the Nightly Maintenance schedule times:)

You can change the time that PaperCut will perform it's nightly maintenance by using the Config Editor. By default these run at 12:55am (the Config Key setting is @@schedule.daily-maintenence=0 55 0 * * ?@@).
Added lines 7-8:
A number of different scheduled tasks run during the nightly maintenance, principally a synchronisation to add new PaperCut users and groups against your defined synchronisation source.
Changed lines 11-12 from:
The format of the value is a string comprised of 6 fields separated by white space. The format is similar to the "cron" format which is a job scheduler used in linux/unix. Fields can contain any of the allowed values, along with various combinations of the allowed special characters for that field. The fields are as follows:
to:
The format of the value is a string comprised of 6 fields separated by white space. The format is similar to the "cron" format which is a job scheduler used in Linux & Unix. Fields can contain any of the allowed values, along with various combinations of the allowed special characters for that field. The fields are as follows:
Changed lines 22-31 from:
The question mark (?) can be considered to be the same as saying "any"
For example:-  If I want my maintenance to run on a particular day of the month (say, the 28th), but don't care what day of the week that happens to be, I would put "28" in the day-of-month field, and "?" in the day-of-week field.

The asterix (*) can be considered to be the same as saying "every"
For example:-  If I want my maintenance to run on a particular day of the month (say, the 28th), but want it to run every month, I would put "28" in the day-of-month field, and "*" in the Month field.

From the example above we have:-  '''''0 0 3 28 * ?'''''
[[<<]]Which means......  Run at '''''3AM''''' - on the '''''28th''''' day of the month - '''''every''''' month - on '''''any''''' day of the week.

More examples:-
to:
The question mark (?) can be considered to be the same as saying "any".\\
For example; if I want my maintenance to run on a particular day of the month (say, the 28th), but I don't care what day of the week that happens to be, I would put "28" in the day-of-month field, and "?" in the day-of-week field.

The asterix (*) can be considered to be the same as saying "every".\\
For example;  if I want my maintenance to run on a particular day of the month (say, the 28th), but I want it to run every month, I would put "28" in the day-of-month field, and "*" in the Month field.

From the example above we have:-  '''''0 0 3 28 * ?'''''\\
Which means...  Run at '''''3AM''''' - on the '''''28th''''' day of the month - '''''every''''' month - on '''''any''''' day of the week.

Others examples:
Changed lines 35-36 from:
[[<<]]
to:

Other Config Keys which uses the cron time format are:

@@schedule.hourly@@ - Responsible for the timing of the
[[https://www.papercut.com/support/resources/manuals/ng-mf/applicationserver/topics/account-sync.html|external Shared Account synchronisation]] and [[https://www.papercut.com/support/resources/manuals/ng-mf/applicationserver/topics/printer-refund-print-jobs.html|Refund Request Emails]].\\
@@schedule.daily@@ - Responsible for the timing of the daily [[https://www.papercut.com/support/resources/manuals/ng-mf/applicationserver/topics/user-quota-allocation.html|Quota Allocation]] task.\\
@@schedule.weekly@@ - Responsible for the timing of the weekly [[https://www.papercut.com/support/resources/manuals/ng-mf/applicationserver/topics/user-quota-allocation.html|Quota Allocation]] task & weekly [[https://www.papercut.com/kb/Main/BackingUpData|Database Backup]].\\
@@schedule.monthly@@ - Responsible for the timing of the monthly [[https://www.papercut.com/support/resources/manuals/ng-mf/applicationserver/topics/user-quota-allocation.html|Quota Allocation]] task.\\

Changed line 52 from:
[-keywords: MON-FRI, cron, schedule, changing schedule, 0 30 10 ? * MON-FRI, 0 20 0 ? * 1, 0 30 0 1 * ?, 0 0 * * * ?, 0 55 0 * * ?, 0 10 0 * * ?, change Scheduled reports delivery times, nightly sync, maintenance window, user sync time, 12.55am-]
to:
[-keywords: MON-FRI, cron, schedule, changing schedule, 0 30 10 ? * MON-FRI, 0 20 0 ? * 1, 0 30 0 1 * ?, 0 0 * * * ?, 0 55 0 * * ?, 0 10 0 * * ?, change Scheduled reports delivery times, nightly sync, maintenance window, user sync time, 12.55am, synchronisation, nightly maintenance, maintenence-]
May 30, 2016, at 08:49 PM by 71.63.207.87 - changed 'the PaperCut' to 'that PaperCut'
Changed line 3 from:
You can change the time the PaperCut will perform it's nightly maintenance by using the Config Editor. By default these run at 12:55am (i.e. the config setting is @@0 55 0 * * ?@@).
to:
You can change the time that PaperCut will perform it's nightly maintenance by using the Config Editor. By default these run at 12:55am (i.e. the config setting is @@0 55 0 * * ?@@).
February 17, 2016, at 08:14 PM by Brian - Fixed a spelling error and some grammar.
Changed lines 5-6 from:
Prior to version 11.2 the daily mainitenance tasks were run at 1:15am.  This was changed to avoid issues around daylight savings change overs, which could result in the job not being run.
to:
Prior to version 11.2 the daily maintenance tasks were run at 1:15am.  This was changed to avoid issues around daylight savings change overs, which could result in the job not being run.
Changed line 9 from:
The format of the value is a string comprised of 6 fields separated by white space. The format is similar to the "cron" format which is a job scheduler used in linux/unix.Fields can contain any of the allowed values, along with various combinations of the allowed special characters for that field. The fields are as follows:
to:
The format of the value is a string comprised of 6 fields separated by white space. The format is similar to the "cron" format which is a job scheduler used in linux/unix. Fields can contain any of the allowed values, along with various combinations of the allowed special characters for that field. The fields are as follows:
December 09, 2015, at 03:56 AM by Shane Higgins -
Changed lines 15-17 from:
 Day of month YES 1-31 ?
Month YES 1-12 or JAN-DEC ?
 Day of week YES 1-7 or SUN-SAT ?
to:
 Day of month YES 1-31 ? or *
 
Month YES 1-12 or JAN-DEC or ? or *
 Day of
week YES 1-7 or SUN-SAT or ?
December 09, 2015, at 03:54 AM by Shane Higgins -
December 09, 2015, at 03:53 AM by Shane Higgins -
Added line 19:
[[<<]]
Changed lines 27-28 from:
[[<<]]Which means......  Run at 3AM - on the 28th day of the month - every month - regardless of what day it is.
to:
[[<<]]Which means......  Run at '''''3AM''''' - on the '''''28th''''' day of the month - '''''every''''' month - on '''''any''''' day of the week.
Added line 33:
[[<<]]
December 09, 2015, at 03:34 AM by Shane Higgins -
Changed lines 25-26 from:
 0 0 12 28 * ? - Run at 12AM - on the 28th day of the month - every month - regardless of what day it is.
to:
From the example above we have:-  '''''0 0 3 28 * ?'''''
[[<<]]Which means......  Run at 3AM
- on the 28th day of the month - every month - regardless of what day it is.
December 09, 2015, at 01:29 AM by Shane Higgins -
Changed line 13 from:
 Minutes   YES 0-59
to:
 Minutes       YES      0-59
Changed lines 19-20 from:
The question mark (?) is useful when you need to specify something in one of the two fields in which the character is allowed, but not the other. For example, if I want my maintenance to run on a particular day of the month (say, the 28th), but don't care what day of the week that happens to be, I would put "28" in the day-of-month field, and "?" in the day-of-week field.
to:
The question mark (?) can be considered to be the same as saying "any"
For example:-  If I want my maintenance to run on a particular day of the month (say, the 28th), but don't care what day of the week that happens to be, I would put "28" in the
day-of-month field, and "?" in the day-of-week field.

The asterix (*) can be considered to be the same as saying "every"
For example:
-  If I want my maintenance to run on a particular day of the month (say, the 28th), but want it to run every month, I would put "28" in the day-of-month field, and "*" in the Month field.

 0 0 12 28 * ? - Run at 12AM - on the 28th day of the month - every month - regardless of what day it is.

More examples:-
Changed line 30 from:
 0  0 2 * * 1 - Sunday 2:00AM
to:
 0  0 2 ? * 1 - Sunday 2:00AM
December 09, 2015, at 01:12 AM by Shane Higgins -
Changed line 13 from:
 Minutes YES 0-59
to:
 Minutes    YES 0-59
Changed line 34 from:
[-keywords: MON-FRI, cron, schedule, changing schedule, 0 20 0 ? * 1, 0 30 0 1 * ?, 0 0 * * * ?, 0 55 0 * * ?, 0 10 0 * * ?, change Scheduled reports delivery times, nightly sync, maintenance window, user sync time, 12.55am-]
to:
[-keywords: MON-FRI, cron, schedule, changing schedule, 0 30 10 ? * MON-FRI, 0 20 0 ? * 1, 0 30 0 1 * ?, 0 0 * * * ?, 0 55 0 * * ?, 0 10 0 * * ?, change Scheduled reports delivery times, nightly sync, maintenance window, user sync time, 12.55am-]
Changed lines 1-2 from:
(:title Change the schedule time:)
to:
(:title Change the schedule timing:)
Added lines 1-2:
(:title Change the schedule time:)
March 13, 2014, at 04:59 PM by TimG - updated keywords to include nightly sync hits
Changed line 32 from:
[-keywords: MON-FRI, cron, schedule, changing schedule, 0 20 0 ? * 1, 0 30 0 1 * ?, 0 0 * * * ?, 0 55 0 * * ?, 0 10 0 * * ?, change Scheduled reports delivery times-]
to:
[-keywords: MON-FRI, cron, schedule, changing schedule, 0 20 0 ? * 1, 0 30 0 1 * ?, 0 0 * * * ?, 0 55 0 * * ?, 0 10 0 * * ?, change Scheduled reports delivery times, nightly sync, maintenance window, user sync time, 12.55am-]
Changed line 32 from:
[-keywords: MON-FRI, cron, schedule, changing schedule, 0 20 0 ? * 1, 0 30 0 1 * ?, 0 0 * * * ?, 0 55 0 * * ?, 0 10 0 * * ?-]
to:
[-keywords: MON-FRI, cron, schedule, changing schedule, 0 20 0 ? * 1, 0 30 0 1 * ?, 0 0 * * * ?, 0 55 0 * * ?, 0 10 0 * * ?, change Scheduled reports delivery times-]
Changed line 32 from:
[-keywords: MON-FRI, cron, schedule, changing schedule-]
to:
[-keywords: MON-FRI, cron, schedule, changing schedule, 0 20 0 ? * 1, 0 30 0 1 * ?, 0 0 * * * ?, 0 55 0 * * ?, 0 10 0 * * ?-]
Changed lines 1-2 from:
You can change the time the PaperCut will perform it's nightly maintenance by using the Config Editor. By default these run at 12:55am (i.e. the config setting is @@0 55 12 * * ?@@).
to:
You can change the time the PaperCut will perform it's nightly maintenance by using the Config Editor. By default these run at 12:55am (i.e. the config setting is @@0 55 0 * * ?@@).
Changed lines 1-2 from:
You can change the time the PaperCut will perform it's nightly maintenance by using the Config Editor. By default this is set to 0 15 1 * * ?.
to:
You can change the time the PaperCut will perform it's nightly maintenance by using the Config Editor. By default these run at 12:55am (i.e. the config setting is @@0 55 12 * * ?@@).

Prior to version 11.2 the daily mainitenance tasks were run at 1:15am.  This was changed to avoid issues around daylight savings change overs, which could result in the job not being run
.
Changed line 30 from:
[-keywords: MON-FRI, cron, schedule, -]
to:
[-keywords: MON-FRI, cron, schedule, changing schedule-]
December 02, 2010, at 11:29 PM by Rick - extra tab in a table
Changed lines 8-9 from:
 - YES 0
 Minutes YES 0-59
to:
 - YES 0
 Minutes YES 0-59
Added lines 29-33:

[-keywords: MON-FRI, cron, schedule, -]
----
''Categories:'' [[!Administration]]
----
November 16, 2010, at 11:54 AM by 203.217.70.151 -
Added line 28:
# For the change to take effect, restart the PaperCut Application Server.
July 05, 2010, at 05:09 AM by 202.129.124.120 -
Changed lines 5-6 from:
The format of the value is a string comprised of 6 fields separated by white space. Fields can contain any of the allowed values, along with various combinations of the allowed special characters for that field. The fields are as follows:
to:
The format of the value is a string comprised of 6 fields separated by white space. The format is similar to the "cron" format which is a job scheduler used in linux/unix.Fields can contain any of the allowed values, along with various combinations of the allowed special characters for that field. The fields are as follows:
Changed line 26 from:
# Change the @@Value@@ to @@N@@.
to:
# Change the @@Value@@ as required.
Changed lines 8-9 from:
 - YES 0
 Minutes YES 0-59
to:
 - YES 0
 Minutes YES 0-59
Added lines 1-27:
You can change the time the PaperCut will perform it's nightly maintenance by using the Config Editor. By default this is set to 0 15 1 * * ?.

!!Format

The format of the value is a string comprised of 6 fields separated by white space. Fields can contain any of the allowed values, along with various combinations of the allowed special characters for that field. The fields are as follows:

 Field Name Mandatory Allowed Values
 - YES 0
 Minutes YES 0-59
 Hours YES 0-23
 Day of month YES 1-31 ?
 Month YES 1-12 or JAN-DEC ?
 Day of week YES 1-7 or SUN-SAT ?

The question mark (?) is useful when you need to specify something in one of the two fields in which the character is allowed, but not the other. For example, if I want my maintenance to run on a particular day of the month (say, the 28th), but don't care what day of the week that happens to be, I would put "28" in the day-of-month field, and "?" in the day-of-week field.

 0 15 1 * * ? - Daily 1:15AM
 0  0 4 * * ? - Daily 4:00AM
 0  0 2 * * 1 - Sunday 2:00AM

!!Making changes
To make this change perform the following steps:
# Log into the PaperCut administration interface.
# Navigate to @@Options -> Config editor (advanced)@@.
# Search for the key @@schedule.daily-maintenence@@.
# Change the @@Value@@ to @@N@@.
# Press @@Update@@.

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on April 25, 2019, at 12:17 PM
Printable View   |   Article History   |   Edit Article