New-PveClusterHaResourcesRelocate
Request resource relocation to another node. This stops the service on the old node, and restarts it on the target node.
API: POST /cluster/ha/resources/{sid}/relocate, Proxmox VE API viewer
Syntax
Section titled “Syntax”New-PveClusterHaResourcesRelocate [-PveTicket <PveTicket>] -Node <string> -Sid <string> [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Node |
string |
Yes | Target node. |
-Sid |
string |
Yes | HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100). |
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.
