Day 9: Using server schedules
Yesterday we started with calendar basics. Today we will create our first server schedules. We will also explore the available start and end actions in this bog post.
Creating server schedules
Start your management console or dashboard and open the calendar tab. Click on “Add new item to calendar”. Then select the server as target device:
Some options are now disabled. These options are only available for client computers. We will discuss this in detail tomorrow.
First of all, you have to think about the 3 different possibilities. Use only a start time, use only an end time or use both. Let’s have a look at each.
Only start time
This selection creates an event that is executed exactly once, at the start date and time. You need to select an additional start action, otherwise that type of schedule makes no sense. Most often you like to start your server from standby or hibernation. Therefore select “Wake up”.
In our example, the server will now start at 6 AM on November 25. Without an end time, the server may or may not keep on running. It depends on your other settings like standard action and monitoring.
You can also start a backup after wake up. In that case the server will wake up and run a backup. The server is active during the backup. It depends on your other settings what happens after backup. If you select “Run a backup” without wake up, the backup is only executed if the server is already running.
Conclusion: Use this type of server schedules to wake the server and optionally run a backup.
Only end time
This opposite selection also creates an event which is only executed only once. But now you have to select an end action. Again “do nothing” makes no sense for this type. All other selections will stop the running server. More information on end actions can be found in the manual.
In our example, the server will save energy at 8 AM on November 25. If there are other active sources, like client computers, the selected end action may be skipped. That’s where the “Force” option comes into play. A forced end action will override any other activity except backup and remote access. Have a look at the manual for a detailed discussion on this topic.
If the server is still running at the specified point in time, then the end action is executed. You can use such an action for example, to ensure that your server is saving energy after midnight.
Conclusion: Use this type of server schedules to stop or restart your server.
Using both start and end time
This is the more traditional schedule. You specify a start and an end time. The server is running during that time frame. Again you can combine that with start and end actions. If you like to run your server with a fixed schedule you can, for example, start at 6AM, run until 8 PM and then save energy:
Using recurring plans
Our plans have a little problem. They are only executed once at November 25. This is a good choice for onetime events. Almost always you require a daily or weekly execution. Therefore, we do now add a recurrence. Edit the server schedule again and click on “Recurrence”.
Preselected is a daily recurrence. If you like to use other rules, click on the “Recurrence pattern” and select a hourly, daily, weekly, monthly or yearly recurrence. Again, you can read more on the different recurrence types in the manual. Click “OK” to add the selected recurrence to your schedule.
You learned how to create server schedules with start and end actions. Tomorrow we will do the same for client computers and create client computer schedules.
Here you will find the complete list of all days of our step-by-step series.