diff --git a/datacenter/dtr/2.0/high-availability/backups-and-disaster-recovery.md b/datacenter/dtr/2.0/high-availability/backups-and-disaster-recovery.md
index 4b6d64cfc6..17dbd8e31f 100644
--- a/datacenter/dtr/2.0/high-availability/backups-and-disaster-recovery.md
+++ b/datacenter/dtr/2.0/high-availability/backups-and-disaster-recovery.md
@@ -86,10 +86,9 @@ $ tar -tf /tmp/backup.tar
 
 ## Restore DTR data
 
-You can restore a DTR node from a backup using the `docker/dtr restore`
-command.
 This command performs a fresh installation of DTR, and reconfigures it with
 the configuration created during a backup.
+When restoring, make sure you use the same version of the `docker/dtr` image that you've used to create the backup.
 
 The command starts by installing DTR, restores the configurations stored on
 etcd, and then restores the repository metadata stored on RethinkDB. You
diff --git a/datacenter/dtr/2.1/guides/high-availability/backups-and-disaster-recovery.md b/datacenter/dtr/2.1/guides/high-availability/backups-and-disaster-recovery.md
index fea949c41b..03beb4029f 100644
--- a/datacenter/dtr/2.1/guides/high-availability/backups-and-disaster-recovery.md
+++ b/datacenter/dtr/2.1/guides/high-availability/backups-and-disaster-recovery.md
@@ -81,10 +81,9 @@ $ tar -tf /tmp/backup.tar
 
 ## Restore DTR data
 
-You can restore a DTR node from a backup using the `restore`
-command.
 This command performs a fresh installation of DTR, and reconfigures it with
 the configuration created during a backup.
+When restoring, make sure you use the same version of the `docker/dtr` image that you've used to create the backup.
 
 The command starts by installing DTR, restores the configurations stored on
 etcd, and then restores the repository metadata stored on RethinkDB. You
diff --git a/datacenter/ucp/1.1/high-availability/backups-and-disaster-recovery.md b/datacenter/ucp/1.1/high-availability/backups-and-disaster-recovery.md
index 325d855e47..8202d99f46 100644
--- a/datacenter/ucp/1.1/high-availability/backups-and-disaster-recovery.md
+++ b/datacenter/ucp/1.1/high-availability/backups-and-disaster-recovery.md
@@ -63,6 +63,7 @@ Enter passphrase: secret
 
 The example below shows how to restore a UCP controller node from an existing
 backup.
+When restoring, make sure you use the same version of the `docker/dtr` image that you've used to create the backup.
 
 First find out the Id of the UCP replica you want to restore:
 
diff --git a/datacenter/ucp/2.0/guides/high-availability/backups-and-disaster-recovery.md b/datacenter/ucp/2.0/guides/high-availability/backups-and-disaster-recovery.md
index 5b8ab96d23..b1834e52b3 100644
--- a/datacenter/ucp/2.0/guides/high-availability/backups-and-disaster-recovery.md
+++ b/datacenter/ucp/2.0/guides/high-availability/backups-and-disaster-recovery.md
@@ -59,6 +59,8 @@ $ docker run --rm -i --name ucp \
   docker/ucp restore --passphrase "secret" < backup.tar
 ```
 
+When restoring, make sure you use the same version of the `docker/dtr` image that you've used to create the backup.
+
 ## Restore your cluster
 
 The restore command can be used to create a new UCP cluster from a backup file.
diff --git a/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery.md b/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery.md
index 422717eee3..a251205627 100644
--- a/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery.md
+++ b/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery.md
@@ -77,6 +77,7 @@ $ gpg --decrypt /tmp/backup.tar | tar --list
 ## Restore your cluster
 
 The restore command can be used to create a new UCP cluster from a backup file.
+When restoring, make sure you use the same version of the `docker/dtr` image that you've used to create the backup.
 After the restore operation is complete, the following data will be recovered
 from the backup file: