]> git.proxmox.com Git - pve-docs.git/blame - pvesr.1-synopsis.adoc
add VLAN explanation.] add VLAN explanation.
[pve-docs.git] / pvesr.1-synopsis.adoc
CommitLineData
efcfc6d8
DM
1*pvesr* `<COMMAND> [ARGS] [OPTIONS]`
2
5d9c884c
DM
3*pvesr create-local-job* `<id> <target>` `[OPTIONS]`
4
5Create a new replication job
6
7`<id>`: `[1-9][0-9]{2,8}-\d{1,9}` ::
8
9Replication Job ID. The ID is composed of a Guest ID and a job number, separated by a hyphen, i.e. '<GUEST>-<JOBNUM>'.
10
11`<target>`: `<string>` ::
12
13Target node.
14
2489d6df 15`--comment` `<string>` ::
5d9c884c
DM
16
17Description.
18
2489d6df 19`--disable` `<boolean>` ::
5d9c884c
DM
20
21Flag to disable/deactivate the entry.
22
2489d6df 23`--rate` `<number> (1 - N)` ::
5d9c884c
DM
24
25Rate limit in mbps (megabytes per second) as floating point number.
26
2489d6df 27`--remove_job` `<full | local>` ::
5d9c884c
DM
28
29Mark the replication job for removal. The job will remove all local replication snapshots. When set to 'full', it also tries to remove replicated volumes on the target. The job then removes itself from the configuration file.
30
2489d6df 31`--schedule` `<string>` ('default =' `*/15`)::
5d9c884c
DM
32
33Storage replication schedule. The format is a subset of `systemd` calender events.
34
35
36
37*pvesr delete* `<id>` `[OPTIONS]`
38
39Mark replication job for removal.
40
41`<id>`: `[1-9][0-9]{2,8}-\d{1,9}` ::
42
43Replication Job ID. The ID is composed of a Guest ID and a job number, separated by a hyphen, i.e. '<GUEST>-<JOBNUM>'.
44
2489d6df 45`--force` `<boolean>` ('default =' `0`)::
5d9c884c
DM
46
47Will remove the jobconfig entry, but will not cleanup.
48
2489d6df 49`--keep` `<boolean>` ('default =' `0`)::
5d9c884c
DM
50
51Keep replicated data at target (do not remove).
52
53
54
55
56*pvesr disable* `<id>`
57
58Disable a replication job.
59
60`<id>`: `[1-9][0-9]{2,8}-\d{1,9}` ::
61
62Replication Job ID. The ID is composed of a Guest ID and a job number, separated by a hyphen, i.e. '<GUEST>-<JOBNUM>'.
63
64
65
66*pvesr enable* `<id>`
67
68Enable a replication job.
69
70`<id>`: `[1-9][0-9]{2,8}-\d{1,9}` ::
71
72Replication Job ID. The ID is composed of a Guest ID and a job number, separated by a hyphen, i.e. '<GUEST>-<JOBNUM>'.
73
74
75
76*pvesr finalize-local-job* `<id> [<extra-args>]` `[OPTIONS]`
77
78Finalize a replication job. This removes all replications snapshots with
79timestamps different than <last_sync>.
80
81`<id>`: `[1-9][0-9]{2,8}-\d{1,9}` ::
82
83Replication Job ID. The ID is composed of a Guest ID and a job number, separated by a hyphen, i.e. '<GUEST>-<JOBNUM>'.
84
85`<extra-args>`: `<array>` ::
86
87The list of volume IDs to consider.
88
2489d6df 89`--last_sync` `<integer> (0 - N)` ::
5d9c884c
DM
90
91Time (UNIX epoch) of last successful sync. If not specified, all replication snapshots gets removed.
92
93
94
95
efcfc6d8
DM
96*pvesr help* `[<cmd>]` `[OPTIONS]`
97
98Get help about specified command.
99
100`<cmd>`: `<string>` ::
101
102Command name
103
2489d6df 104`--verbose` `<boolean>` ::
efcfc6d8
DM
105
106Verbose output format.
107
108
109
110
5d9c884c 111*pvesr list*
efcfc6d8
DM
112
113List replication jobs.
114
115
116
117
5d9c884c
DM
118*pvesr prepare-local-job* `<id> [<extra-args>]` `[OPTIONS]`
119
120Prepare for starting a replication job. This is called on the target node
121before replication starts. This call is for internal use, and return a JSON
122object on stdout. The method first test if VM <vmid> reside on the local
123node. If so, stop immediately. After that the method scans all volume IDs
124for snapshots, and removes all replications snapshots with timestamps
125different than <last_sync>. It also removes any unused volumes. Returns a
126hash with boolean markers for all volumes with existing replication
127snapshots.
128
129`<id>`: `[1-9][0-9]{2,8}-\d{1,9}` ::
130
131Replication Job ID. The ID is composed of a Guest ID and a job number, separated by a hyphen, i.e. '<GUEST>-<JOBNUM>'.
132
133`<extra-args>`: `<array>` ::
134
135The list of volume IDs to consider.
136
2489d6df 137`--force` `<boolean>` ('default =' `0`)::
5d9c884c
DM
138
139Allow to remove all existion volumes (empty volume list).
140
2489d6df 141`--last_sync` `<integer> (0 - N)` ::
5d9c884c
DM
142
143Time (UNIX epoch) of last successful sync. If not specified, all replication snapshots get removed.
144
2489d6df 145`--parent_snapname` `<string>` ::
5d9c884c
DM
146
147The name of the snapshot.
148
2489d6df 149`--scan` `<string>` ::
5d9c884c
DM
150
151List of storage IDs to scan for stale volumes.
152
153
154
155
156*pvesr read* `<id>`
157
158Read replication job configuration.
159
160`<id>`: `[1-9][0-9]{2,8}-\d{1,9}` ::
161
162Replication Job ID. The ID is composed of a Guest ID and a job number, separated by a hyphen, i.e. '<GUEST>-<JOBNUM>'.
163
164
165
166
167*pvesr run* `[OPTIONS]`
168
169This method is called by the systemd-timer and executes all (or a specific)
170sync jobs.
171
2489d6df 172`--id` `[1-9][0-9]{2,8}-\d{1,9}` ::
5d9c884c
DM
173
174Replication Job ID. The ID is composed of a Guest ID and a job number, separated by a hyphen, i.e. '<GUEST>-<JOBNUM>'.
175
2489d6df 176`--verbose` `<boolean>` ('default =' `0`)::
5d9c884c
DM
177
178Print more verbose logs to stdout.
179
180
181
182
183*pvesr schedule-now* `<id>`
184
185Schedule replication job to start as soon as possible.
186
187`<id>`: `[1-9][0-9]{2,8}-\d{1,9}` ::
188
189Replication Job ID. The ID is composed of a Guest ID and a job number, separated by a hyphen, i.e. '<GUEST>-<JOBNUM>'.
190
191
192
193
194*pvesr set-state* `<vmid> <state>`
195
196Set the job replication state on migration. This call is for internal use.
197It will accept the job state as ja JSON obj.
198
199`<vmid>`: `<integer> (1 - N)` ::
200
201The (unique) ID of the VM.
202
203`<state>`: `<string>` ::
204
205Job state as JSON decoded string.
206
207
208
209
210*pvesr status* `[OPTIONS]`
211
212List status of all replication jobs on this node.
213
2489d6df 214`--guest` `<integer> (1 - N)` ::
5d9c884c
DM
215
216Only list replication jobs for this guest.
217
218
219
220
221*pvesr update* `<id>` `[OPTIONS]`
222
223Update replication job configuration.
224
225`<id>`: `[1-9][0-9]{2,8}-\d{1,9}` ::
226
227Replication Job ID. The ID is composed of a Guest ID and a job number, separated by a hyphen, i.e. '<GUEST>-<JOBNUM>'.
228
2489d6df 229`--comment` `<string>` ::
5d9c884c
DM
230
231Description.
232
2489d6df 233`--delete` `<string>` ::
5d9c884c
DM
234
235A list of settings you want to delete.
236
2489d6df 237`--digest` `<string>` ::
5d9c884c
DM
238
239Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
240
2489d6df 241`--disable` `<boolean>` ::
5d9c884c
DM
242
243Flag to disable/deactivate the entry.
244
2489d6df 245`--rate` `<number> (1 - N)` ::
5d9c884c
DM
246
247Rate limit in mbps (megabytes per second) as floating point number.
248
2489d6df 249`--remove_job` `<full | local>` ::
5d9c884c
DM
250
251Mark the replication job for removal. The job will remove all local replication snapshots. When set to 'full', it also tries to remove replicated volumes on the target. The job then removes itself from the configuration file.
252
2489d6df 253`--schedule` `<string>` ('default =' `*/15`)::
efcfc6d8 254
5d9c884c 255Storage replication schedule. The format is a subset of `systemd` calender events.
efcfc6d8
DM
256
257
258
259