Differences

This shows you the differences between two versions of the page.

--- userdoc:tt_tarsnap_online_backup [2018/09/29 15:47] – [Restore to a New Install] abelbeck
+++ userdoc:tt_tarsnap_online_backup [2019/11/21 16:18] (current) – [Restore to a New Install] mkeuter
@@ Line 148: / Line 148: @@
   tarsnap-backup --uninstall-cronjob
+!!Tip:!! Don't use a cronjob between 02:00 and 03:00 in the night, because of DST switching :-).
 \\
@@ Line 175: / Line 177: @@
 !!Note ->!! If you restore to a different media than the original, you need to run this command afterwards to re-create the [[https://www.tarsnap.com/cachedir.html|cache directory]] and to be able to create backups again ((This option is not listed in the program help!)):
-  tarsnap –-fsck
+  tarsnap --fsck
 \\
@@ Line 186: / Line 188: @@
 !!Warning ->!! You should not use a Tarsnap Backup to "clone" an active system to create a new install, as that will duplicate private keys (SSH, VPN, etc.) which must be unique across deployed systems.
-First, configure AstLinux using the standard **[[userdoc:new-install|New Install]]**.  Set the Management Password via the web interface, it may be different from the backup if you wish.
+First, configure AstLinux using the standard **[[userdoc:new-install|New Install]]**.\\
+Set the "Management Password" via the web interface, it may be different from what is archived in the Tarsnap Backup if you wish.
 Then, using the CLI, create the tarsnap directory:
@@ Line 197: / Line 200: @@
   tarsnap -xvf machine-kd-archive -C /mnt/kd
+!!Note ->!! We are skipping restoring the ''machine-asturw-archive'' to ''/oldroot/mnt/asturw'' as it may be hardware specific and the "Management Password" was set above.
 Resync the tarsnap cache directory:
-  tarsnap –-fsck
+  tarsnap --fsck
+Finally, Reboot the system to use the restored data.
 \\