Change "data store" to "datastore" throughout docs
Before, there were mixed usages of "data store" and "datastore" throughout the docs. This improves consistency in the docs by using only "datastore" throughout. Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
This commit is contained in:
parent
068e526862
commit
092378ba92
|
@ -261,7 +261,7 @@ Creating a Datastore
|
||||||
.. image:: images/screenshots/pbs-gui-datastore-create-general.png
|
.. image:: images/screenshots/pbs-gui-datastore-create-general.png
|
||||||
:width: 230
|
:width: 230
|
||||||
:align: right
|
:align: right
|
||||||
:alt: Create a data store
|
:alt: Create a datastore
|
||||||
|
|
||||||
You can create a new datastore from the web GUI, by navigating to **Datastore** in
|
You can create a new datastore from the web GUI, by navigating to **Datastore** in
|
||||||
the menu tree and clicking **Create**. Here:
|
the menu tree and clicking **Create**. Here:
|
||||||
|
@ -528,15 +528,15 @@ You can monitor the roles of each user using the following command:
|
||||||
│ john@pbs │ /datastore/disk1 │ 1 │ DatastoreAdmin │
|
│ john@pbs │ /datastore/disk1 │ 1 │ DatastoreAdmin │
|
||||||
└──────────┴──────────────────┴───────────┴────────────────┘
|
└──────────┴──────────────────┴───────────┴────────────────┘
|
||||||
|
|
||||||
A single user can be assigned multiple permission sets for different data stores.
|
A single user can be assigned multiple permission sets for different datastores.
|
||||||
|
|
||||||
.. Note::
|
.. Note::
|
||||||
Naming convention is important here. For data stores on the host,
|
Naming convention is important here. For datastores on the host,
|
||||||
you must use the convention ``/datastore/{storename}``. For example, to set
|
you must use the convention ``/datastore/{storename}``. For example, to set
|
||||||
permissions for a data store mounted at ``/mnt/backup/disk4/store2``, you would use
|
permissions for a datastore mounted at ``/mnt/backup/disk4/store2``, you would use
|
||||||
``/datastore/store2`` for the path. For remote stores, use the convention
|
``/datastore/store2`` for the path. For remote stores, use the convention
|
||||||
``/remote/{remote}/{storename}``, where ``{remote}`` signifies the name of the
|
``/remote/{remote}/{storename}``, where ``{remote}`` signifies the name of the
|
||||||
remote (see `Remote` below) and ``{storename}`` is the name of the data store on
|
remote (see `Remote` below) and ``{storename}`` is the name of the datastore on
|
||||||
the remote.
|
the remote.
|
||||||
|
|
||||||
Network Management
|
Network Management
|
||||||
|
@ -700,7 +700,7 @@ Garbage Collection
|
||||||
You can monitor and run :ref:`garbage collection <garbage-collection>` on the
|
You can monitor and run :ref:`garbage collection <garbage-collection>` on the
|
||||||
Proxmox Backup Server using the ``garbage-collection`` subcommand of
|
Proxmox Backup Server using the ``garbage-collection`` subcommand of
|
||||||
``proxmox-backup-manager``. You can use the ``start`` subcommand to manually start garbage
|
``proxmox-backup-manager``. You can use the ``start`` subcommand to manually start garbage
|
||||||
collection on an entire data store and the ``status`` subcommand to see
|
collection on an entire datastore and the ``status`` subcommand to see
|
||||||
attributes relating to the :ref:`garbage collection <garbage-collection>`.
|
attributes relating to the :ref:`garbage collection <garbage-collection>`.
|
||||||
|
|
||||||
|
|
||||||
|
@ -1310,7 +1310,7 @@ Garbage Collection
|
||||||
~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
The ``prune`` command removes only the backup index files, not the data
|
The ``prune`` command removes only the backup index files, not the data
|
||||||
from the data store. This task is left to the garbage collection
|
from the datastore. This task is left to the garbage collection
|
||||||
command. It is recommended to carry out garbage collection on a regular basis.
|
command. It is recommended to carry out garbage collection on a regular basis.
|
||||||
|
|
||||||
The garbage collection works in two phases. In the first phase, all
|
The garbage collection works in two phases. In the first phase, all
|
||||||
|
|
|
@ -22,7 +22,7 @@ Architecture
|
||||||
------------
|
------------
|
||||||
|
|
||||||
Proxmox Backup Server uses a `client-server model`_. The server stores the
|
Proxmox Backup Server uses a `client-server model`_. The server stores the
|
||||||
backup data and provides an API to create and manage data stores. With the
|
backup data and provides an API to create and manage datastores. With the
|
||||||
API, it's also possible to manage disks and other server-side resources.
|
API, it's also possible to manage disks and other server-side resources.
|
||||||
|
|
||||||
The backup client uses this API to access the backed up data. With the command
|
The backup client uses this API to access the backed up data. With the command
|
||||||
|
|
Loading…
Reference in New Issue