---------------
{pve} has a very flexible replication scheduler. It is based on the systemd
-time calendar event format.footnote:[see `man 7 sytemd.time` for more information]
+time calendar event format.footnote:[see `man 7 systemd.time` for more information]
Calendar events may be used to refer to one or more points in time in a
single expression.
To allow easier and shorter configuration one or more repetition times can
be set. They indicate that on the start-time(s) itself and the start-time(s)
plus all multiples of the repetition value replications will be done. If
-you want to start replication at 8 AM and repeat it every 15 minutes you
-would use: `'8:00/15'`
+you want to start replication at 8 AM and repeat it every 15 minutes until
+9 AM you would use: `'8:00/15'`
Here you see also that if no hour separation (`:`) is used the value gets
interpreted as minute. If such a separation is used the value on the left
[width="100%",options="header"]
|==============================================================================
|Schedule String |Alternative |Meaning
-|mon,tue,wed,thu,fri |mon..fri |All working days at 0:00
-|sat,sun |sat..sun |Only on weekend at 0:00
+|mon,tue,wed,thu,fri |mon..fri |Every working day at 0:00
+|sat,sun |sat..sun |Only on weekends at 0:00
|mon,wed,fri |-- |Only on Monday, Wednesday and Friday at 0:00
-|12:05 |12:05 |All weekdays at 12:05 PM
-|*/5 |0/5 |Every day all five minutes
+|12:05 |12:05 |Every day at 12:05 PM
+|*/5 |0/5 |Every five minutes
|mon..wed 30/10 |mon,tue,wed 30/10 |Monday, Tuesday, Wednesday 30, 40 and 50 minutes after every full hour
-|mon..fri 8..17,22:0/15 |-- |All working days every 15 minutes between 8 AM and 5 PM plus at 10 PM
+|mon..fri 8..17,22:0/15 |-- |Every working day every 15 minutes between 8 AM and 6 PM and between 10 PM and 11 PM
|fri 12..13:5/20 |fri 12,13:5/20 |Friday at 12:05, 12:25, 12:45, 13:05, 13:25 and 13:45
-|12..22:5/2 |12:5/2 |Every day starting at 12:05 until 22:05 all 2 hours
+|12,14,16,18,20,22:5 |12/2:5 |Every day starting at 12:05 until 22:05, every 2 hours
|* |*/1 |Every minute (minimum interval)
|==============================================================================
WARNING: If expected votes are set avoid changes which affect the cluster
(for example adding/removing nodes, storages, virtual guests) at all costs.
-Only use it to get vital guests up and running again or to resolve to quorum
+Only use it to get vital guests up and running again or to resolve the quorum
issue itself.
- move both guest configuration files form the origin node A to node B:
+
----
-# mv /etc/pve/node/A/qemu-server/100.conf /etc/pve/node/B/qemu-server/100.conf
-# mv /etc/pve/node/A/lxc/200.conf /etc/pve/node/B/lxc/200.conf
+# mv /etc/pve/nodes/A/qemu-server/100.conf /etc/pve/nodes/B/qemu-server/100.conf
+# mv /etc/pve/nodes/A/lxc/200.conf /etc/pve/nodes/B/lxc/200.conf
----
- Now you can start the guests again:
Managing Jobs
-------------
+[thumbnail="screenshot/gui-qemu-add-replication-job.png"]
+
You can use the web GUI to create, modify and remove replication jobs
easily. Additionally the command line interface (CLI) tool `pvesr` can be
used to do this.
guest) in the web GUI. They differ in what jobs get shown: all, only node
specific or only guest specific jobs.
-// TODO insert auto generated images of add web UI dialog
-
Once adding a new job you need to specify the virtual guest (if not already
selected) and the target node. The replication
xref:pvesr_schedule_time_format[schedule] can be set if the default of `all
Command Line Interface Examples
-------------------------------
-Create a replication job which will run all 5 min with limited bandwidth of
+Create a replication job which will run every 5 minutes with limited bandwidth of
10 mbps (megabytes per second) for the guest with guest ID 100.
----