backup
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
backup [2011/11/03 11:39] – damir | backup [2023/08/21 09:14] (current) – admin | ||
---|---|---|---|
Line 13: | Line 13: | ||
In order to answer to these questions, we prepared some systems (hardware and software) that save/ | In order to answer to these questions, we prepared some systems (hardware and software) that save/ | ||
\\ | \\ | ||
- | **Remember that when we say __home directory__, | + | **Remember that when we say __home directory__, |
- | If a workstation stop working is not a problem, we can repair/ | + | If a workstation stop working is not a problem, we can repair/ |
===== Why ===== | ===== Why ===== | ||
- | The most important thing that humans and computer share is just one: **the data of the users**. No matter what kind of computer, interface, | + | The most important thing that humans and computer share is just one: **the data recorded**. No matter what kind of computer, interface, |
===== How ===== | ===== How ===== | ||
Line 24: | Line 24: | ||
To offer the maximum support to users, our Network has different method to backup the data. Each method has pros and cons, and not all the method are accessible directly to the users. In some cases the user must ask to the System Administrators to recover his/hers data from the backup devices. This is necessary to maintain a good level of compromise between access to data and security. The backups are complete collections of all the data that **all** users collect and thus we have to consider the access to these repositories carefully. | To offer the maximum support to users, our Network has different method to backup the data. Each method has pros and cons, and not all the method are accessible directly to the users. In some cases the user must ask to the System Administrators to recover his/hers data from the backup devices. This is necessary to maintain a good level of compromise between access to data and security. The backups are complete collections of all the data that **all** users collect and thus we have to consider the access to these repositories carefully. | ||
\\ | \\ | ||
- | We have 3 different level of backup that offer access to deleted/ | + | We have 2 different level of backup that offer access to deleted/ |
* Backup in the **[[backup: | * Backup in the **[[backup: | ||
* Backup on **[[backup: | * Backup on **[[backup: | ||
- | * Backup on **[[backup: | ||
==== .snapshot directory ==== | ==== .snapshot directory ==== | ||
- | Every user can find inside | + | we maintain a read-only copy of all data directly in the file server, for up to 3 months. Users can request to access |
- | * hourly.[0-3] | + | the possibilities are: |
- | * nightly.[0-3] | + | * hourly: last 24 hours |
- | * weekly.[0-1] | + | * daily: last 3 months or 90 days |
- | As the name suggest, these directory contain the file changed during the **lasts 4 hours, 4 days and 2 weeks** (the 0 **is** something). If the wanted file was deleted/ | + | |
- | Pay attention that inside the .snapshot directories a user can see the **state** of his/hers directory how it was, so if you look inside one of these directory you can see not only the files changed, but all the files you have currently. Amazing, isn' | + | |
- | If the searched file is found, the users can copy it where it want and the restore is done. | + | |
==== Hard Disk in a central backup sever ==== | ==== Hard Disk in a central backup sever ==== | ||
- | Every day at 00.30 start a backup process that copies | + | On a secondary server, accessible only to Network System admins, we store a copy of all the data/files present in the primary |
- | Not vital files aren't backd up. [[backup: | + | Stored in this server we maintain the **last |
- | \\ | + | |
To retrieve a file from this server the user must ask it to System Administrators, | To retrieve a file from this server the user must ask it to System Administrators, | ||
- | ==== Tape cartridge in central backup server | + | ===== Laptops |
+ | Each Laptop managed by the lab must be configured to backup all the work files using the Backup solution provided by EPFL (aTempo Lina, at the moment). | ||
+ | The backup solution for laptop is under the direct control of the user, please follow strictly the directives so to no lose your data/files. | ||
- | Every day there' | ||
\\ | \\ | ||
- | To access the files stored on tapes the user must ask to the System Administrator that forward his/hers request to the backup | + | \\ |
+ | Please refer to [[backup: | ||
- | ===== Laptops ===== | ||
- | Laptops are the nightmare of any system-manager. Not only they are always a special case, therefore taking the same amount of work as 50 identical workstations, | ||
- | 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, | ||
- | 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. | ||
- | \\ | ||
- | \\ | ||
- | Please refer to [[backup: |
backup.1320316768.txt.gz · Last modified: 2011/11/03 11:39 by damir