Add end user restore documentation

modules/administration-guide/pages/devworkspace-backup.adoc

@@ -14,6 +14,8 @@ integrated registry or link:https://quay.io[Quay.io], to store backup archives a
 
 The backup makes a snapshot of *stopped* Workspace PVCs and stores them as tar.gz archives in the specified OCI registry.
 
+Users can restore backups from the {prod-short} dashboard. See xref:end-user-guide:restoring-a-workspace-from-backup.adoc[].
+
 NOTE: By default, the {devworkspace} backup job is disabled.
 
 You can configure the backup by using the `DevWorkspaceOperatorConfig` resource with the following fields:

modules/end-user-guide/nav.adoc

@@ -17,6 +17,7 @@
 **** xref:url-parameter-for-the-existing-workspace-name.adoc[]
 ** xref:starting-a-workspace-from-a-raw-devfile-url.adoc[]
 ** xref:basic-actions-you-can-perform-on-a-workspace.adoc[]
+** xref:restoring-a-workspace-from-backup.adoc[]
 ** xref:authenticating-to-a-git-server-from-a-workspace.adoc[]
 ** xref:using-the-fuse-overlay-storage-driver.adoc[]
 *** xref:accessing-fuse.adoc[]

modules/end-user-guide/pages/getting-started-with-che.adoc

@@ -13,5 +13,6 @@ If your organization is already running a {prod-short} instance, you can get sta
 * xref:optional-parameters-for-the-urls-for-starting-a-new-workspace.adoc[]
 * xref:starting-a-workspace-from-a-raw-devfile-url.adoc[]
 * xref:basic-actions-you-can-perform-on-a-workspace.adoc[]
+* xref:restoring-a-workspace-from-backup.adoc[]
 * xref:authenticating-to-a-git-server-from-a-workspace.adoc[]
 * xref:using-the-fuse-overlay-storage-driver.adoc[]

modules/end-user-guide/pages/restoring-a-workspace-from-backup.adoc

@@ -0,0 +1,69 @@
+:_content-type: CONCEPT
+:description: Restoring a Che workspace from a DevWorkspace backup
+:keywords: workspace, backup, restore, devworkspace, dashboard
+:navtitle: Restoring a workspace from backup
+:page-aliases:
+
+[id="restoring-a-workspace-from-backup"]
+= Restoring a workspace from backup
+
+When backup is enabled for {devworkspace} instances on your cluster, workspace data can be captured when a workspace stops.
+You can then start a new workspace from an existing backup by using the {prod-short} dashboard.
+
+The main purpose of backing up and restoring workspaces is to recover uncommited source code changes, and push them from the restore workspace. Restored workspaces are created with minimal devfiles, and will not be created with the original project's devfile.
+
+[NOTE]
+====
+Backup storage, registry access, and schedules are configured cluster-wide by administrators in the {devworkspace} Operator.
+For administrator steps, see xref:administration-guide:devworkspace-backup.adoc[].
+====
+
+== Understanding workspace backups
+
+After an administrator enables cluster-wide backups, source code data of stopped workspaces will be backed up in a container image, and automatically pushed to an OCI-compatible registry.
+
+*Internal* backups are backups the {prod-short} dashboard detects and lists.
+On {ocp}, they are represented as `ImageStream` resources in your namespace.
+
+*External* backups are backups from a registry not specified by the administrator when cofiguring cluster-wide backups.
+
+From the dashboard you can:
+
+* Open the list of backups and inspect backup status.
+* Restore a workspace from a backup that is already available to you (*internal* backup), or from an image reference you provide (*external* backup).
+* Choose compute limits and the editor for the new workspace before you start the restore.
+
+When the restored workspace is ready, the dashboard opens it in a new browser tab.
+
+[NOTE]
+====
+A restored workspace is created from a minimal devfile with the restored source code being transfered to the workspace from an init container.
+The *Devfile* tab in the workspace will not show the original devfile from the workspace's Git repository.
+====
+
+== Viewing backups in the dashboard
+
+. In the left sidebar, open *Workspace*.
+. Select the *Backups* tab to see available backups.
+
+.The *Backups* tab in the *Workspace* view
+image::workspace-backup/backups_tab.png[Backups tab in the Workspace view of the dashboard,link="{imagesdir}/workspace-backup/backups_tab.png"]
+
+The *Active* tag represents backups for workspaces that still exist in the current cluster. Conversely, the *Deleted* tag represents backups for workspaces that no longer exist in the current cluster.
+
+== Restoring a workspace
+. On the restore page, set the name for the restored workspace, and choose whether to use an internal backup (represented as an `ImageStream` resource in the cluster) or an external backup by providing your own backup image url.
++
+.Restore mode and backup source
+image::workspace-backup/restore_section_1.png[Choosing internal or external backup when restoring a workspace,link="{imagesdir}/workspace-backup/restore_section_1.png"]
+. Optionally set memory and CPU limits, and the editor to use.
++
+.Resource limits and editor for a restored workspace
+image::workspace-backup/restore_section_2.png[Memory limit CPU limit and editor selection when restoring from backup,link="{imagesdir}/workspace-backup/restore_section_2.png"]
+
+. Start the restore by clicking the *Restore Workspace* button and wait until the workspace is running.
+
+.Additional resources
+
+* link:https://github.com/eclipse-che/che-dashboard/pull/1471[che-dashboard pull request #1471: Backup and restore DevWorkspaces]
+* link:https://github.com/eclipse-che/che-dashboard/pull/1478[che-dashboard pull request #1478: Resource limits and related restore UI improvements]