| | 26 | === NEODC === |
| | 27 | |
| | 28 | Once flights are archived with NEODC, we omit them from the mirroring script. However, we still keep a local copy, on the same disk as the current data. It is also still backedup |
| | 29 | |
| | 30 | |
| | 31 | ==== Potential problems === |
| | 32 | |
| | 33 | Occasionally there is a problem overnight and the rsync doesn't run until late. This can mean it is still running when the next rsync begins. This leads to a piling up of multiple instances of the script which just gets worse. It is good practice every now and then to log onto gridmaster4 as arsf and check that there aren't a stupid number of rsync/rdiff processes running (a few concurrent is normal). If so, just kill all instances you can find and let the cron start again as normal the following night. You could automatically check for this problem by modifying repos_back_up_rsync_rdiff.sh to check for rsync/rdiff processes and to fail if they are over a threshold. |
| | 34 | |
| | 35 | Other problems can be found by checking the cron log above. |
| | 36 | |
| | 37 | |
| | 38 | |
| | 39 | |