replication.get_instance ======================== Returns instance matching `id`. If `id` is not found, Validation error is raised. Please see `query` method documentation for `options`. .. raw:: html
Query options customize the results returned by a query method. More complete documentation with examples
are covered in the "Query methods" section of the TrueNAS API documentation.
Extra options are defined on a per-endpoint basis and are described in the documentation for the associated
query method.
An array of field names describing the manner in which query results should be ordered. The field names may
also have one of more of the following special prefixes: -
(reverse sort direction), nulls_first:
(place
any null values at the head of the results list), nulls_last:
(place any null values at the tail of the
results list).
[
"size",
"-devname",
"nulls_first:-expiretime"
]
An array of field names specifying the exact fields to include in the query return. The dot character .
may be used to explicitly select only subkeys of the query result.
[
"username",
"Authentication.status"
]
Return a numeric value representing the number of items that match the specified query-filters
.
Return the JSON object of the first result matching the specified query-filters
. The query fails
if there specified query-filters
return no results.
This specifies the beginning offset of the results array. When combined with the limit
query-option
it may be used to implement pagination of large results arrays. WARNING: some query methods provide
volatile results and the onus is on the developer to understand whether pagination is appropriate
for a particular query API method.
This specifies the maximum number of results matching the specified query-filters
to return. When
combined wtih the offset
query-option it may be used to implement pagination of large results arrays.
WARNING: some query methods provide volatile results and the onus is on the developer to understand whether
pagination is appropriate for a particular query API method.
name for replication task
Must be at least 1
characters long
whether task will PUSH
or PULL
snapshots
method of snapshots transfer
* SSH
transfers snapshots via SSH connection. This method is supported everywhere but does not achieve
great performance
* SSH+NETCAT
uses unencrypted connection for data transfer. This can only be used in trusted networks
and requires a port (specified by range from netcat_active_side_port_min
to netcat_active_side_port_max
)
to be open on netcat_active_side
* LOCAL
replicates to or from localhost
Keychain Credential of type SSH_CREDENTIALS
Distinguishes this Keychain Credential from others.
Must be at least 1
characters long
At least one of the two keys must be provided on creation.
No Additional PropertiesCan be omitted and automatically derived from the private key.
Keychain Credential ID.
Can be discovered with keychaincredential.remotesshhostkeyscan.
Value must be greater or equal to 1
and lesser or equal to 65535
Value must be greater or equal to 1
and lesser or equal to 65535
whether SSH
and SSH+NETCAT
transports should use sudo (which is expected to be passwordless) to run zfs
command on the remote machine.
list of datasets to replicate snapshots from
Must contain a minimum of 1
items
dataset to put snapshots into
whether we should send dataset properties along with snapshots
Must be at least 1
characters long
Each additional property must conform to the following schema
Type: stringlist of periodic snapshot tasks that are sources of snapshots for this replication task. Only push replication
tasks can be bound to periodic snapshot tasks.
"00" - "23"
"1" - "31"
"1" (January) - "12" (December)
"1" (Monday) - "7" (Sunday)
list of naming schemas for pull replication
No Additional Itemslist of naming schemas for push replication
No Additional Itemsreplicate all snapshots which names match specified regular expression
Must be at least 1
characters long
allows replication to run automatically on schedule or after bound periodic snapshot task
schedule to run replication task. Only auto
replication tasks without bound periodic snapshot tasks can have a
schedule
"00" - "23"
"1" - "31"
"1" (January) - "12" (December)
"1" (Monday) - "7" (Sunday)
restricts when replication task with bound periodic snapshot tasks runs. For example, you can have periodic
snapshot tasks that run every 15 minutes, but only run replication task every hour.
"00" - "23"
"1" - "31"
"1" (January) - "12" (December)
"1" (Monday) - "7" (Sunday)
will only replicate snapshots that match schedule
or restrict_schedule
will destroy all snapshots on target side and replicate everything from scratch if none of the snapshots on
target side matches source snapshots
controls destination datasets readonly property:
* SET
will set all destination datasets to readonly=on after finishing the replication
* REQUIRE
will require all existing destination datasets to have readonly=on property
* IGNORE
will avoid this kind of behavior
will prevent source snapshots from being deleted by retention of replication fails for some reason
specifies how to delete old snapshots on target side:
* SOURCE
deletes snapshots that are absent on source side
* CUSTOM
deletes snapshots that are older than lifetime_value
and lifetime_unit
* NONE
does not delete any snapshots
Value must be greater or equal to 1
Each field can either be a single value or a comma-separated list of values.
A "*" represents the full list of values.
"00" - "59"
"00" - "23"
"1" - "31"
"1" (January) - "12" (December)
"1" (Monday) - "7" (Sunday)
Value must be greater or equal to 1
compresses SSH stream. Available only for SSH transport
limits speed of SSH stream. Available only for SSH transport
Value must be greater or equal to 1
number of retries before considering replication failed
Value must be greater or equal to 1