modification

source/talk.tex

@@ -2,7 +2,8 @@
 \usetheme{poul}
 \usepackage[utf8]{inputenc}
 \usepackage[svgpath=images/]{svg}
-%\usepackage{url}
+\usepackage{graphicx}
+\graphicspath{ {images/} }
 \usepackage[hyphenbreaks]{breakurl}
 \usepackage{hyperref}
 \def\UrlBreaks{\do\/\do-}
@@ -31,6 +32,14 @@
   \end{itemize}
 \end{frame}
 
+\begin{frame}
+  \frametitle{Why do we need backups?}
+  \begin{center}
+    \includegraphics[width=0.7\textwidth]{gitlab}
+  \end{center}
+  \footnotetext{\url{https://twitter.com/gitlabstatus/status/826591961444384768}}
+\end{frame}
+
 \begin{frame}
   \frametitle{What are backups?}
   \begin{block}{Definition}
@@ -42,7 +51,7 @@
 \begin{frame}
   \frametitle{What to backup?}
   It is important to distinguish what it is necessary to backup from what
-  it is not.\\
+  it is not.\\\pause
   Obviously this depends on the setup that you are using (native services, containers, VMs etc...)
 \end{frame}
 
@@ -98,7 +107,7 @@
       \item \textbf{out:} output file/device
     \end{itemize}
   \end{itemize}
-  \vfill
+  \vfill\pause
   \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}
@@ -113,10 +122,10 @@
     \begin{itemize}
       \item \textbf{mapfile:} a human readable text file ddrescue uses to manage the copy
     \end{itemize}
-  \end{itemize}
+  \end{itemize}\pause
   \begin{alertblock}{Caution}
     For the rescued data to be correct, both dd and gddrescue are best used on unmounted devices.
-  \end{alertblock}
+  \end{alertblock}\pause
   \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}
@@ -148,11 +157,13 @@
       \item \textbf{r:} recursive directory option
     \end{itemize}
     \vfill
+    \pause
     \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
+    \pause
     \item rsync -aAXv --exclude={...} /* /backup folder
     \begin{itemize}
       \item backup /* while following symlinks and preserving file properties.
@@ -198,9 +209,9 @@
   \frametitle{duplicity: usage}
   \begin{itemize}
     \item duplicity /home/user scp::/user@host//backup/directory
-    \vfill
+    \vfill\pause
     \item duplicity [restore] scp://user@host//backup/directory /home/user
-    \vfill
+    \vfill\pause
     \item duplicity full /home/user scp::/user@host//backup/directory
   \end{itemize}
 \end{frame}
@@ -212,12 +223,12 @@
     \begin{itemize}
       \item list the files contained in the backup.
     \end{itemize}
-    \vfill
+    \vfill\pause
     \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
+    \vfill\pause
     \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.
@@ -226,16 +237,32 @@
 \end{frame}
 
 \begin{frame}
+    \frametitle{Demo}
+    \begin{center}
+        {\Huge Demo!}
+    \end{center}
 \end{frame}
 
 \begin{frame}
+  \frametitle{Last but not Least}
+  \begin{itemize}
+    \item When you use duplicity with encryption enabled always remember to backup the gpg keys you use to encrypt and sign the backup.\\
+    If you loose them you won't be able to restore the backup.\pause
+    \item Always check that the backup is taking place, don't just assume that everything is working fine because you followed exactly the suggested guide.\pause
+    \item Always try to test that the backup is really working by trying to restore the backup. You'll be surprised to know how many times the backup procedures are not really working, and unfortunately if you do not test them you'll notice it only when the files are gone.
+  \end{itemize}
 \end{frame}
 
 \begin{frame}
-    \frametitle{Demo}
-    \begin{center}
-        {\Huge Demo!}
-    \end{center}
+  \frametitle{Hi again GitLab}
+  \begin{center}
+    \includegraphics[width=0.9\textwidth,height=0.5\textheight]{gitlab2}
+  \end{center}
+  \footnotetext{\url{https://docs.google.com/document/d/1GCK53YDcBWQveod9kfzW-VCxIABGiryG7_z_6jHdVik/pub}}
+  \pause
+  %\footnotesize{I don't want to put shame on GitLab for this incident, but only to use it as a case study.\\ In fact I think that the incident has been managed really well by the GitLab Team.\\
+  %Instead of starting blaming each other and finding silly excuses as usually happens in cases like this, they have been really open from the beginning about the problem and put as a priority the restore of the functionality of the service.}
+
 \end{frame}
 
 \begin{frame}
@@ -245,6 +272,7 @@
         \item \url{https://wiki.archlinux.org/index.php/Duplicity}
         \item \url{http://duplicity.nongnu.org/}
         \item \url{https://www.digitalocean.com/community/tutorials/how-to-use-duplicity-with-gpg-to-securely-automate-backups-on-ubuntu}
+        \item \url{https://github.com/zertrin/duplicity-backup.sh}
     \end{itemize}
 \end{frame}