some work

source/talk.tex

@@ -48,11 +48,13 @@
   \begin{itemize}
     \item /home
   \end{itemize}
+  \vfill
   At your discretion:
   \begin{itemize}
     \item /etc
     \item /var
   \end{itemize}
+  \vfill
   Not necessary\footnote{if these folders contain something important probably you are doing something wrong in your setup}:
   \begin{itemize}
     \item /proc /sys /tmp
@@ -61,7 +63,7 @@
 \end{frame}
 
 \begin{frame}
-  \framtetitle{Backup types}
+  \frametitle{Backup types}
   Backups can be:
   \begin{itemize}
     \item \textbf{full}: a complete backup of a all files and folder starting from a root node.
@@ -88,20 +90,157 @@
   \begin{itemize}
     \item \textit{dd if=/dev/sdX of=/dev/sdY \&\& sync\footnote{useful to actually wait the end of data transfer and avoid corrupted copies}}
     \begin{itemize}
-      \textbf{if:} input file/device
-      \textbf{out:} output file/device
+      \item \textbf{if:} input file/device
+      \item \textbf{out:} output file/device
     \end{itemize}
   \end{itemize}
+  \vfill
   \begin{alertblock}{Caution}
     Since \textbf{dd} often requires \textit{sudo} privileges to run, if you mismatch the name of a device you can actually wipe the content of your primary hard disk, double check always the arguments before pressing enter.
   \end{alertblock}
+\end{frame}
+
+\begin{frame}
+  \frametitle{GNU ddrescue}
+  gdrescue is an enhanced version of dd that tries to rescue good parts in case of read errors. It may be usefull to recover data from a drive with some damaged sector.\\
+  Usage Example:
+  \begin{itemize}
+    \item \textit{ddrescue [options] /dev/sdX outfile mapfile}
+    \begin{itemize}
+      \item \textbf{mapfile:} a human readable text file ddrescue uses to manage the copy
+    \end{itemize}
+  \end{itemize}
+  \begin{alertblock}{Caution}
+    For the rescued data to be correct, both dd and gddrescue are best used on unmounted devices.
+  \end{alertblock}
+  \begin{block}{Tip}
+    gddrescue can also be useful when trying to reallocate sectors on a drive with a few sector unreadable. Doing a wipe of the drive with gddrescue should reallocate bad sectors.
+  \end{block}
+\end{frame}
+
+\begin{frame}
+  \frametitle{rsync}
+  Also known as an advanced version of cp
+  \begin{exampleblock}{Pros}
+    \begin{itemize}
+      \item (unlike cp) preserves hard and symbloic links, file permissions and ownerships, modification times, etc.
+      \item designed to be network efficient because only transfers file changes.
+      \item easy to use.
+    \end{itemize}
+  \end{exampleblock}
+  \begin{alertblock}{Cons}
+    \begin{itemize}
+      \item no storage encryption.
+    \end{itemize}
+  \end{alertblock}
+\end{frame}
+
+\begin{frame}
+  \frametitle{rsync: usage}
+  \begin{itemize}
+    \item rsync -Pr source destination
+    \begin{itemize}
+      \item \textbf{P:} keep partially transferred files if the transfer is interrupted.
+      \item \textbf{r:} recursive directory option
+    \end{itemize}
+    \vfill
+    \item rsync source host:destination\footnote{But please don't do this \textit{rsync -av --delete source host:$\sim$/}}
+    \begin{itemize}
+      \item uses ssh by default, but can also be forced with the -e ssh option.
+    \end{itemize}
+    \vfill
+    \item rsync -aAXv --exclude={...} /* /backup folder
+    \begin{itemize}
+      \item backup /* while following symlinks and preserving file properties.
+    \end{itemize}
+  \end{itemize}
+\end{frame}
+
+\begin{frame}
+  \frametitle{rsnapshot: rsync automated}
+  rsnapshot produces automated, periodical system snapshots
+  \vfill
+  \begin{exampleblock}{Pros}
+    \begin{itemize}
+      \item preserves hard and symbolic links, file permissions and ownership, modification times, etc.
+      \item network efficient.
+      \item each snapshot contains a full system backup.
+      \item easy to use.
+    \end{itemize}
+  \end{exampleblock}
+  \vfill
+  \begin{alertblock}{Cons}
+    \begin{itemize}
+      \item no storage encryption.
+    \end{itemize}
+  \end{alertblock}
+\end{frame}
 
+\begin{frame}
+  \frametitle{duplicity}
+  duplicity produces encrypted, incremental backups in tar format.
+  \begin{exampleblock}{Pros}
+    \begin{itemize}
+      \item preserves hard and symbolic links, file permissions and ownership, modification times, etc.
+      \item network efficient.
+      \item incremental backups.
+      \item supports storage encryption with gpg.
+      \item easy to use.
+    \end{itemize}
+  \end{exampleblock}
+\end{frame}
+
+\begin{frame}
+  \frametitle{duplicity: usage}
+  \begin{itemize}
+    \item duplicity /home/user scp::/user@host//backup/directory
+    \vfill
+    \item duplicity [restore] scp://user@host//backup/directory /home/user
+    \vfill
+    \item duplicity full /home/user scp::/user@host//backup/directory
+  \end{itemize}
+\end{frame}
+
+\begin{frame}
+  \frametitle{duplicity: usage}
+  \begin{itemize}
+    \item duplicity list-current-files scp::/user@host//backup/directory
+    \begin{itemize}
+      \item list the files contained in the backup.
+    \end{itemize}
+    \vfill
+    \item duplicity [restore] -t 3D scp://user@host//backup/directory /home/user
+    \begin{itemize}
+      \item specify the time from which to restore files.
+    \end{itemize}
+    \vfill
+    \item duplicity remove-older-than 30D scp::/user@host//backup/directory
+    \begin{itemize}
+      \item remove from the backup full backups older than the specified period.
+    \end{itemize}
+  \end{itemize}
+\end{frame}
+
+\begin{frame}
+\end{frame}
+
+\begin{frame}
+\end{frame}
+
+\begin{frame}
 \end{frame}
 
 \begin{frame}
 \end{frame}
 
 \begin{frame}
+  \frametitle{License}
+  \begin{center}
+    {\large Thank you!}
+    \vfill
+    \includesvg[height=1.5cm]{by-sa}\\
+    {\footnotesize These slides are published under a Creative Commons Attribution-ShareAlike 4.0 license.}
+  \end{center}
 \end{frame}
 
 \end{document}