- * Configure all HNs as Hosts (backup/restore targets in BackupPC) per normal
- BackupPC instructions. Until the HNs can be succesfully backed up and
- restored, these operations cannot be successfully completed on any VEs. We
- reccommend the rsync or tar XferMethods, using ssh as a transport. Only
- the rsync method has been tested at this time.
-
- * Install a recent version of rsync (we use 3.0.0pre6+) into each VE. Note
- that a recent version of rsync is also required to successfully perform
- online migration, a very useful ovz function.
+ * Install a recent version of rsync (we use 3.0.0pre6+) into each HN and the
+ BackupPC's VE. A recent version of rsync is also required inside any VE
+ that may be online migrated via vzmigrate when shared storage is not in use.
+ (In otherwords, install rsync 3.0.0pre6+ on all HN's and inside all VEs).
+
+ NOTE: BackupPC doesn't have to be installed in a VE; it could be installed
+ on a separate server. Do not install BackupPC or any other application
+ directly onto an HN (see the BackupPC FAQs).
+
+ * Configure all HNs as Hosts (backup/restore targets in BackupPC) per standard
+ BackupPC instructions and verify that backup and restore operations work
+ correctly. Until the HNs can be succesfully backed up and restored,
+ operations on VE's cannot be successfully completed. We 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. Keys do NOT need to be installed
+ in the VEs themselves.
+
+ * Create the file /etc/backuppc/BackupPC_ovz.hnlist. Its contents should
+ contain the fully qualified hostname of each HN. An example:
+
+ ---- /etc/backuppc/BackupPC_ovz.hnlist ----
+ # List the HNs by hostname of IP address in this file.
+ pe18001.mydomain.com
+ pe18002.mydomain.com
+ pe18003.mydomain.com
+ ---- end of file ----