Add SSH key notes and the tested configuration.

diff --git a/README b/README
index 375aee8096ebf2b10469ad3904eb059b8e13a7c9..a2c27875e5820fa9475ec19e369973e340eae1ee 100644 (file)
--- a/README
+++ b/README
@@ -87,6 +87,12 @@ To install BackupPC_ovz:
    reccommend the rsync or tar XferMethods, using ssh as a transport.  Only
    the rsync method has been tested at this time.
 
+   - On the BackupPC SSH FAQ, there are instructions for installing an SSH
+     key on servers to be backed up by BackupPC.  Because VEs are actually
+     backed up and restored through the context of the hardware node (HN),
+     only the HNs need to have the keys.  They do NOT need to be installed
+     in the VEs themselves.
+
  * Install a recent version of rsync (we use 3.0.0pre6+) into each HN.  Note
    that a recent version of rsync is also required inside the VE to
    successfully perform online migration without shared storage.
@@ -161,3 +167,16 @@ hosted the VE before.
    files from the VE's /etc/vzdump directory into the appropriate locations
    of the HN's /etc/vz/conf directory.
  * Start the VE using ovz's vzctl utiltiy.
+
+Configurations Tested:
+
+ * Twin Dell PowerEdge 1800 servers (the HNs).
+   Running a minimal Ubuntu Gutsy server OS.
+   Raid disks running under LVM2.
+   XFS filesystem for VE private areas.
+ * BackupPC running as a VE on one of the PE1800's.
+ * A number of other VE's distributed between the two PE1800's.
+ * VEs running various OS's: Mandrake 2006, Ubuntu Feisty, Ubuntu Gutsy.
+ * VE backups and restores using the rsync method.
+ * All VEs and HNs have rsync 3.0.0pre6 or newer installed.
+