Differences

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

--- backup:laptops [2009/08/27 15:53] – cangiani
+++ backup:laptops [2019/11/06 10:44] – admin
@@ Line 3: / Line 3: @@
 The files on a laptop are much more in danger than those on a workstation or on a file server: the laptop HardDisk is smaller and more fragile, the laptop can get stolen or lost, laptops get into many different uncontrolled networks....
 Nevertheless, we know that very few users backup their data on a regular basis.
-As Laptops become more and more convinient to use, the important work data also becomes more and more in danger. It is useless to have a sophisticated centralized backup system as the one described above if users keep their important data on their laptop. So **please backup your work data as often as possible**. Afterall, your work data belongs to EPFL.
+As Laptops become more and more convenient to use, the important work data also becomes more and more in danger. It is useless to have a sophisticated centralized backup system if users keep their important data on their laptop. So **please backup your work data as often as possible**. Afterall, your work data belongs to EPFL.
+===== EPFL Backup System for Laptop ====
+** All Employee of EPFL are required to do regular backups of the laptop computer they use **\\
+For this reason EPFL provide a backup service (Druva InSync) free of charge that every user can request to use, if he/she do not have other solutions.
+to get your Druva InSync account, please contact your system administrator; once installed and configured, the program will backup your files every 4 hours even if you're not connected to EPFL networks.
+===== Personal Laptops =====
+The lab doesn't provide direct support to personal laptops, but you can use different services of our filer structure to your gain. The use of these services as backup system is under your only responsibility, we don't control what you do and how you do it.
+  - Homedir: the home directory is to store your work related documents/programs/stuff, but you can use it also to store some personal related data (protos/images, videos, documents) if the footprint is relatively small (under 100 GB).
+  - Scratch server: The scratch server provide space for everyone and there's no limit on the use of it. plesae use it as you like, but adopt a fair play policy, as everyone in the lab will need to store data.
+  - google disk/dropbox/microsoft onedrive: these and others internet services are offering storage space for your personal data, **but their storage/use policy is against the rules of EPFL, the European GDPR and/or the Swiss laws regarding privacy** . We do not recommend using them.
 ===== Syncronizing work stuff with Unison =====
-[[http://www.cis.upenn.edu/~bcpierce/unison/|Unison]] is a very fast, efficient and easy to use file-synchronization tool for Unix and Windows.
+[[http://www.cis.upenn.edu/~bcpierce/unison/|Unison]] is a very fast, efficient and easy to use file-synchronization tool for Unix (Linux and Apple OsX) and Windows.
 Note that, although very convenient, **Unison is not a real backup tool**: it does not keep an history of files, and it tends to replicate mistakes instead of repearing them (a file deleted by mistake on one machine will be deleted also on the other machine). On the other hand, we keep various backup of your home directory on the server. Therefore keeping your laptop in sync with your directory on our file-server is almost like backing it up.
@@ Line 103: / Line 117: @@
 If D is renamed to D' on the remote machine, and this change is propagated to the local machine, all such files or subdirectories P will be deleted. This is because Unison sees the rename as a delete and a separate create: **it deletes the old directory (including the ignored files) and creates a new one** (notincluding the ignored files, since they are completely invisible to it).
 </note>
 ==== Do it! ====
 Now that you've prepared and tested your perfect configuration file, it is time to make sure that unison is executed periodically. On unix (linux and mac) you can symply call unison from a script like the following:
@@ Line 144: / Line 157: @@
   if [ $? -eq 0 ] ; then
     msg=$(grep "Synchronization complete" $ofile; grep "Nothing to do:" $ofile)
-#    notify-send -u low "Unison Sync OK" "$msg"                  # linux version
+#    DISPLAY=:0.0 notify-send -u low "Unison Sync OK" "$msg"                  # linux version
     growlnotify --title "Unison Sync OK" -p Low -m "$msg"       # mac version
   else
@@ Line 150: / Line 163: @@
     msg2=$(grep '<-?->' $ofile | grep "new file" | head -n 1)
     msg3=$(grep '<-?->' $ofile | grep "changed" | head -n 1)
-#    notify-send -u critical -t 0 "Unison Sync Err" "$msg1 $msg2 $msg3"        # linux version
+#    DISPLAY=:0.0 notify-send -u critical -t 0 "Unison Sync Err" "$msg1 $msg2 $msg3"        # linux version
     growlnotify --title "Unison Sync Err" -s -p High -m "$msg1 $msg2 $msg3"   # mac version
   fi
@@ Line 158: / Line 171: @@
 {{backup:unison.sh|Here}} is the file I actually use.