Citrix Systems 6 User Manual

149

The exact 

 parameters differ depending on the device 

. See 

 for details of these

parameters across the different storage backends.

sr-destroy

 uuid=

<sr_uuid>

Destroys the specified SR on the XenServer host.

sr-enable-database-replication

 uuid=

<sr_uuid>

Enables xapi database replication to the specified (shared) SR. For example:

xe sr-enable-database-replication uuid=

<sr-uuid>

sr-disable-database-replication

 uuid=

<sr_uuid>

Disables xapi database replication to the specified SR. For example:

xe sr-enable-database-replication uuid=

<sr-uuid>

sr-forget

 uuid=

<sr_uuid>

The 

xapi

 agent forgets about a specified SR on the XenServer host, meaning that the SR is detached and you

cannot access VDIs on it, but it remains intact on the source media (the data is not lost).

sr-introduce

 name-label=

<name>

physical-size=

<physical_size>

type=

<type>

content-type=

<content_type>

uuid=

<sr_uuid>

Just  places  an  SR  record  into  the  database.  The 

device-config

  parameters  are  specified  by 

device-

config:

<parameter_key>

=

<parameter_value>

, for example:

xe sr-introduce device-config:

<device>

=

</dev/sdb1>

This command is never used in normal operation. It is an advanced operation which might
be useful if an SR needs to be reconfigured as shared after it was created, or to help recover
from various failure scenarios.

sr-probe

 type=

<type>

 [host-uuid=

<uuid_of_host>

] [device-config:

<config_name>

=

<value>

]

Performs  a  backend-specific  scan,  using  the  provided 

  keys.  If  the 

  is

complete for the SR backend, then this will return a list of the SRs present on the device, if any. If the 

 parameters are only partial, then a backend-specific scan will be performed, returning results that will

guide you in improving the remaining 

 parameters. The scan results are returned as backend-

specific XML, printed out on the CLI.

The exact 

 parameters differ depending on the device 

. See 

 for details of these

parameters across the different storage backends.

sr-scan

 uuid=

<sr_uuid>