backup:snapshot
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
backup:snapshot [2007/02/23 19:06] – created damir | backup:snapshot [2015/07/01 15:42] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | Every user can find inside his/hers homedir on the central filer an hidden directory named **.snapshot**. Inside this directory exists others directories that have name | + | A photograph is something that stop the time. Whatever else you do, or how you change after taking |
- | * hourly.[0-3] | + | |
- | * nightly.[0-3] | + | |
- | * weekly.[0-1] | + | |
- | As the name suggest, these directory contain | + | |
- | < | + | A **snapshot** in our case is the same thing, but related to file and directories. If we take a **snapshot** of a particular directory or file, we can always access this file **as it was**, no matter how much we changed the file or if the file was completely deleted. We can access this type of information at least until we delete the **snapshot** we took. |
- | Pay attention that inside the .snapshot directories a user can see the **state** of his/hers directory how it was at the time of **snaphot**, so looking | + | |
+ | |||
+ | ===== For NetApp Filer Users (IPG users) ===== | ||
+ | |||
+ | ==== How it works ==== | ||
+ | The filer that serve the IPG user create these **snapshots** automatically and in a trasparent fashion, the user's don't have to manage any configuration to activate this feature. | ||
+ | The system generate a **snapshot** of the user's directory every hour and save it in a separate space (not really, but just to maintain the things simple). The users can access these data just browsing the homedir. No need to use some strange and unfriendly software. | ||
+ | Maintaining a copy of every modify of a file is impossible, so the **snapshots** are created at regular intervals every hour and then every day and then every week. With this mechanism the user can access his/hers old file inside an hidden directory named **.snapshot** resident in the homedir. Inside this directory exists others directories that have name | ||
+ | * hourly.[0-23] | ||
+ | * nightly.[0-6] | ||
+ | * weekly.[0-3] | ||
+ | As the name suggest, these directory contain the files changed during the lasts 24 hours, 7 days and 4 weeks. 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 | ||
+ | If the file is found, the users can copy it where it want and the restore is done (the .snapshot directories are accessible only in read mode). | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ==== User point of view ==== | ||
+ | |||
+ | Every user of the labs can find inside his/hers homedir on the central filer an hidden directory named **.snapshot**. Inside this directory exists others directories: | ||
+ | < | ||
+ | ls .snapshot/ | ||
+ | hourly.0 | ||
+ | hourly.1 | ||
+ | hourly.... | ||
+ | nightly.0 | ||
+ | nightly.1 | ||
+ | nightly.... | ||
+ | weekly.0 | ||
+ | weekly.1 | ||
+ | weekly... | ||
+ | </ | ||
+ | |||
+ | As the name suggest, every directory of the list contain the files changed during the last 24 hours, 7 days and 4 weeks (the 0 **is** something). If the wanted file was deleted/ | ||
If the file is found, the users can copy it where it want and the restore is done. | If the file is found, the users can copy it where it want and the restore is done. | ||
+ | \\ | ||
+ | \\ | ||
+ | **Don' | ||
+ | |||
+ | <note warning> | ||
+ | Pay attention that inside the .snapshot directories you can see the **state** of his/hers directory how it was at the time of **snaphot**, | ||
+ | </ | ||
+ | |||
+ |
backup/snapshot.txt · Last modified: 2015/07/01 15:42 by 127.0.0.1