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 10:18] – 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, which will overwrite the large dcd files. |
- | <code commend> passwd </ | ||
- | |||
- | 2. Setting up password-less login to backup server from DT1 or DT2 | ||
- | |||
- | This is key for doing automatic backups and allows you to login to the server without prompting the password. | ||
- | |||
- | * login to DT1 or DT2 | ||
- | * From you home on DT open .ssh/ | ||
- | * Type // | ||
- | * Press y (when asked y/n?) and ' | ||
- | * // | ||
- | * Try //ssh username@klauda-bkup1.umd.edu// | ||
- | |||
- | 3. Creating backup directories | ||
- | |||
- | * Once you are logged in on the backup server, go to / | ||
- | * Inside that create two directories named full and weekly | ||
- | * Inside weekly create 12 directories corresponding to 12 months 01, 02, 03 ... 12 | ||
- | |||
- | 4. Creating backup scripts on DT1 or DT2 | ||
- | |||
- | * Create a directory named backup in your home directory on DT1 or DT2 | ||
- | * Copy backup-full.scr and backup-weekly.scr from / | ||
- | * There will be two paths: | ||
- | * Path of your directory on deepthought that will be backed up on the server. It should generally be "/ | ||
- | * Path of directory on server where it will be backed up. This will be "/ | ||
- | * Double check whether you have made these changes. Otherwise when you run your backup, data will not be backed up. | ||
- | |||
- | 5. Setting up crontab | ||
- | |||
- | Crontab will schedule your weekly and monthly backups automatically on DT1/DT2 | ||
- | |||
- | * When you are on DT, type crontab -e, a crontab window will open up | ||
- | * Use the following as a template to create your crontab | ||
- | |||
- | <code commend> 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 * * / | ||
- | |||
- | * 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. Pick random numbers for X (single digit) to prevent everyone starting this at the same time) | ||
- | * When you save and exit, it will install crontab | ||
- | * Check whether crontab is installed or not using crontab -l | ||
- | |||
- | 6. Run backup-full to backup your data: <code commend> | ||
- | |||
- | **Note**: You must do this for DT1 and DT2 if you have data on both of these machines. Make sure you check on Monday that you've backup up the data on the weekly backup. | ||
backup.1497363503.txt.gz · Last modified: 2017/06/13 10:18 by admin