backup
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
backup [2017/06/13 09:55] – admin | backup [2023/09/01 16:06] (current) – admin | ||
---|---|---|---|
Line 4: | Line 4: | ||
- | Contained in this wiki are instructions for backing your data on the **Klauda Lab Backup Server**. The name of this server is // | + | Contained in this wiki are instructions for backing your data on the **Klauda Lab Backup Server**. The name of this server is // |
==== Policies ==== | ==== Policies ==== | ||
Line 12: | Line 12: | ||
// Unpublished Data // | // Unpublished Data // | ||
- | This will be the data you are currently running simulations and analysis on. This will be backed up on a weekly incremental | + | This will be the data you are currently running simulations and analysis on. This will be automatically |
// Published Data // | // Published Data // | ||
- | Once you have data that is published, you need to reduce the trajectory file sizes and make a single tarred and compressed file (.tar.gz). The name of this file should make it clear to me what publication this is from and be placed in your backup directory on the backup server. Then you will create another backup on an external hard drive (see Dr. Klauda) and remove data from DT1/DT2. So you still have two locations (external HD and backup server). The DCD/ | + | Once you have data that is published, you need to reduce the trajectory file sizes and make a single tarred and compressed file (.tar.gz). The name of this file should make it clear to me what publication this is from and be placed in your backup directory on the backup server. Then you will create another backup on an external hard drive (see Dr. Klauda) and remove data from ZT1. So you still have two locations (external HD and backup server). The DCD/ |
- | ==== Backup | + | ==== File Reduction |
- | The following | + | Download the following |
- | 1. Create your login and password on backup server | + | {{ ::truncate.tar.gz |}} |
- | We will create a username as your UMD username and provide you with an initial password. Then you can ssh to // | + | When ready, mv the files into the dcd directory, |
- | + | ||
- | <code commend> passwd </ | + | |
- | + | ||
- | 2. Setting up password-less login to backup server from deepthought | + | |
- | + | ||
- | a. login to deepthought\ | + | |
- | b. From you home on deepthought open .ssh/ | + | |
- | c. Type ssh-keygen/ | + | |
- | d. Press y (when asked y/n?) and ' | + | |
- | e. ssh-copy-id -i ~/ | + | |
- | f. Try ssh username@klauda-bkup1.umd.edu | + | |
- | + | ||
- | 3. Creating backup directories | + | |
- | + | ||
- | a. Once you are logged in on the backup server, go to / | + | |
- | username | + | |
- | b. Inside that create two directories named full and weekly | + | |
- | c. Inside weekly create 12 directories corresponding to 12 months 01, 02, 03 ... 12 | + | |
- | + | ||
- | 4. Creating backup scripts on deepthought | + | |
- | + | ||
- | a. Create a directory named backup in your home directory on deepthought | + | |
- | b. Copy backup-full.scr and backup-weekly.scr from / | + | |
- | c. Change the username from ' | + | |
- | d. There will be two paths - i) Path of your directory on deepthought that will be backed up on the | + | |
- | server. It should generally be "/ | + | |
- | re it will be backed up. This will be "/ | + | |
- | e. Double check whether you have changed the username. Otherwise when you run your backup, my data w | + | |
- | ill be lost. | + | |
- | + | ||
- | 5. Setting up crontab | + | |
- | + | ||
- | Crontab will schedule your weekly and monthly backups | + | |
- | a. When you are on deepthought, type crontab -e, a crontab window will open up | + | |
- | b. Use the following as a template to create your crontab | + | |
- | + | ||
- | SHELL=/ | + | |
- | # Weekly Incremental Backups | + | |
- | # Sat at 0X:0X am | + | |
- | 0X 0X * * 6 / | + | |
- | # Monthly Full Backups | + | |
- | # 1st day of month at 11:01 am | + | |
- | 0X 0X 1 * * / | + | |
- | c. 0X:0X am is the time at which your data will be automatically backed up every Saturday and first | + | |
- | day of the month. We keep our backup times few hours apart from each other. Once everything else is | + | |
- | completed, we can decide on these times for everyone. | + | |
- | d. When you save and exit, it will install crontab | + | |
- | e. Check whether crontab is installed or not using crontab -l | + | |
- | + | ||
- | + | ||
- | Listed below are instructions for setting up accounts on deepthought1 (DT1) and deepthought2 (DT2) located at UMD. | + | |
- | + | ||
- | // | + | |
- | + | ||
- | You will assigned one or both clusters based on your simulation needs by Dr. Klauda. These instructions work for both, so do these on the cluster(s) you are assigned. Dr. Klauda will submit a request to add you as a user to my account on DT1 and/or DT2. Once this is done, you should get a generic email from IT regarding the resource. | + | |
- | + | ||
- | Details of DT1 and DT2 can be found: | + | |
- | + | ||
- | http:// | + | |
- | + | ||
- | Now for the cluster setup: | + | |
- | + | ||
- | If you are not familiar with the use of LINUX, I would first go through some on-line tutorials for commands to use in LINUX and here ([[Linux Guide]]). To login to DT1 (login.deepthought.umd.edu) or DT2 (login.deepthought2.umd.edu) with Windows you will need to have PuTTY ([[Extra Software]]) to connect to deepthought: | + | |
- | + | ||
- | http:// | + | |
- | + | ||
- | And the following program will be useful to transfer | + | |
- | + | ||
- | http:// | + | |
- | + | ||
- | Built-in commands for MAC users can be used to connect via the command line (scp) and apps for file transfer (eg, cyberduck). | + | |
- | + | ||
- | Then, take a general look at the website of the HPCC OIT to get a general idea on how to login and submit jobs. Your jobs should not run in your home directory. | + | |
- | + | ||
- | <code commend> pico .cshrc.mine </ | + | |
- | + | ||
- | At the end of the file add the following line: | + | |
- | + | ||
- | <code commend> unset noclobber </ | + | |
- | + | ||
- | This is needed for the simulations to allow for files to write over existing files. | + | |
- | + | ||
- | One more recent change is that you will need to allow me to look into your /lustre files. | + | |
- | + | ||
- | <code commend> | + | |
- | chmod a+r . | + | |
- | chmod -R a+r * | + | |
- | find . -type d -exec chmod a+x {} \; </ | + | |
backup.1497362106.txt.gz · Last modified: 2017/06/13 09:55 by admin