New-PveNodesReplicationScheduleNow
Schedule replication job to start as soon as possible.
API: POST /nodes/{node}/replication/{id}/schedule_now, Proxmox VE API viewer
Syntax
Section titled “Syntax”New-PveNodesReplicationScheduleNow [-PveTicket <PveTicket>] -Id <string> -Node <string> [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Id |
string |
Yes | Replication Job ID. The ID is composed of a Guest ID and a job number, separated by a hyphen, i.e. ‘<GUEST>-<JOBNUM>’. |
-Node |
string |
Yes | The cluster node name. |
Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.
Output
Section titled “Output”A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.
