backup:snapshot
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
backup:snapshot [2007/05/26 21:50] – damir | backup:snapshot [2015/07/01 15:42] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== What do you mean with " | ====== What do you mean with " | ||
- | A photograph is something that stop the time. Whatever else you do or you change after taking the photo isn't important, because you can always know how the things where at the time of the photo. | + | A photograph is something that stop the time. Whatever else you do, or how you change after taking the photo, isn't important, because you can always know how the things where at the time of the shot. |
- | A **snapshot** 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 | + | A **snapshot** |
+ | |||
+ | ===== 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 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. | ||
- | Every hour the system generate a **snapshot** of the user's directory and save it in a separate space (not really, but just to maintain the thing simple). The users can access these data just browsing the homedir, without the need to use some strange and unfriendly software. | + | The system generate a **snapshot** of the user's directory |
- | 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 users can access his/hers old file inside an hidden directory named **.snapshot** resident in their homedir. Inside this directory exists others directories that have name | + | 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-3] | + | * hourly.[0-23] |
- | * nightly.[0-3] | + | * nightly.[0-6] |
- | * weekly.[0-1] | + | * weekly.[0-3] |
- | As the name suggest, these directory contain the file changed during the lasts 4 hours, | + | As the name suggest, these directory contain the files changed during the lasts 24 hours, |
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' | 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 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 (the .snapshot directories are accessible only in read mode). |
- | ====== User point of view ====== | ||
- | Every user of the LTHC, LTHI and LCM labs can find inside his/hers homedir on the central filer an hidden directory named **.snapshot**. Inside this directory exists others directories: | + | |
+ | ==== 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/ | ls .snapshot/ | ||
hourly.0 | hourly.0 | ||
hourly.1 | hourly.1 | ||
- | hourly.2 | + | hourly.... |
- | hourly.3 | + | |
nightly.0 | nightly.0 | ||
nightly.1 | nightly.1 | ||
- | nightly.2 | + | nightly.... |
- | nightly.3 | + | |
weekly.0 | weekly.0 | ||
weekly.1 | weekly.1 | ||
+ | weekly... | ||
</ | </ | ||
- | As the name suggest, every directory of the list contain the files changed during the lasts 4 hours, | + | As the name suggest, every directory of the list contain the files changed during the last 24 hours, |
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. | ||
\\ | \\ | ||
Line 42: | Line 47: | ||
Pay attention that inside the .snapshot directories you can see the **state** of his/hers directory how it was at the time of **snaphot**, | 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.1180209052.txt.gz · Last modified: 2007/05/26 21:50 by damir