|
|
@@ -69,12 +69,13 @@
|
|
|
\begin{itemize}
|
|
|
\item /etc
|
|
|
\item /var
|
|
|
+ \item /mnt /media
|
|
|
\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
|
|
|
- \item /dev /mnt /media
|
|
|
+ \item /proc /sys
|
|
|
+ \item /dev /tmp
|
|
|
\end{itemize}
|
|
|
\end{frame}
|
|
|
|
|
|
@@ -104,7 +105,7 @@
|
|
|
\textbf{dd} is a powerful tool that basically can copy everything that is a file or a block device. It is common to use it for disk cloning.\\
|
|
|
Usage example:
|
|
|
\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}}
|
|
|
+ \item \textit{dd if=/dev/sdX of=/dev/sdY conv=fdatasync\footnote{useful to actually wait the end of data transfer and avoid corrupted copies}}
|
|
|
\begin{itemize}
|
|
|
\item \textbf{if:} input file/device
|
|
|
\item \textbf{out:} output file/device
|
|
|
@@ -139,7 +140,7 @@
|
|
|
Also known as an advanced version of cp
|
|
|
\begin{exampleblock}{Pros}
|
|
|
\begin{itemize}
|
|
|
- \item (unlike cp) preserves hard and symbolic links, file permissions and ownerships, modification times, etc.
|
|
|
+ \item (unlike cp) preserves 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}
|
|
|
@@ -161,13 +162,13 @@
|
|
|
\end{itemize}
|
|
|
\vfill
|
|
|
\pause
|
|
|
- \item rsync source host:destination\footnote{But please don't do this \textit{rsync -av --delete source host:$\sim$/}}
|
|
|
+ \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
|
|
|
+ \item rsync -aAXv -{}-exclude=\{...\} /* /backup folder
|
|
|
\begin{itemize}
|
|
|
\item backup /* while following symlinks and preserving file properties.
|
|
|
\end{itemize}
|
|
|
@@ -180,7 +181,7 @@
|
|
|
\vfill
|
|
|
\begin{exampleblock}{Pros}
|
|
|
\begin{itemize}
|
|
|
- \item preserves hard and symbolic links, file permissions and ownership, modification times, etc.
|
|
|
+ \item preserves links, file permissions and ownership, modification times, etc.
|
|
|
\item network efficient.
|
|
|
\item each snapshot contains a full system backup.
|
|
|
\item easy to use.
|
|
|
@@ -199,7 +200,7 @@
|
|
|
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 preserves links, file permissions and ownership, modification times, etc.
|
|
|
\item network efficient.
|
|
|
\item incremental backups.
|
|
|
\item supports storage encryption with gpg.
|
|
|
@@ -290,9 +291,8 @@
|
|
|
\end{frame}
|
|
|
|
|
|
\begin{frame}
|
|
|
- \frametitle{Problems}
|
|
|
- RAID can help in the event of a disk failure, but it doesn't protect us against \textbf{Silent Data Corruption}.\\\pause
|
|
|
- To address this problem new generation filesystems like ZFS or Btrfs have been created. Classical features that we can find in this kind of filesystems are:
|
|
|
+ \frametitle{New generation filesystems}
|
|
|
+ There are new kind of filesystems that try to resolve some problems that we usually have in data storage. The two main examples are ZFS and Btrfs\footnote{Please remind that Btrfs is still in heavy development, before using it in production check at \url{https://btrfs.wiki.kernel.org/index.php/Status} that the features you will need are considered stable.} Classical features that we can find in this kind of filesystems are:
|
|
|
\begin{itemize}
|
|
|
\item CopyOnWrite.
|
|
|
\item Deduplication.
|
