16427: Rename undelete -> recover-collection.

[arvados.git] / doc / admin / recovering-deleted-collections.html.textile.liquid

diff --git a/doc/admin/undeleting-collections.html.textile.liquid b/doc/admin/recovering-deleted-collections.html.textile.liquid
similarity index 72%
rename from doc/admin/undeleting-collections.html.textile.liquid
rename to doc/admin/recovering-deleted-collections.html.textile.liquid
index 461671b53b776d0148250b4f9ab370fec1bcb1ed..59c576ce03c90f08a42426128fcf24afb0a96786 100644 (file)
--- a/doc/admin/undeleting-collections.html.textile.liquid
+++ b/doc/admin/recovering-deleted-collections.html.textile.liquid
@@ -1,7 +1,7 @@
 ---
 layout: default
 navsection: admin
-title: Undeleting collections
+title: Recovering deleted collections
 ...
 
 {% comment %}
@@ -18,14 +18,14 @@ Possibility of recovery depends on many factors, including:
 * Whether the data blocks have been unreferenced long enough to be marked for deletion/trash by keep-balance
 * Blob signature TTL, trash lifetime, trash check interval, and other config settings
 
-To attempt recovery of a previous version of a deleted/modified collection, use the @arvados-server undelete@ command. It should be run on one of your server nodes where the @arvados-server@ package is installed and the @/etc/arvados/config.yml@ file is up to date.
+To attempt recovery of a previous version of a deleted/modified collection, use the @arvados-server recover-collection@ command. It should be run on one of your server nodes where the @arvados-server@ package is installed and the @/etc/arvados/config.yml@ file is up to date.
 
 Specify the collection you want to recover by passing either the UUID of an audit log entry, or a file containing the manifest.
 
-If recovery is successful, the undelete program saves the recovered data a new collection belonging to the system user, and print the new collection's UUID on stdout.
+If recovery is successful, the @recover-collection@ program saves the recovered data a new collection belonging to the system user, and prints the new collection's UUID on stdout.
 
 <pre>
-# arvados-server undelete 9tee4-57u5n-nb5awmk1pahac2t
+# arvados-server recover-collection 9tee4-57u5n-nb5awmk1pahac2t
 INFO[2020-06-05T19:52:29.557761245Z] loaded log entry                              logged_event_time="2020-06-05 16:48:01.438791 +0000 UTC" logged_event_type=update old_collection_uuid=9tee4-4zz18-1ex26g95epmgw5w src=9tee4-57u5n-nb5awmk1pahac2t
 INFO[2020-06-05T19:52:29.642145127Z] recovery succeeded                            UUID=9tee4-4zz18-5trfp4k4xxg97f1 src=9tee4-57u5n-nb5awmk1pahac2t
 9tee4-4zz18-5trfp4k4xxg97f1
@@ -34,4 +34,4 @@ INFO[2020-06-05T19:52:29.644699436Z] exiting
 
 In this example, the original data has been restored and saved in a new collection with UUID @9tee4-4zz18-5trfp4k4xxg97f1@.
 
-For more options, run @arvados-server undelete -help@.
+For more options, run @arvados-server recover-collection -help@.